Volmgr 161 + WHEA

Hahaha, when I swaptested the PSU, I did so with a 1200W PSU, and the same thing occurred. We can safely rule out the PSU being any cause imo. I will try to hunt down another BSOD whilst having only one monitor plugged, but they’ve been few and far between as of late. Hope to have an update to share within the next few days - thanks.

- - - Updated - - -



Just got another one - BSOD screen attached. Didn't seem to have any codes showing top left, which it typically does, but same Whea uncorrectable error. There was no flickering going on, was streaming an NBA game on one monitor and playing minecraft on main monitor. PC did sound like it was working on the harder side, but nothing major. I've now disconnected the displays to only have one connected to see if I'm able to replicate this issue. In the meantime, please let me know what file(s) you need me to run/attach for further diagnosis. Thanks!

- - - Updated - - -

Just got another BSOD, same WHEA error with only one monitor connected and just Minecraft running. It did take a lot longer this time, so I’m guessing it has something to do with a heat issue? The GPU was at about 66 degrees celsius last I checked it before it BSOD’d. This would make a little bit more sense why the old CPU (which we saw on HWmonitor at 90 degrees celsius, and the new one is at 45ish) perhaps contributed to the BSODs. Just throwing this out there, but would “undervolting” the GPU be of any possible help? I have no experience in this part, but just something I’ve heard in terms of getting the exact same performance, yet being able to run the system with less power and therefore cooler.

I don't think those temps would cause BSODs and I wasn't even aware that you could undervolt a GPU? I would not advise messing about with CPU/GPU voltages in the midst of a BSOD problem in any case. One war at a time.

You can upload the System and Applications logs if you like, though I don't expect to find anything in them...

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.

2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.

3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).

4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).

5. Zip the Application.evtx and System.evtx files together and upload the zip file here.

Application+Sys.zip

Agreed, one war at a time. Fingers crossed

There are some interesting logs in your System log.

There are eleven WHEA errors...

Code:

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          02/05/2023 09:30:02
Event ID:      1
Task Category: None
Level:         Error
Keywords:      WHEA Error Event Logs
User:          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.

In every case, and less than 10 seconds earlier, is this warning message...

Code:

Log Name:      System
Source:        disk
Date:          02/05/2023 09:29:54
Event ID:      158
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-31HHLHG
Description:
Disk 3 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.

It's important to mention that this disk warning message occurs multiple times in your log and is not always followed by a WHEA error. I looked up KB2983588 and it would seem that this issue can cause problems for some people. It seems it may also be an issue following a disk clone. I also found a couple of websites that provide more details and ways to fix this:

https://learn.microsoft.com/en-gb/ar...ure-collisions

How to Change the Disk Signature of a Drive Without Losing Existing Data or Reformatting (howtohaven.com)

You should probably know that Mark Russinovich is THE Windows Internals guru, and you can take whatever he says as the absolute truth. I don't know whether this is related to the volmgr issue, but it might be. It's certainly worth investigating, but I don't think it's causing the WHEA errors.

There is another pattern with these WHEA error messages that it might be worth investigating. Each of the eleven WHEA messages follows the same pattern...

Code:

Log Name:      System
Source:        Service Control Manager
Date:          02/05/2023 09:30:07
Event ID:      7026
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-31HHLHG
Description:
The following boot-start or system-start driver(s) did not load: 
dam

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          02/05/2023 09:30:02
Event ID:      1
Task Category: None
Level:         Error
Keywords:      WHEA Error Event Logs
User:          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.

Log Name:      System
Source:        Microsoft-Windows-WLAN-AutoConfig
Date:          02/05/2023 09:30:02
Event ID:      10001
Task Category: None
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      DESKTOP-31HHLHG
Description:
WLAN Extensibility Module has successfully started.

Log Name:      System
Source:        Microsoft-Windows-WLAN-AutoConfig
Date:          02/05/2023 09:30:02
Event ID:      4000
Task Category: None
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      DESKTOP-31HHLHG
Description:
WLAN AutoConfig service has successfully started.

Log Name:      System
Source:        Microsoft-Windows-DHCPv6-Client
Date:          02/05/2023 09:30:00
Event ID:      51046
Task Category: Service State Event
Level:         Information
Keywords:      
User:          LOCAL SERVICE
Computer:      DESKTOP-31HHLHG
Description:
DHCPv6 client service is started

Log Name:      System
Source:        Microsoft-Windows-Dhcp-Client
Date:          02/05/2023 09:30:00
Event ID:      50103
Task Category: Service State Event
Level:         Information
Keywords:      
User:          LOCAL SERVICE
Computer:      DESKTOP-31HHLHG
Description:
DHCPv4 client registered for shutdown notification

Log Name:      System
Source:        Microsoft-Windows-Dhcp-Client
Date:          02/05/2023 09:30:00
Event ID:      50036
Task Category: Service State Event
Level:         Information
Keywords:      
User:          LOCAL SERVICE
Computer:      DESKTOP-31HHLHG
Description:
DHCPv4 client service is started

Each WHEA error is immediately preceded by networking startup messages. We see the DHCPv4 and DHCPv6 clients start, then the WLAN config and WLAN EM start, then we immediately see the WHEA error, and then finally the Windows Desktop Activity Manager (DAM) fails to load. Might there be a networking connection to these WHEA messages?

There are a huge number of informational messages relating to your AX210 adapter driver (Netwtw12.sys)....

Code:

Log Name:      System
Source:        Netwtw12
Date:          02/05/2023 20:05:07
Event ID:      7002
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-31HHLHG
Description:
The description for Event ID 7002 from source Netwtw12 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\NDMP3
Intel(R) Wi-Fi 6E AX210 160MHz

The message resource is present but the message was not found in the message table

These are not uncommon in event logs it must be said, but I think it worth removing the AX210 and using the LAN cable connection to your router (even temporarily) to completely eliminate the AX210.

As you can see, all my disks clearly have different unique identifiers.

It seems that this is a Microsoft issue. Following the thread below, many users have experienced the same issue.

https://social.technet.microsoft.com...0itprohardware

- - - Updated - - -



As you can see, all my disks clearly have different unique identifiers.

It seems that this is a Microsoft issue. Following the thread below, many users have experienced the same issue.

https://social.technet.microsoft.com...0itprohardware

I couldn't find where this shows it was installed (KB2983588), so does that mean it was installed with the initial windows installation and I can't remove it? If this is the cause, this would've had to have been present 3+ years ago, not sure if this update has or not.

"Each WHEA error is immediately preceded by networking startup messages. We see the DHCPv4 and DHCPv6 clients start, then the WLAN config and WLAN EM start, then we immediately see the WHEA error, and then finally the Windows Desktop Activity Manager (DAM) fails to load. Might there be a networking connection to these WHEA messages?"

---Is there a way for me to check/test this? Not sure how to proceed.

"There are a huge number of informational messages relating to your AX210 adapter driver (Netwtw12.sys)....These are not uncommon in event logs it must be said, but I think it worth removing the AX210 and using the LAN cable connection to your router (even temporarily) to completely eliminate the AX210."

---I believe the AX210 is the wifi card, which is part of the motherboard itself and I am unable to remove it. I don't have any other wifi/ethernet things going on, except a switch. My current setup for LAN cable to my PC goes like this:

-Modem----->Router (TPLink Archer AX21, which seems oddly close to AX210) ------->LAN cabled to switch, which has three LAN cables coming off of it, one to PC, one to xbox, one to TV.

We semi-recently switched routers to the AX21, so I don't think this has any relevance.

Ok re the disk identifier. I'm really scraping the bottom of the barrel now...

You're not actually using the AX210 then? You're LAN connected to the router? It might be worth, just as a test, to eliminate the switch and connect the PC directly into the router? This is such an unusual problem that it's worth checking everything.

Regarding the AX210, it would seem to be active because we see those WLAN messages in the log and and information message for its driver (netwtw12.sys) so that driver is definitely loaded. Can you then disable the AX210 in Device Manager and reboot (to unload the driver)?

We need to be thinking not just outside the box but outside the known Universe! One of my 'rules' is that "if the problem is not where you're looking then it must be somewhere else".

Isn’t the AX210 everything Network+Wi-Fi, inclusive of the Ethernet? Or is it solely Wi-Fi?

I would say sure why not, try this as well, which obviously I’m going to. However, this issue persisted well before this newer motherboard, and the last one (ROG z490-f) did not have built-in WiFi.

The WIiFi and LAN network adapters are separate entities, each with their own driver. The AX210 is just WiFi.

I'd be interested to see the System log entries when/if it BSODs without the AX210 involvement.

Will keep you updated! Thanks

- - - Updated - - -

Had the AX210 disabled. My PC BSODd today with the same WHEA Uncorrectable Error, and this time I wasn’t even home using it. Just idled other than having Rocket League open on the main menu. Anything you’d like me to send in particular next, or always just the application+system zip? Hopefully these new logs are helpful