Volmgr 161 + WHEA

I didn't check that link, but now I have. That's interesting, I'll probably avoid an Asus board for my next build!

Well that was short-lived. Got the adapter installed, worked for about an hour and then same WHEA crash... I would assume the dumpfile would have to look at least a little different though..? Attaching all info just in case. Hopefully there is some new info in there. I still have the WD drive plugged into the second NVMe slot on the board, but from what we've been seeing it was the main Samsung NVME that was included in the dump.


************* 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.141 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 = 0xfffff800`48400000 PsLoadedModuleList = 0xfffff800`4902a2d0
Debug session time: Sat Jul 15 13:50:54.934 2023 (UTC - 7:00)
System Uptime: 0 days 1:06:33.537
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`487fc0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8307`2f0a7390=0000000000000124
15: 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: ffffd18a5b0e3028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffd18a4086692c
Arg4: ffffd18a408b41a0

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: 2843

Key : Analysis.Elapsed.mSec
Value: 2933

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

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

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

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

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

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

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: ffffd18a5b0e3028

BUGCHECK_P3: ffffd18a4086692c

BUGCHECK_P4: ffffd18a408b41a0

FILE_IN_CAB: MEMORY.DMP

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8307`2f0a7388 fffff800`489b9a8c : 00000000`00000124 00000000`00000010 ffffd18a`5b0e3028 ffffd18a`4086692c : nt!KeBugCheckEx
ffff8307`2f0a7390 fffff800`489ba5e9 : ffffd18a`5eed8690 ffffd18a`5eed8690 ffffd18a`40866900 ffffd18a`5dcc8328 : nt!WheaReportHwError+0x3ec
ffff8307`2f0a7470 fffff800`489ba705 : 00000000`00000000 00000000`00000062 ffffd18a`5eed8690 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffff8307`2f0a74a0 fffff800`4dc63831 : 00000000`00000000 ffff8307`2f0a76c0 ffffd18a`408b41a0 ffffd18a`408b10ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffff8307`2f0a7500 fffff800`4dc5cc10 : 00000000`00000000 ffffd18a`408b41a0 ffffd18a`407e71a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffff8307`2f0a7590 fffff800`4dc2f0bc : fffff800`4dc89000 00000000`00000062 00000000`00000000 ffff8307`2f0a7930 : storport!StorpMarkDeviceFailed+0x358
ffff8307`2f0a7820 fffff800`4dceb57d : 00000000`00000100 ffffd18a`408b1020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffff8307`2f0a78f0 fffff800`4dcee78e : ffffd18a`c1000002 00000000`00000000 ffffd18a`408b1020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffff8307`2f0a7970 fffff800`4dced6ef : ffffd18a`408b1020 ffffd18a`408b4050 ffffd18a`54eeac90 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffff8307`2f0a79a0 fffff800`4dc5a306 : ffffd18a`54eeac90 ffffd18a`408b4050 ffffd18a`3ede9040 ffffd18a`3eb12a20 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffff8307`2f0a79d0 fffff800`48643fa5 : ffffd18a`5ea666e0 ffffd18a`5ea666e0 ffffd18a`408b4050 fffff800`61e35e70 : storport!StorPortWorkItemRoutine+0x46
ffff8307`2f0a7a00 fffff800`4868e5c5 : ffffd18a`5238f040 ffffd18a`5238f040 fffff800`48643e70 ffffd18a`00000000 : nt!IopProcessWorkItem+0x135
ffff8307`2f0a7a70 fffff800`48726915 : ffffd18a`5238f040 00000000`00000080 ffffd18a`3eb02080 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105
ffff8307`2f0a7b10 fffff800`48804cf8 : ffffc181`d9889180 ffffd18a`5238f040 fffff800`487268c0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8307`2f0a7b60 00000000`00000000 : ffff8307`2f0a8000 ffff8307`2f0a1000 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
---------

apps+sys.zip - Google Drive apps+sys
DESKTOP-31HHLHG-(2023-07-15_13-59-12).zip - Google Drive V2 Log collector

The BSOD is for exactly the same reasons as before, so nothing new there. Whilst trawling your System log however I noticed the load of a driver called gameflt.sys, this is a Microsoft driver that's loaded by default as part of the XBox driver package. It's called the Microsoft Gaming Install Filter Driver and if you have an XBox connected then you probably need this driver. However, I have seen (on other fora) that this driver does cause BSODs in some circumstances. I've never ever seen it cause a 0x124 bugcheck but there is a first time for everything.

If you're up for it we can remove that driver (if you're not using an XBox) and see whether it makes any difference? If you're up for this lets start by confirming that gameflt.sys is loaded. Open an elevated command prompt or PowerShell session, enter the following command, and copy the output into your next post...

Code:

fltmc filters

When you say "using an xbox," I do have an xbox, but it's not connected to my PC. What IS connected to my PC however is the xbox app in which I'm logged into. Happy to remove that driver (or just uninstall the xbox app fully as well) to see if that'll make a difference.

I connected with someone via reddit last night that dealt with all the same things i have been for quite some time as well, and he was able to fully fix it by disabling hardware acceleration in chrome, steam, discord, etc. I've done the same to see if that helps.

- - - Updated - - -

C:\Windows\system32>fltmc filters

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
bindflt 1 409800 0
WdFilter 7 328010 0
storqosflt 0 244000 0
wcifs 1 189900 0
gameflt 4 189850 0
CldFlt 0 180451 0
FileCrypt 1 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
Wof 4 40700 0
FileInfo 7 40500 0

C:\Windows\system32>

Looks like gameflt is loaded, just restarted to make sure as well. What's our next step captain?

- - - Updated - - -

Oh before I forget, a completely and totally separate question but perhaps y'all have some insight on this:

I have a triple monitor setup with a folder of wallpapers that spans across the setup, looks really nice. However, and this only started a few months ago- on startup, the wallpaper just duplicates across the three monitors rather than extending. I can easily fix this my going into display settings, changing any one of the monitor settings, then revert back and it fixes it until the next power on. Any thoughts on this?

Hardware acceleration often causes issues, especially in browsers. The other thing in browsers to watch out for are extensions. A badly coded browser extension can cause BSODs. The way to test is to start the browser without any extensions loaded (Google how to do that).

I can't help much with the monitor issue, but I also don't believe in coincidences. That you have 0x124 BSODs and a display issue could well be related. What changed "a few months" ago when that started?

I don't have an XBox and consequently know less than nothing about using one. What is the XBox app you're logged into, and why if the XBox isn't plugged in to the PC?

I'm not sure that uninstalling the XBox app will uninstall the gameflt.sys driver. It's a core component of Windows now.

I also firmly believe in changing one thing at a time, so let's see whether disabling hardware acceleration helps. If not, then come back and we'll see about uninstalling gameflt.sys (and the XBox app).

Will do- I had no crashes yesterday after disabling hardware acceleration on as many apps I could find it enabled as an option.

So with the xbox app, microsoft store has an app for xbox, which basically allows you to voice chat, message, add friends… basically gives you the whole ecosystem of Xbox’s social side but on a PC. Sometimes my friends and I will use this space for voice chat while playing a separate game like Apex on the PC.

My Xbox is plugged into my big TV, so there’s no way of touching the xbox app with the physical xbox.

I am not sure what changed a few months ago, I’m thinking could’ve been some random windows auto-update, but apparently this is a common issue across windows as well.

I’m leaning toward these two issues not being related at all, considering I’ve been dealing with this for 3+ years and this display thing only started a few months ago

- - - Updated - - -

Update, just crashed :/ same thing as always.

However, I'm now getting this error on startup, and when I set the preference to system managed and then restart, it gives me the same prompt again and says it's shows it not selected as system managed:

IMG_0045.jpg - Google Drive

Well it's been over a couple months now, and am moving out in less than a week. It has also been one month officially since my last BSOD, and wanted to give y'all an update.

I ended up getting another SSD, same exact samsung 970 evo off Amazon (to replace the new one I bought from Best buy.. to replace the original one), and haven't had a crash since. I can't say I'm ecstatic about all the time more or less wasted thereafter changing the SSD the first time and writing that off as not the issue, but I guess (if in fact this solved it, which I'm 60% sure it did at this point) it just goes to show that certain parts have a decent chance at being faulty multiple times over, even if Samsung Magician and the like shows otherwise. I'm happy to see what I believe to be the solution before having moved and possibly brought in a multitude of unexpected issues. I appreciate you for the taking the time and going on this journey with me- 18 pages has got to be close to a record, no? XD Thanks again, and in the nicest way, I hope I don't have to come back to this thread in the future, haha! God bless.

Fingers crossed for you then. The dumps certainly pointed at the NVMe drive but I too am surprised it took three attempts to find a good one. Best hold off on buying a lottery ticket for a while! 🤣

Best of luck with the upcoming move.

Happy Holidays and guess who’s back?!? Hello to my favorite support team. I am sad to report the exact same error is back “WHEA Uncorrectable error” and seemingly came out of nowhere. Funny enough, it had been good for a handful of months now (6 months?) and my dad asked me about it and the very next day it bluescreened. I haven’t done the steps you all need me to do to get a proper diagnostic to you, so if you wouldn’t mind letting me know what to do, I’d be happy to get those files to you ASAP. Thanks for all you do and hopefully this is a quicker fix this time around.

- - - Updated - - -

I’d like to add every time I boot up my computer, I get a command box that goes away by itself after ten seconds that says “try our new windows powershell”

Just commenting again to bump my response. Hopefully you guys are able to assist once again. Thanks either way!