Windows 8 and 8.1 Forums


BSOD when the PC Start, "the day after"

  1. #1


    Posts : 5
    Windows 8.1 x64

    BSOD when the PC Start, "the day after"


    Hello everyone
    I have this problem to the PC for many months .. and I've done countless tests to solve it but nothing .. always manifests itself!
    List the tests that I've done:
    -Ram-TEST lasted nine hours and successfully completed
    -Change the motherboard (ASUS Sabertooth 990FX From R2.0 to MSI 890FX-GD70, the latter shall use at this time, the other I sold it)
    -Changed video card (ATI 6870 Updated NVIDIA 760)
    -Replaced SSD where the system resides, had a value SMART wrong, incorrectly replaced by Samsung (EVO 250GB)
    -Analyzed by-DUMP bluescreenanalizer and semrpe the same file with the same bug tails
    -Windows-formatted 3 times already

    The temperatures are good .. I also have a Corsair H100i and a fairly spacious case that allows good ventilation (CM Storm Trooper)
    This is my components:
    CPU: AMD FX8350
    RAM: 16GB (4 x 4) G SKILL 1866 MHz CAS 8
    SSD: 250GB Samsung EVO
    Video Card: Zotac 760 amp edition!
    HDD: 3TB WD, 250GB WD
    Motherboard: MSI 890FX-GD70
    Sound Card: Asus Xonar Phoebus ONLY
    Case: CM Storm Trooper Black
    Win 8.1 x64 Original
    I repeat that I do not overclock, the frequencies are those of series

    Now I'll explain when I turn on my pc at COLD (the day after practically) happens to me .. and not always! However, if you reboot immediately after work PERFECTLY, and for hours and hours! without presenting problems or other, and even under stress.
    The next day, however, having been off the night it happens it happens .. this blue screen without doing anything specific! Coincidentally, sometimes even if I do nothing on windows just turned on, or a complete on the internet, or other, causally!
    I have no idea how to solve this problem .. I hope you can help me! Thank you
    In conclusion, after which it remains off for the night MAY encounter this problem, but for now it occurs often.
    I apologize for my English but I used google translator

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Tommyatlon & Welcome to the forums ^_^,

    No problem that you speak Italian and not english, it is far better to understand the problem mate ^_^. I have analyzed your Dump files and all of them are of the "Driver_Power_State_Failure" with the first argument as 3. This means that a driver failed to complete and Input/Output Request in a timely manner. Below has been provided an analysis of your latest dump file :-
    Code:
    0: kd> !analyze -v*******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001f2f36060, Physical Device Object of the stack
    Arg3: fffff800cc4b78b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001f2f185c0, The blocked IRP
    
    
    Debugging Details:
    ------------------
    
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
    ***                                                                   ***
    *************************************************************************
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    
    IMAGE_NAME:  usbhub.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53649d13
    
    
    MODULE_NAME: usbhub
    
    
    FAULTING_MODULE: fffff80080e7d000 usbhub
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x9F
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  2
    
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    
    DPC_STACK_BASE:  FFFFF800CC4BFFB0
    
    
    STACK_TEXT:  
    fffff800`cc4b7878 fffff800`cac09c1e : 00000000`0000009f 00000000`00000003 ffffe001`f2f36060 fffff800`cc4b78b0 : nt!KeBugCheckEx
    fffff800`cc4b7880 fffff800`cac09b3e : ffffe001`f1647130 ffffe000`ffffffff ffffe001`f1647170 fffff800`caa6a240 : nt!PopIrpWatchdogBugcheck+0xde
    fffff800`cc4b78e0 fffff800`caa66810 : 00000000`00000000 fffff800`cc4b7a30 ffffe001`f1647168 fffff800`00000002 : nt!PopIrpWatchdog+0x32
    fffff800`cc4b7930 fffff800`cab64aea : fffff800`cacf3180 fffff800`cacf3180 fffff800`cad5aa00 ffffe001`f2a07080 : nt!KiRetireDpcList+0x4f0
    fffff800`cc4b7be0 00000000`00000000 : fffff800`cc4b8000 fffff800`cc4b1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_AVerAF35_IMAGE_usbhub.sys
    
    
    BUCKET_ID:  0x9F_3_POWER_DOWN_AVerAF35_IMAGE_usbhub.sys
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_averaf35_image_usbhub.sys
    
    
    FAILURE_ID_HASH:  {e10270c8-c1b9-874c-4480-2f4d2835426a}
    
    
    Followup: MachineOwner
    ---------
    
    
    0: kd> !irp ffffe001f2f185c0
    Irp is active with 8 stacks 6 is current (= 0xffffe001f2f187f8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
         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
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    
                Args: 00000000 00000000 00000000 00000000
     [ 16, 0]   0  0 ffffe001f2f36060 00000000 fffff80080c20058-ffffe001f2bc84a0    
               \Driver\usbhub    ks!KsGetDeviceForDeviceObject
                Args: 00000000 00000000 00000000 00000002
    >[ 16, 2]   0  1 ffffe001f1b9b220 00000000 00000000-00000000    pending
              Unable to load image \SystemRoot\System32\Drivers\AVerAF35.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AVerAF35.sys
    *** ERROR: Module load completed but symbols could not be loaded for AVerAF35.sys
     \Driver\AVerAF35
                Args: 00051100 00000001 00000001 00000002
     [ 16, 2]   0 e1 ffffe001f0d5be40 00000000 fffff800cab2b2d8-ffffe001f1647130 Success Error Cancel pending
               \Driver\ksthunk    nt!PopRequestCompletion
                Args: 00051100 00000001 00000001 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe001f1647130    
    
    
                Args: 00000000 00000000 00000000 00000000
    If we run an !irp on the last parameter, we get the driver blamed is "AverAF35.sys" which is the driver for your AVerMedia A835 USB DVB-T.

    If we check the modules list, the date of the driver is in the year of 2012 which is extremely old and is not compatible with Windows 8.1 . Please visit the above driver link to find the information from where to update the driver.

    Please update this driver and let me know if the issue still persists or not. In case the issue persists, we would be glad to help you out further ^_^
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 8.1 x64


    Quote Originally Posted by blueelvis View Post
    Hi Tommyatlon & Welcome to the forums ^_^,

    No problem that you speak Italian and not english, it is far better to understand the problem mate ^_^. I have analyzed your Dump files and all of them are of the "Driver_Power_State_Failure" with the first argument as 3. This means that a driver failed to complete and Input/Output Request in a timely manner. Below has been provided an analysis of your latest dump file :-
    Code:
    0: kd> !analyze -v*******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001f2f36060, Physical Device Object of the stack
    Arg3: fffff800cc4b78b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001f2f185c0, The blocked IRP
    
    
    Debugging Details:
    ------------------
    
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
    ***                                                                   ***
    *************************************************************************
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    
    IMAGE_NAME:  usbhub.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53649d13
    
    
    MODULE_NAME: usbhub
    
    
    FAULTING_MODULE: fffff80080e7d000 usbhub
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x9F
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  2
    
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    
    DPC_STACK_BASE:  FFFFF800CC4BFFB0
    
    
    STACK_TEXT:  
    fffff800`cc4b7878 fffff800`cac09c1e : 00000000`0000009f 00000000`00000003 ffffe001`f2f36060 fffff800`cc4b78b0 : nt!KeBugCheckEx
    fffff800`cc4b7880 fffff800`cac09b3e : ffffe001`f1647130 ffffe000`ffffffff ffffe001`f1647170 fffff800`caa6a240 : nt!PopIrpWatchdogBugcheck+0xde
    fffff800`cc4b78e0 fffff800`caa66810 : 00000000`00000000 fffff800`cc4b7a30 ffffe001`f1647168 fffff800`00000002 : nt!PopIrpWatchdog+0x32
    fffff800`cc4b7930 fffff800`cab64aea : fffff800`cacf3180 fffff800`cacf3180 fffff800`cad5aa00 ffffe001`f2a07080 : nt!KiRetireDpcList+0x4f0
    fffff800`cc4b7be0 00000000`00000000 : fffff800`cc4b8000 fffff800`cc4b1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_AVerAF35_IMAGE_usbhub.sys
    
    
    BUCKET_ID:  0x9F_3_POWER_DOWN_AVerAF35_IMAGE_usbhub.sys
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_averaf35_image_usbhub.sys
    
    
    FAILURE_ID_HASH:  {e10270c8-c1b9-874c-4480-2f4d2835426a}
    
    
    Followup: MachineOwner
    ---------
    
    
    0: kd> !irp ffffe001f2f185c0
    Irp is active with 8 stacks 6 is current (= 0xffffe001f2f187f8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
         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
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    
                Args: 00000000 00000000 00000000 00000000
     [ 16, 0]   0  0 ffffe001f2f36060 00000000 fffff80080c20058-ffffe001f2bc84a0    
               \Driver\usbhub    ks!KsGetDeviceForDeviceObject
                Args: 00000000 00000000 00000000 00000002
    >[ 16, 2]   0  1 ffffe001f1b9b220 00000000 00000000-00000000    pending
              Unable to load image \SystemRoot\System32\Drivers\AVerAF35.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AVerAF35.sys
    *** ERROR: Module load completed but symbols could not be loaded for AVerAF35.sys
     \Driver\AVerAF35
                Args: 00051100 00000001 00000001 00000002
     [ 16, 2]   0 e1 ffffe001f0d5be40 00000000 fffff800cab2b2d8-ffffe001f1647130 Success Error Cancel pending
               \Driver\ksthunk    nt!PopRequestCompletion
                Args: 00051100 00000001 00000001 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe001f1647130    
    
    
                Args: 00000000 00000000 00000000 00000000
    If we run an !irp on the last parameter, we get the driver blamed is "AverAF35.sys" which is the driver for your AVerMedia A835 USB DVB-T.

    If we check the modules list, the date of the driver is in the year of 2012 which is extremely old and is not compatible with Windows 8.1 . Please visit the above driver link to find the information from where to update the driver.

    Please update this driver and let me know if the issue still persists or not. In case the issue persists, we would be glad to help you out further ^_^
    THANK YOU !
    I tried to remove it and everything seems to be going well!
    Really .. thanks a lot!
    I can't update the drivers because they are already the last .. but it does not matter, I did not use ever!
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    You are welcome :arigato:

    Please test your system extensively and in case of any problem, do post here back ^_^
      My System SpecsSystem Spec

BSOD when the PC Start, "the day after"
Related Threads
53107 this is the screenshot.You see "Start" letter is there and can't do anything about it. Left or right clicking doesn't do anyhting. It happened after i removed ViStart. I have tried reinstalling ViStart and removing it again but no changes. I am running Windows 8.1 Pro x64 Waiting...
Hi all, So I'm kind of stuck.. I currently have the problem where I am in an endless cycle of "loading files" -> "Windows Boot Manager" (see: How To Boot Into Safe Mode On Windows 8 (The Easy Way)). I have tried to load all of the options -- and none successfully load. I also end up at...
Hello, Following the forum guidelines I am posting a compressed file from your SF Diagnostic tool. This was done shortly after a BSOD. Thanks for your support in helping me understand what is the cause of those frequent BSOD. Joce
Help! I've been trying for a few days to solve this, but MS and Google Searches haven't been able to help out at all. On Windows 8 the Windows Store fails to start up on my wife's account. When you click on the app, you get the start screen for the windows store with the circle animation at the...
Hi everybody, since maybe 2 weeks I get randomly BSODs, sometimes with "Multiple_IRP_Completed_Requests", sometimes with "PFN_LIST_CORRUPT" errors. It felt to me that they appeared more often after starting the computer out of standby/hibernate. But today it happend while watching a video...
I just saw this on a new HP laptop I am working on, it actually makes a kind of Program Menu, so if you don't want a full Start Menu like Windows 7, you can use this to just have links to your Programs: 32513 The HP Quick Start Application (Windows 8) | HP® Support Installation Causes a...
BSOD/Computer re-start " Bad_Pool_Header" ???? in BSOD Crashes and Debugging
Is this driver related has happened twice after leaving laptop alone for about an hour then going back to find re-started and message of mini dump on screen.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook