[SOLVED] Computer is BSOD during streaming. BUGCODE_USB_DRIVER

[Savvii6]

So I've been trying to help a buddy out with fixing his computer for maybe around a week now and I've reached a point of being completely stumped.
Currently, the PC only blue screens whenever he tries to steam off of OBS, but during normal usage. It's happened consistently whenever he tries to stream, usually within 1/2 hour of starting.

His current computer build is
MSI 970 Gaming MOBO
24 GB RAM G.Skills Ripjaw
Ryzen 370 Graphics Card
Corsair CX430 Power Supply
AMD FX 8320e CPU
And a Cooler Master Hyper 212 CPU cooler.

Now I tried looking up the error it was spitting out, the BUGCODE_USB_DRIVER and we tried a fair deal of the solutions that it gave.
Namely trying to update drivers (through SDI), unplugging the webcam, and trying to play around with the settings.
It's still happening, however.
Now, I've never dealt with reading dump files before, so I'm extremely green when it comes to understanding it. I would appreciate it immensely if someone could spotcheck me and help point me in the right direction.

From my understanding of it, it seems to me that we need to update his USB drivers?

Again, thanks, and let me know if I missed anything that would help you guys better understand.

Here's the crash analysis I got from OSR:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff8057dc02000 PsLoadedModuleList = 0xfffff8057e01d9f0
Debug session time: Thu Mar 14 14:04:06.114 2019 (UTC - 4:00)
System Uptime: 0 days 3:18:54.937
***

• *
• Bugcheck Analysis *
• *

***

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000002, BAD_URB The USB client driver has submitted a URB that is
still attached to another IRP still pending in the bus
driver.
Arg2: ffff858cb1b80d00, Address of pending IRP.
Arg3: ffff858cb5e89010, Address of IRP passed in.
Arg4: ffff82045ad723e0, Address URB that caused the error.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

HARDWARE_VENDOR_ID: VID1002

HARDWARE_DEVICE_ID: PID4396

HARDWARE_SUBSYS_ID: REV00

HARDWARE_ID: VID1002_PID4396

IRP_ADDRESS: ffff858cb1b80d00

DEVICE_OBJECT: ffff858cac593050

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: obs64.exe

CURRENT_IRQL: 2

BAD_PAGES_DETECTED: df58

LAST_CONTROL_TRANSFER: from fffff8058761d3db to fffff8057ddb55e0

STACK_TEXT:
ffff82045ad72048 fffff8058761d3db : 00000000000000fe 0000000000000002 ffff858cb1b80d00 ffff858cb5e89010 : nt!KeBugCheckEx
ffff82045ad72050 fffff805876058f4 : ffff858cb5e89010 ffff858cac5931a0 ffff858cb5e89010 fffff8057dcbba74 : USBPORT!USBPORT_ProcessURB+0x177ab
ffff82045ad721b0 fffff8057dcba0d9 : ffff858cacb9b000 0000000000220003 0000000000000000 ffff858cacb9b060 : USBPORT!USBPORT_Dispatch+0x1d4
ffff82045ad72210 fffff805877c6981 : 0000000000220003 ffff858cacb9b060 ffff858cb5e89010 fffff8057dd2e91c : nt!IofCallDriver+0x59
ffff82045ad72250 fffff805877cb013 : ffff8204496f3034 fffff8054f494449 ffff858cacb9b060 ffff858cb5e89010 : usbhub!UsbhPdoInternalDeviceControl+0x1f1
ffff82045ad722c0 fffff8057dcba0d9 : 0000000000000000 0000000000000000 0000000000000701 ffff82045ad72390 : usbhub!UsbhGenDispatch+0x43
ffff82045ad722f0 fffff805853652ac : 00000000000000c8 fffff80500000005 ffff858cb16b0520 fffff8057dcbbd87 : nt!IofCallDriver+0x59
ffff82045ad72330 00000000000000c8 : fffff80500000005 ffff858cb16b0520 fffff8057dcbbd87 0000000000000000 : ElgatoGC658+0x52ac
ffff82045ad72338 fffff80500000005 : ffff858cb16b0520 fffff8057dcbbd87 0000000000000000 0000000000000000 : 0xc8
ffff82045ad72340 ffff858cb16b0520 : fffff8057dcbbd87 0000000000000000 0000000000000000 ffff97819c680101 : 0xfffff80500000005 ffff82045ad72348 fffff8057dcbbd87 : 0000000000000000 0000000000000000 ffff97819c680101 ffff82045ad72390 : 0xffff858cb16b0520
ffff82045ad72350 ffff858cb1dca6d8 : 000000005a060000 ffff82045ad72398 ffff82045ad72398 0000000000020032 : nt!IopFreeIrp+0x107
ffff82045ad72390 000000005a060000 : ffff82045ad72398 ffff82045ad72398 0000000000020032 ffff858ca5961610 : 0xffff858cb1dca6d8 ffff82045ad72398 ffff82045ad72398 : ffff82045ad72398 0000000000020032 ffff858ca5961610 fffff805853653c5 : 0x5a060000 ffff82045ad723a0 ffff82045ad72398 : 0000000000020032 ffff858ca5961610 fffff805853653c5 0000000000000000 : 0xffff82045ad72398
ffff82045ad723a8 0000000000020032 : ffff858ca5961610 fffff805853653c5 0000000000000000 fffff8057dd1a200 : 0xffff82045ad72398 ffff82045ad723b0 ffff858ca5961610 : fffff805853653c5 0000000000000000 fffff8057dd1a200 ffff858cb1dca4a0 : 0x20032 ffff82045ad723b8 fffff805853653c5 : 0000000000000000 fffff8057dd1a200 ffff858cb1dca4a0 ffff858c7070534b : 0xffff858ca5961610
ffff82045ad723c0 0000000000000000 : fffff8057dd1a200 ffff858cb1dca4a0 ffff858c7070534b 0000000000170088 : ElgatoGC658+0x53c5


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

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

*** Memory manager detected 57176 instance(s) of page corruption, target is likely to have memory corruption.

Just in case, here's the actual file, if it's needed: http://www.mediafire.com/file/ddggbi3y0ggyqqq/031419-26687-01.dmp

 

[Andrei N]

you are describing a memory corruption.
The system description that you provided is also very unclear.

MSI 970 Gaming MOBO - has 4 slots of RAM
24 GB RAM G.Skills Ripjaw - is made of 6 sticks of 4 GB each.
Ryzen 370 Graphics Card - sensible chuckle here.

Now you should start by checking the RAM DIMMS and make sure they are the same. You can use CPU-z for this.
After that try a memtest and check from there.

Also event viewer should show some insights into the issue.

 

[Savvii6]

My apologies on the description, I was doing it from memory. Perhaps I'm the one with memory corruption.
The 24 GB of RAM are split into 2 sticks of 8GB and 2 sticks of 4GB. Both pairs came in a paired set when they were ordered. They are all DDR3, which I think is what you mean by the DIMMS, correct?
The GPU is an AMD Radeon R9 360 that was pulled from his old pre-built computer.

As far as event viewer, what should I be looking for in particular? Should I focus on the system logs or the application logs? And alongside that, should I focus of the error entries, or would I get some insight from the information entries as well?

 

[Andrei N]

So let's start from the beginning: The R9 360 barely passes a gaming benchmark and is barely capable of both gaming and streaming, considering you use CPU compression in OBS - this alone can be a starting cause.
Next, DDR3 memory is more sensible to imbalances than DDR2, also DDR4 is more sensible than DDR3. Some people might argue that the memory does not matter, only the MB's capability of balancing the memories.
For this I would strongly suggest to start off with a single stick of RAM (8GB, in the first slot) and try to recreate the issue. Then move on to 16 GB and then adding the fours together. If the RAM speeds and timings match perfectly you could go 8 -> 12 ->24 but I still suggest 8->16->24.
In the event viewer you go for system and try to match the times of the BSOD to the times inside event viewer, very easy to do after it just happened and you jump in event viewer - > winodws logs -> system

 

[Savvii6]

So, I've just finished working on it with him to try again.

I should clarify that his streaming setup is to use an Elgato HD capture card that transfers it to the OBS. We haven't tried to both run games and stream from the same PC, mostly because we saw how taxing it can be on the system. He instead runs the games on console.

The memory test didn't show any errors from the RAM. I tried to recreate the blue screen with the 8 gigs, then 16, and then the 24, and it blue screened each time.
A little aside, this issue has only happened when we tried to stream. Recording did not cause any issues and it doesn't blue screen during normal non-OBS use.

I updated the MSI drivers that were provided on the manufacturer's website and I also updated the BIOS to the newest version that was provided.

I pulled the last 2 minidumps and tried reading them using nirsoft's bluescreenview. One had the "caused by driver" marked as "USBPORT.SYS", the other had USBPORT.sys and another error called "ntoskrnl.exe".

I also pulled the log from OBS from the last time it blue screened.

Here's the first Minidump I got: https://www.mediafire.com/file/d8cmcukokdudcbm/031519-29390-01.dmp/file

This was the second one: https://www.mediafire.com/file/azcc2zm5bva7yyq/031519-24781-01.dmp/file

And this is the OBS log: https://www.mediafire.com/file/j4r4nhrw4i4ro7v/2019-03-15_15-35-40.txt/file

Looking at it, would it be logical to think that the blue screen is being caused by some type of USB driver?

Honestly, I have a very limited knowledge about this type of thing, so I'm very appreciative for the help I've received so far.

 

[gardenman]

Update this driver if possible:

Nov 05 2015

ElgatoGC658.sys

AVSTREAM driver (Elgato Systems)

It was mentioned in all 3 dump files along with OBS. Usually software (OBS) isn't the problem. It's either hardware (Elgato or something else) or drivers (Elgato or something else).

If the driver update doesn't help, and if the Elgato is an external device, try going without it if possible and see if the crashes stop.

A few lines from the dump file:

BugCheck FE, {2, ffffaf82233b77b0, ffffaf822d90c010, fffffe87729ca3e0}

*** WARNING: Unable to verify timestamp for ElgatoGC658.sys

*** ERROR: Module load completed but symbols could not be loaded for ElgatoGC658.sys

Probably caused by : ElgatoGC658.sys ( ElgatoGC658+52ac )

PROCESS_NAME:  obs64.exe

 

[Savvii6]

Very happy to return with the issue being fixed.
We updated the Elgato's driver and the software itself. We also switch the USB slot it was in.
Doing those few things allowed us to run the stream without any blue screens.

Thanks for the help!