Volmgr 161 + WHEA

Well that's disappointing!

This look like exactly the same NVMe drive error we were seeing before. The WHEA error is a Device Driver Error and the device is the NVMe driver again...

Code:

ffffce05`94faf8f0 fffff800`812ff4ce : ffffbb8f`c1000002 00000000`00000000 ffffbb8f`8fde7020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffce05`94faf970 fffff800`812fe42f : ffffbb8f`8fde7020 ffffbb8f`8fedd050 ffffbb8f`a86c5410 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffce05`94faf9a0 fffff800`8126a306 : ffffbb8f`a86c5410 ffffbb8f`8fedd050 ffffbb8f`8fe47040 ffffbb8f`8e097a20 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffce05`94faf9d0 fffff800`7c443f85 : ffffbb8f`a96dd8e0 ffffbb8f`a96dd8e0 ffffbb8f`8fedd050 ffffbb8f`8e0ce080 : storport!StorPortWorkItemRoutine+0x46

I confess that I'm stumped now, I had hoped we'd got to the bottom of that. I still think this is some sort of power problem though. Perhaps it's environmental? Is the PC on a power ring with other electrically noisy devices (fridge, washing machine, etc)? Are there any (portable) florescent lights connected to the same ring? Is the PC plugged into a surge protector (it really should be) and is there anything else also plugged in there?

Can you possibly try moving the PC and plugging it in to a different power ring?

I have a rule that; if the problem isn't where you're looking then it's somewhere else. That applies here I think. You've looked all over that PC and so the problem has to be somewhere else......

Well, that's really unfortunate

I am moving out in a couple months, so that'll be a good opportunity to try a different ring, amid possible other environmental occurrences as well. Thanks again for your continued support.

I know I've asked this before, but doesn't it seem odd that I was experiencing this crash at a minimum once a day, I change the power supply cables, and have no crashes for over a month. Couple that with the fact that I was pushing it to similar screens in game that seemed to have common crashes as before, now (until today) it had just powered through those lags and whatnot. But no crashes for a month? PSU cables HAD to have something to do with it, right?

I would like to think so, it does suggest that this is possibly a power problem of some sort.

The move couldn't come at a better time, it should eliminate all environmental causes - unless you take the problem device with you of course!

I once spent weeks trying to solve a WiFi issue that turned out to be an arcing light switch right next to the wireless router. I also heard of a failing fridge compressor causing power noise that affected a PC on the same ring.

If you can try looking at your power feed and at other devices in the home, then do. The upcoming move will be a good test though.

So the crash just happened again, so doesn't look like a fluke by any means...

Interestingly enough, I got the volmgr 161 error back meaning that the dump file didn't create in what is still the f drive. The whole PC just froze, and no monitor found its way to a bsod. Very odd

I think the dump is not being created because whatever this is causes a 'surprise removal' of the NVMe drive - and that's where the dump would be written.

If the PC is good, and you've literally changed everything, then the problem has to be outside the PC....

Well if you recall, we changed the location where the dump should be written, which is why we started receiving dump files (from NVMe C drive to other ssd (f drive). So whatever it was had to be enough of a full system shutdown for the pc to not write to the f drive as well.

I tested the different circuits this morning, and all our appliances are on a circuit separate that of my computer's, so that shouldn't be the issue.

The only other thing I can think of is that I get pretty decent ground fault loop sounds through my speakers when on my computer's input. Not sure if this has any implication on my situation, but thought it best to at least mention. Here's a thread for possible helpful info: Static causes BSOD | Tom's Hardware Forum

That's interesting, though that link is scary for safety reasons!

Hadn't crashed since I last posted, so just about a week now. Then, interestingly enough, my dad turned the furnace on and my pc crashed with the WHEA uncorrectable error code (could be coincidental, considering the furnace is on a separate 220 line and my PC is on a 110 line- I'm not sure how this works in terms of all the electricity going to the house or something like that, idk). Got a dump file this time, so including it just in case y'all are able to notice a difference between this one and the last. Appreciate all that you do! Dump below:


************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.140 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Parker\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff801`70600000 PsLoadedModuleList = 0xfffff801`7122a2d0
Debug session time: Thu Jul 13 12:22:47.199 2023 (UTC - 7:00)
System Uptime: 0 days 0:47:46.818
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols

Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`709fc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcc89`76d72390=0000000000000124
14: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000010, Device Driver Error
Arg2: ffffe1835fd89028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffe1834dc21aac
Arg4: ffffe1834dce91a0

Debugging Details:
------------------

*** WARNING: Check Image - Checksum mismatch - Dump: 0x7b5e, File: 0x7eb6 - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2921

Key : Analysis.Elapsed.mSec
Value: 4072

Key : Analysis.IO.Other.Mb
Value: 4

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 24

Key : Analysis.Init.CPU.mSec
Value: 827

Key : Analysis.Init.Elapsed.mSec
Value: 16193

Key : Analysis.Memory.CommitPeak.Mb
Value: 108

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Failure.Bucket
Value: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffe1835fd89028

BUGCHECK_P3: ffffe1834dc21aac

BUGCHECK_P4: ffffe1834dce91a0

FILE_IN_CAB: MEMORY.DMP

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffcc89`76d72388 fffff801`70bb9a8c : 00000000`00000124 00000000`00000010 ffffe183`5fd89028 ffffe183`4dc21aac : nt!KeBugCheckEx
ffffcc89`76d72390 fffff801`70bba5e9 : ffffe183`65302610 ffffe183`65302610 ffffe183`4dc21a80 ffffe183`627a4378 : nt!WheaReportHwError+0x3ec
ffffcc89`76d72470 fffff801`70bba705 : 00000000`00000000 00000000`00000062 ffffe183`65302610 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffcc89`76d724a0 fffff801`76063831 : 00000000`00000000 ffffcc89`76d726c0 ffffe183`4dce91a0 ffffe183`4dce70ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffcc89`76d72500 fffff801`7605cc10 : 00000000`00000000 ffffe183`4dce91a0 ffffe183`4dd291a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffcc89`76d72590 fffff801`7602f0bc : fffff801`76089000 00000000`00000062 00000000`00000000 ffffcc89`76d72930 : storport!StorpMarkDeviceFailed+0x358
ffffcc89`76d72820 fffff801`760eb57d : 00000000`00000000 ffffe183`4dce7020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffcc89`76d728f0 fffff801`760ee78e : ffffe183`c1000002 00000000`00000000 ffffe183`4dce7020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffcc89`76d72970 fffff801`760ed6ef : ffffe183`4dce7020 ffffe183`4dce9050 ffffe183`5eeca550 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffcc89`76d729a0 fffff801`7605a306 : ffffe183`5eeca550 ffffe183`4dce9050 ffffe183`4dc03040 ffffe183`4bf02a60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffcc89`76d729d0 fffff801`70843fa5 : ffffe183`67cc5d40 ffffe183`67cc5d40 ffffe183`4dce9050 ffffe183`4bee8040 : storport!StorPortWorkItemRoutine+0x46
ffffcc89`76d72a00 fffff801`7088e5c5 : ffffe183`4dc6d040 ffffe183`4dc6d040 fffff801`70843e70 ffffe183`00000000 : nt!IopProcessWorkItem+0x135
ffffcc89`76d72a70 fffff801`70926915 : ffffe183`4dc6d040 00000000`00000080 ffffe183`4be9a0c0 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105
ffffcc89`76d72b10 fffff801`70a04cf8 : ffffa901`f1780180 ffffe183`4dc6d040 fffff801`709268c0 0020004d`00500053 : nt!PspSystemThreadStartup+0x55
ffffcc89`76d72b60 00000000`00000000 : ffffcc89`76d73000 ffffcc89`76d6c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Followup: MachineOwner
---------

- - - Updated - - -

Check this outttt

Question - 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys | Page 2 | Tom's Hardware Forum

The dump is the same as all the others; a failure of the NVMe drive - though not a 'surprise remove' this time, just a controller reset.

I would experiment with the furnace again when you can, that's the kind of thing I think is your problem.

Alternatively come here, to Crete (Greece). We're having highs around 102F at the moment - no need for a furnace here!

We’ll be there for me and my gf’s honeymoon someday!

Worked back and forth with the furnace, must’ve just been a coincidence. Did you check that link out at the bottom? Apparently Asus boards NVMe’s are known to be shoddy, which would make sense as both my old and new board are Asus. The OP in that thread mentions using a SSD port nvme adapter to plug the 970 nvme into, and he hasn’t had a problem since (or just didnt bother to follow up months in the future).