Windows 10 BSOD only when streaming?

  • Thread starter Thread starter Achi1
  • Start date Start date
A

Achi1

Hi,


I've been having issues with streaming on my newly built pc for the past week. My streams can last varying from 15 mins-3 hours. I don't have any issues when only playing games, just when playing and streaming at the same time. Specifically I've been trying to play Genshin Impact and stream with Streamlabs OBS.


Things I've attempted already:

Updating my device drivers (Still had issues when updating my intel wireless driver, so I rolled back to a previous version. Stream lasted longer than usual to around ~3 hrs after rolling back to a previous version though I don't know if that's just a coincidence). I've also connected via ethernet cable+power adapter previously and stream would still crash

Updated my gpu drivers

Resetting windows 10 and uninstalled my virus software

Memtest on ram (0 errors noted)

sfc /scannow

Removed my capture card and pcie extension to remove as possible source of crashing

Windows memory diagnostic

Disabled fast startup

Tried to play Genshin Impact in Windows Mode and stream with lower settings (still crashed lol)



I have not overclocked my pc

System information:

Windows version: Windows 10, 10.0, version 2009, build: 19042
Hardware: MS-7C87, Micro-Star International Co., Ltd., B450M BAZOOKA MAX WIFI (MS-7C87)
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 17126584320 bytes (16.0GB)

Not an overheating issue, max temp it hits when streaming/gaming is 65 degrees but mainly around mid 50s-low 60s




Current Streamlab OBS settings: (Stream lasted for 3 hours on these settings)

Stream -

Encoder: Hardware (NVENC) (new)

Rate Control: CBR

Bitrate: 5000

Keyframe interval: 2

Preset: Quality

Profile: high

Look-ahead: off

Psycho visual tuning: on

GPU: 0

Max B-frames: 2


Video -

Base (Canvas) Resolution: 1920x1080

Output (Scaled) Resolution: 1280x720

Downscale Filter: Bicubic (Sharpened scaling, 16 samples)

FPS type: Common FPS Values

Common FPS Values: 60


WhoCrashed analysis:

On Fri 2020-11-06 7:38:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ndu.sys (Ndu+0x6D7C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80659BFC4D7, 0xFFFFF18F735B6F28, 0xFFFFA681154D2920)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a 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 Fri 2020-11-06 1:28:47 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110620-5953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8021D1FC4D7, 0xFFFF8C8C8CABCE78, 0xFFFFC401BEBAD920)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 2020-11-06 7:38:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110620-5500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80659BFC4D7, 0xFFFFF18F735B6F28, 0xFFFFA681154D2920)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Mini dump files zipped up here:



Any help would be greatly appreciated!! It's been so frustrating trying to troubleshoot ): Not sure if at this point I should try to replace my hardware one by one and see if that would help?

Continue reading...
 

Similar threads

C
Replies
0
Views
2
Cristian Chavez4
C
K
Replies
0
Views
1
Keed Laranga
K
S
Replies
0
Views
17
SadiqKasumi
S
Back
Top