ntoskrnl.exe/DRIVER_POWER_STATE_FAILURE and MEMORY_MANAGEMENT Bsod

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

There's no dump

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.

Capt.Jack Sparrow said:

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.

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

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.