Volmgr 161 + WHEA

Page 5 of 19 FirstFirst ... 3456715 ... LastLast

  1. Posts : 402
    Windows 10 and Windows 11
       #41

    I don't think that MpKslDrv.sys is the root cause here, mainly because it's a Microsoft driver. AFAIK it's part of the Defender definitions update process.

    I think what this dump shows is that MpKslDrv.sys triggered the page fault and bugcheck, but it wasn't this driver that was at fault. Some other driver earlier in the process fouled up and it wasn't until MpKslDrv.sys acted on that information that we got the page fault.

    You've run Driver Verifier long enough to have caught a rogue third-party driver, so we can reasonably assume that this problem isn't a third-party driver.

    I have come across this, very similar, problem to yours from February this year. This BSOD also occurred whilst MsMpEng.exe was running, and so during a Defender definition update. The module containing the failing instruction is also the same - including the offset...
    Code:
    YOURS:
    FAILED_INSTRUCTION_ADDRESS: 
    nt!HalpSetSystemInformation+e12c2
    fffff803`5941c022 488d0dc7ee4300  lea     rcx,[nt!HalpPerfInterruptHandlerRegistrationLock (fffff803`5985aef0)]
    
    THEIRS:
    FAILED_INSTRUCTION_ADDRESS: 
    nt!HalpSetSystemInformation+e12c2
    fffff803`08c26022 488d0de7ec4300  lea     rcx,[nt!HalpPerfInterruptHandlerRegistrationLock (fffff803`09064d10)]
    Do you have update KB5022834 installed, and if you do can you try and uninstall it (and hide it to stop it coming back) and see whether the issues stop?

    It's a long-shot I know, but it's worth investigating.
    Last edited by ubuysa; 23 Apr 2023 at 03:13.
      My Computer


  2. Posts : 95
    Windows 10
    Thread Starter
       #42

    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.
      My Computer


  3. Posts : 402
    Windows 10 and Windows 11
       #43

    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.
      My Computer


  4. Posts : 95
    Windows 10
    Thread Starter
       #44

    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!!
      My Computer


  5. Posts : 41,455
    windows 10 professional version 1607 build 14393.969 64 bit
       #45

    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
      My Computer


  6. Posts : 95
    Windows 10
    Thread Starter
       #46

    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
      My Computer


  7. Posts : 41,455
    windows 10 professional version 1607 build 14393.969 64 bit
       #47

    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.
      My Computer


  8. Posts : 95
    Windows 10
    Thread Starter
       #48

    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?
      My Computer


  9. Posts : 402
    Windows 10 and Windows 11
       #49

    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...?

    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?

    The storage ports for your motherboard (from the manual are these)...
    Supports 4 x M.2 slots and 6 x SATA 6Gb/s ports
    Intel®11th &10th Gen Processors*

    M.2_1 slot (Key M), type 2242/2260/2280/22110
    - Only Intel® 11th Core™ processors support PCIe 4.0 x4 mode, this slot will be disabled for other CPUs

    M.2_2 slot (Key M), type 2242/2260/2280/22110
    - Intel® 11th processors support PCIe 4.0 x4 mode
    - Intel® 10th processors support PCIe 3.0 x4 mode

    Intel® Z590 Chipset

    M.2_3 slot (Key M), type 2242/2260/2280/22110 (supports PCIe 3.0 x4 mode)

    M.2_4 slot (Key M), type 2242/2260/2280 (supports PCIe 3.0 x4 & SATA modes)*

    *When M.2_4 is operating in SATA device, SATA6G_2 will be disabled.
    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?

    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'm no hardware expert, but I wonder whether there is some BIOS setting that isn't optimised? Others can help with this I hope....?

    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.....
    Last edited by ubuysa; 24 Apr 2023 at 06:58.
      My Computer


  10. Posts : 659
    10 preview 64bit
       #50

    Hi
    This maybe a red herring but needs to be done anyway

    Within the Speccy log there is an update in progress... KB4023057 dated 4/13
    However the OP mentioned that this has been a long ongoing problem..... and this KB is one of MS's recurrent updates and definately been going for years, if previous versions of it were having the same issue then it could be causing the wufd problem entry

    please follow the instructions here
    How to delete pending updates on Windows 10 - Pureinfotech
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:11.
Find Us




Windows 10 Forums