F5F Stay Refreshed Software Operating Systems The BSOD occurred due to an OBS crash.

The BSOD occurred due to an OBS crash.

The BSOD occurred due to an OBS crash.

A
Alex__Pro
Member
51
02-14-2026, 08:41 PM
#1
Exciting times ahead.
Yesterday afternoon started with OBS showing bluescreen errors. The message reads SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and points to dxgmms2.sys. These issues pop up unexpectedly while OBS is running, but they tend to happen more often when another demanding program is active—like GIMP, which is my primary image editor.

So far I’ve tried:
- Restoring to an older version of OBS (but no improvement).
- Contacting OBS Support; they noted two crashes with a specific code (0xc0000409) and mentioned possible plugin issues.
- Running memory checks (memtest), which confirmed no corruption.
- Using DDU to clear graphics drivers, though reinstalling didn’t resolve the problem.
- Testing other graphically heavy processes (e.g., games) to see if they trigger the same crash.

I haven’t tried anything else yet, just to confirm if other intense tasks cause a similar failure. I’ve reviewed several forum threads about BSODs and now have my own findings. If you can help, it would be greatly appreciated. Thank you.
A
Alex__Pro
02-14-2026, 08:41 PM #1

Exciting times ahead.
Yesterday afternoon started with OBS showing bluescreen errors. The message reads SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and points to dxgmms2.sys. These issues pop up unexpectedly while OBS is running, but they tend to happen more often when another demanding program is active—like GIMP, which is my primary image editor.

So far I’ve tried:
- Restoring to an older version of OBS (but no improvement).
- Contacting OBS Support; they noted two crashes with a specific code (0xc0000409) and mentioned possible plugin issues.
- Running memory checks (memtest), which confirmed no corruption.
- Using DDU to clear graphics drivers, though reinstalling didn’t resolve the problem.
- Testing other graphically heavy processes (e.g., games) to see if they trigger the same crash.

I haven’t tried anything else yet, just to confirm if other intense tasks cause a similar failure. I’ve reviewed several forum threads about BSODs and now have my own findings. If you can help, it would be greatly appreciated. Thank you.

A
Alterfuse
Member
67
02-14-2026, 08:41 PM
#2
When updating your BIOS, it's important to stay current with the AMD AGESA microcode, particularly if you encounter issues. Since there have been five AGESA updates since your BIOS version, updating should be your first priority.
A
Alterfuse
02-14-2026, 08:41 PM #2

When updating your BIOS, it's important to stay current with the AMD AGESA microcode, particularly if you encounter issues. Since there have been five AGESA updates since your BIOS version, updating should be your first priority.

M
Marinehobo
Member
63
02-14-2026, 08:41 PM
#3
Welcome to the forums, newcomer! Here are the details of your build in the requested format:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:

Please include the age of the PSU along with its make and model. Also, provide the current BIOS version for your motherboard.

You can check memory usage by opening Task Manager and viewing processes under vmmem.
M
Marinehobo
02-14-2026, 08:41 PM #3

Welcome to the forums, newcomer! Here are the details of your build in the requested format:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:

Please include the age of the PSU along with its make and model. Also, provide the current BIOS version for your motherboard.

You can check memory usage by opening Task Manager and viewing processes under vmmem.

I
iDoNotEvenLift
Posting Freak
936
02-14-2026, 08:41 PM
#4
CPU: AMD Ryzen 7 2700X 3.7 GHz 8-Core
CPU cooler: AMD Wraith (included with CPU, thermal paste refreshed mid-2025)
Motherboard: MSI X470 GAMING PRO ATX AM4
Memory: (2x) Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 CL15
Storage: Multiple drives. Windows is installed on Samsung 970 Evo 500 GB M.2-2280 PCIe 3.0 X4 NVME
GPU: Zotac AMP GeForce GTX 1080 8 GB
Power Supply: EVGA SuperNOVA 650 G2 650 W 80+ Gold
Case: NZXT Phantom ATX Full Tower
Operating System: Windows 10 Pro (ESU active)
Display: (2x) Samsung Odyssey G5 C27G55TQWN
Power supply has been in use since the PC's inception. Roughly from 2017 to 2018. It consistently stays within normal power consumption limits. BIOS version 1.F0 (UEFI format)
EDIT: Upon first launching OBS, vmmem appeared briefly before terminating. Usage data was recorded during its operation. Thank you for the friendly introduction!
This build details were gathered from PCPartPicker.
I
iDoNotEvenLift
02-14-2026, 08:41 PM #4

CPU: AMD Ryzen 7 2700X 3.7 GHz 8-Core
CPU cooler: AMD Wraith (included with CPU, thermal paste refreshed mid-2025)
Motherboard: MSI X470 GAMING PRO ATX AM4
Memory: (2x) Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 CL15
Storage: Multiple drives. Windows is installed on Samsung 970 Evo 500 GB M.2-2280 PCIe 3.0 X4 NVME
GPU: Zotac AMP GeForce GTX 1080 8 GB
Power Supply: EVGA SuperNOVA 650 G2 650 W 80+ Gold
Case: NZXT Phantom ATX Full Tower
Operating System: Windows 10 Pro (ESU active)
Display: (2x) Samsung Odyssey G5 C27G55TQWN
Power supply has been in use since the PC's inception. Roughly from 2017 to 2018. It consistently stays within normal power consumption limits. BIOS version 1.F0 (UEFI format)
EDIT: Upon first launching OBS, vmmem appeared briefly before terminating. Usage data was recorded during its operation. Thank you for the friendly introduction!
This build details were gathered from PCPartPicker.

J
JosephGamez
Member
141
02-14-2026, 08:41 PM
#5
After first launching and stopping OBS, vmmem appeared briefly before closing completely. If you have a spare drive, consider reinstalling the OS offline on that drive while disconnecting all other drives to check if the problem persists. If it doesn’t occur, the issue likely lies with the existing OS on your original drive. Using WinDBG, I found vmmem among the failing modules.

Curious about the RAM kits, were they purchased simultaneously or spaced out over time? If they were bought months or years apart, please share images of the PCB versions for both kits.

BIOS version 1.F0 (UEFI)
https://www.msi.com/Motherboard/X470-GAMING-PRO/support

According to your motherboard’s support page, your BIOS is awaiting an update. Ensure you’re using the latest chipset drivers from AMD’s support site and then flash the BIOS to version 7B79v1L7 (beta).
J
JosephGamez
02-14-2026, 08:41 PM #5

After first launching and stopping OBS, vmmem appeared briefly before closing completely. If you have a spare drive, consider reinstalling the OS offline on that drive while disconnecting all other drives to check if the problem persists. If it doesn’t occur, the issue likely lies with the existing OS on your original drive. Using WinDBG, I found vmmem among the failing modules.

Curious about the RAM kits, were they purchased simultaneously or spaced out over time? If they were bought months or years apart, please share images of the PCB versions for both kits.

BIOS version 1.F0 (UEFI)
https://www.msi.com/Motherboard/X470-GAMING-PRO/support

According to your motherboard’s support page, your BIOS is awaiting an update. Ensure you’re using the latest chipset drivers from AMD’s support site and then flash the BIOS to version 7B79v1L7 (beta).

B
bushminecraft
Member
189
02-14-2026, 08:41 PM
#6
Sorry, I currently lack a second drive that supports an OS install. The other SSD in this build is running Fedora KDE (which isn’t compatible), and the two HDDs are set up for specific uses. I’m wondering if OBS might have triggered virtual memory issues without any active recording or streaming. If the OS installation itself became corrupted—making SFC unable to detect and fix it—I really don’t have much time left. I’d probably need a few days to gather everything and do a soft reinstall. I should open her up to retrieve PCB version labels, but I no longer have original packaging. The second set of 2x8GB was purchased last year, and I made sure they matched the first model. If you really need those images, I can send them over in about a week once I install a new case fan I just bought. I’m not sure how I feel about flashing the BIOS to a beta version, but I’ll go for the latest stable release (1K) as soon as possible and then decide next steps. Given that my hardware is getting older, I hope you can understand my reluctance at the moment.
B
bushminecraft
02-14-2026, 08:41 PM #6

Sorry, I currently lack a second drive that supports an OS install. The other SSD in this build is running Fedora KDE (which isn’t compatible), and the two HDDs are set up for specific uses. I’m wondering if OBS might have triggered virtual memory issues without any active recording or streaming. If the OS installation itself became corrupted—making SFC unable to detect and fix it—I really don’t have much time left. I’d probably need a few days to gather everything and do a soft reinstall. I should open her up to retrieve PCB version labels, but I no longer have original packaging. The second set of 2x8GB was purchased last year, and I made sure they matched the first model. If you really need those images, I can send them over in about a week once I install a new case fan I just bought. I’m not sure how I feel about flashing the BIOS to a beta version, but I’ll go for the latest stable release (1K) as soon as possible and then decide next steps. Given that my hardware is getting older, I hope you can understand my reluctance at the moment.

S
Sneakyginger8
Senior Member
580
02-14-2026, 08:41 PM
#7
As previously mentioned about updating your BIOS, keeping up with the AMD AGESA microcode is crucial, particularly when encountering issues. Since five AGESA updates have been released since your current BIOS version, performing a BIOS update should be the initial step.

In the dumps, which are largely identical, we can observe the actual failure in the context record...
S
Sneakyginger8
02-14-2026, 08:41 PM #7

As previously mentioned about updating your BIOS, keeping up with the AMD AGESA microcode is crucial, particularly when encountering issues. Since five AGESA updates have been released since your current BIOS version, performing a BIOS update should be the initial step.

In the dumps, which are largely identical, we can observe the actual failure in the context record...

1
111carys111
Posting Freak
832
02-14-2026, 08:41 PM
#8
I understand the explanation you're looking at. I have some questions about it, but I'll investigate further when possible. Right now I'm using 1K and plan to leave my computer running with OBS open overnight to check if the issue recurs after the BIOS update. Your advice was helpful.
1
111carys111
02-14-2026, 08:41 PM #8

I understand the explanation you're looking at. I have some questions about it, but I'll investigate further when possible. Right now I'm using 1K and plan to leave my computer running with OBS open overnight to check if the issue recurs after the BIOS update. Your advice was helpful.

L
livtheviking
Posting Freak
846
02-14-2026, 08:41 PM
#9
Bluescreens are now under control, even though OBS continues to crash for other issues. Appreciate everyone's help.
L
livtheviking
02-14-2026, 08:41 PM #9

Bluescreens are now under control, even though OBS continues to crash for other issues. Appreciate everyone's help.