Constant BSOD issues

Roolek

Roolek

Well-known member
Joined
Dec 12, 2020
Posts
45
  • A brief description of your problem (but you can also include the steps you tried) Constant - Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
  • System Manufacturer? Personal build
  • Laptop or Desktop? Desktop
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) Windows 11
  • x86 (32bit) or x64 (64bit)? x64
  • What was original installed OS on system? Windows 11 pro
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? full retail version
  • Age of system? (hardware) mid-2020
  • Age of OS installation? 03/‎10/‎2022
  • Have you re-installed the OS? On that date in 2022
  • CPU AMD Ryzen 9 5900X 12-Core Processor 3.70 GHz
  • RAM (brand, EXACT model, what slots are you using?) Corsair VENGEANCE RGB PRO 64GB (2x32GB) DDR4 3600 (PC4-28800) C18 Desktop memory – Black, 2 x 32 GB (Amazon.co.uk)
  • Video Card - MSI GeForce RTX 3080 Gaming X Trio 10GB GDDR6X PCI-Express Graphics Card
  • MotherBoard - ROG CROSSHAIR VIII HERO (WI-FI)
  • Power Supply - Corsair hx1000
  • Is driver verifier enabled or disabled? Disabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Done antimalwarebytes
  • Are you using proxy, vpn, ipfilters or similar software? No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? No
 
I don't see anything in the data that might account for the 0x124 BSODs so I think some basic hardware tests are called for....
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
And also...
  1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
  2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
  3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
  4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp reaches 95°C (Tmax for your CPU), then stop Prime95 and let us know what happened.
Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.
 
Ran memtest once, all passed, no errors, will run again tonight but takes a while so will have to be overnight

Also ran Prime95 for an hour each test, no errors/warnings, no crashes/freezes/BSOD's, temps reach 88.5 degrees at one point but was generally around 80 but spiked a few times
 

Attachments

Do these BSODs happen ONLY when playing games that use the Riot Vanguard anti-cheat tool? Can you make it BSOD from a cold boot without Riot Vanguard having been used at all?

I'm asking because in every one of those dumps the Riot Vanguard driver vgk.sys appears in the list of unloaded modules...
Rich (BB code): 
Unloaded modules:
fffff802`445f0000 fffff802`445fe000   WdmCompanion
fffff802`27c80000 fffff802`27ca1000   dam.sys 
fffff802`27cb0000 fffff802`27cc0000   KMPDC.sys
fffff802`26b40000 fffff802`27f80000   vgk.sys 
fffff802`14f80000 fffff802`14f8c000   WdBoot.sys
fffff802`16200000 fffff802`16212000   hwpolicy.sys
The vgk.sys driver is a (very) well known cause of BSODs and that it's unloaded just before each of these BSODs is too much of a coincidence to ignore. It is thus most important that you see whether the BSODs are limited to Vanguard use or whether they happen at other times. To be certain it's not Vanguard you MUST shutdown and reboot and then NOT play any game that requires Vanguard. We need to be certain that the vgk.sys driver is not being loaded into memory at all. Can you make it BSOD without loading Vanguard?
 
I actually don't play any riot games anymore, but Vanguard is just always running, I'll completely remove that and see how I get on, will update
 
It seems to happen quite a bit more with World of Warcraft open, not sure if that's relevant to anything
 
It was important to remove Vanguard, especially if you no longer need it. As I'm sure you know, the most recent BSOD was another 0x124 WHEA bugcheck. They are most usually hardware related, but we've run the two main hardware stress tests (RAM and CPU). That most recent BSOD was referencing the graphics card in the lead-up to the bugcheck, we see dxgkrnl.sys (the Windows DirectX kernel driver) and nvlddmkm.sys (the Nvidia graphics driver) called, so it's well worth also stress testing the GPU and driver.

Either download Furmark, the traditional, free, and well-known GPU stress testing tool, or the more recent OCCT Personal (free), which can stress test all aspects of your system - select the GPU stress test if you decide to use this tool (it has three GPU stress tests). FWIW I use OCCT for stability testing when I build a new PC. Let's just check to see whether the GPU is the source of these 0x124 BSODs before looking elsewhere.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top