Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Daily BSOD that seems to be USB related


  • Please log in to reply
3 replies to this topic

#1 BoomSchtick

BoomSchtick

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:00 PM

Posted 10 May 2017 - 11:45 AM

I check the .dmp file:

 

BugCheck 9F, {3, ffff9f018e258e20, fffff801b84028e0, ffff9f01937274f0}
 
Probably caused by : UsbHub3.sys
 
· OS - Windows 10 x64 
· What was original installed OS on system?  Windows 10 as far as I know
· Is the OS an OEM version:  Yes
· Age of system (hardware):  Less than a year
· Age of OS installation - have you re-installed the OS? Same as age of system - I have not reinstalled
 
· CPU:  Processor Intel® Core™ i7-6700 CPU @ 3.40GHz, 3408 Mhz, 4 Core(s), 8 Logical Processor(s)
· Video Card:  Intel® HD Graphics 530
· MotherBoard - Dell
· Power Supply - Unknown - Dell
 
· System Manufacturer - Dell
· Exact model number: Optiplex 7040
 
· Laptop or Desktop:  Desktop

 

 

 
I have tried to find a newer USB driver, but all I could find on Intel's website was a driver for Windows 7.

Attached Files



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:00 AM

Posted 10 May 2017 - 12:07 PM

My analysis of the latest dump file...

STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE bugcheck, indicating that a driver has failed to complete a power IRP within a specific time:

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: ffff9f018e258e20, Physical Device Object of the stack
Arg3: fffff801b84028e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9f01937274f0, The blocked IRP
We need to have a look at the IRP using the !irp command:
0: kd> !irp ffff9f01937274f0
Irp is active with 15 stacks 12 is current (= 0xffff9f01937278d8)
 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
 [  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
 [  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, 2]   0 e1 ffff9f018e258e20 00000000 fffff804dcae5770-ffff9f018e23d4f0 Success Error Cancel pending
           \Driver\USBHUB3    UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion
            Args: 00041100 00000001 00000001 00000002
Unable to load image \SystemRoot\system32\DRIVERS\USA19Hx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USA19Hx64.sys
*** ERROR: Module load completed but symbols could not be loaded for USA19Hx64.sys
 [ 16, 2]   0 e1 ffff9f018e258e20 00000000 fffff804dd8d04d0-ffff9f018e271ca0 Success Error Cancel pending
           \Driver\USBHUB3    USA19Hx64
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 ffff9f018e271ca0 00000000 fffff801b639cff0-ffff9f01932cd1a0 Success Error Cancel pending
           \Driver\USA19H    nt!PopRequestCompletion
            Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffff9f01932cd1a0    

            Args: 00000000 00000000 00000000 00000000
Looks like USA19Hx64.sys is to blame:
0: kd> lm k vm USA19Hx64
start             end                 module name
fffff804`dd8d0000 fffff804`dd984b00   USA19Hx64 T (no symbols)           
    Loaded symbol image file: USA19Hx64.sys
    Image path: \SystemRoot\system32\DRIVERS\USA19Hx64.sys
    Image name: USA19Hx64.sys
    Timestamp:        Tue Oct 30 15:52:45 2007 (47278B8D)
    CheckSum:         000C302B
    ImageSize:        000B4B00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
No wonder, it's a decade old and not supposed to be used on Windows 10. Therefore, please uninstall your Keyspan USB Serial Adapter driver... if need be physically remove the device from the system.

Good luck!

Kind regards,
bwv848

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 BoomSchtick

BoomSchtick
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:00 PM

Posted 10 May 2017 - 12:45 PM

Many thanks bwv848.

 

TripLite has a download for Windows 10, but it's the same driver from 2007 that's packaged with it.  I deleted and reinstalled it.  If the BSOD's continue, I'll order him another brand.

 

You knowledge of the ins and outs of BSOD's is impressive!



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:00 AM

Posted 10 May 2017 - 01:13 PM

You're quite welcome. 0x9Fs are the easiest to debug actually. :) How about bugging TripLite support and ask them what's going on? They really shouldn't be giving out Vista drivers.

 

Regards,

bwv848


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users