BSOD, BCCode f9, Caused by ntoskrnl.exe

Soundman · 31 Dec 2013

This is a little over a week old computer and I've had nine BSODs since I got it. Using BlueScreenView tells me that ntoskrnl.exe is the cause. I have no idea what the means... BCCode f9. I'm wondering if it has something to do with my mouse since sometimes after the crash my mouse won't work. But there have been days I've used my mouse for hours and never had a problem... Hopefully I ran the diagnostic tool correctly and someone here can tell me what the problem is. :)

Oh, and I also completely uninstalled and then reinstalled my video card driver last Wednesday after two BSODs. Had two back to back BSODs today, none in between.

My system:
Mythlogic Pollox 1413
nVIDIA GTX 765M
Intel Core i7-4700
8gb RAM (two 4GB sticks)
Windows 7 64bit

All up to date.

Golden · 31 Dec 2013

Code:

IMAGE_VERSION:  6.1.7601.18251

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_image_usbhub.sys

FAILURE_ID_HASH:  {ec46ebd8-431a-da69-d1c8-e27212f72a5c}

Followup: MachineOwner
---------

0: kd> lmvm usbhub
start             end                 module name
fffff880`05eb4000 fffff880`05f0e000   usbhub     (pdb symbols)          c:\symbols\usbhub.pdb\037DF7A248D4468EB53CC2809E03ED871\usbhub.pdb
    Loaded symbol image file: usbhub.sys
    Mapped memory image file: c:\symbols\usbhub.sys\5227239A5a000\usbhub.sys
    Image path: \SystemRoot\system32\drivers\usbhub.sys
    Image name: usbhub.sys
    Timestamp:        Wed Sep 04 21:42:10 2013 (5227239A)
    CheckSum:         00056519
    ImageSize:        0005A000
    File version:     6.1.7601.18251
    Product version:  6.1.7601.18251
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     usbhub.sys
    OriginalFilename: usbhub.sys
    ProductVersion:   6.1.7601.18251
    FileVersion:      6.1.7601.18251 (win7sp1_gdr.130903-1532)
    FileDescription:  Default Hub Driver for USB
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
0: kd> !drvobj fffffa8014213a10 f
fffff80002e2d010: Unable to get value of ObpRootDirectoryObject
fffff80002e2d010: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa8014213a10) is for:
 \Driver\usbhub

The problem certainly appears to be related to the USB driver. Unfortunately your upload is incomplete.....I need your MSINFO file. Please attach it using the SFDiagnostic tool.

Soundman · 31 Dec 2013

I think this is it.

Golden · 31 Dec 2013

Thanks I'll try take a look tonight if I'm sober enough.

In the meantime also do this:
Download and execute Driverview
1. View > Hide Microsoft Drivers
2. Edit > Select all
3. File > Save Selected Items

In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
Zip the .txt file and upload it here.

Soundman · 31 Dec 2013

Thanks! Here it is.

Golden · 31 Dec 2013

OK. Lets try this first:

Turn OFF USB Selective Suspend please:
USB Selective Suspend - Turn On or Off

Now monitor your system - anymore crashes, repost the new dmp file.

Soundman · 31 Dec 2013

Done, thanks. I'll monitor the system and report back if it crashes again.

Soundman · 11 Jan 2014

Had two BSODs, one today and one yesterday. Both were on startup, hadn't opened a single program yet (don't think I even logged in on the first one). Only one dmp file because it wouldn't make one yesterday and I ended up having to force my computer to shut down. Today when it restarted from the BSOD my mouse wouldn't work.

Oh, the first one had the same name as this second one.

Thanks!

Soundman · 11 Jan 2014

Had two more. Restarted my computer to try and get my mouse back and it wouldn't shut down (15 minutes with it saying it was shutting down) so I forced it. On restart it had a BSOD (Power Driver State Failure) before it even got to the login screen.

Then when it restarted again (it auto restarts after each BSOD) it did the same as my last post and didn't create a dmp file, had to force it off again. Now it's working correctly.

Soundman · 12 Feb 2014

Had two more. One on the 26th and one today the 12th.