29 replies to this topic

[Scorbing]

Windows 7 crashed on me on boot. This is the second time it does that. Last time was about 3 months ago. Has anyone experienced this?


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 00000000003E5A73
BCP3: 0000000000000000
BCP4: 0000000000003A73
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\010213-12807-01.dmp
C:\Users\Scorbing\AppData\Local\Temp\WER-20794-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[cluberti]

A "4e" bugcheck equals "PFN_LIST_CORRUPT". According to Microsoft:

Quote

Cause

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.

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.

[Scorbing]

cluberti, on 03 January 2013 - 01:51, said:

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.

Video driver perhaps?

[cluberti]

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.

http://msdn.microsof...2(v=VS.85).aspx

[Scorbing]

cluberti, on 03 January 2013 - 02:05, said:

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.

http://msdn.microsof...2(v=VS.85).aspx

Mmmmmm...I wonder if its Skydrive?

[Neu B]

It might be the motherboards northbridge or southridge chips that might be acting up. Have you tried updating MB drivers? Maybe the BIOS needs an update. These two things I would try first.

[jkrupa128]

One (or more) memory modules going bad...

[Michael Lacey]

Start wirth the usual hard drive and memory test to get those out of the way. Leave memtest on overnight when you do,.

[John.D]

If it can boot imto windows install bluescreenview see what that says

[Scorbing]

It just did it again. Gonna do the Memtest thing now.

[Scorbing]

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?

[Scorbing]

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.

[osuwildlifer]

Scorbing, on 03 January 2013 - 13:49, said:

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?

Just remove the sticks one by one and retest until you figure out which one is is. Can be a bit tedious, but it's the best way to know for sure which one is faulty.

Edit: Just saw your recent post with the screenshot. Well, at least you have a 50/50 chance of pulling the right one first! Based on your image, I would try the 2nd populated RAM slot first. The slots will be numbered on the mobo.

[Obi-Wan Kenobi]

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!

[Tyler R.]

Scorbing, on 03 January 2013 - 18:54, said:

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.

You're not screwed. 8gb should easily get you by until you replace it. Take one module out at a time (place it in DIMM 1), run the test, if it passes, that's a good stick. To make sure the other really is bad, take out the good one and put in the bad. Your computer should go "beeeeeeeppp". Shut it down, put the good one in. Windows should start up fine now.

obiwankenobi, on 03 January 2013 - 19:01, said:

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!

Are you sure the pins are on correctly?