BSOD caused by driver power state failure.

drager204 · Jul 6, 2014

I recently bought a ASUS G750jm laptop. in the past 30 days of receiving it it has BSOD six times. Five have been caused by a DRIVER_POWER_STATE_FAILURE and the most recent was
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. I have tried researching and calling in to ASUS and they were no help. I am just looking for advice on what to do. Thanks.

Below i included all the crash dumps.

blueelvis · Jul 6, 2014

Hi Drager204 & Welcome to the forums ^_^,

I have analyzed your dump files and below is a summary of your dump file having the Driver_Power_State_Failure bugcheck.

Code:

2: kd> !irp ffffe001e9619ca0
Irp is active with 6 stacks 4 is current (= 0xffffe001e9619e48)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 ffffe001e4ded5b0 00000000 fffff80191c21fc4-ffffd0006bf0f8f0 Success Error Cancel pending
           \Driver\pci    dxgkrnl!DpiFdoPowerCompletionRoutine
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001e8cc41f0 00000000 fffff80066ba02d8-ffffe001e9f54f08 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\[U][B]nvlddmkm.sys[/B][/U], Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 \Driver\nvlddmkm    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001e9f54f08    

            Args: 00000000 00000000 00000000 00000000

We see that the Nvidia Driver is to be blamed for the bugchecks (Rest of the bugchecks also blames this). Now, below is a list of 3rd party drivers which should update :-

Code:

**************************Sun Jul  6 11:36:58.119 2014 (UTC + 5:30)**************************
ASMMAP64.sys                Thu Jul  2 14:43:26 2009 (4A4C7A36)
AiCharger.sys               Fri Sep 23 07:34:40 2011 (4E7BE938)
btwl2cap.sys                Thu Jul 26 20:44:41 2012 (50115EE1)
kbfiltr.sys                 Thu Aug  2 08:52:22 2012 (5019F26E)
atkwmiacpi64.sys            Tue Jul  2 14:05:32 2013 (51D290D4)
plctrl.sys                  Thu Jul 11 08:53:44 2013 (51DE2540)
L1C63x64.sys                Tue Jul 16 12:26:31 2013 (51E4EE9F)
ETD.sys                     Thu Aug  1 13:09:54 2013 (51FA10CA)
bcbtums.sys                 Wed Aug  7 20:41:22 2013 (5202639A)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
btwampfl.sys                Sat Aug 31 00:02:26 2013 (5220E53A)
TeeDriverx64.sys            Thu Sep  5 23:32:18 2013 (5228C72A)
iaStorA.sys                 Wed Sep 18 21:03:51 2013 (5239C7DF)
dump_iaStorA.sys            Wed Sep 18 21:03:51 2013 (5239C7DF)
iwdbus.sys                  Fri Sep 27 03:08:04 2013 (5244A93C)
bcmwl63a.sys                Sun Sep 29 01:05:45 2013 (52472F91)
btwavdt.sys                 Tue Oct  1 06:53:03 2013 (524A23F7)
btwaudio.sys                Tue Oct  1 06:55:30 2013 (524A248A)
btwrchid.sys                Tue Oct  1 06:55:58 2013 (524A24A6)
AsHIDSwitch64.sys           Tue Oct  8 07:15:17 2013 (525363AD)
mbam.sys                    Wed Oct 30 21:41:45 2013 (52712FC1)
igdkmd64.sys                Thu Dec 19 02:19:12 2013 (52B20A48)
RTKVHD64.sys                Fri Jan 24 15:46:24 2014 (52E23D78)
MBAMSwissArmy.sys           Fri Mar 21 03:42:35 2014 (532B67D3)
nvvad64v.sys                Fri Mar 28 19:02:06 2014 (533579D6)
nvlddmkm.sys                Tue May 20 04:38:44 2014 (537A8EFC)
NvStreamKms.sys             Thu May 22 22:13:14 2014 (537E2922)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 28 22:52:56.748 2014 (UTC + 5:30)**************************
dc3d.sys                    Wed May 18 13:37:24 2011 (4DD37E3C)
IntcDAud.sys                Wed Nov 27 19:55:44 2013 (529600E8)
mwac.sys                    Wed Mar  5 03:17:40 2014 (531649FC)

BSOD caused by driver power state failure.

drager204

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One