Frequent BSOD's, ntoskrnl and usb drivers

[Newtype]

Hi, I've been getting Blue Screens after leaving my computer on for anything over 8 or so hours. I've had these issues for a while and I can't quite recall when I first started getting them, but I believe it was around the time I put in my new video card and set my ram to it's proper XMP profile. Turning the XMP profile back off resulted in the same blue screens, and I've also ran memtest86, albeit only once, for 9 hours overnight with it displaying no problems with my memory. Since then I just recently manually set my ram voltage properly due to noticing XMP not adjusting the voltage to it's correct setting in hopes that it might fix my problems, but, just last night I got another bluescreen. My computer was also just built in the beginning of the year, if that matters.

These BSOD's have happened when the computer's idle, or I'm in game, or just browsing the internet. Since I don't have much knowledge about what causes this, I've just been using BlueScreenView which has highlighted multiple issues, recently ntoskrnl.exe, USBPORT.SYS, and iusb3xhc.sys.

Hopefully I've attached the files correctly.

 

[Thedoctor44]

Your Intel USB 3.0 Extensible driver appears to be causing problems. Please update it here.

https://downloadcenter.intel.com/default.aspx

Your Nvidia graphics driver also appears to be causing some problems. Please roll back to the 334.89 version here

www.geforce.co.uk/drivers

I would try rolling back the graphics driver as it is the latest version.

Your Killer e2200 PCI-E Gigabit Ethernet Controller appears to be causing problems. Pick the Killer E2200 64bit version. Please update it here.

https://www.qca.qualcomm.com/resources/driverdownloads/

You also have a few memory references. Please run memtest86 to scan for errors. Please run for at least 8 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

[COLOR="Red"]Probably caused by : iusb3xhc.sys[/COLOR] ( iusb3xhc+3203f )

fffff880`0fd23000 fffff880`0fde6000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        [COLOR="red"]Fri Mar 29 12:36:19 2013[/COLOR] (51558AC3)
    CheckSum:         000C59AC
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[COLOR="red"]Probably caused by : nvlddmkm.sys[/COLOR] ( nvlddmkm+6b475 )

fffff880`0f036000 fffff880`0fc8e000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="red"]Tue Mar 04 11:07:52 2014[/COLOR] (5315B408)
    CheckSum:         00C20523
    ImageSize:        00C58000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[COLOR="red"]Probably caused by : e22w7x64.sys[/COLOR] ( e22w7x64+19fa0 )

fffff880`03e00000 fffff880`03e2a000   e22w7x64 T (no symbols)           
    Loaded symbol image file: e22w7x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e22w7x64.sys
    Image name: e22w7x64.sys
    Timestamp:        [COLOR="red"]Wed Dec 05 16:43:48 2012[/COLOR] (50BF79C4)
    CheckSum:         00035FA2
    ImageSize:        0002A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Gandalf]

Addition info...

This was probably caused by the following module: [FONT=Segoe UI, Arial]usbport.sys[/FONT] (USBPORT!USBPORT_TxCsqFindIrp+0x66)
Bugcheck code: 0xD1 (0x56796177, 0x2, 0x0, 0xFFFFF8800420FB72)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]

This was probably caused by the following module: [FONT=Segoe UI, Arial]iusb3xhc.sys[/FONT] (iusb3xhc+0x3203F)
Bugcheck code: 0xD1 (0x72056A2A, 0x2, 0x1, 0xFFFFF8800FD5503F)

This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x6B475)
Bugcheck code: 0xD1 (0xFFFFFFFFE8C15040, 0x6, 0x1, 0xFFFFF8800F0A1475)

This was probably caused by the following module: [FONT=Segoe UI, Arial]e22w7x64.sys[/FONT] (e22w7x64+0x19FA0)
Bugcheck code: 0xD1 (0xFFFFF8800B7AD000, 0x2, 0x0, 0xFFFFF88003E19FA0)

This was probably caused by the following module: [FONT=Segoe UI, Arial]netio.sys[/FONT] (NETIO!FsbFree+0x56)
Bugcheck code: 0xD1 (0xFFFFFA7FC5FAC227, 0x2, 0x1, 0xFFFFF88001583D36)
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr!FltpFastIoQueryOpen+0x86)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFE8, 0x0, 0xFFFFF880010D5A16, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]

This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF80002DADF00, 0x8, 0xFFFFF80002DADF00, 0x0)
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035262D0, 0xFFFFF8800961FF00, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]

This was probably caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (0xFFFFF88001869762)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001869762, 0xFFFFF8800BB987D0, 0x0)
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1!VIDMM_GLOBAL:: DestroyOneAllocation+0x2B9)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A012604CD0, 0xFFFFF8A012604CE0, 0x5010209)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl!DXGDEVICE::CreateAllocationObjects+0x2A)
Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA80101FBB50, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032C229D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF800033C816E)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
----------------------------------------------------------------------------------------------
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x41C235)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF8801021C235)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP
[/FONT][FONT=Segoe UI, Arial]----------------------------------------------------------------------------------------------

Hope this helps.

[/FONT]

 

[Thedoctor44]

Some good research there Gandalf. Thanks for your help.
However some of those possible causes are Windows system files which should never be altered.
for example netio.sys is the network input output system, these are pointed to because windows can't identify the 3rd party driver responsible so it points to the windows system file. The e22w7x64.sys is the Killer E2200 network driver so that will probably be the cause of one of the BSODs.
If a Windows system file or Dynamic Link Library is damaged or missing the best option is to use the installation CD to repair windows. Downloading hotfixes or files that are supposed to replace those missing can cause more harm than good.

 

[Newtype]

Appreciate the quick and helpful responses, thank you both. I'll update those drivers you listed/rollback the Nvidia one and run Memtest overnight.

I'll reply once I BSOD again, if it happens. Usually can take a day or two and I'll check in either way.

 

[Gandalf]

Doctor - Would sfc /scannow help?

 

[Thedoctor44]

I'm not too sure it would help as such but no harm should come from it.
You may as well give it a shot if the options I've suggested above don't work.

 

[Newtype]

A few hours prior to making this thread I had already updated the Intel USB 3.0 Extensible driver to what the MSI guys had on the G45 driver support page, I also uninstalled both the Power Charger Driver and another Intel one (Smart Connect I think). Anyway, there' surprisingly been no Blue Screen since and my uptimes about to reach three days. That's the longest I've had it go without crashing.

I made the thread a bit premature because I've tried quite a number of things already and didn't think that would work, so I was already sort of expecting to BSOD again soon. I'll reply again and update if everything continues to work properly or if it crashes again.

 

[Newtype]

Hi, even after ceasing to post on this thread I've continued to get BSODs, just didn't want to bump it because I wasn't going to be active enough to respond quickly and I didn't want to waste anyone's time.

I've since reinstalled Windows and have only (I think) installed my Killer Network Driver and my Intel USB 3.0 driver. I went 5 days without getting a bluescreen only to have my computer freeze in game (no BSOD) and then they became somewhat regular again, happening every day or every other day since then. I believe I uninstalled and reinstalled the Intel USB 3.0 driver to latest version and now every time I restart my computer through the start menu, or even shut it down, I bluescreen. So that's something new.

Prior to reinstalling Windows, I switched out my Ram for some old sticks I used in my previous computer thinking that might fix the problem, but I got two more BSOD's and put my newer ones back in. I ran memtest over night for only 5 passes and it found no problems, I forgot Thedoctor wanted 8 so I'll let it run again tonight. I also noticed my ram isn't listed as supported on my motherboard's website, so I'm not sure if that's a factor in anything or how accurate it is. Also, as mentioned in the OP, this started happening around the time I got a new video card. I haven't switched back to the old one to check if that can be it, but I also don't get any artifacting in games or over heating. Still, that might be it.

Running sfc /scannow didn't find any integrity violations.

 

[Thedoctor44]

I think Driver Verifier is needed because your dump files contain little information.
Follow these instructions on how to enable it.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier can stop your PC booting sometimes so it is recommended you create a system restore point before hand.
Please follow these instructions first.

http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

BugCheck F4, {3, fffffa800f2cdb30, fffffa800f2cde10, fffff80002d8f7b0}

Probably caused by : [COLOR="red"]svhost.exe[/COLOR]

Followup: MachineOwner

PROCESS_OBJECT: fffffa800f2cdb30

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: [COLOR="Red"]svhost[/COLOR]

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  [COLOR="red"]csrss.exe[/COLOR]

BUGCHECK_STR:  0xF4_csrss.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002e18ab2 to fffff80002a8abc0

Svhost is getting the blame because it is the Windows System process that hosts Windows Services.

The process being terminated is csrss.exe which stands for Client/Server Runtime Subsystem, this is the user mode subsystem for Windows32, it basically allows for the majority of system calls.
Without this process windows cannot function so it results in a bugcheck.

 

[Newtype]

Before you posted that I restarted, Bluescreened as I restarted then again on start up. Windows went to the repair screen and used an older restore point (one that still had the regular bluscreens, but not the wonky ones on shut down or restart). Now shutting down and restarting is fine. Just created another restore point and enabled driver verifier. I promise I won't mess with anything else lol, and I really appreciate the help.

 

[Thedoctor44]

There's nothing to promise, we're here as guidance, we don't own your PC so what you do is up to you.
However while you are coming to us for help we recommend no altering any settings as it makes it harder for us to help you.

Just upload any new dump files.

 

[Gandalf]

Doctor, Doctor - a couple ideas, I have.

Based on what the OP has written, I'm thinking the reinstall kind of points to a hardware issue. One can not just put different RAM strips into the PC and expect the PC to function well. PCs are like wizards. You need to treat them with tender loving care. If the motherboard website says no to a curtain type of RAM strip, then you should not use those strips in that PC. Of course, if he has downloaded drivers from bad sites, then you could have a bad driver, too.

As for the GPU, perhaps Furmark is worth a try.

A variation on your Signature's If it ain't broke, don't fix it. I say, If it ain't broke, don't fix it. Give it to me.

 

[Newtype]

Doctor, Doctor - a couple ideas, I have.

Based on what the OP has written, I'm thinking the reinstall kind of points to a hardware issue. One can not just put different RAM strips into the PC and expect the PC to function well. PCs are like wizards. You need to treat them with tender loving care. If the motherboard website says no to a curtain type of RAM strip, then you should not use those strips in that PC. Of course, if he has downloaded drivers from bad sites, then you could have a bad driver, too.

As for the GPU, perhaps Furmark is worth a try.

A variation on your Signature's If it ain't broke, don't fix it. I say, If it ain't broke, don't fix it. Give it to me.

I'm not too savvy with computer hardware or computers in general. I wasn't aware certain motherboards don't function well with specific ram or that they'd have a list of working ram on their website. With that said, I don't think the website said "no" to my specific ram, it just wasn't on the supported list. The ram that I had put in was the one I had used in a previous functioning computer and I was just testing whether or not my new ram was the problem.

The new RAM worked fine for a month when it was underclocked by default. I switched to the XMP profile the day I got my new video card and that's when I believe problems started occurring. So I turned XMP off and still had BSOD's, I also tried to set the clock speed and voltage manually in BIOS because I noticed the XMP profile set the voltage incorrectly. That didn't work either, unless I set it up incorrectly, which might be a a real possibility lol

"One can not just put different RAM strips into the PC and expect the PC to function well."

My computer is 4 months old and all the parts were completely new, I only put my old ram in when I was testing things to try and find the problem. I now know to look at the motherboard's website when purchasing new ram though

 

[Newtype]

This one happened coming off of standby/sleep

 

[Thedoctor44]

Doctor, Doctor - a couple ideas, I have.

Based on what the OP has written, I'm thinking the reinstall kind of points to a hardware issue. One can not just put different RAM strips into the PC and expect the PC to function well. PCs are like wizards. You need to treat them with tender loving care. If the motherboard website says no to a curtain type of RAM strip, then you should not use those strips in that PC. Of course, if he has downloaded drivers from bad sites, then you could have a bad driver, too.

As for the GPU, perhaps Furmark is worth a try.

A variation on your Signature's If it ain't broke, don't fix it. I say, If it ain't broke, don't fix it. Give it to me.

Unfortunately I disagree, just because he has re-installed Windows that doesn't mean it's a hardware issue at all.
I have had multiple cases, myself included where re-installing doesn't fix the problem because there is a common factor with each re-install (excluding hardware). There is probably a driver responsible that we can't identify that the user thinks is doing no harm.

 

[Thedoctor44]

The driver responsible appears to be linked with your Intel Smart Technology Driver.

An update might help but for the time being I suggest removing it.
Especially if it's unnecessary.

If you must update it then please go here.

http://www.intel.com/p/en_US/support/highlights/sftwr-prod/smrt_cnct

Unable to load image \SystemRoot\system32\DRIVERS\ISCTD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ISCTD64.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]ISCTD64.sys[/COLOR]

fffff880`043ca000 fffff880`043db000   ISCTD64  T (no symbols)           
    Loaded symbol image file: ISCTD64.sys
    Image path: \SystemRoot\system32\DRIVERS\ISCTD64.sys
    Image name: ISCTD64.sys
    Timestamp:        [COLOR="red"]Tue Nov 27 19:52:34 2012[/COLOR] (50B51A02)
    CheckSum:         00016374
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Newtype]

The driver responsible appears to be linked with your Intel Smart Technology Driver.

An update might help but for the time being I suggest removing it.
Especially if it's unnecessary.

If you must update it then please go here.

Support for the Intel® Smart Connect Technology

Unable to load image \SystemRoot\system32\DRIVERS\ISCTD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ISCTD64.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]ISCTD64.sys[/COLOR]

fffff880`043ca000 fffff880`043db000   ISCTD64  T (no symbols)           
    Loaded symbol image file: ISCTD64.sys
    Image path: \SystemRoot\system32\DRIVERS\ISCTD64.sys
    Image name: ISCTD64.sys
    Timestamp:        [COLOR="red"]Tue Nov 27 19:52:34 2012[/COLOR] (50B51A02)
    CheckSum:         00016374
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Was this from my most recent dump file? I don't see Intel Smart Connect under the list of programs I can uninstall and I don't believe I installed it again after reinstalling Windows

 

[Thedoctor44]

I'm on a lot of threads so I can't say to be honest.

Can you please enable Driver Verifier by follow these instructions.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Newtype]

I'm on a lot of threads so I can't say to be honest.

Can you please enable Driver Verifier by follow these instructions.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier is enabled currently, I think I had it on for my last dump file as well. That's the only one in the thread I've had it enabled for though, still waiting for my next BSOD to upload it here.

Apologies if I'm wrong and it wasn't enabled for that one though, but I believe it was.