Volmgr 161 + WHEA

I will check shortly, but are you saying that update kb5022834 could possibly have something to do with WHEA-Uncorrectable Error / Volmgr 161?

- - - Updated - - -

I checked in the programs and features > view installed updates, and I do not see this update installed.

Ah well, it was worth checking.

No, I wasn't suggesting the update was related to the volmgr errors, I was just following that latest BSOD.

In your first post you said this...

Samsung 970 evo plus NVMe SSD (also tried a WD SSD, and took that out thinking it was the culprit).

Were you getting exactly the same errors on the WD SSD?
When you swapped to the 970 EVO did you clone the WD across or reinstall Windows? If you cloned it then how?

You also said this...

I’ve been working to fix my custom built PC for 3+ years now, as I’ve experienced the same BSOD throughout 10+ fresh windows installations, changing every single part of the PC...

Has this issue been present from day one then? Have you changed the motherboard, amongst all the changes you've made?

When you reinstalled 10+ times did you immediately reinstall all your third-party software etc. or did you try and test it with just vanilla Windows installed? It's entirely possible that you've been reinstalling the problem. In addition, when you reinstall do you delete all existing partitions on the system drive and then install into the unallocated space? Do you run Windows Update (across reboots) until no more updates are found? Do you then check in View optional updates for any driver updates? If you do another reinstall please stop once Windows and the drivers are installed and see whether you can make if BSOD then. I would then suggest installing all your third-party software and devices one at a time, testing after each install to try and discover what makes it fail.

You said you've run Samsung Magician in the past and it didn't find anything wrong. Did you also check for an updated driver for the 970 EVO (with Magician)? Did you check for updated firmware for the 970 EVO (with Magician)? If not, can you do both please.

Can you also please download and run the free version of Speccy. Once it's analysed your system, click the File menu item and then click 'Publish snapshot'. You'll get a URL in return, please post that URL here.

I was getting the exact same errors on the WD SSD, yes. This led me to getting the Samsung 970 EVO, thinking this would solve the issue. I did not clone the SSDs or transfer anything old. All partitions were fully deleted and a clean windows install followed.

This issue started probably a few months after I got the custom PC from the builder. He's definitely an expert in the field, and I bothered him for over a year about a solution, but we couldn't find one. If it had been present from the start, I would've just returned it to him. I have changed the motherboard as well as everything else in the machine, and made sure it was properly installed.

After reinstalling windows, evidently I've tried many many different things. A handful of times were not reinstalling anything as you mentioned. The only thing I did was the minimum that I knew could cause a BSOD. This is typically something like Minecraft or Apex Legends. Given my Minecraft stuff takes a lot longer to install, I just tried with Apex. So the only thing that would be installed is the nvidia drivers, my xbox controller directly plugged in, and steam launcher to launch the game. I have also tried this without installing any nvidia drivers, but still experienced the same.

I delete all the existing partitions when I reinstall a fresh windows. Both the WD and Samsung were completely cleaned out before the clean installs.

I just ran Samsung magician again and it still says everything is good to go, and the firmware is still fully updated. I am not sure where to check if the drivers are updated. Checked through google and it just mentions the firmware. I've done the autosearch in control panel, though and never find updated drivers for the ssd's.

I'm actually kinda surprised that changing the CPU didn't fix it, because the last one in HWMonitor said it was 90 degrees celsius, and now it's hovering around a normal 40 something. I guess it could've just been monitoring wrong too, who knows at this point.

Here is the speccy URL: http://speccy.piriform.com/results/t...uWHoxsWzVgISG0

Thanks again for your time!!

The V2 log collector share link in post #38 is old if there was a new clean install.

Please indicate the date and time of the most recent clean install.

The last BSOD WHEA 124 was yesterday 04/22/2023 and that appears to be after the CPU was replaced.

If the new V2 log collector (post new clean install) displays new unexpected shutdowns and restarts and / or BSOD WHEA 124 then consider swap testing the motherboard.


Continue monitoring the computer with Reliability Monitor:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

In searching systeminfo in command prompt, I see that the latest Windows install is 4/10/2023. I did not re-install windows once again since changing the CPU, which was done I believe last Wednesday the 19th. Immediately after doing so, I ran Apex again and it bluescreened with the same error, telling me that it most likely wasn't the CPU despite the temperature difference I mentioned. The V2 I shared should've been the newest one collected right at that time, but in any case, I just ran it again and have attached the file below.

DESKTOP-31HHLHG-(2023-04-23_16-38-21).zip

The computer had unexpected shutdowns and restarts after replacing the CPU.

If you want additional confirmation that it is malfunctioning hardware then plan another clean install.

Otherwise see if you can swap test the motherboard.

When was the PSU replaced or swap tested?

Code:

Event[7589]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-04-22T13:54:22.2800000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-31HHLHG
  Description: 
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Code:

Event[8562]:
  Log Name: System
  Source: EventLog
  Date: 2023-04-23T16:24:40.1800000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-31HHLHG
  Description: 
The previous system shutdown at 1:41:58 PM on ?4/?23/?2023 was unexpected.

Code:

Event[8572]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2023-04-23T16:24:31.2810000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-31HHLHG
  Description: 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The PSU was swap-tested about 6 months ago. In the codes you're showing (and I know it's not great timing but nothing I can do about it), the first one is indeed a WHEA uncorrectable error unexpected shutdown. The following two are just from a power outage from a construction project at my house. I would've turned my PC off if I was informed, but such is life.

I'm still running my ram sticks one by one, and I also closed the back of the case up to see if the added pressure on the wires will give me another BSOD tonight. If I hit another one after confirming that all my Ram sticks are good, I'll keep all ram sticks in and take the back of the case off, relieving the pressure from its cables. If that still doesn't stop it, then I should do another clean install of windows. That sound about right?