BSOD (KMODE_EXCEPTION_NOT_HANDLED) while streaming

J

jrl818

New Member
hey all, i recently built my first gaming pc (with help of a knowledgeable friend). every time i try to stream, whether it’s X-split, SLOBS, or Twitch Studio, it causes a BSOD with a kmode exception not handled code. i’ve tried troubleshooting steps microsoft recommended, but nothing has worked. here’s my specs:
CPU- AMD Ryzen 7 3700x
MOTHERBOARD- MSI MAG Tomahawk ATX AM4 B550
MEMORY- G.Skill Trident Z RGB 16GB STORAGE- (SSD)Samsung 970 EVO 500GB M.2-2280 NVME
(Hard Drive) Seagate Barracuda Compute 2TB 7200RPM
GRAPHICS CARD- EVGA GeForce RTX 2070 Super 8GB XC Ultra
POWER SUPPLY- Corsair RM 750w 80+ Gold Certified Fully Modular ATX
 
R

R1CH

Forum Admin
Developer
BSODs generally indicate unstable hardware or drivers and aren't a result of a specific program.
 
H

hwarning

New Member
The expert is wrong here - these crashes are with OBS and SLOBS and the memory dumps clearly show an error in the direction of the control of the hardware encoder.
 
H

hwarning

New Member
Thank you for the nice tips. I'll stick to the Windows technical reference on page 1460 (German edition). According to poolmon.exe (Windows Driver Kit), cuda64 will probably overflow the core stack. It can be assumed that the memory is not released correctly in the course of the stream.
Therefore, a test with the Windows Hardware Labor Kit was carried out on the system in question, which did not reveal any problems. According to support from NVIDIA, a test of the CUDA system was performed. The direct stream with NVDIA went smoothly.
In addition, with SLOBS Vers. 0.25 (including the files from OBS from October 27th, 2020) no more crashes occur when using the "Hardware (NVENC)" encoder. Poolmon.exe also no longer displays errors.
 
gmesmer

gmesmer

New Member
hwarning said:
Thank you for the nice tips. I'll stick to the Windows technical reference on page 1460 (German edition). According to poolmon.exe (Windows Driver Kit), cuda64 will probably overflow the core stack. It can be assumed that the memory is not released correctly in the course of the stream.
Therefore, a test with the Windows Hardware Labor Kit was carried out on the system in question, which did not reveal any problems. According to support from NVIDIA, a test of the CUDA system was performed. The direct stream with NVDIA went smoothly.
In addition, with SLOBS Vers. 0.25 (including the files from OBS from October 27th, 2020) no more crashes occur when using the "Hardware (NVENC)" encoder. Poolmon.exe also no longer displays errors.
Click to expand...
could you go into more detail as to which versions of release version of OBS and which release version of SLOBS seem to not have the bug?
 
You must log in or register to reply here.
Top