Question System crashing due to several BSOD errors encountered ?

[ApexDorifto]

Hello everyone!

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

---

Problem/s​

• WHEA_UNCORRECTABLE_ERROR
• *DPC_WATCHDOG_VIOLATION
• *DRIVER_STACK_OVERRAN_BUFFER

• These BSOD errors 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 2666MHz	KF2666C16D4
Slot 2:​	SK Hynix V-Color 8GB 2666MHz	TD48G26S819-VC
SSD	Hikvision 240GB	HKVSN HS-SSD-C100/240G
HDD	Western Digital 1TB (Green)	WDC WD10EURX-63UY4Y0
PSU	Thermaltake 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.​
• *Reinstalled AMD Radeon Software for GPU​

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!
​

---

*EDIT: I've added the other BSOD errors that occurs, reinstalled GPU software. And also, added new minidump files that were newly created due to BSOD occurring again.

 

[johnbl]

is there a reason you do not update the bios to the current version?
2018 bios is really old. lots of cpu security fixes since then.

last bugcheck was
PROCESS_NAME: MemCompression
STORE_DATA_STRUCTURE_CORRUPTION (1c7)
The store component detected a corruption in its data structures.
Arguments:
Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match.
Arg2: ffffd587eaff5000, Chunk heap buffer whose hash didn't match.
Arg3: 0000000021c0e153, Expected buffer hash.
Arg4: 00000000002feff5, Page frame number of the corrupted page.

system was up 1.5 hours or so.

if you are having intermittent memory problems, you might have a crack in the memory traces. this type of problem can result in thermal breaks that connect and disconnect depending on thermal expansion. ie when cold the memory block has one memory address but when the chip heats up the connection is made and the memory block has a different memory address.
(assuming a bad connection on a address line to a memory chip)

sometimes you can find these by heat/cool testing. most often you get something like, you get a bugcheck after you boot up the machine in the morning but then you reboot and it runs fine all day but the next morning the cycle starts again. thermal problem are hard to find, you can heat an area with a heat gun, or cool an area with freon to try to find a bad component. even then you end up having to take off heatsinks and do a visual inspection with a stereoscope so you can actually look for chips legs that have lifted off of the circuit board traces.
I have found these before, I would find the correct data in kernel memory but at the wrong address. It was confusing, until I took the heat sink off of the memory stick and looked at the legs and found a chip leg that had lifted from the circuit board.

 

[ApexDorifto]

is there a reason you do not update the bios to the current version?
2018 bios is really old. lots of cpu security fixes since then.

last bugcheck was
PROCESS_NAME: MemCompression
STORE_DATA_STRUCTURE_CORRUPTION (1c7)
The store component detected a corruption in its data structures.
Arguments:
Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match.
Arg2: ffffd587eaff5000, Chunk heap buffer whose hash didn't match.
Arg3: 0000000021c0e153, Expected buffer hash.
Arg4: 00000000002feff5, Page frame number of the corrupted page.

system was up 1.5 hours or so.

I'm quite hesitant when doing the BIOS version as I've been using the same version ever since I've been using this PC around 2020 and had no problems ever since. I just really don't think that the crashes are related to the BIOS version.

EDIT: I've just got another BSOD while watching on Youtube, I have uploaded the minidump file in the Google Drive Folder.

---

Minidump Files & Log Files (as of May 05, 2025)

Minidump files: Windows Minidump Files (Google Drive Folder)

Log Files: HWiNFO64 Log Files (Google Drive Folder)​

 

[ubuysa]

In those minidumps at least one was likely caused by vgk.sys...

FAILURE_BUCKET_ID:  AV_R_(null)_vgk!unknown_function

That driver is part of Riot's Vanguard anti-cheat tool and it's a VERY well-known cause of BSODs. It's important now to reboot (to unload the driver) and then see whether you can generate BSODs without running Vanguard - which probably means without running any Riot games.

 

[ApexDorifto]

In those minidumps at least one was likely caused by vgk.sys...

FAILURE_BUCKET_ID:  AV_R_(null)_vgk!unknown_function

That driver is part of Riot's Vanguard anti-cheat tool and it's a VERY well-known cause of BSODs. It's important now to reboot (to unload the driver) and then see whether you can generate BSODs without running Vanguard - which probably means without running any Riot games.

I did uninstall VALORANT and the Riot Client itself after getting that BSOD and checked if I'd get any BSODs, unfortunately the same night, just a few hours after, I just got another BSOD.

I've uploaded the minidump file after uninstalling the game.

The minidump is named 050725-7171-01.dmp

 

[johnbl]

I'm quite hesitant when doing the BIOS version as I've been using the same version ever since I've been using this PC around 2020 and had no problems ever since. I just really don't think that the crashes are related to the BIOS version.

EDIT: I've just got another BSOD while watching on Youtube, I have uploaded the minidump file in the Google Drive Folder.

---

Minidump Files & Log Files (as of May 05, 2025)

Minidump files: Windows Minidump Files (Google Drive Folder)

Log Files: HWiNFO64 Log Files (Google Drive Folder)​

windows continues to make updates and will assume that your bios is getting updated. Windows can patch some CPU bugs with a cpu specific microcode patch. Specifications for the interfaces that are supported in bios change over time. if you do not update the bios you should block windows updates also. When window error reporting detect a bug in non microsoft code, they will report it to the vendor who will make driver and bios updates a few months later. BIOS updates are required.
Some systems actually now push out firmware updates via windows update since users often fail to update the bios. there also have been a bunch of cpu malware attacks the will actually load malware into the cpu core. BIOS updates are required to block these. intel me update needed to fix these.

 

[johnbl]

last bugcheck was
nt!RtlIpv4StringToAddressW+0x31

this is a pretty simple function to convert a IPV 4 address string
to a binary number.

looks like the null pointer was converted and bugchecked.

it might be called by a network driver since it is network related.
debugger indicated it was called by the system process.

you have a generic microsoft bluetooth driver installed but i was not sure what device is being used. or maybe you have a custom network utility running?
maybe Realtek 8118 Gaming LAN bandwidth Control Utility
something that did not set up correctly

 

[ApexDorifto]

last bugcheck was
nt!RtlIpv4StringToAddressW+0x31

this is a pretty simple function to convert a IPV 4 address string
to a binary number.

looks like the null pointer was converted and bugchecked.

it might be called by a network driver since it is network related.
debugger indicated it was called by the system process.

I'm confused if it is a network driver. The last time that I've installed a network driver was from the website of the manufacturer of my motherboard (H310M H 2.0)

Here's the screenshot of my device manager.

https://imgur.com/2eU4V0U

 

[johnbl]

I'm confused if it is a network driver. The last time that I've installed a network driver was from the website of the manufacturer of my motherboard (H310M H 2.0)

Here's the screenshot of my device manager.

https://imgur.com/2eU4V0U

what is the bluetooth device? it did not look like your motherboard had bluetooth built in.

I am trying to figure out why the system would make the call so late (after 1.5 hour of boot) I was thinking maybe your bluetooth device went to sleep, then woke up and the system read a registry value that was not set correctly and ended up using a NULL pointer then bugchecked.

the function was not called from a network driver but the system. More likely something is trying to setup a network function incorrectly or bad registry entry.
maybe a bluetooth device that has LAN functions that you do not use? Headset?

 

[ApexDorifto]

what is the bluetooth device? it did not look like your motherboard had bluetooth built in.

I'm using a bluetooth dongle I've bought few years ago. I don't think it would be one of the possible culprit of the BSODs as it was working well since I've bought it.

I'm currently using a speaker (connected to the motherboard), and earphones (connected to the front panel of the PC case).

 

[johnbl]

I'm using a bluetooth dongle I've bought few years ago. I don't think it would be one of the possible culprit of the BSODs as it was working well since I've bought it.

what is connected to the bluetooth dongle? anything that can transfer files?

the kernel dump did show a bluetooth personal area network but it look like it was uninitialized from here in the registry:
\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\BthPan

 

[ApexDorifto]

what is connected to the bluetooth dongle? anything that can transfer files?

There's nothing connected to the bluetooth dongle as of the moment, and yeah, it can transfer files but I don't use it to transfer files.

 

[johnbl]

There's nothing connected to the bluetooth dongle as of the moment, and yeah, it can transfer files but I don't use it to transfer files.

looks like a browser reading a web page can try to scan your local area network ports.

it might explain why the call was not made until 1.5 hours after bootup.

browser web page trying to scan a port with a null ipv 4 address.
rather than the exploit address of 0.0.0.0

exploit documented in aug 2024
https://www.oligo.security/blog/0-0-0-0-day-exploiting-localhost-apis-from-the-browser

for this exploit the browser would try to use 0.0.0.0😛ort number
to try to read info from the local area network know ports.

you might also run cmd.exe as an admin then run
ipconfig.exe /all

and look to see if your dhcp lease expired and was being renewed.
at the time of the bugcheck.