|
|||||||
| Other Tech News The latest community based technology news from across the globe. (If you aren't a community newsposter then use the "Submit News" section.) |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
DriverHeaven Founder
Join Date: May 2002
Posts: 32,480
Rep Power: 179 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Beginners Guides: Diagnosing Bad Memory
Does your Windows-based PC crash for no apparent reason? Well OK, mine does too, but does yours crash often? At random times? With Nasty blue Screens of Death? If the answer is "yes", you may very well have a memory problem. Faulty memory, or RAM, is often the cause of the dreaded 'flaky PC' syndrome, those hard-to-replicate errors that get you nasty looks from the store technician because "…nothing seems to be wrong with it. Sir."
pcstats |
|
|
|
|
|
#2 |
|
Apple Fanboy?
|
hmm this may just solve my problem…
__________________
Chris - The Aussie Super Mod
Hardwareheaven Rules - Sig Request Thread How you can help HardwareHeaven by using Digg! Hardwareheaven Super-Moderator |
|
|
|
|
|
#3 |
|
Flash Banner Hater
|
You also need a LOT of patience to track down memory which is merely "unreliable".
The Bios RAM test (with quick boot disabled) will normally find any unconditionally bad, hard-fault ridden memory - and the system would be pretty well inoperable. A single "all test" pass with any of the test software, should find any more complex, but repeatable errors. I'm not convinced that most of the test programs have an optimum strategy for finding UNRELIABLE memory... I just wish I was good enough to add my own tests... 1. Use optimized writes - 8 byte MMX registers, or SIMD streaming. 2. Use a simple strategy (eg. seeded/reseeded random number generator) 3. To test working/holding, divide the memory into two groups, and alternate several rapid cycles on one, with a longer duration store and verify on the other |
|
|
|
![]() |
| Thread Tools | |
|
|