Hello. I'd first like to say I'm pretty much at beginner level when it comes to PC stuff, so you'll have to excuse me. I've had issues with my PC for a long time, but nothing bad enough to make it unusable. I recently startet getting BSOD and tried using event viewer to find out the issue. I found an error code/ bug check that was called 0x000000a. After some googling, it was recommended on Microsoft website to use driver verifier through cmd. I tried this and was asked to restart my PC.
Now this is where it went really badly. Now my PC boots normally, but takes a very long time to get past the welcome screen. After getting to the main screen, everything gets super laggy, CPU usage goes to 100% because of "System interupts", all fans go crazy and loud, and after about 2 minutes I get BSOD. Error code on BSOD reads: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
I'm not really able to gather any information before BSOD. Any pointer, or at least where I can start? Last resort is to take my PC to a repair shop. Thanks!
Here is the link to the dump files: https://files.catbox.moe/lrcf79.rar
I managed to boot into Safe Mode with Networking, but still unsure what the issue could be. I'm starting to believe it may be a driver related problem, as Safe Mode uses very few drivers and only launches what is necessary. This is just a theory though.
Now this is where it went really badly. Now my PC boots normally, but takes a very long time to get past the welcome screen. After getting to the main screen, everything gets super laggy, CPU usage goes to 100% because of "System interupts", all fans go crazy and loud, and after about 2 minutes I get BSOD. Error code on BSOD reads: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
I'm not really able to gather any information before BSOD. Any pointer, or at least where I can start? Last resort is to take my PC to a repair shop. Thanks!
Here is the link to the dump files: https://files.catbox.moe/lrcf79.rar
I managed to boot into Safe Mode with Networking, but still unsure what the issue could be. I'm starting to believe it may be a driver related problem, as Safe Mode uses very few drivers and only launches what is necessary. This is just a theory though.