problikne modrá smrt a restart

[sonny81]

jak taková adresa vypadá?

[Reklama]

[jaro3]

Udělej tohle:
Memtest 86
http://www.memtest86.com/
klikni vlevo na Free Download , vyber:
ISO image for creating bootable CD (Windows - zip) , stáhni , rozbal , otevři , vypal třeba v programu:
http://www.slunecnice.cz/sw/active-iso-burner/
Vlož do mechaniky a nabootuj z něj.
Test udělej alespoň 8h ( přes noc).

Příklad:

DIAGNOSTICS
The program prints a small amount of information about how it was
invoked before running tests:

Successfully allocated 4194304 bytes.
Aligning memory...settling on 4190208 bytes at 0x400b7000...
Proceeding to lock pages...success. Starting tests...

memtest typically tests a slightly smaller amount of memory than is
specified on the commandline. This is because it aligns its memory
allocation to a page boundary before attempting to lock its pages into
memory. This is a requirement on some Unix systems. With very small
allocations of memory (typically only used during debugging of
memtest), it may fail to align to a page boundary with a message
similar to this:

Aligning memory...allocation too small to align to pagesize of 4096 bytes.
Failed to get sufficient memory. Exiting...

If not run as root, the memlock will fail as follows:

Proceeding to lock pages...mlock failed: only root can lock pages.
Continuing with unlocked pages. Results are less reliable.

Then, as the program runs through tests, it prints the current ‘run’
(cycle of tests) and test number and name. It also prints status
information on the progress of the tests. This will look like the
following:

Run 1:
Test 1: Random value: Setting...Testing...Passed.
Test 2: XOR comparison: Setting...Testing...Passed.

If one of the tests finds an error in memory, a message like the
following will be printed:

FAILURE: 0x5aa0f5c5 != 0x5aa0f585 at offset 0x0067f837.
Skipping to next test...

If the Stuck Address test finds a failure, it outputs a slightly
different message, to remind the user that other tests are unreliable
if an addressing problem exists:

FAILURE: possible bad address line at offset 0x004563f3.

At the end of each ‘run’ it will print a summary of that run as
follows:

Run 1 completed in 114 seconds (2 tests showed errors).

When the program completes (is interrupted by a signal, or finishes its
last run, when a limit is specified on the commandline), it will print
an overall summary:

2 runs completed. 2 errors detected. Total runtime: 235 seconds.
Exiting...

např:
FAILURE: 0x5aa0f5c5 != 0x5aa0f585 at offset 0x0067f837.--to je ta adresa.
Skipping to next test...