hey everyone been having some issues with either some driver or program interfering with my obs and any multiplayer game to the point where i can even use facebook video chat at some times. here is the log from studio from my latest try and i also included the crash reports when my pc BSOD while streaming. thanks in advance!
https://gist.github.com/68d3233b28aa8c4fdf349517cbb447cf
CRASH REPORTS
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/9/2017 8:48:05 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030917-6328-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x107D6)
Bugcheck code: 0xD1 (0xFE3E57AE, 0x2, 0x1, 0xFFFFF80197C807D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/9/2017 8:42:58 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030917-5921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC00E4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802680D70E4, 0xFFFFE5016224D5C8, 0xFFFFE5016224CDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/9/2017 3:59:35 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030917-5656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002C54D0E4, 0xFFFFCF01B916CFB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/8/2017 12:28:57 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030817-6453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x162 (0xFFFFAB02A6CD3080, 0xFFFFF8033BB3BD68, 0xFFFFFFFF, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/5/2017 11:58:42 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030517-6890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC00E4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801395440E4, 0xFFFF9A009D24D5C8, 0xFFFF9A009D24CDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
https://gist.github.com/68d3233b28aa8c4fdf349517cbb447cf
CRASH REPORTS
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/9/2017 8:48:05 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030917-6328-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x107D6)
Bugcheck code: 0xD1 (0xFE3E57AE, 0x2, 0x1, 0xFFFFF80197C807D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/9/2017 8:42:58 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030917-5921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC00E4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802680D70E4, 0xFFFFE5016224D5C8, 0xFFFFE5016224CDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/9/2017 3:59:35 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030917-5656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002C54D0E4, 0xFFFFCF01B916CFB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/8/2017 12:28:57 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030817-6453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x162 (0xFFFFAB02A6CD3080, 0xFFFFF8033BB3BD68, 0xFFFFFFFF, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 3/5/2017 11:58:42 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030517-6890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC00E4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801395440E4, 0xFFFF9A009D24D5C8, 0xFFFF9A009D24CDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
