Pc Keeps Crashing BSOD

D

Danishm

Member
Hi,

Recently got my pc and I have been having a lot of BSOD with the code whea_uncorrectable_error. I Can't seem to figure out what's causing it. I've updated all my drivers and even reseated my memory and GPU but for a little bit it will be fine, and then randomly crash every now and then with the above error

My memory dump file can be found here. I think this is the right one but if not please let me know!

1drv.ms

memory dump.txt

Text Document
1drv.ms

CaseCORSAIR CRYSTAL SERIES 680X RGB GAMING CASE
Processor (CPU)AMD Ryzen 9 5900X 12 Core CPU (3.7GHz-4.8GHz/70MB CACHE/AM4)
MotherboardASUS® ROG STRIX X570-F GAMING (USB 3.2 Gen 2, PCIe 4.0) - ARGB Ready!
Memory (RAM)Corsair VENGEANCE DDR4 3600MHz (4 x 8GB)
Graphics Card10GB NVIDIA GEFORCE RTX 3080
1st Storage Drive4TB SEAGATE IRONWOLF PRO 3.5", 7200 RPM 128MB CACHE
2nd Storage DriveNONE
1st M.2 SSD Drive500GB SEAGATE FIRECUDA 520 GEN 4 PCIe NVMe (up to 5000MB/R, 2500MB/W)
2nd M.2 SSD Drive2TB SAMSUNG 970 EVO PLUS M.2, PCIe NVMe (up to 3500MB/R, 3300MB/W)
DVD/BLU-RAY DriveNOT REQUIRED
Power SupplyCORSAIR 850W RMx SERIES™ MODULAR 80 PLUS® GOLD, ULTRA QUIET
Power Cable1 x 1 Metre UK Power Cable (Kettle Lead)
Processor CoolingCorsair H115i RGB PLATINUM Hydro Series High Performance CPU Cooler
Thermal PasteARCTIC MX-4 EXTREME THERMAL CONDUCTIVITY COMPOUND
Sound CardONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card10/100/1000 GIGABIT LAN PORT (Wi-Fi NOT INCLUDED)
Wireless Network Card10/100/1000 GIGABIT LAN PORT (Wi-Fi NOT INCLUDED)
down_right_arrow.gif
Change to: WIRELESS INTEL® Wi-Fi 6 AX200 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
 

Attachments

  • memory dump.txt
    2 KB · Views: 169
ubuysa

ubuysa

The BSOD Doctor
Can you upload the minidump itself please? It will be in C:\Windows\Minidumps (upload all dumps you find in there).

WHEA_UNCORRECTABLE_ERROR is a hardware issue (WHEA is the Windows Hardware Error Architecture). Rather than the minidump(s) you have, a kernel dump would be of more use. If there is one in C:\Windows\Memory.dmp please upload it.

Upload dumps to the cloud somewhere and post a link to them here. :)
 
D

Danishm

Member
ubuysa said:
Can you upload the minidump itself please? It will be in C:\Windows\Minidumps (upload all dumps you find in there).

WHEA_UNCORRECTABLE_ERROR is a hardware issue (WHEA is the Windows Hardware Error Architecture). Rather than the minidump(s) you have, a kernel dump would be of more use. If there is one in C:\Windows\Memory.dmp please upload it.

Upload dumps to the cloud somewhere and post a link to them here. :)
Click to expand...
I believe these are the files are you asked for?

the Memory dump https://1drv.ms/u/s!AvRxtPFEJX8r-meBR4cWmNJxFESc?e=6s9K1U

the mini dumps https://onedrive.live.com/?authkey=!AITXErcViV7SqCo&id=2B7F2544F1B471F4!15725&cid=2B7F2544F1B471F4
 
ubuysa

ubuysa

The BSOD Doctor
Well the minidumps got me worried so I waited for the kernel dump to download and that scared me even more...

I think you have a fatal CPU (or motherboard) issue. The kernel dump error record shows the failure was caused by a BUS ERROR, specifically it was a BUSL1_SRC_IRD_I_NOTIMEOUT_ERR (Proc 10 Bank 1).

I suggest you call PCS in the morning, point them to this thread and point them at the kernel dump (not the minidumps, they don't contain the critical error record). I think you're looking at an RMA I'm afraid.....

A note for @SpyderTracks: Use the !errrec command with the address in arg2 as a parameter to see the error record. :)
 
D

Danishm

Member
I did have a question however, I've been looking around trying to see if it could be any thing else and I've found my ram got very hot and after looking into it, the RAM was overclocked to 3600hz in Bios. Could these crashes be a possible due to an unstable ram overclock?
 
ubuysa

ubuysa

The BSOD Doctor
Danishm said:
I did have a question however, I've been looking around trying to see if it could be any thing else and I've found my ram got very hot and after looking into it, the RAM was overclocked to 3600hz in Bios. Could these crashes be a possible due to an unstable ram overclock?
Click to expand...
It's possible that it's RAM related and it's certainly worth removing the RAM overclock for a while and see whether it stabilises? RAM does get hot though - especially when overclocked.

It might also be worth removing two of the RAM stick and seeing whether it's stable at 3600MHz on just two sticks? There is another active thread on here with someone having problems with 4 RAM sticks. See https://www.pcspecialist.co.uk/foru...ly-as-theyre-booting.76266/page-2#post-544585 see also https://www.pcspecialist.co.uk/forums/threads/faulty-ram.75252/. A workaround in that last thread was to lower the RAM frequency to the point at which it's stable.

It's also worth ensuring that any future dumps are kernel dumps and not minidumps. Enter sysdm.cpl as a command in the Run box, click the Advanced tab, and then the bottom one of the three Settings buttons (the one in Start-up and Recovery). In the pull-down menu list select Kernel memory dump, also uncheck the box that says Overwrite any existing file.

This will build up several (large) kernel dumps so once you've collected two or three more, check the overwrite box again (each kernel dump is over 1GB in size). Upload all C:\Windows\Memoryn.dmp files (where n is a number) to the cloud with a link here. :)
 
Last edited:
D

Danishm

Member
Hi,

Thanks for your help. I did everything you asked and after testing it with many memory stick congifurations and doing memtest on the ram and running them at stock, I am still getting BDODs. I let my pc collect a few over the past few days. I emailed PCS right away however I'm still awaiting their reply. In the mean I have another link for a my kernal dump if you wouldn't mind looking into them to get a better picture?

The dump file - https://1drv.ms/u/s!AvRxtPFEJX8r-meBR4cWmNJxFESc?e=jG1UtD

Thanks very much!
 
ubuysa

ubuysa

The BSOD Doctor
Danishm said:
Hi,

Thanks for your help. I did everything you asked and after testing it with many memory stick congifurations and doing memtest on the ram and running them at stock, I am still getting BDODs. I let my pc collect a few over the past few days. I emailed PCS right away however I'm still awaiting their reply. In the mean I have another link for a my kernal dump if you wouldn't mind looking into them to get a better picture?

The dump file - https://1drv.ms/u/s!AvRxtPFEJX8r-meBR4cWmNJxFESc?e=jG1UtD

Thanks very much!
Click to expand...
I'm drawn to memory dumps like a moth to a flame - I'll leave you to explain to my wife why I definitely needed to look at yours tonight....! ;)

This dump is pretty much the same as the last, it's a WHEA_UNCORRECTABLE_ERROR (WHEA is the Windows Hardware Error Architecture) caused by a BUS Error - so a hardware failure. Again it's specifically a BUSL1_SRC_IRD_I_NOTIMEOUT_ERR (Proc 11 Bank 1).

We know it's not a RAM issue (which was the most likely cause) from all the good work you've done, so I've done a bit of research on this and there are a few things I'd like you to try....

1. Turn off Fast Startup - I'm not at all sure how this is related but I've seen suggestions that this could be a cause of WHEA failures on some motherboards.

2. Reset the CMOS, either via a jumper on the board (RTFM) or by removing the CMOS battery for a couple of minutes and then replacing it. Don't touch the battery with your naked fingers (the oils in your skin do the battery no good at all).

3. Completely uninstall Norton Security - I've seen it cause all manner of problems, though I'm not at all sure it's related to this one to be honest. All you need is Windows Defender - which is free for one thing - Norton is a waste of your money and often a source of problems.

4. I also notice that you're running Python. Do you have any Python applications that directly access Windows features or services? Disable them if you do - just in case.

I honestly think this is a hardware fault, if not the RAM then a fault on the motherboard. It's worth trying the above suggestions though.

Now I'm off to try and placate my wife (again)......😇
 
D

Danishm

Member
Hey, Just thought I would post an update since it's been a while.

I sent the pc back to PCS and they found the problem with the CPU. They replaced it and stress tested it and now it runs fine! They sent it back and I should be receiving it soon!

Wanted to give a big thanks to Ubuysa for all their help and going through my kernal dumps and all the advice!
 
ubuysa

ubuysa

The BSOD Doctor
Danishm said:
Hey, Just thought I would post an update since it's been a while.

I sent the pc back to PCS and they found the problem with the CPU. They replaced it and stress tested it and now it runs fine! They sent it back and I should be receiving it soon!

Wanted to give a big thanks to Ubuysa for all their help and going through my kernal dumps and all the advice!
Click to expand...
That's interesting, do come back if you gave any further issues. :)
 
You must log in or register to reply here.
Top