Volmgr 161 + WHEA

Page 14 of 19 FirstFirst ... 41213141516 ... LastLast

  1. Posts : 264
    Windows 10 Home 21H2
       #131

    I'm not finding anything about it causing BSOD crashes or making a system drive go offline. Rather, they all seem to be system freezes. My recollection is that it was a PCIE Gen 4 GPU installed in a Gen 4 slot with a PCIE Gen 3 NVMe drive installed in a PCIE Gen 4 slot. It was probably that the owner claimed they needed to set the GPU slot to Gen 3 but I'm not certain.

    NVMe drives seem to fail a lot. To the point of making me wonder if there is any quality control at all. There doesn't seem to be a reliable publicly available way of testing everything that can go wrong with an NVMe drive, either. I'd probably try a different PSU with the cables it came with to rule it out but I'm not convinced it will help. From a probability standpoint, I'd say it's more likely you were unlucky and ended up with two bad NVMe drives versus the likelihood of that being true for the other components. More so due to the type of crashes you're getting.
      My Computer


  2. Posts : 95
    Windows 10
    Thread Starter
       #132

    Well, on that note, since I'm waiting for the PSU for another week or so, I could just order another samsung 970 and give that a try.?

    In the last three years, on top of all the other parts gone wrong, I have also had three out of five monitors crap out on me never to receive a signal again. This being said, I see bad NVMes as well in the range of possibilities

    - - - Updated - - -

    NVME SSD Causing BSOD ??? | Page 2 | Overclock.net

    Somewhat similar story here I guess
      My Computer


  3. Posts : 264
    Windows 10 Home 21H2
       #133

    Page 53 in this document is where the PCIE settings I've mentioned should be according to Asus. I don't know why it would manifest as a drive related problem but can you try setting the PCIEX16_1 link speed to Gen3 and then try to reproduce a crash?
      My Computer


  4. Posts : 95
    Windows 10
    Thread Starter
       #134

    I set pcie 16_1 and 2 link speeds to Gen3 now. Gen4 is not offered as a choice, so Iím guessing the system can already tell and acts as if theyíre Gen 3 as thatís how Iíve heard it works anyway, but will give it a try nevertheless.

    I also found another setting under:
    Advanced>PCH config\pci express config was set to auto, so I changed that to gen3 just in case. Thanks! Also have another samsung 970 evo arriving tomorrow morning just in case
      My Computer


  5. Posts : 402
    Windows 10 and Windows 11
       #135

    I'm in full support of the above BIOS setting changes, but if you were able to install Windows on that HDD - and it proved stable - then we'd know for certain that the issue was isolated to the NVMe drive. All we have to go on so far is a single dump , and although it points very clearly at the NVMe drive, we need to be careful not to rush down a rabbit hole.

    I'd very much like to prove that the PC is stable with no NVMe drives involved.
      My Computer


  6. Posts : 95
    Windows 10
    Thread Starter
       #136

    Now this is interesting...

    For whatever reason, I was getting a little confident that the recent NVMe configurations solved the issue after pushing my PC pretty hard and not getting a BSOD for ~24 hours. Needless to say, it did not.

    I got the laptop in, and wanted to run a side-by-side UserBenchmark Test.

    I started the tests on both, and a few minutes in, my PC crashed and showed this screen.
    Volmgr 161 + WHEA-triplemonitors.jpg

    Even further, I went to the Event Viewer after forcing my PC off and turning it back on (it did not go to bluescreen), I noticed the volmgr 161 error was back, evidently because the dumpfile was unable to be written.. however we moved the dumpfiles to the other SSD (drive F) so that it WOULD work, and it had been every time since (thanks cwsink!). That being said, I would assume this means we got some kind of full system crash during the UserBenchmark Test.

    I've linked the apps+systems logs here. Lots of 10000 errors every exactly 10 minutes, any way to get rid of those? Also the error ID 2's?
    appsandsystemsincenvmeconfig.zip - Google Drive

    This probably even further pushes the narrative the PSU cables need replacing (still waiting on that to arrive, May 19-24). Any thoughts here y'all? Thanks as always

    Oh also, I got this sound video of inside my PC, a certain ticking sound that doesn't sound completely constant throughout. I know this is mostly software experts, but just thought to mention it as I hadn't been hearing it before- most likely nothing.

    soundvideo.mp4.MOV - Google Drive
      My Computer


  7. Posts : 402
    Windows 10 and Windows 11
       #137

    The 10000 System log errors are all related to OneDrive (though I've not checked every single one!)..
    Code:
    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          18/05/2023 00:13:44
    Event ID:      10000
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          S-1-5-21-3821167752-2690546062-1683153293-1001
    Computer:      DESKTOP-31HHLHG
    Description:
    Unable to start a DCOM Server: {94269C4E-071A-4116-90E6-52E557067E4E}. The error:
    "2147942402"
    Happened while starting this command:
    "C:\Users\Parker\AppData\Local\Microsoft\OneDrive\23.086.0423.0001\FileCoAuth.exe" -Embedding
    DCOM errors like these are common in most people's logs, and since they relate to OneDrive I think you can probably ignore them.

    There is however an NTFS message reporting an error in the filesystem structure of the C: drive. It doesn't look to be for anything important - but any corruption is not good. There does seem to be just the one message, but even one is bad...
    Code:
    Log Name:      System
    Source:        Ntfs
    Date:          16/05/2023 02:28:58
    Event ID:      55
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      DESKTOP-31HHLHG
    Description:
    A corruption was discovered in the file system structure on volume C:.
    
    A corruption was found in a file system index structure.  The file reference number is 0x20000000740c2.  The name of the file is "\Users\Parker\Desktop\Jackbox Games\The Jackbox Party Pack 6\games\RoleModels\content\RMSituationalPrompt\57324".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

    There are also of course the more familiar WHEA hardware errors in there, and many of them too...
    Code:
    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          13/05/2023 02:02:18
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      DESKTOP-31HHLHG
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000010, 0xffff9202a57d5028, 0xffff920292fb7aac, 0xffff9202970171a0). A dump was saved in: F:\DUMPFILES\MEMORY.DMP. Report Id: 9d8b6827-5bc9-49c9-92e3-47a096c7aa2a.
    
    Log Name:      System
    Source:        Microsoft-Windows-WHEA-Logger
    Date:          18/05/2023 00:21:00
    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.

    All this does kind of suggest a power problem, and the GPU testing display you got (I can't read the red text) would also gel with some sort of power problem. I too am really interested to see what happens with new PSU cables!!
      My Computer


  8. Posts : 95
    Windows 10
    Thread Starter
       #138

    Good to know! The red text is shown in the mp4 video i linked at the bottom of that message. Going to be very interesting to see what the PSU cables swap brings.

    I have OneDrive turned off, so perhaps the code 10000 is just a checker considering itís perfectly every ten minutes.

    That NTFS error is just from a game, nothing to worry about.

    And then our beloved WHEA error <3

    I wasnít overly impressed with the laptopís performance, despite it scoring 19,000 versus my Desktopís 16,000 on 3DMark- it just felt like there was a certain smoothness lacking with the laptop.

    Looking forward to our next update being a big one!
      My Computer


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

    As I mentioned, gaming laptops are often throttled in their BIOS settings (which you usually can't change) in order to prevent overheating. Flashing a non-standard BIOS can often let you remove these throttles - at the risk of overheating and shortening the laptop's life - but doing that will void any warranty you have. The term 'gaming laptop' really is an oxymoron...
      My Computer


  10. Posts : 95
    Windows 10
    Thread Starter
       #140

    I hear ya.. hey since we've set the Nvme/PCIE's to Gen 3 rather than auto, no WHEA BSOD's yet at all, just the full system crash when running the benchmark test
      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 13:44.
Find Us




Windows 10 Forums