BSOD Bad_Pool_Header (dxgmms1.sys, ntoskrnl.exe, nvlddmkm.sys)

[Addled]

Hi All,

I recently built a new computer and am faced with blue screens. I completed multiple passes of memtest86+ without error, as well as a diskchk on both of my drives. After that I put a fresh copy of Windows 7 Professional x64 with SP1 included on the machine. I then allowed windows update to run, installed Avast and SpyBot Search&Destroy, and allowed SP-S&D to immunize my FF and IE.

After that I began to play games and had a BSOD, BAD_POOL_HEADER, and decided I needed to seek assistance.

I am hoping that this issue is software related and that someone here at sevenforums has the expertise required to resolve my dilemma. I ran Capt.'s Windows 7 Diagnostic Tool and attached the results to this post.

​

-Addled

 

[Arc]

Welcome aboard.

The display driver version you are using is sometimes troublesome.

lmvm nvlddmkm
start             end                 module name
fffff880`0f486000 fffff880`1017a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Oct 02 23:51:13 2012 (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Let us know the results. Depending on it, will decide our next steps.

 

[Addled]

Hi Arc,

First off, thank you for the speedy reply! I followed your instructions to the dot:

1) Installed Driver Fusion, after installing v4.0 of .Net framework.
2) Rebooted in safe mode, analyzed Nvidia Drivers/Chipsets, and deleted all results.
3) Installed NVidia Driver "306.23-desktop-win8-win7-winvista-64bit-english-whql.exe"

I am writing this post immediately after completing these steps. I have not had a blue screen yet - however - I had two during step 1 of the process above. These BSODs did not create minidump files, despite no changes in my logging settings. The BSOD error messages were page_fault_in_nonpaged_area and memory_management.

For now I will wait and see if I continue to get BSODs. If there is anything I can do to investigate the two BSOD mentioned above, please let me know.

Your support is greatly appreciated,
-Addled

PS. I re-ran the SF Diagnostics Tool and attached the new(?) results (original Minidump still included). Also, I'll start taking photos of the BSODs.
​

 

[Arc]

Can you enable driver verifier?

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Addled]

Driver Verifier

Hi Arc,

I activated Driver Verifier with custom settings to include everything except Microsoft, <unknown>, and Macrovision (secdrv.sys). I did however include vkbms.sys ("Windows(R) Win 7 DDK provider").

A few minutes after reboot, having not done a thing but stare at my desktop, a BSOD occurred. It did not seem to create/overwrite the existing Minidump file. I attached a screenshot of my logging settings, as well as a photo of the BSOD itself. I also attached the SF_Diagnostic zip.

Driver Verifier is disabled. Is it worth enabling it again to see if I can cause a different type of BSOD?

EDIT: From what I read about PFN_LIST_CORRUPT it seems like the stop code information is relatively useless without a record of the kernel stack. I re-enabled driver verifier with the same settings and have been operating ok. I'll leave it on till I BSOD again, and post results.

Again, your help is greatly appreciated,
-Addled

BSOD Summary:
PFN_LIST_CORRUPT

STOP:
0x0000004E (0x0000000000000099, 0x00000000003892D6, 0x0000000000000003, 0x0000000000388E55)

0x99 = A page table entry (PTE) or PFN is corrupted. From: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559014.aspx

 

[Arc]

Just out of curiosity, as you have stated about the mouse driver, I searched for it, and got the result that it is somehow old.

 lmvm vkbms
start             end                 module name
fffff880`047ef000 fffff880`047fa000   VKbms      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\VKbms.sys
   [COLOR=Red] Image name: VKbms.sys
    Timestamp:        Thu Sep 30 21:46:33 2010[/COLOR] (4CA4B7E1)
    CheckSum:         00006C3A
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Razer Support.

A stop 0x4E itself is not any big information, coz it is caused by a device driver. So, enable DV again, make it sure that no drivers from microsoft or unknown provider is selected.

 

[Addled]

Hi Arc,

DV is activated and running. Last night things seemed to operate fine after the PFN_LIST_CORRUPT BSOD. I'd be surprised if that Razer driver is the issue - I used it for ages on my last Win 7 machine. The only reason I'm hesitant to update it is that Razer removed stand-alone drivers and only distributes a cloud based solution - which I find highly irritating. I don't want or need my mouse settings in the cloud.

However, for the sake of narrowing down possible causes (and respecting your input) I will update the Razer driver to their new Synapse thingy-ma-bob. I re-ran Memtest86+ overnight and it completed 4 passes without error. I'll re-check my disks tonight and continue to leave DV on.

As always, your feedback is greatly appreciated,
-Addled

 

[Arc]

The mouse driver is not necessarily in problem, but it is old, so an update may be needed.

Let us know the result of DV.

 

[Addled]

Small Update: Back from work and using my quirky machine with DV enabled. For now I'm just using a simple mouse driver - no Razer software. This way if we can find an issue and resolve it I can always experiment with the Razer driver on my own later. I'm all for removing factors... simple is easy.

-Addled

 

[Addled]

Hi Arc,

I have been using my computer, when possible, with DV enabled. I noticed some adverse effects from DV, specifically related to updating and installing/uninstalling programs(stuck at 0%). I actively used my computer for roughly 12 hours with DV enabled and have not had a blue screen. Are there still DV results despite the lack of a BSOD?

Also - while I had DV disabled to install a program I had another BSOD with the same PFN_LIST_CORRUPT stop message. I attached the latest folder generated by SF_Diagnostics.

What is the next step? I still have DV on - trying to cause a crash.

As always, thanks
-Addled

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 2b5327, 2, 2b66a6}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

But I am thinking, there might be something else playing behind ... something network related, but not getting adequate information. As a test, will you uninstall Avast, if somehow it is causing any blocking?

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.