Windows 10: need help reading a Bsod dump, specifically FAILURE_BUCKET_ID:...

Hello all, thanks for any help in advance. This is my first BSOD on this system and it might be nothing but since I have an intel 13700k I am worried do to failure rates in the news. I was playing Hogwarts legacy and it froze then bluescreened, with the BSOD error code DPC WATCHDOG VIOLATION. I'm hoping this is just because it timed out , and again not the cpu since the game is buggy and i also have a mod running to help fix performance issues in the game. the BSOD memory dump I believe says the issue is FAILURE_BUCKET_ID: 0x133_ISR_dxgmms2!VIDMM_MDL_RANGE::Lock. im including the ful;l dump.

:)

 

Reading driver verifier crash dump

Here are the other two images:
Ill try what you suggested, thank all of you for the help so far.

 

Need help on reading dump files.

This forum is primarily aimed at home users. Although there used to be some responders who were familiar with interpreting dump files, most, if not all, of them no longer monitor the forum.

I suggest you try asking here: BSOD Crashes, Kernel Debugging

Do read the "posting instructions" post that's pinned at the top.

 

BAD_POOL_HEADER BSOD, Dump File attached


Hi Groggubus,

Welcome to the 10forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please follow this suggestion for the BSOD

1. Please open BitDefender and go to the modules,
2. Go to the firewall settings,
3. Uncheck 'Block port scans in the network',
4. Reboot your system <-- IMPORTANT