#DPC_WATCHDOG_VIOLATION Error

1 messages · Page 1 of 1 (latest)

hot rain
#

Hi,

Every so often when I have my computer on eventually it'll blue screen with the same error and this has been happening for months on end now. I'm still trying to figure out what it could be; this error only ever occurs when I'm playing roblox and on no other game. It's really odd on what's happening but something unique about the BSOD is that wallpaper engine's wallpaper will still show and the crash will happen. It'll look like anything with a blue tint in the front of it. I have reinstalled Windows 11, well replaced it with Tiny11 just to get rid of a lot of bloatware and this issue is still happening.

I reboot every single time like nothing happened go into terminal (command prompt) and run the same command over and over again 'sfc /scannow'. It'll always report that a windows file got corrupted and it'll fix itself for a while. To then give it a while and the same error will occur and I will do the same fix again. It's hard to say what the issue is but i'm suspecting either a software conflict with roblox and wallpaper engine or part of my hardware is failing like my SSD. All my other parts are fine and have been working in order for a while now. Though something to note is I did see an increase for a short period of time when using overlays, which gives me reason to think that it's wallpaper engine causing crashes and conflicting with other bits of software; I have asked my friend if they experience the same but they said they don't and everything is working orderly for them. In which gives me reason to believe my issue is also hardware related. Especially, it going on for months on end.

I have a picture from a while ago and thought it was cool - this image dates back to around October 10th, probably a few days before so around 5th October at the earliest when I encountered this issue.

Does anybody have any suggestions as to what the problem could potentially be and/or has somebody else encountered this issue before?

vocal wadi
#

damn thats a cool bsod

#

but i hsve no idea how to fix it

#

try finding stuff in event viewer