Windows 8 Fixing DRIVER_POWER_STATE_FAILURE BSOD After Gaming

J

JesseT

New Member
Joined
Oct 25, 2014
Messages
6
Hello, I've been getting a DRIVER_POWER_STATE_FAILURE BSOD a lot lately and it seems to be happening after I've finished playing a game. I've tried going through Windows support where I uploaded my minidump files on my OneDrive and they stated that it was my video driver. The suggestion was to download and revert to a previous driver update and that should fix the problem. However, nothing was fixed. Here are my two most recent dmp files. Someone please help me with this. I'm tired of this stupid thing crashing every time I finish playing a game.
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001e4bce060, fffff80022612960, ffffe001e4d13010}

Probably caused by : pci.sys

Followup: MachineOwner
Hi,
the above dump file caused by a driver not doing it's job correctly although something else could be causing the driver to act in that way like...
Sort by date Sort by votes
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001e4bce060, fffff80022612960, ffffe001e4d13010}

Probably caused by : pci.sys

Followup: MachineOwner
Hi,
the above dump file caused by a driver not doing it's job correctly although something else could be causing the driver to act in that way like corruption or incompatibility.
Firstly do a search for command prompt, right click on it and run as admin. Type:
sfc /scannow
Press enter and await results. This will look for and hopefully repair any corruption.

AiCharger.sys Fri Sep 23 03:04:40 2011: Asus Charger Driver possible BSOD cause. Uninstall to test.

ASMMAP64.sys Thu Jul 02 10:13:26 2009: ATK Generic Function Service possibly tied in with the driver below.

atkwmiacpi64.sys Tue Jul 02 09:35:32 2013: ATKACPI driver and hotkey-related utilities. 2014 version on System support page:
http://www.asus.com/uk/Notebooks_Ultrabooks/ASUS_ROG_G750JM/HelpDesk_Download/

As you probably know Laptop drivers are supplied by the manufacturer. Please apply any updates that relate to your machine including Bios. It looks like there are updates for most things. It's almost always better to be on the latest driver.
http://www.asus.com/uk/Notebooks_Ultrabooks/ASUS_ROG_G750JM/HelpDesk_Download/

Post any new dump files.
If the bsod's start up again then we may consider the driver verifier. See how you go first.
 
Upvote 0 Downvote
Solution
So I did the scan for corruption and my computer crashed. Then after it restarted I conducted the scan again. There are corrupted files in my computer and the command prompt said that Windows Resource Protection found corrupt files but was unable to fix some of them. So what do I do there? Also, here's the dmp file for the most recent crash.
 

Attachments

Upvote 0 Downvote
Also, where would I find the Asus Charger Driver? I'm looking in the batteries area for a possible charger driver and I see that there is an ac adapter driver. Would that be it?
 
Upvote 0 Downvote
JesseT said:
Also, where would I find the Asus Charger Driver? I'm looking in the batteries area for a possible charger driver and I see that there is an ac adapter driver. Would that be it?
Click to expand...
Check add and remove programs. It could be under Asus Utilities.
 
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001d21c0060, fffff8021be12960, ffffe001d21e8520}

Probably caused by : pci.sys

Followup: MachineOwner
Hi,
please apply the updates outlined above and see how you go. Regarding the corruption, please post the CBS logs where the sfc scan logs are held and i'll have a look through. You'll find them in the Windows folder.
 
Upvote 0 Downvote
Hello, I've looked at the add/remove folder and only saw a USB charger for the ASUS area. Is that what you want me to uninstall? Here is the CBS that you have requested and thank you for patiently helping me. I had to put it in a compressed folder. I hope that you receive it.
 

Attachments

Upvote 0 Downvote
Code: 
2014-10-25 22:41:47, Info                  CSI    00000008 CSI Store 396826945904 (0x0000005c64baa970) initialized
2014-10-25 22:41:47, Info                  CSI    00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:78{39}]"6.3.9600.17246 (winblue_r2.140731-1615)".
2014-10-25 22:41:47, Info                  CSI    0000000a@2014/10/26:02:41:47.930 Starting corruption detection (InnerFlags=5)
2014-10-25 23:44:27, Info                  CSI    0000000b Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:Fh/u9J3QWQ2PCSeXVGxcoBdJhf6eUYMi1It0ET1wuME=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-10-25 23:45:35, Info                  CSI    0000000c@2014/10/26:03:45:35.955 Corruption detection complete. numCorruptions = 1, Disp = 1.
2014-10-25 23:45:36, Info                  CBS    Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2014-10-25 23:45:36, Info                  CSI    0000000d@2014/10/26:03:45:36.705 CSI Transaction @0x5c68021480 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [26]"TI5.30404805_3478654543:1/"

2014-10-25 23:45:36, Info                  CSI    0000000e@2014/10/26:03:45:36.741 CSI Transaction @0x5c68021480 destroyed
2014-10-25 23:45:36, Info                  CBS    Repr: CSI Store check completes
2014-10-25 23:45:36, Info                  CBS    Ensure CBS corruption flag is clear
2014-10-25 23:45:36, Info                  CBS   
=================================
Checking System Update Readiness.

(p)    CSI Payload Corrupt            amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB

Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption:    1
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    1
Total Repaired Corruption:    0
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    CSI Payload Repaired:    0
    CSI Store Metadata refreshed:    True

Total Operation Time: 4076 seconds.

2014-10-25 23:45:36, Info                  CBS    SQM: CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2014-10-25 23:45:36, Info                  CBS    Count of times corruption detected: 1
2014-10-25 23:45:36, Info                  CBS    Failed to delete current corruption first found value. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2014-10-25 23:45:36, Info                  CBS    Failed getting last corruption first found time [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2014-10-25 23:45:36, Info                  CBS    Seconds between initial corruption detections: -1
2014-10-25 23:45:36, Info                  CBS    Seconds between corruption and repair: -1
2014-10-25 23:45:40, Info                  CBS    SQM: Upload requested for report: CheckSurSqm, session id: 142858, sample type: Standard
2014-10-25 23:45:40, Info                  CBS    SQM: Warning: Failed to get machine name. The data won't be available. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-10-25 23:45:40, Info                  CBS    SQM: Warning: Failed to get domain name. The data won't be available. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-10-25 23:45:40, Info                  CBS    SQM: Queued 1 file(s) for upload with pattern: C:\Windows\servicing\sqm\CheckSurSqm_*_std.sqm, flags: 0x2
2014-10-25 23:45:40, Info                  CBS    SQM: Upload callback called with file path: C:\Windows\servicing\sqm\CheckSurSqm_0_std.sqm, status: 0x0, HTTP response: 403
2014-10-25 23:45:41, Info                  CBS    Reboot mark cleared
2014-10-25 23:45:41, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2014-10-25 23:45:41, Info                  CBS    Winlogon: Stopping notify server
2014-10-25 23:45:41, Info                  CBS    Winlogon: Unloading SysNotify DLL
2014-10-25 23:45:41, Info                  CBS    Exec: Processing complete, session(Corruption Detecting): 30404805_3478654543 [HRESULT = 0x00000000 - S_OK]
2014-10-25 23:45:41, Info                  CBS    Session: 30404805_3478654543 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2014-10-25 23:45:55, Info                  CBS    Session: 30404815_1492915329 initialized by client DISM Package Manager Provider.
2014-10-25 23:47:14, Info                  CBS    Session: 30404815_2282156070 initialized by client DISM Package Manager Provider.
2014-10-25 23:47:14, Info                  CBS    Client specifies store corruption detect and repair.
2014-10-25 23:47:14, Info                  CBS    Exec: Session processing started.  Client: DISM Package Manager Provider, Session(Store Corruption Detect/Repair): 30404815_2282156070
2014-10-25 23:47:14, Info                  CBS    Reboot mark set
2014-10-25 23:47:14, Info                  CBS    Winlogon: Registering for CreateSession notifications
2014-10-25 23:50:50, Info                  CBS    Repr: CBS Store check completes
2014-10-25 23:50:50, Info                  CSI    0000000f StoreCorruptionRepair transaction begun. WcpVersion: [l:78{39}]"6.3.9600.17246 (winblue_r2.140731-1615)".
2014-10-25 23:50:50, Info                  CSI    00000010@2014/10/26:03:50:50.052 Starting corruption detection (InnerFlags=5)

Hi,
above is just a little of the CBS log and your install does look a little corrupted.
Similar to the System File Checker is the DISM Tool. This will, if possible, download files to repair missing or corrupt data. Opn the admin command prompt and type:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results.

Regarding the ASUS driver... That sounds about right and once we've determined the cause of the bsod you can always re-install it.
 
Upvote 0 Downvote
I've just had a recent crash. Everything was working fine for the last few days. Admittedly, I did not remove the USB charger driver like you suggested. I noticed that there was an update and thought that if I downloaded it, everything might get better. Apparently not. Please help?

Here's the dmp file to the most recent crash:
 

Attachments

Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001345c7880, fffff800a9612960, ffffe001343d7010}

Probably caused by : pci.sys

Followup: MachineOwner
Hi,
The above is caused by a driver not doing a certain function correctly:

AiCharger.sys Fri Sep 23 03:04:40 2011: Asus Charger Driver can be a likely BSOD cause please remove to test.

ASMMAP64.sys Thu Jul 02 10:13:26 2009: ATK Hotkey ATK0101 ACPI UTILITY please either remove or update
 
Upvote 0 Downvote
So I've removed the Asus Charger Driver and the computer still seems to be crashing. Here is the new dmp file from my most recent crash. I'm hoping that there is a different problem than the charger driver since there is none now. I will be removing the hotkey atk0101 acpi utility right now.
 

Attachments

Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe00097f60060, ffffd00157123cb0, ffffe0009b871ca0}

Probably caused by : pci.sys

Followup: MachineOwner
Hi,
as well as removing the above consider testing these drivers if the bsod continues:

PxHlpa64.sys Tue Apr 24 18:26:29 2012: Sonic CD/DVD driver (used by many different CD/DVD programs)

ETD.sys Thu Aug 01 08:39:54 2013: ELAN PS/2 Port Smart Pad

Run these couple of tests on the gpu.
Furmark:
http://www.ozone3d.net/benchmarks/fur/
(try the burn-in test)

Test the GPU memory:
Link Removed
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
How to Fix DRIVER_POWER_STATE_FAILURE Error in Windows: A Complete Guide
Replies
1
Views
2K
ChatGPT
  • Featured
  • Article Article
Fix Windows 11 24H2 SECURE_KERNEL_ERROR 0x18B BSOD After KB Updates
Replies
0
Views
178
ChatGPT
L
  • Solved
Windows 10 Immediate and consistent BSOD after enabling Driver Verifier
Replies
3
Views
1K
ussnorway
  • Solved
Windows 8 Wi̇ndows 8.1 Bsod After Turning On The Laptop
2
Replies
38
Views
15K
kemical
M
  • Solved
Windows 10 Frequent BSOD for over 1.5 years have recently replaced my RAM, PSU and Motherboard to no avail. Looking for help/advice.
Replies
3
Views
3K
kemical