BSOD Restart error code 0x000009f


  1. Posts : 5
    Windows 7 Professional x86
       #1

    BSOD Restart error code 0x000009f


    I've got several BSOD with error code 0x000009f.
    Drivers are up to date.
    No new hardware have been connected.
    Please help.
      My Computer

  2.    #2

    Code:
    BugCheck 9F, {3, 88680030, 8078adb0, 8537f788}
    
    Probably caused by : usbccgp.sys
    Code:
    0: kd> !irp 8537f788
    Irp is active with 20 stacks 18 is current (= 0x8537fa5c)
     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
     [  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 e0 88680030 00000000 8a9b01e8-886a5bc0 Success Error Cancel 
    	       \Driver\usbccgp	ks!CKsDevice::CompleteDevicePowerIrp
    			Args: 00000000 00000001 00000001 00000000
     [ 16, 2]   0 e1 886a5e68 00000000 00000000-00000000    pending
    	       \Driver\usbvideo
    			Args: 00000000 00000001 00000001 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-885fdfc0    
    
    			Args: 00000000 00000000 00000000 00000000
    Scan for any missing, modified or corrupted protected Windows files with:
      My Computer


  3. Posts : 5
    Windows 7 Professional x86
    Thread Starter
       #3

    Random BSOD


    Hello, a friend's laptop have got Random Blue screen in diferents days.
    Drivers and Windows are up to date.
    No new hardware or change have been made.

    I Upload the result of the SF Scan.

    Tks.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Did your friend receive any BSOD after 23rd of Jan?
      My Computer


  5. Posts : 5
    Windows 7 Professional x86
    Thread Starter
       #5

    koolkat77 said:
    Did your friend receive any BSOD after 23rd of Jan?
    No, but the notebook was frozen several times after days (yesterday).
      My Computer

  6.    #6

    Code:
    BugCheck 9F, {3, fffffa8006154a00, fffff80000b9c4d8, fffffa8006e7fa20}
    
    Unable to load image \SystemRoot\system32\DRIVERS\ks.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ks.sys
    *** ERROR: Module load completed but symbols could not be loaded for ks.sys
    Probably caused by : usbccgp.sys
    Code:
    0: kd> lmvm ks
    start             end                 module name
    fffff880`00db5000 fffff880`00df8000   ks       T (no symbols)           
        Loaded symbol image file: ks.sys
        Image path: \SystemRoot\system32\DRIVERS\ks.sys
        Image name: ks.sys
        Timestamp:        Thu Mar 04 04:32:25 2010 (4B8F37D9)
        CheckSum:         000410FC
        ImageSize:        00043000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    There also appears to be problems with your Kernel CSA Library, which is sourced from Windows Update, what are the results of the System File Scan?
      My Computer


  7. Posts : 5
    Windows 7 Professional x86
    Thread Starter
       #7

    BSOD Restart several times


    Hello, i´ve got on a friend's laptop several BSOD.
    In the event viewer apear system restart after error check, error code 0x00009f.

    I attach Minidumps generated.
      My Computer


  8. Posts : 5
    Windows 7 Professional x86
    Thread Starter
       #8

    x BlueRobot said:
    Code:
    BugCheck 9F, {3, 88680030, 8078adb0, 8537f788}
     
    Probably caused by : usbccgp.sys
    Code:
    0: kd> !irp 8537f788
    Irp is active with 20 stacks 18 is current (= 0x8537fa5c)
     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
     [  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 e0 88680030 00000000 8a9b01e8-886a5bc0 Success Error Cancel 
               \Driver\usbccgp    ks!CKsDevice::CompleteDevicePowerIrp
                Args: 00000000 00000001 00000001 00000000
     [ 16, 2]   0 e1 886a5e68 00000000 00000000-00000000    pending
               \Driver\usbvideo
                Args: 00000000 00000001 00000001 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-885fdfc0    
     
                Args: 00000000 00000000 00000000 00000000

    Scan for any missing, modified or corrupted protected Windows files with:
    The SFC /SCANNOW result in 100% OK, after system restart again this morning.
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any. And, dont create multiple threads on a same issue.
      My Computer

  10.    #10

    Follow Arc's suggestion, Windows isn't crashing at the right time, in order to show the true driver which causing the crash, that's why it is blaming Windows files which tend to rarely to be problem.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:35.
Find Us