Computer keeps blue screening

[Kirikoza]

Hey guys, I keep getting blue screen crashes on my computer. Common errors include kmode exception not handled and driver overran stack error.

 

I bought this computer used. The guy previous said it would crash for him sometimes but seemed to work fine running 4k. That so far hasnt entirely been my experience, it crashes regardless.

 

Specs:

i7 9700

Asrock b365M-HDV

16gb Corsair Vengence DDR4 2666mhz

PNY 4060 8GB

500gb SSD (dont recall the brand)

500w Thermaltake 80+ psu

 

The ram was previously 3000mhz... I downgraded it due to motherboard limitations hoping it'd help. I also put the new power supply in when I got it. BIOS is on the most recent version. I've reinstalled a few of the drivers, did a clean install for the graphics drivers. Of course when I replaced the ram I seated it properly and double triple checked it...

I disabled windows fast boot to ensure drivers reloaded when the computer restarted as well, no luck.

 

We just use it for gaming and videos. So far no specific task causes the crash, seems to come out of nowhere.

 

I have a few dump files from crashes, one as recent as today. If someone is able to analyze these and determine what could be the cause I'd greatly appreciate it. Now that I have uploaded these dump files I'm going to reinstall Windows 11 and pray that helps.

ugh.zip

[Kirikoza]

Lol sorry about the file name on this I've been struggling with this. I think that reflects my mental exhaustion at this point lol

[Tetras]

With BSODs, I would always run memtest, to verify that your memory is not faulty.

 

16 minutes ago, Kirikoza said:

500gb SSD

Can you find out the exact model (e.g. from device manager) and post the SMART data.

 

16 minutes ago, Kirikoza said:

I'm going to reinstall Windows 11 and pray that helps.

If there has been instability over a long period then the SSD may have a bunch of corrupted files, which could easily lead you down to the wrong path.

[Kirikoza]

9 minutes ago, Tetras said:

With BSODs, I would always run memtest, to verify that your memory is not faulty.

 

Can you find out the exact model (e.g. from device manager) and post the SMART data.

 

If there has been instability over a long period then the SSD may have a bunch of corrupted files, which could easily lead you down to the wrong path.

Apologies, I should have mentioned I ran memtest on the last set of ram and it failed. Once I replaced the RAM I reran the test and it passed.

 

I have not ran SMART monitoring test before I am unsure how to do that, is there a tool you recommend installing to get this data or are there command prompts I can use?

[Kirikoza]

20 minutes ago, Tetras said:

With BSODs, I would always run memtest, to verify that your memory is not faulty.

 

Can you find out the exact model (e.g. from device manager) and post the SMART data.

 

If there has been instability over a long period then the SSD may have a bunch of corrupted files, which could easily lead you down to the wrong path.

Also checked device manager it just says PCIe SSD. Its on the back of the mobo so I would have to take the whole motherboard out to get to it to check it. From what I recall it was a real generic no name brand, nothing like my Samsung Evo in my main build. I'm willing to condeed it could be this SSD causing the issues

[Tetras]

6 minutes ago, Kirikoza said:

I have not ran SMART monitoring test before I am unsure how to do that, is there a tool you recommend installing to get this data or are there command prompts I can use?

Ideally you'd run the manufacturer tools, but since you don't know, I'd try CrystalDiskInfo.

 

3 minutes ago, Kirikoza said:

From what I recall it was a real generic no name brand, nothing like my Samsung Evo in my main build. I'm willing to condeed it could be this SSD causing the issues

It could be, but just to be clear, by corrupted files I didn't mean from the SSD making them, I meant that if the memory is faulty (which you have confirmed it previously was), then it can slowly corrupt the files being modified/saved to your SSD and this can result in BSODs in Windows until you're able to repair or reinstall it.

 

Reinstalling Windows will confirm if that is the problem ^^

 

The no name brand and "PCIe SSD" ID is a concern though, yeah.

[Kirikoza]

3 hours ago, Tetras said:

Ideally you'd run the manufacturer tools, but since you don't know, I'd try CrystalDiskInfo.

 

It could be, but just to be clear, by corrupted files I didn't mean from the SSD making them, I meant that if the memory is faulty (which you have confirmed it previously was), then it can slowly corrupt the files being modified/saved to your SSD and this can result in BSODs in Windows until you're able to repair or reinstall it.

 

Reinstalling Windows will confirm if that is the problem ^^

 

The no name brand and "PCIe SSD" ID is a concern though, yeah.

Got into the computer, found the SSD, it was actually an Inland from microcenter, so I kinda doubt it's the issue but who knows. Kinda bizarre it doesn't identify itself in device manager. If I have any further issues I will get it's SMART data and follow up on that.

I reinstalled Win11 and getting drivers up on it, we'll see if that fixes it.

 

Thank you for mentioning that the old RAM could have left corrupt files on the machine. That didn't cross my mind so I was just thinking some other part was failing. Crossing my fingers we're all good from here.

[Tetras]

9 hours ago, Kirikoza said:

Thank you for mentioning that the old RAM could have left corrupt files on the machine. That didn't cross my mind so I was just thinking some other part was failing. Crossing my fingers we're all good from here.

Yeah, if the memory is super faulty (like thousands of errors when you run the tests) then potentially it may have committed LOTS of corrupted data to disk, which could screw with Windows files, drivers and who knows what else. 

 

Hopefully the reinstall will do the job for you!

[Kirikoza]

On 10/6/2024 at 8:03 AM, Tetras said:

Yeah, if the memory is super faulty (like thousands of errors when you run the tests) then potentially it may have committed LOTS of corrupted data to disk, which could screw with Windows files, drivers and who knows what else. 

 

Hopefully the reinstall will do the job for you!

Well do I have an update for you!

 

I've reinstalled Windows since this post and have reinstalled graphics drivers. The system seems fine without the graphics card. The moment it's introduced the PC freaks out.

 

 Check out this picture. Does this look like a graphics card related BSOD to you?

 

(Call of duty in the bg of a BSOD)

[Tetras]

1 hour ago, Kirikoza said:

Does this look like a graphics card related BSOD to you?

It is impossible to say really, there's not much to go on.

 

If I google "system service exception", there's loads of possible problems/fixes.

 

1 hour ago, Kirikoza said:

The system seems fine without the graphics card. The moment it's introduced the PC freaks out.

Assuming there's nothing obvious like a faulty riser then you're likely to be stuck swapping parts out I'm afraid.

[Bjoolz]

14 hours ago, Kirikoza said:

Well do I have an update for you!

 

I've reinstalled Windows since this post and have reinstalled graphics drivers. The system seems fine without the graphics card. The moment it's introduced the PC freaks out.

 

 Check out this picture. Does this look like a graphics card related BSOD to you?

 

(Call of duty in the bg of a BSOD)

I can tell you that from the dump files, it doesn't look like the GPU at all. It looks like memory. Memory doesn't have to mean RAM, but with the errors in Memtest it's quite likely (Could still be the memory controller, meaning CPU).

 

If it crashes this quickly, just try to use it with one stick at a time.