Jump to content
|Topic||Stats||Last action by|
|My Christmas present to myself||
|The Witcher 3: Wild Hunt||
|Where to download the latest Windows 10 build?||
|Wish to purchase a console, recommendations please||
|Husband accidentally trades Xbox game with precious family photos inside||
Posted 03 January 2013 - 01:48
Posted 03 January 2013 - 01:51
This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.
If a kernel debugger is available, examine the stack trace.
Posted 03 January 2013 - 01:53
A "4e" bugcheck equals "PFN_LIST_CORRUPT". According to Microsoft:
In my experience, this is usually the case - a driver has caused some sort of memory list issue in the way it's freeing memory pages, and causes the crash. Without at least a kernel memory dump file of the issue, however, you now know everything that can be gleaned from the crash.
Posted 03 January 2013 - 02:05
Posted 03 January 2013 - 02:31
Who knows? Usually something loaded in nonpaged pool, but honestly it could be any driver that is accessing memory. The video driver isn't necessarily the only kind of driver that can do that . I usually suspect storage drivers, but I've seen video drivers do it, ramdisk drivers, etc.
Posted 03 January 2013 - 02:49
Posted 03 January 2013 - 04:01
Posted 03 January 2013 - 04:05
Posted 03 January 2013 - 05:15
Posted 03 January 2013 - 13:49
Posted 03 January 2013 - 18:54
Posted 03 January 2013 - 18:55
OK I left Memtest86+ running all night and although its still not done yet, it found 5 errors. Now my question:
How do I know which memory chip is bad? Does Memtest86+ tell you which one is bad? Anyone knows?
Posted 03 January 2013 - 19:01
Posted 03 January 2013 - 19:05
Well the tests are done. Here's the results. I guess I'm screwed. My question is though, which module is bad? How can I tell from this result which one is faulty?
I have two 8GB modules installed for a total of 16GB.
I feel you, scorbing! I woke up on Christmas day to a desktop that just won't power on. If it wasn't the one with all of my movies/mp3's on it, I wouldn't really care too much, but now I have to save up for a new power supply. Sorry that had to happen though, bro!