locked
I got BSOD once, but never again, is my PC okay? RRS feed

  • Question

  • I just got a brand new HP pavillion yesterday which I love. Today when i plugged my iPod touch into my computer for the first time the computer forze up a bit and just got really slow. I tried to open iTunes and it didn't respond. I suppose it was installing the driver software. Anyway, I rebooted my computer so I could get things running again, but upon reboot I had the BSOD, it just said if this is the first time, restart. It also said stuff about possible new software working incorrextly if the problem persists. Anyway, so i had to do a hard reset (hold down the power button) and It started up and now everything works perfectly including my iPod and iTunes. My computer wasn't completely up to date as I just purchased it and I hadn't finished installing all the available updates.Not sure if that measn anything. Anyway, I'm paranoid and I need to know if my computer is okay. Was it just a hicup in the wondows system, or is there something seriousely wrong with my computer? I doubt there is as everything is working perfectly now, but I just need peace of mind. I mean it's brand new! Anyway, is my computer okay, it only happened once!
    Sunday, August 7, 2011 5:56 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80091ae6e0, Physical Device Object of the stack
    Arg3: fffff80000ba2748, Functional Device Object of the stack
    Arg4: fffffa800b7704d0, The blocked IRP
    Debugging Details:
    ------------------
    *** WARNING: Unable to verify timestamp for nusb3xhc.sys
    *** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  nusb3xhc.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d01b19b
    MODULE_NAME: nusb3xhc
    FAULTING_MODULE: fffff880060d3000 nusb3xhc
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`02ef89c2 : 00000000`0000009f 00000000`00000003 fffffa80`091ae6e0 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`02e97652 : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00ba27a0 fffff800`02e974f6 : fffff800`03033f00 00000000`00036d5f 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00ba2810 fffff800`02e973de : 00000008`287b86a7 fffff800`00ba2e88 00000000`00036d5f fffff800`03001e68 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`02e971c7 : fffff800`02ffeec1 fffffa80`00036d5f fffffa80`08922a30 00000000`0000005f : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02e8e765 : 00000000`00000000 fffffa80`06570680 00000000`00000000 fffff880`044ac588 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02e8e57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`037428d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_3_nusb3hub_IMAGE_nusb3xhc.sys
    BUCKET_ID:  X64_0x9F_3_nusb3hub_IMAGE_nusb3xhc.sys
    Followup: MachineOwner
    ---------
    0: kd> lmvm nusb3xhc
    start             end                 module name
    fffff880`060d3000 fffff880`06104000   nusb3xhc T (no symbols)           
        Loaded symbol image file: nusb3xhc.sys
        Image path: \SystemRoot\system32\DRIVERS\nusb3xhc.sys
        Image name: nusb3xhc.sys
        Timestamp:        Fri Dec 10 05:50:35 2010 (4D01B19B)
        CheckSum:         00038099
        ImageSize:        00031000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ------------------------------------------------------------------------------------------------------------------------------------------------
    Your BSOD was caused by nusb3xhc.sys driver. More about it: http://systemexplorer.net/db/nusb3xhc.sys.html
    You can try to update it or uninstalling it. If this does not help, contact its developer Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    Sunday, August 7, 2011 7:07 PM

All replies

  • Hello,

    please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here.

    You can also contact Microsoft CSS.

     

    I should look to the dump file to determine the reasons of the crash. Possible a driver should be updated.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 


     

    Sunday, August 7, 2011 2:42 PM
  • I trired to upload it with Skydrive, but It gets an error when ever i try to upload my minidump file...any ideas? Also, when I tried standard upload and it says I don't have permission to upload the file! I am the admistrator so I'm not sure what the heck is going on there. Sorry I kinda freaking out, but I really want to fix this! If it even neeeds fixing. I tried openning the file in my library, and it tried to open with my visual basic 2010 compiler, however I do't think it had the righ plug in as it said:

    Skydrive error ^^                                                                          

    Sunday, August 7, 2011 3:49 PM
  • Okay, never mind, i figured out I had to put it in a zip folder first. Okay so here is the link:

    https://skydrive.live.com/redir.aspx?cid=73de0b386918f775&resid=73DE0B386918F775!105&authkey=PSvQWtSYbMc%24

    Please help ASAP! Thanks for your time!

    PS. The folder is called crash dump aug 6

    Sunday, August 7, 2011 5:06 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80091ae6e0, Physical Device Object of the stack
    Arg3: fffff80000ba2748, Functional Device Object of the stack
    Arg4: fffffa800b7704d0, The blocked IRP
    Debugging Details:
    ------------------
    *** WARNING: Unable to verify timestamp for nusb3xhc.sys
    *** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  nusb3xhc.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d01b19b
    MODULE_NAME: nusb3xhc
    FAULTING_MODULE: fffff880060d3000 nusb3xhc
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`02ef89c2 : 00000000`0000009f 00000000`00000003 fffffa80`091ae6e0 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`02e97652 : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00ba27a0 fffff800`02e974f6 : fffff800`03033f00 00000000`00036d5f 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00ba2810 fffff800`02e973de : 00000008`287b86a7 fffff800`00ba2e88 00000000`00036d5f fffff800`03001e68 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`02e971c7 : fffff800`02ffeec1 fffffa80`00036d5f fffffa80`08922a30 00000000`0000005f : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02e8e765 : 00000000`00000000 fffffa80`06570680 00000000`00000000 fffff880`044ac588 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02e8e57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`037428d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_3_nusb3hub_IMAGE_nusb3xhc.sys
    BUCKET_ID:  X64_0x9F_3_nusb3hub_IMAGE_nusb3xhc.sys
    Followup: MachineOwner
    ---------
    0: kd> lmvm nusb3xhc
    start             end                 module name
    fffff880`060d3000 fffff880`06104000   nusb3xhc T (no symbols)           
        Loaded symbol image file: nusb3xhc.sys
        Image path: \SystemRoot\system32\DRIVERS\nusb3xhc.sys
        Image name: nusb3xhc.sys
        Timestamp:        Fri Dec 10 05:50:35 2010 (4D01B19B)
        CheckSum:         00038099
        ImageSize:        00031000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ------------------------------------------------------------------------------------------------------------------------------------------------
    Your BSOD was caused by nusb3xhc.sys driver. More about it: http://systemexplorer.net/db/nusb3xhc.sys.html
    You can try to update it or uninstalling it. If this does not help, contact its developer Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    Sunday, August 7, 2011 7:07 PM
  • Thank you for your help. I located the usb 3.0 drivers and attempted to update them. As I suspected, my drivers were already up to date and were most likely updated when I udated windows after the error occured. Looks like the problem was with the USB 3.0 when I stuck my iPod USB in there. It seems windows resolved it during its update. I feel much better now! Thank you!

    Sunday, August 7, 2011 7:34 PM