Win11 - NVMe crashes sinds Steam-download op 2 PCs

[dion_b]

Mijn vraag

Ik heb op meerdere PCs Windows 11 Pro draaien, waaronder die van mijn jongste zoon en mijzelf. Normaliter geheel stabiel. Een tijdje terug klaagde mijn jongste over random crashes na installeren van een of andere game. De crashes waren duidelijk en waren volgens memory dump gerelateerd aan z'n SSD - device errors in stornvme en storport. Klinkt als stervende SSD. Geen goede timing gezien prijzen, maar kan gebeuren...

...alleen heb ik zijn SSD vervangen en na enige tijd, toevallig weer na Steam actie, kreeg hij op de nieuwe SSD zelfde problemen. Ondertussen heb ik de oude SSD in een ander systeem gescanned, nul fouten gevonden en draai ik er probleemloos Linux op.

Enfin, fast-forward een paar weken. Nog geen oplossing gevonden voor zijn issues. Ik heb Steam ook geinstalleerd staan en gisteren zag ik de Steam Ukrainian Games Festival. Ik heb meerdere games tegen flinke korting gekocht: Cossacks III, Metro 2033 Redux, Panzer Strategy en Strategic Mind Spectre of Communism, en los van die actie ook nog Total War Warhammer III. Geklikt op installeren en wat Youtube-filmpjes gaan kijken in LibreWolf browser (met uBlock Origin). Na paar minuten opeens cursor niet meer responsive en bevroren video van filmpjes (terwijl audio wel door gaat). En dan blue screen.

Na reboot diagnostics gedaan en jawel, ook bij mij 'opeens' NVMe problemen. Ook na de reboot blijft het instabiel. Meest recente MEMORY.DMP, output van !analyze -v in WinDbg 1.2606.2201.0 (Administrator):

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
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.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

Primary dump contents written successfully


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff803`5e400000 PsLoadedModuleList = 0xfffff803`5f0135a0
Debug session time: Thu Aug 20 23:26:29.818 2026 (UTC + 2:00)
System Uptime: 0 days 7:18:07.661
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols

Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`5e81e230 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff40b`62594f70=0000000000000124
6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols

Loading unloaded module list
..........................
*******************************************************************************
* *
* 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: ffffad07e8304028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffad07d679892c
Arg4: ffffad07d680c1a0

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1687

Key : Analysis.Elapsed.mSec
Value: 1740

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.29617.1000

Key : Analysis.Version.Description
Value: 10.2604.29.1 amd64fre

Key : Analysis.Version.Ext
Value: 1.2604.29.1

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 0x1800

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : Failure.Bucket
Value: 0x124_16_AuthenticAMD__UNKNOWN_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {590f0c83-3219-aceb-da4c-6b8bc7c00f79}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x1497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

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

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 0x4a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7

Key : SecureKernel.HalpHvciEnabled
Value: 1

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1

Key : WER.System.BIOSRevision
Value: 5.17.0.0


BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffad07e8304028

BUGCHECK_P3: ffffad07d679892c

BUGCHECK_P4: ffffad07d680c1a0

FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1800

FAULTING_THREAD: ffffad07e8699540

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


PROCESS_NAME: System

STACK_TEXT:
fffff40b`62594f68 fffff803`5ea1081b : 00000000`00000124 00000000`00000010 ffffad07`e8304028 ffffad07`d679892c : nt!KeBugCheckEx
fffff40b`62594f70 fffff803`5ea11343 : ffffad07`d6767110 ffffad07`d6767110 ffffad07`d6798900 fffff40b`625950a0 : nt!WheaReportHwError+0x37b
fffff40b`62595040 fffff803`5ea11465 : 00000000`00000000 00000000`000000ba ffffad07`d6767110 ffffad07`d6858000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xf3
fffff40b`62595070 fffff803`623b0988 : fffff40b`625952b0 fffff40b`625952b0 ffffad07`d680c050 00000000`00000001 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
fffff40b`625950d0 fffff803`623aa0c3 : 00000000`00000000 00000000`00000000 ffffad07`d680c1a0 00000000`00000000 : storport!StorpWheaReportError+0xb8
fffff40b`62595160 fffff803`6238ce3c : ffffad07`000003e8 00000000`00000000 00000000`00000000 ffffad07`d67ec010 : storport!StorpMarkDeviceFailed+0x3ff
fffff40b`62595410 fffff803`6248dd48 : ffffad07`d67ec010 ffffad07`d67ec010 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x1e3dc
fffff40b`625954e0 fffff803`6248e6c5 : ffffad07`d67ec010 ffffad07`d67ec010 fffff40b`62595820 fffff40b`62595820 : stornvme!NVMeControllerInitPart2+0x2a8
fffff40b`625955e0 fffff803`6248869a : ffffad07`d680c1a0 ffffad07`d67ec010 fffff40b`62595820 fffff803`6237d46b : stornvme!NVMeControllerReset+0x145
fffff40b`625956f0 fffff803`623980db : 00000000`c0000010 ffffad07`d68751a0 ffffad07`e4dc2160 00000000`00000000 : stornvme!NVMeHwResetBus+0x1a
fffff40b`62595720 fffff803`623c1e5c : ffffad07`d68751a0 ffffad07`d68751a0 00000000`c0000010 ffffad07`d68751b8 : storport!RaidAdapterResetBus+0x18b
fffff40b`62595880 fffff803`623c0efa : ffffad07`e69443a0 ffffad07`d68758d0 ffffad07`e69443a0 ffffad07`e69443a0 : storport!RaidUnitHierarchicalReset+0x108
fffff40b`62595940 fffff803`5e71e5d0 : ffffad07`e69443a0 00000000`00000000 ffffad07`d6875050 00000000`00000000 : storport!RaidHierarchicalResetWorkRoutine+0x8a
fffff40b`62595990 fffff803`5e6becb5 : ffffad07`d3f52c50 ffffad07`e8699540 fffff40b`62595b00 00000000`00000000 : nt!IopProcessWorkItem+0x100
fffff40b`62595a00 fffff803`5e70bbf7 : ffffad07`e8699540 00000000`000003cc ffffad07`e8699540 fffff803`5e6beb60 : nt!ExpWorkerThread+0x155
fffff40b`62595bf0 fffff803`5e8233a4 : ffff8880`9a051180 ffffad07`e8699540 fffff803`5e70bba0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff40b`62595c40 00000000`00000000 : fffff40b`62596000 fffff40b`62590000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .process /r /p 0xffffad07d3ef0040; .thread /r /p 0xffffad07e8699540 ; kb

FAILURE_BUCKET_ID: 0x124_16_AuthenticAMD__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {590f0c83-3219-aceb-da4c-6b8bc7c00f79}

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

Jawel. stornvme en storport in de STACK_TEXT.

Exact zelfde symptomen als bij mijn zoontje. Zelfde trigger: games installeren via Steam. En weer een NVMe-schijf die nul SMART errors heeft en ook met chksdsk etc geen problemen geeft.

Kan zijn dat het puur toeval is en we allebei een stealthily stervende SSD hebben, maar ik ruik een Windows <-> Steam softwareissue.

Iemand een suggestie hoe verder te kijken?


Relevante software en hardware die ik gebruik
Win11 Pro, 23H2 22631.
6199 Windows Feature Experience Pack 1000.22700.1108.0

Mijn PC:
Asus TUF Gaming B550M-Plus moederbord (AMD B550 chipset en dus NVME)
AMD Ryzen 5 3600 CPU
Kingston SKC2500M81000G 1TB NVMe SSD

Zoonlief:
MSI H270 Moederbord (Intel H270 chipset en NVMe)
Intel Core i5-7500 CPU
Samsung NVMe SSD

(verschillende storage drivers dus)


Wat ik al gevonden of geprobeerd heb

Event viewer gechecked
- meldingen van onverwachte reboots (no shit...)
- verder alleen qua critical errors dat Google Chrome updater een bestand niet kon vinden
Windbg gedraaid en analyse laten doen
Nieuwste drivers van Asus.com gehaald voor moederbord chipset (waaronder storage).