Volmgr 161 + WHEA

Had a late change of plans, but will do so once I’m back. :)

- - - Updated - - -

The value is set to 41. Data= 0x00000041 (65)

It's not that then. Lets see whether the new cables were the solution....

I've come across another one similar to yours: Question - Frequent BSODs ? | Tom's Hardware Forum

Code:

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: ffffdf0fb6fc0028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffdf0f9df3f92c
Arg4: ffffdf0fa105a1a0

......

STACK_TEXT:
ffffdc8a`5ecfa448 fffff805`049b9abc : 00000000`00000124 00000000`00000010 ffffdf0f`b6fc0028 ffffdf0f`9df3f92c : nt!KeBugCheckEx
ffffdc8a`5ecfa450 fffff805`049ba619 : ffffdf0f`b627d290 ffffdf0f`b627d290 ffffdf0f`9df3f900 ffffdf0f`b48d4378 : nt!WheaReportHwError+0x3ec
ffffdc8a`5ecfa530 fffff805`049ba735 : 00000000`00000000 00000000`00000062 ffffdf0f`b627d290 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdc8a`5ecfa560 fffff805`07843721 : 00000000`00000000 ffffdc8a`5ecfa780 ffffdf0f`a105a1a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffdc8a`5ecfa5c0 fffff805`0783cb00 : 00000000`00000000 ffffdf0f`a105a1a0 ffffdf0f`9df9c1a0 00000000`00000001 : storport!StorpWheaReportError+0x9d
ffffdc8a`5ecfa650 fffff805`0780f07c : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed+0x358
ffffdc8a`5ecfa8e0 fffff805`078cc33d : fffff805`05125440 ffffdf0f`9df96020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdc8a`5ecfa9b0 fffff805`078cf55a : ffffdf0f`00000001 00000000`c1000002 ffffdf0f`9df96020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdc8a`5ecfaa30 fffff805`078ce4af : ffffdf0f`9df96020 ffffdf0f`a105a050 ffffdf0f`b62b0340 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffdc8a`5ecfaa60 fffff805`0783a1f5 : ffffdf0f`b62b0340 ffffdf0f`a105a050 ffffdf0f`b217e040 ffffdf0f`9b8d5a60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdc8a`5ecfaa90 fffff805`04643f85 : ffffdf0f`cbb1eba0 ffffdf0f`cbb1eba0 ffffdf0f`a105a050 fffff805`2ce76af0 : storport!StorPortWorkItemRoutine+0x45
ffffdc8a`5ecfaac0 fffff805`0468e5c5 : ffffdf0f`b2341040 ffffdf0f`b2341040 fffff805`04643e50 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdc8a`5ecfab30 fffff805`047265f5 : ffffdf0f`b2341040 00000000`00000080 ffffdf0f`9b8c4080 ffff98fb`88600000 : nt!ExpWorkerThread+0x105
ffffdc8a`5ecfabd0 fffff805`048048d8 : ffffa900`b4040180 ffffdf0f`b2341040 fffff805`047265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffdc8a`5ecfac20 00000000`00000000 : ffffdc8a`5ecfb000 ffffdc8a`5ecf4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

This one is almost certainly a power problem I think. The user only complains about BSODs in certain games. They are running an Radeon RTX 6750XT graphics card on a 650W PSU. The AMD site for that card recommends a minimum 650W PSU. I reckon the odd GPU power spikes in some games is overloading the PSU causing power issues on the board.

I'm hoping the lack of news from you is good news....?

It’s good news so far! No issues or crashes since changing the GPU cables. Definitely not going to consider it solved for quite some time, but I appreciate your constant help and support my friend! I looked excitedly for your replies every morning- means a lot!

Could you do me a favour please and run the V2 log collector again and upload the zip file?

DESKTOP-31HHLHG-(2023-06-02_13-49-54).zip - Google Drive

Thanks as always!

1)Report any hangs or freezes.


2) Run: chkdsk /b /v C:

Run overnight while sleeping.


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: y

Reboot.


3) Run:

https://www.tenforums.com/attachment...p_plus_log.bat

https://www.tenforums.com/attachment...iskparinfo.bat

https://www.tenforums.com/attachment...kfromevent.bat

parallelpark said:

Well… it had been about a month or so since our last issue, and naturally I got confident and was excited to inform you. However, I just received the same blue screen-

WHEA uncorrectable error. This time, it did get to 100% so I should have the dmp file. I will upload once I’m home (my brother facetimed me my computer screen). Here are the codes for the time being:

0x0000000000000010
0xFFFFBB8FAB06B028
0xFFFFBB8F8FE66AAC
OXFFFFBB8F8FEDDIAO


Follow up:

Here's that dmp file results. Please let me know what you think, and thanks as always-

************* 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`7c200000 PsLoadedModuleList = 0xfffff800`7ce2a2d0
Debug session time: Mon Jul 3 15:54:35.739 2023 (UTC - 7:00)
System Uptime: 0 days 7:35:25.357
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`7c5fc030 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffce05`94faf390=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: ffffbb8fab06b028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffbb8f8fe66aac
Arg4: ffffbb8f8fedd1a0

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

Key : Analysis.Elapsed.mSec
Value: 5387

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

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

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

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

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

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

BUGCHECK_P3: ffffbb8f8fe66aac

BUGCHECK_P4: ffffbb8f8fedd1a0

FILE_IN_CAB: MEMORY.DMP

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffce05`94faf388 fffff800`7c7b9a1c : 00000000`00000124 00000000`00000010 ffffbb8f`ab06b028 ffffbb8f`8fe66aac : nt!KeBugCheckEx
ffffce05`94faf390 fffff800`7c7ba579 : ffffbb8f`aa5c5410 ffffbb8f`aa5c5410 ffffbb8f`8fe66a80 ffffbb8f`a9b58378 : nt!WheaReportHwError+0x3ec
ffffce05`94faf470 fffff800`7c7ba695 : 00000000`00000000 00000000`00000062 ffffbb8f`aa5c5410 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffce05`94faf4a0 fffff800`81273831 : 00000000`00000000 ffffce05`94faf6c0 ffffbb8f`8fedd1a0 ffffbb8f`8fde70ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffce05`94faf500 fffff800`8126cc10 : 00000000`00000000 ffffbb8f`8fedd1a0 ffffbb8f`940c71a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffce05`94faf590 fffff800`8123f0bc : fffff800`81299000 00000000`00000062 00000000`00000000 ffffce05`94faf930 : storport!StorpMarkDeviceFailed+0x358
ffffce05`94faf820 fffff800`812fc2bd : 00000000`00000100 ffffbb8f`8fde7020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
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
ffffce05`94fafa00 fffff800`7c48e5c5 : ffffbb8f`ab43c040 ffffbb8f`ab43c040 fffff800`7c443e50 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffce05`94fafa70 fffff800`7c5268f5 : ffffbb8f`ab43c040 00000000`00000080 ffffbb8f`8e0960c0 ffffbb8f`9f764c80 : nt!ExpWorkerThread+0x105
ffffce05`94fafb10 fffff800`7c604c68 : ffff8501`534e5180 ffffbb8f`ab43c040 fffff800`7c5268a0 fffff800`7c828662 : nt!PspSystemThreadStartup+0x55
ffffce05`94fafb60 00000000`00000000 : ffffce05`94fb0000 ffffce05`94fa9000 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
---------

Highlighted relevant portions. Its complaining about your nvme

Thank you for the response. Would you say this was a "it happens" error and shouldn't be a frequent occurrence (and more importantly, not related to all the past issues?) The NVMe is good quality, newer, tested, swaptested, etc.