Volmgr 161 + WHEA

Had 44 items in there, can't hurt to try. Thanks! @hawkman

- - - Updated - - -

ubuysa said:

I have a question regarding the Speccy output for your two SSDs..

Code:

Samsung SSD 970 EVO Plus 2TB (SSD)
Manufacturer: SAMSUNG
Interface: Unknown
Capacity: 1863 GB
Real size: 2,000,398,934,016 bytes
RAID Type: None
S.M.A.R.T S.M.A.R.T not supported
Partition 0
Partition ID: Disk #0, Partition #0
File System: FAT32
Volume Serial Number: 18A63DF9
Size: 96 MB
Used Space: 26.5 MB (27%)
Free Space: 69 MB (73%)
Partition 1
Partition ID: Disk #0, Partition #1
Disk Letter: C:
File System: NTFS
Volume Serial Number: 7EA77321
Size: 1862 GB
Used Space: 329 GB (17%)
Free Space: 1532 GB (83%)
Partition 2
Partition ID: Disk #0, Partition #2
File System: NTFS
Volume Serial Number: 70E20AE8
Size: 529 MB
Used Space: 445 MB (84%)
Free Space: 84 MB (16%)

WDS500G3X0C-00SJG0 (SSD)
Manufacturer: Western Digital
Form Factor: GB/2.5- to 3.5-inch adapter
Interface/Connector: ATA with 33-pin connector (zero insertion forceZIF)
Interface: Unknown
Capacity: 465 GB
Real size: 500,107,862,016 bytes
RAID Type: None
S.M.A.R.T S.M.A.R.T not supported
Partition 0
Partition ID: Disk #1, Partition #0
File System: FAT32
Volume Serial Number: 9ABB1709
Size: 96 MB
Used Space: 26.6 MB (27%)
Free Space: 69 MB (73%)
Partition 1
Partition ID: Disk #1, Partition #1
Disk Letter: F:
File System: NTFS
Volume Serial Number: 08ABF3BC
Size: 465 GB
Used Space: 110 MB (0%)
Free Space: 465 GB (100%)
Partition 2
Partition ID: Disk #1, Partition #2
File System: NTFS
Volume Serial Number: 68B28AAC
Size: 508 MB
Used Space: 424 MB (83%)
Free Space: 84 MB (17%)

Is that WD drive the original WD drive that you had Windows installed on? It seems to have the same three partitions (EFI, Windows, Recovery) as the 970 EVO? I can see that drive F: (the old Windows partition?) is empty, but the EFI and Recovery partitions are not. Since it appears that there is nothing on drive F: can you please disconnect that drive and see whether the problem persists? I know that having two drives with Windows installed can cause problems, I'm wondering whether even having two Recovery partitions and two EFI partitions might be causing problems...?

Yes, that is the original drive. I know the WD isn't at fault as I had it taken out for a long while, last few months or so, and just put it back in when the new CPU got here since I had it opened up anyways. That is odd that it still has the recovery partition on it as well, but I'm not sure how to get rid of it. I know I've formatted it since, but perhaps it's only formatting the New Volume (F). I've done enough swapping, taking out, etc. to know that neither of the drives are an issue, and all of my drives including the SSD's also test 100% healthy.

In addition, the WDS500G3X0C-00SJG0 (SSD) is an NVMe drive using an M.2 socket, so what is this all about?...

Code:

Form Factor: GB/2.5- to 3.5-inch adapter
Interface/Connector: ATA with 33-pin connector (zero insertion forceZIF)

I've no idea what that all means for an M.2 NVMe SSD? An NMVe SSD uses the PCIe interface. There seems to be something unusual about that WD drive (in addition to appearing to having an old Windows system on it). It's not plugged in to a SATA M.2 port is it?

I don't know a whole lot about the NVMe/M.2 space. I believe the ports are Samsung = M.2-3; WD = M.2-4. Again, I've switched these around, and nothing has made a difference. From what I'm reading, either M.2 slot should be fine for these SSDs. "*When M.2_4 is operating in SATA device, SATA6G_2 will be disabled." <- not sure if that plays a role.

The storage ports for your motherboard (from the manual are these)...


Later Update: I also checked that your RAM is on the QVL list for that board and it is, but it's listed as 3600MHz, is there a reason why you're only running it at 2666MHz?

I've ran the RAM sticks both at stock (2666MHz) and at 3600MHz as it is right now. Doesn't seem to make a difference.

You're on the latest BIOS but there is an IntelME update, dated 21st April 2023, that seems to fix a security risk but which it might be worth installing. It's here: ROG STRIX Z590-E GAMING WIFI.

I'll add an update on this shortly, thanks

I'm no hardware expert, but I wonder whether there is some BIOS setting that isn't optimised? Others can help with this I hope....?

As far as I know everything seems to be optimized fine. I have zero experience in "clock speeds" or anything of that nature, but everything always says just hit load optimized defaults with this motherboard and you'll be fine, so that's what I've always had it on other than running XMP 1 for 3600MHz.

The difficulty I have with this issue is that the PC appears stable in Safe Mode, which suggests that the problems are with a third-party driver (because they're not loaded in Safe Mode). However, you have enabled Driver Verifier for all third-party drivers (you did follow my instructions for Drvier Verifier?) and it didn't BSOD at all. That suggests that your third-party drivers are good. These two tests (Safe Mode and Driver Verifier) are giving conflicting results, which is confusing.....

I hear ya, and yes I ran the driver verifier many a times, and correct about safe mode, however I'm not sure really how to push the system in safe mode as everything that's BSOD'd me in normal mode isn't operational in safe mode (Easy Anti-Cheat doesn't want to run in safe mode, even despite doing safe mode with networking).

- - - Updated - - -

I'm nervous to install the MEUpdate as my PC continues not to blue screen for I think this is the third day now as I continue testing the RAM sticks.

In the four slots, so far it's gone like this (1 = RAM in, 0 = open slot).

Day one: 0 1 0 0 = no BSOD

Day two: 0 1 0 1 = no BSOD

Day three: 1 1 0 1 = no BSOD

...and I'm giving all of today to test these three. Perhaps putting the fourth one in its open slot (3) will lead me to the treasure. I highly doubt it's been the RAM all along.

parallelpark said:

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.

There was no information in the thread until this post that there were power outages.

If this happens frequently then a UPC may be an option:
https://www.amazon.com/Computer-Unin...F8&node=764572


The unexpected shutdowns and restarts are useful data when troubleshooting computers.
However if there are power outages it is no longer possible to distinguish between what was caused by a power outage and what happened spontaneously with the computer.

Once the computer is used in a stable environment or with a UPS the log files can be scanned and used to detect unexpected shutdowns and restarts.


Consider this approach once there is a stable power source:
a) Make free backup images and save the images to another disk drive or the cloud
b) Clean install Windows 10
c) Monitor the computer for unexpected shutdowns and restarts using Reliability Monitor

No no, it was just that moment in time. Typically never have power outages actually. Our house is getting remodeled but the electrical is all done.

This kinda just goes back to the original problem though, which is that the PC doesn’t collect dumpfiles with this Volmgr 161 unexpected shutdown. So even if I continue to just use the reliability monitor and view the logs post-BSOD, there won’t be anything there.

- - - Updated - - -

Was able to get the extra windows partitions off the WD SSD, so there's only one big simple volume now.

Can you try and determine when it BSODs? Ae there things you can do where it won't BSOD for example? If so, can you kind of expand your list of tasks until you start to get BSODs. If we could isolate these BSODs to specific apps (games) etc. that might help.

You mentioned EasyAntiCheat and that's a known BSOD causer. All the anticheat 'tools' are known to cause BSODs but EasyAntiCheat is one of the worst (Battleye is the worst). If there is any way you can uninstall it and see whether the BSODs stop that would be worthwhile. I don't game so I know nothing about these anticheat tools - beyond seeing them again and again in memory dumps.

I now think you have two separate issues, one is whatever is causing the BSODs and the other is the volmgr and failure to write dumps issue. I would think that it's important to stop the BSODs first.

BTW I second the UPS suggestion. My PC, monitor, backup drive, and router, sit behind a UPS. It's saved me on more than one occasion.

I’m going on ~four days since the last BSOD, running multiple apps, games, and websites at the same time. I can’t get it to BSOD, which is a good and a bad thing- a bad thing because all the times it’s done this, it eventually came back. I would love to figure out the volmgr 161 error, because I think fixing this will allow me to store minidumps for the next time it BSODs, so we can actually figure out what causes it. EasyAntiCheat has definitely been a pain, but for at least this WHEA-logger issue, I think I’m sold on that not being the issue. I’ve deleted, reinstalled, repaired, verified many times. Unfortunately, you can’t run Apex without running EAC. However, I’ve got minecraft up and running and that always caused a BSOD eventually as well, so stay tuned on that. Noted on the UPS device, good to know just out of my budget for the time being.

Throughout these past three years, from what I can recall, the code was sometimes different than WHEA uncorrectable error on the BSOD screen. However, I know for certain that volmgr 161 has ALWAYS been part of the BSOD, what part it plays I have no idea. This BSOD was entirely random, happening during web browsing, youtubing, gaming, even on idle. As of late, this WHEA uncorrectable error seems to only happen when a game is running, and I would say more particularly an intense game such as a huge minecraft world or apex legends.

Also, I replaced the cmos battery again about four days ago to see if this changed anything. I had already done this in the past and it went unchanged, but perhaps these cmos batteries I have (Amazon’d) aren’t cutting it (since the BSOD has turned to WHEA uncorrectable). This wouldn’t explain the first couple years of BSOD +volmgr 161 as it had the cmos battery that the PC builder installed it with, which looked to have good quality markings on it.

- - - Updated - - -

Alright, was finally able to get a BSOD through running Minecraft. Got the same WHEA uncorrectable error, and no minidump. I haven’t put the fourth and final RAM stick back in, so any thoughts of where to go from here? I’m going to try running minecraft and its server I host again in safe mode to see if I can get it to occur again

- - - Updated - - -

Well this could be something. While running in safe mode, only have the minecraft server started up (wouldn’t let me play for whatever reason), but the screen is glitching every ten or so seconds. I’ll post a video once I’m back home, just thought this could be of possible help

- - - Updated - - -

IMG_8804.MOV - Google Drive

It's getting worse the more I'm using my PC right now. -Most likely disregard this, crappy displayport cable of course :)

- - - Updated - - -

Running the latest IntelME tool, nothing happens. It asked for admin approval, I click yes, and then just nothing.

- - - Updated - - -

To add to what I saw during minecraft, which happens routinely any time there’s been this BSOD, is that in the game, the land that you’re exploring that goes on forever stops generating, meaning I just see myself walk straight into nothingness, but can see the pre-generated world behind me. About ten seconds goes by and then BSOD whea uncorrectable. I’m only pointing this out as it almost seems like perhaps some kind of cache is quickly filling up for whatever reason? Just throwing it out there

Are you sure that's in Safe Mode? The screen resolution looks pretty good for safe mode. Does this 'cache filling' display error also happen in Safe Mode?

It might be worth getting hold of something like a small rubber hammer - a rubber handled screwdriver for example. Take the covers off the PC and whilst it's running in Safe Mode gently tap components with the rubber hammer (graphics card, RAM, motherboard, etc.) to see whether that alters the display or causes a BSOD.

It will also be worth checking that everything is setup for capturing dumps...

1. The page file must be on the same drive as your operating system (C:)
2. Set page file to be only on the C: drive and set the size manually (custom size) to an initial size of 32968MB (max RAM + 200MB) and a maximum size of 33792MB (33GB). That will guarantee enough paging file space to write any size of dump.
3. Set system crash/recovery options to "kernel memory dump" and uncheck "Automatically restart". Be sure to check "Overwite any existing file" (that is important!).
4. The Windows Error Reporting (WER) system service should be set to MANUAL
5. User account control must be enabled.

Alright, got all those set. Just btw, when all four sticks are plugged in I have 64gb ram, so should I switch the numbers you gave or are they so high at 32gb ram that it doesn’t matter?

Hang on.... The Speccy output you posted shows only 32GB of RAM? So does the most recent V2 Collector zip file.

When we're trying to help with a WHEA error it makes no sense for you to start changing the hardware config. Are the extra RAM stick matched to the existing ones for example?

It's impossible to troubleshoot a moving target!

I noted in the earlier posts that I was testing RAM stick by RAM stick, swapping combinationd and whatnot to see if one or more in particular were the cause. However, they all checked out fine so I put them back in. They are all the exact same specs, so this really shouldn’t affect whatever issue is really going on as far as I know. I just ran the speccy in the midst of testing the different RAM sticks.