Frequent BSOD's, ntoskrnl and usb drivers

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.

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.

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.

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.

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.

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.

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

Driver Verifier - Enable and Disable

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.

System Restore Point - Create

Code:

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

Probably caused by : svhost.exe

Followup: MachineOwner

Code:

PROCESS_OBJECT: fffffa800f2cdb30

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: svhost

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

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.