Question System Crashing with WHEA_UNCORRECTABLE_ERROR BSOD ?

ApexDorifto

Honorable
Apr 29, 2018
9
0
10,510
Hello everyone!

I'd like to address about my PC throwing BSOD.


Problem
  • The BSOD (WHEA_UNCORRECTABLE_ERROR) occurs at random times, but I have observed that it usually appears when:
    • I'm editing my videos using DaVinci Resolve 20
    • Playing games (rarely for BSOD to occur)


PC Specs:

Part​
Brand/Model/etc.​
Part/Serial No.​
CPU
Intel i5-8400 (with Intel Stock Cooler)
GPU
Gigabyte AORUS RX 570 (4GB)GV-RX570AORUS-4GD
MOBO
Gigabyte H310M H 2.0
RAM
Slot 1:
Samsung Kingston 8GB 2666MHzKF2666C164
Slot 2:
SK Hynix V-Color 8GB 2666MHz (TD48G26S819-VC)TD48G26S819-VC
SSDHikvision 240GBHKVSN HS-SSD-C100/240G
HDDWestern Digital 1TB (Green)WDC WD10EURX-63UY4Y0
PSUThermaltake TR2 S 600W



Troubleshoots I've Made
  • Re-applying thermal paste on my CPU
  • Stress tested my CPU using Intel Processor Diagnostic Tool
    • NOTE: Did not show any BSOD
  • Checked CPU temperatures
    • NOTE: reaches around 42°C at idle; ~75°C-80°C at full load.
  • Checked GPU temperatures
    • NOTE: reaches around 47°C-50°C at idle; 80°C at full load.
  • Checked CPU and GPU clockings
    • NOTE: Everything is at default, none are overclocked.
  • Reset BIOS/UEFI settings to "Default"
  • Checked RAM Timings at GIGABYTE UEFI
    • NOTE: Everything is at "Auto"
  • Ran several commands in CMD/Windows Powershell
    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
    • mdsched (no errors)
  • Tried to use PC one RAM stick per RAM slot
    • NOTE: I used DaVinci Resolve to let the BSOD appear whjle doing this troubleshoot.
RAM Stick/Slot​
Time of BSOD Appearing​
Time of BSOD Appearing​
Time Duration between Boot Time and Time of BSOD Appearing​
SK Hynix @ Slot 1​
8:39 AM​
8:54 AM​
~15 minutes​
SK Hynix @ Slot 2​
9:03 AM​
9:17 AM​
~14 minutes​
Kingston @ Slot 1​
9:22 AM​
9:41 AM​
~19 minutes​
Kingston @ Slot 2​
9:49 AM​
9:57 AM​
~8 minutes​



Minidump Files

Here are the Minidump files after BSOD crashes.

Windows Minidump Files (Google Drive Folder)


If I need to do something to troubleshoot more or any questions need to be answered, let me know, any help will be greatly appreciated, thanks in advance!:bounce:
 
Last edited:
MOBOGigabyte H310M H 2.0
What BIOS version are you on for your motherboard?

RAM
Slot 1:
Samsung Kingston 8GB 2666MHzKF2666C164
Slot 2:
SK Hynix V-Color 8GB 2666MHz (TD48G26S819-VC)TD48G26S819-VC
Looks like the Kingston stick might be at fault or the memory controller on your processor is having trouble with said Kingston ram stick. I would also advise against mixing and matching ram sticks, they are usually the cause for instabilities.

PSUThermaltake TR2 S 600W
That's a horrible PSU.
 
  • Like
Reactions: ApexDorifto
Mixing different RAM is always a bad idea. RAM should always be purchased in a pack of matched sticks. In addition, I'm getting bad symbol errors on four of your dumps and a fully corrupted dump in the other. These are also strong indicators of a RAM issue.

I would definitely remove whichever RAM stick was the most recently installed, at least until this issue has been resolved. That said, you seem to be getting BSODs on only one stick, so RAM isn't the whole story here.

The other common cause of dump corruption is a flaky system drive. I'm not familiar at all with Hikvision SSDs but check to see whether they have a diagnostic tool. If they do then run the maximal diagnostic they have on the drive. If not, then upload the SMART data for the drive, a tool like CrystalDiskInfo can show you that. Post the SMART data here if you like.

I'm also a bit concerned about your CPU. The stock Intel coolers are barely adequate, I would never recommend using one. Even though your "full load" test only reached 80°C it's quite possible that you may have exceeded the 100°C Tmax temp at times, especially if you're gaming.

I would also help if you copuld please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem much easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
 
Last edited:
  • Like
Reactions: ApexDorifto
MOBOGigabyte H310M H 2.0
What BIOS version are you on for your motherboard?

RAM
Slot 1:
Samsung Kingston 8GB 2666MHzKF2666C164
Slot 2:
SK Hynix V-Color 8GB 2666MHz (TD48G26S819-VC)TD48G26S819-VC
Looks like the Kingston stick might be at fault or the memory controller on your processor is having trouble with said Kingston ram stick. I would also advise against mixing and matching ram sticks, they are usually the cause for instabilities.

PSUThermaltake TR2 S 600W
That's a horrible PSU.
I've checked my BIOS version and it says "F2".

(I'm also pretty sure that the BIOS version isn't the issue here because I've been using this motherboard on the same BIOS version ever since we bought this PC, and no problems we're occuring up until the BSOD appeared from last month up until today.)

Unfortunately, I don't have any spare RAM sticks, that's why I can't prevent doing mix-matching with my current RAMs, and also determine which RAM stick is at fault.

Maybe these pictures will help.




I did changed the position of the RAM sticks just a few moments ago.
 
Last edited:
Mixing different RAM is always a bad idea. RAM should always be purchased in a pack of matched sticks. In addition, I'm getting bad symbol errors on four of your dumps and a fully corrupted dump in the other. These are also strong indicators of a RAM issue.

I would definitely remove whichever RAM stick was the most recently installed, at least until this issue has been resolved. That said, you seem to be getting BSODs on only one stick, so RAM isn't the whole story here.
Yes, my older brother and I we're both suspecting that one of the RAMs are failing now ever since it was bought. The SK Hynix was the older one compared to my Kingston RAM stick. I didn't had any idea at that time when I bought the RAM stick (Kingston) which is completely my fault.
 
Mixing different RAM is always a bad idea. RAM should always be purchased in a pack of matched sticks. In addition, I'm getting bad symbol errors on four of your dumps and a fully corrupted dump in the other. These are also strong indicators of a RAM issue.

I would definitely remove whichever RAM stick was the most recently installed, at least until this issue has been resolved. That said, you seem to be getting BSODs on only one stick, so RAM isn't the whole story here.

The other common cause of dump corruption is a flaky system drive. I'm not familiar at all with Hikvision SSDs but check to see whether they have a diagnostic tool. If they do then run the maximal diagnostic they have on the drive. If not, then upload the SMART data for the drive, a tool like CrystalDiskInfo can show you that. Post the SMART data here if you like.

I'm also a bit concerned about your CPU. The stock Intel coolers are barely adequate, I would never recommend using one. Even though your "full load" test only reached 80°C it's quite possible that you may have exceeded the 100°C Tmax temp at times, especially if you're gaming.

I would also help if you copuld please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the available troubleshooting data and will make diagnosing your problem much easier. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
Here's the SMART data of my SSD and HDD


 
best guess is overheated cpu
-----------
all the bugchecks were called by the CPU.
I would be looking for a overheated cpu/ fan that is not working. Then I would look at the power supply and confirm that the levels are correct (see if the bios will report the voltages)

your build has various problems that need to be addressed. modified windows core files, old bios, old drivers. suspect drivers installed but I would check cpu temps/voltages as a direct cause of the bugchecks.
I did not see a driver issue that would cause this bugcheck. Ram sticks should not cause this problem.
----------------------------
last bugcheck called by cpu after 18 minutes of uptime.
debugger does not like your build. various issues.. will take a quick look at the other dumps.
----------
second bugcheck same as first
System Uptime: was 8 minutes
------------
third bugcheck same as others, system uptime 25 minutes
-----------
4th bugcheck same as others, system uptime 19 mins
----------
5th bugcheck same as others. system uptime 13 minutes

notes:
\SystemRoot\System32\Drivers\WinRing0x64.sys Sat Jul 26 06:29:37 2008
win32kbase.sys Wed Nov 7 17:02:09 2001
\SystemRoot\System32\DriverStore\FileRepository\heci.inf_amd64_85021432489d6a1c\x64\TeeDriverW8x64.sys Thu Apr 4 02:38:40 2019
\SystemRoot\system32\drivers\RTKVHD64.sys Tue May 14 04:25:05 2019
\SystemRoot\System32\drivers\RtkBtfilter.sys Wed Oct 31 18:51:00 2018
\SystemRoot\System32\drivers\rt640x64.sys Mon May 10 20:30:41 2021

\SystemRoot\system32\drivers\rawaccel.sys Sat Sep 18 03:42:08 2021
C:\Windows\system32\drivers\MsIo64.sys Sun Jan 19 19:35:15 2020
\SystemRoot\system32\drivers\iriuna0.sys Thu Oct 22 08:22:10 2020
C:\Windows\system32\drivers\IntelHaxm.sys Tue Aug 25 03:11:09 2020
SystemRoot\System32\drivers\dtlitescsibus.sys Mon Nov 12 19:11:07 2018
SystemRoot\System32\drivers\dtliteusbbus.sys Mon Jul 26 11:43:47 2021
C:\Windows\system32\drivers\CtiIo64.sys Tue Apr 26 20:01:30 2022

\SystemRoot\system32\DRIVERS\bddci4.sys Fri Feb 7 02:51:15 2025
SystemRoot\System32\DriverStore\FileRepository\atihdwt6.inf_amd64_5bf3de4243c61001\AtihdWT6.sys
C:\Users\ADMINI~1\AppData\Local\Temp\ALSysIO64.sys Tue Oct 18 07:38:31 2022

1: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.1, DMIVersion 0, Size=4557]
BiosMajorRelease = 5
BiosMinorRelease = 12
BiosVendor = American Megatrends Inc.
BiosVersion = F2
BiosReleaseDate = 06/22/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H310M H 2.0
SystemFamily = Default string
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = H310M H 2.0
BaseBoardVersion = x.x


1: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2808
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 158 Stepping 10
ProcessorNameString = REG_SZ Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz
Update Status = REG_DWORD 0
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD b400000000

cpu released in October 2017
 
Last edited: