mikeymikec
Lifer
- May 19, 2011
- 17,574
- 9,263
- 136
Memory problems can result in just about any stability symptom in my experience. You can be fortunate and simply get a MEMORY_MANAGEMENT BSOD, but because all it needs is for a system driver to be stored in the dodgy segment of memory, possibly a different driver each time, and you can get BSODs pointing at just about anything but memory (except when you have a few randomly-pointing BSODs, that should clue you into memory if you haven't already run memtest86+ (not memtest86)).
I don't know if someone else has mentioned it already, but as well as trying each memory module in turn, try them in different slots. It possibly could be a slot problem (though I haven't seen a slot problem in a long time).
There are some classic BSODs that point at memory, PFN_LIST_CORRUPT is another one. KERNEL_MODE_EXCEPTION_NOT_HANDLED tends to raise my eyebrow in a 'dodgy memory' sort of way despite not necessarily being a memory issue.
I don't know if someone else has mentioned it already, but as well as trying each memory module in turn, try them in different slots. It possibly could be a slot problem (though I haven't seen a slot problem in a long time).
There are some classic BSODs that point at memory, PFN_LIST_CORRUPT is another one. KERNEL_MODE_EXCEPTION_NOT_HANDLED tends to raise my eyebrow in a 'dodgy memory' sort of way despite not necessarily being a memory issue.
Last edited: