New
#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.
I've got several BSOD with error code 0x000009f.
Drivers are up to date.
No new hardware have been connected.
Please help.
Code:BugCheck 9F, {3, 88680030, 8078adb0, 8537f788} Probably caused by : usbccgp.sysScan for any missing, modified or corrupted protected Windows files with: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
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.
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.sysThere 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?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
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.
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.
InformationWhy 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.
WarningBefore 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.
Let us know the results, with the subsequent crash dumps, if any. And, dont create multiple threads on a same issue.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
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.