Windows 7: ntoskrnl.exe/DRIVER_POWER_STATE_FAILURE and MEMORY_MANAGEMENT Bsod

koolkat77 · 15 Sep 2012

Probably
See if this helps How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)

jbucko · 15 Sep 2012

ok so i did the removal tool and then went back to normal use of the computer and i got a BSOD. this one is one i have never seen before though.

On Sun 9/16/2012 4:13:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-13026-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6282)
Bugcheck code: 0x19 (0x3, 0xFFFFF900C4E1FA40, 0xFFFFF900C4E1FA40, 0xFFFFF900C4E1FA50)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

koolkat77 · 15 Sep 2012

There's no dump

jbucko · 15 Sep 2012

13026 is the one that i never got before and 12792 is the one that i got when tryin to upload the dump file

koolkat77 · 15 Sep 2012

Hmm
Dumps don't give the accurate information but from the bug checks and their usual causes:

STOP 0x0000001A: MEMORY_MANAGEMENT BSOD Index

Usual causes: Device driver, memory, kernel

STOP 0x00000019: BAD_POOL_HEADER BSOD Index

Usual causes: Device driver

Before I tell you to test your memory and so on lets enable driver verifier to rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Quote: Originally Posted by Capt.Jack Sparrow

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

jbucko · 15 Sep 2012

ok so i am trying to select all the nonmicrosoft drivers and there is none and i dont know the location to find them to add them to the list. last time i ran the driver verifier i just made it do all of the drivers.

Arc · 16 Sep 2012

Let us see the screenshots of the verifier window, showing the steps you followed as per the tutorial Driver Verifier - Enable and Disable.

jbucko · 16 Sep 2012

just got this.

jbucko · 16 Sep 2012

Quote: Originally Posted by Arc

Let us see the screenshots of the verifier window, showing the steps you followed as per the tutorial Driver Verifier - Enable and Disable.

i was opening the verifier through the diagnostic tool. it works now, didnt think it made a difference thanks. Restarting the computer hoping for a BSOD.

Arc · 16 Sep 2012

Well, this is Gigabyte Easy Saver - mobo power utility driver.

Code:

......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff9807caceff0, fffff9807caceffc, 69000c, 24}

Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+30c7 )

Let us see how old the driver is:

Code:

0: kd> lmvm gdrv
start             end                 module name
fffff880`0c30e000 fffff880`0c317000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Fri Mar 13 08:52:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Very old, undoubtedly.

Go to the manufacturer's website, update the driver, and report us back.

And, disable the driver verifier for the time being. If it crashes again, we may suggest you to enable it again.

Windows 7: ntoskrnl.exe/DRIVER_POWER_STATE_FAILURE and MEMORY_MANAGEMENT Bsod

ntoskrnl.exe/DRIVER_POWER_STATE_FAILURE and MEMORY_MANAGEMENT Bsod problems?