Bugcheck Analysis: 0000000000000010, Device Driver Error

Question

Hi Guys,

My Windows 10 PC rebooted occasionally in the past few days. 

Microsoft (R) Windows Debugger Version 10.0.22621.1778 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\071223-20734-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff80674000000 PsLoadedModuleList = 0xfffff80674c2a350

Debug session time: Wed Jul 12 22:28:30.726 2023 (UTC + 9:00)

System Uptime: 0 days 0:02:04.532

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.................................

Loading User Symbols

Loading unloaded module list

.............

For analysis of this file, run !analyze -v

7: 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: ffffb40fdd3a1028, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: ffffb40fc5e16b5c

Arg4: ffffb40fc5e0b1a0

Debugging Details:

---

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4281 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 45476 

Key  : Analysis.Init.CPU.mSec 

Value: 2952 

Key  : Analysis.Init.Elapsed.mSec 

Value: 99444 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 94 

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Timestamp 

Value: 2019-12-06T14:06:00Z 

Key  : WER.OS.Version 

Value: 10.0.19041.1 

FILE_IN_CAB: 071223-20734-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffb40fdd3a1028

BUGCHECK_P3: ffffb40fc5e16b5c

BUGCHECK_P4: ffffb40fc5e0b1a0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffff8006e8b38388 fffff806745b9a1c : 0000000000000124 0000000000000010 ffffb40fdd3a1028 ffffb40fc5e16b5c : nt!KeBugCheckEx

ffff8006e8b38390 fffff806745ba579 : ffffb40fd8776610 ffffb40fd8776610 ffffb40fc5e16b30 ffffb40fd13a0128 : nt!WheaReportHwError+0x3ec

ffff8006e8b38470 fffff806745ba695 : 0000000000000000 0000000000000062 ffffb40fd8776610 0000000000000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9

ffff8006e8b384a0 fffff80676643831 : 0000000000000000 ffff8006e8b386c0 ffffb40fc5e0b1a0 ffffb40fc5e100ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5

ffff8006e8b38500 fffff8067663cc10 : 0000000000000000 ffffb40fc5e0b1a0 ffffb40fc5eb91a0 0000000000000000 : storport!StorpWheaReportError+0x9d

ffff8006e8b38590 fffff8067660f0bc : fffff80676669000 0000000000000062 0000000000000000 ffff8006e8b38930 : storport!StorpMarkDeviceFailed+0x358

ffff8006e8b38820 fffff806766cb57d : 0000000000000100 ffffb40fc5e10020 0000000000000000 0000000000000000 : storport!StorPortNotification+0x91c

ffff8006e8b388f0 fffff806766ce78e : ffffb40fc1000002 0000000000000000 ffffb40fc5e10020 0000000000000003 : stornvme!ControllerReset+0x1a1

ffff8006e8b38970 fffff806766cd6ef : ffffb40fc5e10020 ffffb40fc5e0b050 ffffb40fd84df490 8000000000002000 : stornvme!NVMeControllerReset+0x10a

ffff8006e8b389a0 fffff8067663a306 : ffffb40fd84df490 ffffb40fc5e0b050 ffffb40fcabac040 ffffb40fc48b5c60 : stornvme!NVMeControllerAsyncResetWorker+0x3f

ffff8006e8b389d0 fffff80674243f85 : ffffb40fd6e6c130 ffffb40fd6e6c130 ffffb40fc5e0b050 fffff8068a985440 : storport!StorPortWorkItemRoutine+0x46

ffff8006e8b38a00 fffff8067428e5c5 : ffffb40fc5dea080 ffffb40fc5dea080 fffff80674243e50 0000000000000000 : nt!IopProcessWorkItem+0x135

ffff8006e8b38a70 fffff806743268f5 : ffffb40fc5dea080 0000000000000080 ffffb40fc48ab1c0 000fa4efbd9bbfff : nt!ExpWorkerThread+0x105

ffff8006e8b38b10 fffff80674404c68 : fffff8066f277180 ffffb40fc5dea080 fffff806743268a0 0000000000000000 : nt!PspSystemThreadStartup+0x55

ffff8006e8b38b60 0000000000000000 : ffff8006e8b39000 ffff8006e8b32000 0000000000000000 0000000000000000 : 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

---

Answer 1

Your minidump files all indicate the Intel chipset drives, and related to an NVMe drive are causing your system to crash.

Go to the support page for your B460M DS3H V2 Motherboard on the manufacturers website, then from there, download and install the version of chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

Answer 2

There was a restriction I'm sorry. I shared it

https://drive.google.com/file/d/1SkqLAnfw2W2GAV-mfUzJOGzSv_yMxoYX/view?usp=drivesdk

Answer 3

I tried to download your file(s) from Google Drive, but they are not shared, please try sharing them again, also I sent a share request on Google Drive, that may be in your Email.

Please let me know here when they are shared.

Answer 4

https://drive.google.com/file/d/1SkqLAnfw2W2GAV-mfUzJOGzSv_yMxoYX/view?usp=drivesdk

Answer 5

Hi 상헌 이1,

I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.