Freeze for ~1 minute into BSOD DPC_WATCHDOG_VIOLATION when playing 3D Games

exodunes · Nov 25, 2023

Hey there,

So I've been getting these freezes that last for about a minute and then go straight into a bluescreen when playing any 3D game. The game in question right now is House Flipper, but I've also tried Little Big Workshop which had the same issue.

Funnily enough, when playing a 2D Game like The Binding of Isaac, it doesn't happen.

The following steps were already taken:

Memtest
sfc /scannow
chkdsk
Defragmented my drive
BIOS Update
Uninstalled all MSI Center applications
GPU Driver update
- After using DDU to uninstall it
Intel GPU Driver update
- After using DDU to uninstall it
Turned off Intel GPU via Device Manager
Reinstalled Windows 11 after formatting my hard drive
Installed Various Intel drivers that MSI recommended
Deactivated Intel ME Engine
Checked my computer for viruses both before and after formatting

None of the above steps seem to have helped.

Here's a link to the Google Drive folder where the V2 Logs are:
Google Drive Link

If there's any more info you need, please do ask.

Thanks!

ubuysa · Nov 25, 2023

We need the full kernel dump for that particular bugcheck, it's the file C:\Windows\Memory.dmp and it will be large. Please upload that with a link to it here.

All the dumps point at nvlddmkm.sys but it's important to see the full kernel dump before making any kind of reliable diagnosis.

BTW. Before you post another V2 log please change your system language to English, it's not possible for us to read your logs unless they are in English.

exodunes · Nov 25, 2023

ubuysa said:
We need the full kernel dump for that particular bugcheck, it's the file C:\Windows\Memory.dmp and it will be large. Please upload that with a link to it here.

All the dumps point at nvlddmkm.sys but it's important to see the full kernel dump before making any kind of reliable diagnosis.

BTW. Before you post another V2 log please change your system language to English, it's not possible for us to read your logs unless they are in English.

Okay, sorry for the German Language. This is my wife's computer.

Now, regarding the Memory.dmp, I'll have to cause a crash again before I can give you that since my setting was set to Small Memory Dump. At least I think that's what that would say in English.

Will come back to you in a few hours, I'd guess.

Thanks though!

exodunes · Nov 25, 2023

ubuysa said:
We need the full kernel dump for that particular bugcheck, it's the file C:\Windows\Memory.dmp and it will be large. Please upload that with a link to it here.

All the dumps point at nvlddmkm.sys but it's important to see the full kernel dump before making any kind of reliable diagnosis.

BTW. Before you post another V2 log please change your system language to English, it's not possible for us to read your logs unless they are in English.

That crash came faster than I expected this time.

Here's the link:
Link to Memory.dmp

If the language is still an issue, it won't be a problem changing the system language for the time being and waiting for another crash.

Thanks in advance!

zbook · Nov 26, 2023

The log files were in a foreign language and could not be scanned.

Please temporarily use English as the default language during the troubleshooting.

Ten Forums - Windows 10 Help and Support Forum

Windows 10 troubleshooting help and support forum, plus thousands of tutorials to help you fix, customize and get the most from Microsoft Windows 10.

www.tenforums.com

Change Display Language in Windows 10

How to Change Display Language in Windows 10

www.tenforums.com

Run:

a) V2

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

b) Tuneup plus:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Uninstall and reinstall:
a) nvlddmkm.sys
b) igdkmdn64.sys

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

www.nvidia.com

Download Intel Drivers and Software

Download new and previously released drivers including support software, bios, utilities, firmware and patches for Intel products.

www.intel.com

Support for Intel® Graphics

Find support information, product highlights, featured content, downloads, and more for Intel® Graphics.

www.intel.com

For driver reinstallation whenever possible install drivers displayed on the computer or motherboard manufacturer websites.

Code:

Name    Intel(R) UHD Graphics
PNP-Gerätekennung    PCI\VEN_8086&DEV_46A3&SUBSYS_13C71462&REV_0C\3&11583659&0&10
Adaptertyp    Intel(R) UHD Graphics Family, Intel Corporation-kompatibel
Adapterbeschreibung    Intel(R) UHD Graphics
Adapter-RAM    1,00 GB (1.073.741.824 Bytes)
Installierte Treiber    <>,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5b1252b3763da959\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5b1252b3763da959\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5b1252b3763da959\igd12umd64.dll
Treiberversion    31.0.101.4255
INF-Datei    oem26.inf (Abschnitt iADLPD_w10_DS)
Treiber    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_5B1252B3763DA959\IGDKMDN64.SYS (31.0.101.4255, 50,11 MB (52.542.408 Bytes), 22.11.2023 20:17)
   
Name    NVIDIA GeForce RTX 4060 Laptop GPU
PNP-Gerätekennung    PCI\VEN_10DE&DEV_28A0&SUBSYS_13C81462&REV_A1\4&217FF2CC&0&0008
Adaptertyp    NVIDIA GeForce RTX 4060 Laptop GPU, NVIDIA-kompatibel
Adapterbeschreibung    NVIDIA GeForce RTX 4060 Laptop GPU
Adapter-RAM    (1.048.576) Bytes
Installierte Treiber    C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_a29eb0fbdc950996\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_a29eb0fbdc950996\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_a29eb0fbdc950996\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_a29eb0fbdc950996\nvldumdx.dll
Treiberversion    31.0.15.2892
INF-Datei    oem6.inf (Abschnitt Section235)
Treiber    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVMI.INF_AMD64_A29EB0FBDC950996\NVLDDMKM.SYS (31.0.15.2892, 55,40 MB (58.091.520 Bytes), 22.11.2023 20:11)

ubuysa · Nov 26, 2023

The reason for asking for the kernel dump is because this particular variant of the 0x133 bugcheck (with argument 1 set to 1) was caused by a collection of DPCs running for too long. A minidump only contains the data structures for the failing processor but for this bugcheck we need to see the DPCs running across all processors - hence the need for the kernel dump.

We extract the WMI trace records for DPCs across all processors from the kernel dump and save those in a form that the Windows performance Analyzer (WPA) can read. We can then use the WPA to sort all running DPCs on their execution time - the ones at the top of this list are the longest running and contributing most to the bugcheck. Here's this display for your kernel dump...

We can ignore the ntoskrnl.exe entry because that's the Windows kernel. Microsoft recommend that no DPC run for longer than 100 microseconds (0.1ms) yet you have several DPCs running for longer than this:

MpKslDrv.sys is a Windows Defender driver (so this driver isn't at fault).
Wdf01000.sys is the Windows Driver Foundation driver (and it's not at fault). However, many third-party drivers are written using WDF libraries and this driver will be managing them. There may be a flaky WDF third-party driver here.
Nvlddmkm.sys is the Nvidia graphics driver (so this could well be at fault) and it's by far the longest running DPC, by a long way!

The place to start is with the longest running DPC because it could be causing the others to run longer than usual. A problem with nvlddmkm.sys could be either a driver problem of a graphics card problem. In addition, this is a laptop and laptops very often use customised graphics drivers, both for operational and power-saving reasons. The generic Nvidia drivers, which don't contain these customisations, sometimes don't work properly in laptops.

The driver download page for your laptop contains drivers for both the Intel GPU and the Nvidia GPU that are dated this year. I would strongly suggest that you install the existing graphics drivers (both Intel and Nvidia) and then download and install the two graphics drivers on this MSI website.

exodunes · Nov 26, 2023

ubuysa said:
The reason for asking for the kernel dump is because this particular variant of the 0x133 bugcheck (with argument 1 set to 1) was caused by a collection of DPCs running for too long. A minidump only contains the data structures for the failing processor but for this bugcheck we need to see the DPCs running across all processors - hence the need for the kernel dump.

We extract the WMI trace records for DPCs across all processors from the kernel dump and save those in a form that the Windows performance Analyzer (WPA) can read. We can then use the WPA to sort all running DPCs on their execution time - the ones at the top of this list are the longest running and contributing most to the bugcheck. Here's this display for your kernel dump...

We can ignore the ntoskrnl.exe entry because that's the Windows kernel. Microsoft recommend that no DPC run for longer than 100 microseconds (0.1ms) yet you have several DPCs running for longer than this:

MpKslDrv.sys is a Windows Defender driver (so this driver isn't at fault).

Wdf01000.sys is the Windows Driver Foundation driver (and it's not at fault). However, many third-party drivers are written using WDF libraries and this driver will be managing them. There may be a flaky WDF third-party driver here.

Nvlddmkm.sys is the Nvidia graphics driver (so this could well be at fault) and it's by far the longest running DPC, by a long way!

The place to start is with the longest running DPC because it could be causing the others to run longer than usual. A problem with nvlddmkm.sys could be either a driver problem of a graphics card problem. In addition, this is a laptop and laptops very often use customised graphics drivers, both for operational and power-saving reasons. The generic Nvidia drivers, which don't contain these customisations, sometimes don't work properly in laptops.

The driver download page for your laptop contains drivers for both the Intel GPU and the Nvidia GPU that are dated this year. I would strongly suggest that you install the existing graphics drivers (both Intel and Nvidia) and then download and install the two graphics drivers on this MSI website.

Alright, thank you for the explanation! I have used DDU to uninstall my display drivers and then installed them again after downloading the versions from the manufacturers website.

Then, I tried playing the game again, but alas, another crash after a maximum of 15 minutes of play.
I have changed the system language to English, so this should now have everything in english.

You will find the new V2 Logs and the Memory dump from that crash in this link
Google Drive Link to new files

My best guess would be that the GPU itself might be faulty or something, but maybe you guys have more information on this one.

zbook · Nov 26, 2023

There were recurrent display driver BSOD (NVidia) with the same display driver versions (31.0.15.2892).

Please test another one or two versions.

If there are recurrent BSOD then swap test the NVidia card.

Code:

Name    Intel(R) UHD Graphics
PNP Device ID    PCI\VEN_8086&DEV_46A3&SUBSYS_13C71462&REV_0C\3&11583659&0&10
Adapter Type    Intel(R) UHD Graphics Family, Intel Corporation compatible
Adapter Description    Intel(R) UHD Graphics
Adapter RAM    1.00 GB (1,073,741,824 bytes)
Installed Drivers    <>,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5b1252b3763da959\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5b1252b3763da959\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5b1252b3763da959\igd12umd64.dll
Driver Version    31.0.101.4255
INF File    oem72.inf (iADLPD_w10_DS section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_5B1252B3763DA959\IGDKMDN64.SYS (31.0.101.4255, 50.11 MB (52,542,408 bytes), 11/26/2023 10:57 AM)
 
Name    NVIDIA GeForce RTX 4060 Laptop GPU
PNP Device ID    PCI\VEN_10DE&DEV_28A0&SUBSYS_13C81462&REV_A1\4&217FF2CC&0&0008
Adapter Type    NVIDIA GeForce RTX 4060 Laptop GPU, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 4060 Laptop GPU
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_2d970ceb19513e73\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_2d970ceb19513e73\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_2d970ceb19513e73\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_2d970ceb19513e73\nvldumdx.dll
Driver Version    31.0.15.2892
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVMI.INF_AMD64_2D970CEB19513E73\NVLDDMKM.SYS (31.0.15.2892, 55.40 MB (58,091,520 bytes), 4/17/2023 11:29 AM)

ubuysa · Nov 26, 2023

It's a laptop so the graphics card is probably soldered in. IN addition, if it BSODs with the latest manufacturer's graphics drivers then it's probably the graphics card.

That latest minidump is another 0x133 with argument 1 set to 0x1, but in common with all the other dumps, nvlddmkm.sys is the most likely suspect driver. This makes it highly likely it's the graphics card at fault because that driver should be fine.

Is it possible to disable the Nvidia card and just run with the Intel iGPU? I appreciate of course that graphics performance will be dire and games likely unplayable, but if it doesn't BSOD it's pretty certain to be the Nvidia card sadly.

exodunes · Nov 26, 2023

Thank you guys for answering. I'm going to try disabling the Nvidia GPU and then try again. I don't think the game will even start to be honest, but it's worth a shot.

If it's the Graphics Card, I'll just contact the laptop's manufacturer and get help there. Haven't paid a boatload of money for a gaming machine that crashes when playing basic 3d games.

If it does BSOD again, I will probably be replying rather quickly.

Thank you so much again!