Windows 7: BOSD 0x4E PFN_LIST_CORTUPT (mainly while booting)

Tenhi · 26 Sep 2011

Quote: Originally Posted by zigzag3143

Quote: Originally Posted by Tenhi

New crash while booting today happened 3 times before I was able to get to Windows.

This one was Related to rdyboost.sys ReadyBoost Drive from Microsoft Corporation. I would disable it.

I cant really find a way to disable it... searching the Internet I found the Info that I have to disable Superfetch? Is that correct?

zigzag3143 · 26 Sep 2011

Quote: Originally Posted by Tenhi

Quote: Originally Posted by zigzag3143

Quote: Originally Posted by Tenhi

New crash while booting today happened 3 times before I was able to get to Windows.

This one was Related to rdyboost.sys ReadyBoost Drive from Microsoft Corporation. I would disable it.

I cant really find a way to disable it... searching the Internet I found the Info that I have to disable Superfetch? Is that correct?

It will be in the properties of any flash drive you plug in. See snip

Tenhi · 26 Sep 2011

My 2gig flash drive isnt plugged in during the booting routine but I plugged it in and the readyboost is turned off for it.

I tried to turn it off for the 2 external HDDs that I use (they are connected via USB) but they arent able to use rdyboost...

So there is nothing that would use rdyboost :/

Edit: Also the 2 HDDs are normaly turned off during the booting routine...

Tenhi · 26 Sep 2011

Hey zigzag3143,

is there something else I could do? If not I think I will just buy new RAM and see if that helps... if that doesnt help I will turn the MoBo in and see if that helps -_-

Tenhi · 28 Sep 2011

Hello zigzag3143,

yesterday I could boot just fine without a BSOD. Today... 3 BSODs in a row before I was able to get to Windows. The cause was again rdyboost.sys... is there a way to permanently disable it? It looks like its tied to Superfetch... is that correct? What will happen if I disable Superfetch?

Edit: I didnt buy the new RAM yet, was waiting for an answer if there is anything else I can do.

Edit2: I enabled the Driver Verifier again. System is right now running for 20min+ without an BSOD... when I tried to use it before it crashed after maybe 1-5mins. Not too sure what I should think about this.

Tenhi · 28 Sep 2011

Ok the System just crashed to the same old 0x4E while the driver verifier was running (it was enabled up till now). After the reboot I went for Safe Mode to disable the Driver Verifier. After that the PC crashed during the rebooting... 3 times in a row (its allways 3 times Oo).

Those are the 2 dumpfiles that where created the first one should be the one during the driver verifier and the 2nd after I disabled it

zigzag3143 · 28 Sep 2011

Quote: Originally Posted by Tenhi

Ok the System just crashed to the same old 0x4E while the driver verifier was running (it was enabled up till now). After the reboot I went for Safe Mode to disable the Driver Verifier. After that the PC crashed during the rebooting... 3 times in a row (its allways 3 times Oo).

Those are the 2 dumpfiles that where created the first one should be the one during the driver verifier and the 2nd after I disabled it

These are both driver verified and both pointing to memory corruption. What were the memtest results? How long did you run it (how many passes?)

Code:

Probably caused by : memory_corruption ( nt!MiBadRefCount+4f )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a, 
Arg2: 000000000011df63
Arg3: 0000000000000006
Arg4: 0000000000000201

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_9a

CUSTOMER_CRASH_COUNT:  1

Tenhi · 29 Sep 2011

I posted the results one page earlier. Post #17. But I will post the results again.

Both Sticks together: Slot A1 and B1 - 14 Passes no Errors
Slot A2 and B2 - System does not boot

Stick 1 alone: Slot A1 - 6 Passes no Errors
Slot A2 - System does not boot
Slot B1 - 3 Passes 1 Error (I stoped the Memtest there)
Slot B2 - System does not boot

Stick 2 alone: Slot A1 - 6 Passes no Errors
Slot A2 - System does not boot
Slot B1 - 6 Passes no Errors
Slot B2 - System does not boot

Slot A2/B2 are only for a full setup with 4 Sticks the MoBos manual states that you should use A1 or B1 for single channel and A1+B1 for dual channel.

Tenhi · 01 Oct 2011

New Crash... again rdyboost.sys...

Tenhi · 06 Oct 2011

Hello zigzag3143,

after a while a new report. I'm not sure if that has something to do with my old problem... while surfing (with Firefox 7.0.1) I noticed that my screen was flickering. It happens when I hover over the windows symbol (the start menu symbol). It doesnt happen everytime I hover over the symbol. I'm not sure what thats all about... if I disable "hardware acceleration" in Firefox it looks like it stops. I tried it with the Explorer and there it happens too. I activated the driver verifier again and it gave me a new BSOD OxA (IRQL_NOT_LESS_OR_EQUAL), I checked it with WhoCrashed and it says it was caused by nvlddmkm.sys... thats the Nvidia Display Driver isnt it? Could the two Problems be related? The 0x4E BSOD and now the OxA? I thought maybe the Motherboard is defect and causing those two problems?

Here the BSOD from the Verifier (the 0xA).

Edit: Now that I think about it I had some issues with my GPU around the same time the BSODs started. I installed the latest (280.26) Nvidia Driver and had some issues with stopping Drivers and Windows recovering from them. Also I think my Monitor went black for a sec and came back again with a recoverd Nvidia driver. After rolling back to 275.33 everything was fine again until now. I checked the Temperaturs and my GPU is running @30°C idle and, depending on the load up to ~63°C. So I dont think its temperatur related.

Windows 7: BOSD 0x4E PFN_LIST_CORTUPT (mainly while booting)

BOSD 0x4E PFN_LIST_CORTUPT (mainly while booting) problems?