Question Getting a dxgmms2.sys BSOD in the same software on Windows 11 ?

Mar 24, 2025
4
0
10
Hi. I'm getting the same BSODs in the same software - Davinci Resolve - in Windows 11 24H2.
i7-14700K, RTX 4080, 65GB of RAM (XMP 5600). Latest BIOS

First of all there's no overheating or errors - I tested my rig everywhere. OCCT, Cinebench, Prime95, MemTest, Windows memory test, AIDA, Superposition and others. Max CPU temp - 84, max GPU temp - 74. In games they both hardly hit 65. In pro software like Premiere Pro, After Effects, Topaz Video AI, Shutter Encoder, different AI-plugins - everywhere everything is fine. But not in Davinci Resolve.
- to reproduce the issue, create an empty timeline (1920x1080), place a video on it, turn on NVidia SuperScale x4, turn on and analyze Lens correction. Place the playhead over the video and move it back and forth. It may happen instantaneously, in 5 seconds or in some minutes.

  • when it happens, it's always a dxgmms2.sys bsod
  • it happens with any material and any codec
  • it happens with 570.xx and 566.xx drivers
  • it happens with new and older iGPU drivers
  • it happens with the iGPU turned off (in the device manager which is = in Bios)
  • it happens both with & without third-party plugins used in the project, even with an unedited video.
  • it happens with XMP and CPU downvolting as well as BIOS set to defaults
  • it happens with all the non-Windows processes turned off on load
  • it happens only in Davinci Resolve.
  • didn't happen when SuperScaling was not used, but I'd worked in DR for 2 weeks (12 short videos made), so this one is not 100%.

One could say "It's Davinci Resolve's fault", but the guys in Backmagic community and techs on Reddit say it's a hardware or software issue and DR has nothing to do with it.

I sent bug reports to:
  • Blackmagic - no response
  • Nvidia - suggested workarounds none of which helped (DDU, Disable Hardware Accelerated GPU scheduling in Windows, set Nvidia settings to forced 4080 in Cuda, OpenGL and max powerplan, turn off services in MSCONFIG > Services).
  • Palit (my card's vendor) - "we don't make drivers, ask NVidia"
  • Microsoft - no respose. MS community: "try older drivers"

I'm out of ideas. Need assistance.

How it happens: https://drive.google.com/file/d/16I41ftnOEUbpAkq6lsRyUKXy0Eb028eH/view
My logs: https://drive.google.com/drive/folders/1vOwug6Xf1TUOhQSoV0Tc4WVFg9J97OfN
There are more but they are all the same.
 
Last edited:
Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some error code, warning, or even and informational event just before or at the time of the BSODs

Reliability History is end user friendly and the timeline format may reveal some pattern.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Both tools support clicking to obtain more details. The details may or may not be helpful.
 
try 551 drivers

try nvidia studio drivers
try game ready drivers

reinstall davinci

uninstall windows update 24H2
  • it happens with 570.xx and 566.xx drivers - this includes both, GR and Studio drivers. Tried reinstalling DR too. You suggested the most obvious solutions I tried first. I cannot reinstall Win for now because of lots of projects going, but I'll do that too in some time, though I'm not sure if it helps.
 
Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some error code, warning, or even and informational event just before or at the time of the BSODs

Reliability History is end user friendly and the timeline format may reveal some pattern.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Both tools support clicking to obtain more details. The details may or may not be helpful.
https://ibb.co/VWhH0hpS The event viewer shows the same - just an error in this sys file and the following restart
 
Possibly a corrupted or buggy DirectX file.

Try running the built in Windows troubleshooters. The troubleshooters may find and fix something.

Then run "dism" and "sfc /scannow".

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161


If you install or reinstall other drivers do so directly via the applicable manufacturer's website.

Manually download, install, and configure - no third party tools or installers.

Also be sure that the source website is actually that of the manufacturer. Just because the manufacturer's name or product model number, etc. appears in the URL does not mean that the website is the manufacturer.
 
Reinstalling Windows with a minimum of software installed (Adobe package, browser, shutter encoder, no antivirus or other software at all) didn't help.