locked
DRIVER_POWER_STATE_FAILURE & BUGCODE_USB_DRIVER RRS feed

  • Question

  • Hi Team,

     I am having trouble with my laptop since long, It restarts suddenly & randomly not sure why, When observed Minidumb below are the info

    Crash List



    Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time
    090214-16972-01.dmp 9/2/2014 11:24:40 PM BUGCODE_USB_DRIVER 0x000000fe 00000000`00000008 00000000`00000006 00000000`0000000b fffffa80`08bc2b20 usbhub.sys usbhub.sys+129ec         x64 ntoskrnl.exe+71f00         C:\Windows\Minidump\090214-16972-01.dmp 8 15 7600 262,144 9/2/2014 11:26:26 PM
    050214-17160-01.dmp 5/2/2014 7:44:57 PM DRIVER_POWER_STATE_FAILURE 0x1000009f 00000000`00000004 00000000`00000258 fffffa80`05b04680 fffff800`00b9c4d0 ntoskrnl.exe ntoskrnl.exe+77dda NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+77dda         C:\Windows\Minidump\050214-17160-01.dmp 8 15 7600 545,520 5/2/2014 7:46:10 PM

    Please let me know if any other file is required. MEMORY DUMP file not sure how to upload here.

    Thanks in Advance.!!

     

    Tuesday, October 21, 2014 8:27 PM

Answers

  • SH

    The dates on those 2 DMP files are from May and from September so not relevant to the current situation.  The first thing you should do is to update to SP-1, then if you continue to crash run driver verifier to find the underlyinf cause.

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these tests to verify your memory and find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    Since it is more likely to be a driver please run verifier first.
    1-Driver verifier (for complete directions see our wiki here)

    If verifier does not find the issue we can move on to this.
    2-Memtest. (You can read more about running memtest here)

    If you cannot boot after enabling verifier reboot into safe mode
    In Vista & win 7 (F8)

    Co-Authored by  JMH3143
    .


    Wanikiya and Dyami--Team Zigzag

    Tuesday, October 21, 2014 8:50 PM

All replies

  • http://wikisend.com/download/906142/050214-17160-01.dmp

    http://wikisend.com/download/340010/090214-16972-01.dmp

    Tuesday, October 21, 2014 8:38 PM
  • SH

    The dates on those 2 DMP files are from May and from September so not relevant to the current situation.  The first thing you should do is to update to SP-1, then if you continue to crash run driver verifier to find the underlyinf cause.

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these tests to verify your memory and find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    Since it is more likely to be a driver please run verifier first.
    1-Driver verifier (for complete directions see our wiki here)

    If verifier does not find the issue we can move on to this.
    2-Memtest. (You can read more about running memtest here)

    If you cannot boot after enabling verifier reboot into safe mode
    In Vista & win 7 (F8)

    Co-Authored by  JMH3143
    .


    Wanikiya and Dyami--Team Zigzag

    Tuesday, October 21, 2014 8:50 PM