Question My pc keeps crashing showing various BSOD

Jun 20, 2022
3
0
10
0
Hello,
This is a desperate call for help. My PC crashes every now and then (mostly while surfing the web and sometimes when doing nothing). I managed to write down several BSOD I encountered:
KMODE_EXCEPTION NOT HANDLED
CLOCK_WATCHDOG_TIMEOUT
SYSTEM SERVICE EXCEPTION
SYSTEM THREAD EXCEPTION NOT HANDLED
I didn't change anything on my PC hardware, so no overclocking or something of the sort.
I suspect it has something to do with drivers, so I reinstalled windows 11 (keeping my files) and reinstalled all the drivers again to their latest version. I also updated my BIOS. still no luck...
I decided to ask for help. I'll put a link to the dump file contents as well hoping it may show you the problem I have.
https://files.catbox.moe/a0btxr.txt
Thank you :)

*update
I got more BSOD’s
DPC_WATCHDOG_VIOLATION
IRQL NOT LESS OR EQUAL
It definitely seems like a driver issue, but how can I find the problematic driver? Every time I boot into windows after couple of seconds I notice that the screen froze and immediately I get BSOD…
 
Try to boot off your install media and tell it you want to to repair your computer, it should give options for troubleshooting, maybe then you can go to safe mode or do a system restore.

In windows 10 you could get to the same mode if it didn’t boot I think 3 times. So while you get the spinning dots, hold the power button down until it says it is repairing then it may give that menu.
 
you would need to copy the minidump files to a cloud server, share them for public access and post a link.

the text for the bugcheck showed an attempt to run a invalid op code.
most likely a corrupted stack.
generally, you would want to update the bios and motherboard drivers as a first fix attempt. the memory dump files can provide more specific suggestions.
 
Jun 20, 2022
3
0
10
0
you would need to copy the minidump files to a cloud server, share them for public access and post a link.

the text for the bugcheck showed an attempt to run a invalid op code.
most likely a corrupted stack.
generally, you would want to update the bios and motherboard drivers as a first fix attempt. the memory dump files can provide more specific suggestions.
Updating the BIOS and motherboard drivers was the first thing I've done..

I managed to get more dump files, hope it will come in handy.
https://files.catbox.moe/wquzrn.txt
https://files.catbox.moe/q6mv0g.txt
https://files.catbox.moe/s85j5o.txt
 
Last edited:
Jun 20, 2022
3
0
10
0
need the actual .dmp file rather than a txt file so I can look at it with the windows debugger.

very short system up time 14 seconds
looks like a stack overflow/malware attack/overheating.
I no longer have access to the original files, is there a way to re-create them with these text files?
 

ASK THE COMMUNITY