Windows 10: Help with BSOD dumpfile analysis

Hi Community,


For several months I have been having intermittent BSOD issues. Today, my computer finally generated a dump file. Every other time the system has crashed, it displays the blue screen for less than a second and crashes without generating a dump file. For the older crashes, the bugcheck code was 292 with an event ID of 41.

For this crash, I have a bugcheck code of 124 from the dump file with even viewer showing 292/41 still. It sounds like this is a hardware issue. I've run memcheck for several hours to test ram as well as stress testing CPU and PSU and such and I've had no crashes or errors from this process. Perhaps I need to run tests longer.


Below, I have placed the content of the dump file analysis. Module_name: authenticAMD makes me think it's a CPU problem, but the CPU could be trying to access bad memory in main storage or RAM, so it's hard to tell. I'm not too familiar with hardware stuff nor this file format and was hoping someone might have some advice on further debugging, or can pull any useful information off this dump.


Thanks in advance!




2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************WHEA_UNCORRECTABLE_ERROR 124A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.Arguments:Arg1: 0000000000000010, Error Source TypeArg2: ffffdf82c48ad028Arg3: ffffdf82b6397aacArg4: ffffdf82b64911a0Debugging Details:------------------fffff80563a0f340: Unable to get Flags value from nt!KdVersionBlock*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 7311 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-JRDPG10 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 9754 Key : Analysis.Memory.CommitPeak.Mb Value: 87 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 124BUGCHECK_P1: 10BUGCHECK_P2: ffffdf82c48ad028BUGCHECK_P3: ffffdf82b6397aacBUGCHECK_P4: ffffdf82b64911a0BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffba84`ea659488 fffff805`633b4cbc : 00000000`00000124 00000000`00000010 ffffdf82`c48ad028 ffffdf82`b6397aac : nt!KeBugCheckExffffba84`ea659490 fffff805`633b5819 : ffffdf82`c90db590 ffffdf82`c90db590 ffffdf82`b6397a80 ffffdf82`c2519378 : nt!WheaReportHwError+0x3ecffffba84`ea659570 fffff805`633b5935 : 00000000`00000000 00000000`00000062 ffffdf82`c90db590 00000000`00040246 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9ffffba84`ea6595a0 fffff805`66440fe5 : 00000000`00000000 ffffba84`ea6597c0 ffffdf82`b64911a0 00000000`00000000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5ffffba84`ea659600 fffff805`6643a450 : 00000000`00000000 ffffdf82`b64911a0 ffffdf82`b64961a0 00000000`00000000 : storport!StorpWheaReportError+0x9dffffba84`ea659690 fffff805`66420b90 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffdf82`b6438020 : storport!StorpMarkDeviceFailed+0x358ffffba84`ea659920 fffff805`663c9fcd : 00000000`00000500 ffffdf82`b6438020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x139a0ffffba84`ea6599f0 fffff805`663cd14a : ffffdf82`c1000002 00000000`00000000 ffffdf82`b6438020 00000000`00000003 : stornvme!ControllerReset+0x1a1ffffba84`ea659a70 fffff805`663cc0cf : ffffdf82`b6438020 ffffdf82`b6491050 ffffdf82`c8b23960 80000000`00002000 : stornvme!NVMeControllerReset+0x10affffba84`ea659aa0 fffff805`66437ba0 : ffffdf82`c8b23960 ffffdf82`b6491050 ffffdf82`c0a6e040 ffffdf82`b2c6a260 : stornvme!NVMeControllerAsyncResetWorker+0x3fffffba84`ea659ad0 fffff805`6301aad5 : ffffdf82`c7310420 ffffdf82`c7310420 ffffdf82`b6491050 fffff805`70f45d20 : storport!StorPortWorkItemRoutine+0x40ffffba84`ea659b00 fffff805`631034b5 : ffffdf82`c2d52040 ffffdf82`c2d52040 fffff805`6301a9a0 00000000`00000000 : nt!IopProcessWorkItem+0x135ffffba84`ea659b70 fffff805`630a29a5 : ffffdf82`c2d52040 00000000`00000080 ffffdf82`b2ca5040 00000000`00000000 : nt!ExpWorkerThread+0x105ffffba84`ea659c10 fffff805`631fc868 : ffffcf00`8eb36180 ffffdf82`c2d52040 fffff805`630a2950 00000000`00000246 : nt!PspSystemThreadStartup+0x55ffffba84`ea659c60 00000000`00000000 : ffffba84`ea65a000 ffffba84`ea654000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28MODULE_NAME: AuthenticAMDIMAGE_NAME: AuthenticAMD.sysSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0x124_10_AuthenticAMD_IMAGE_AuthenticAMD.sysOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {ece6babd-57c0-a970-9089-3f33001893be}Followup: MachineOwner---------

:)

 

BSoD Analysis request

No dump file is created despite that I followed the instructions in this link:

How to read dumpfiles after a blue screen of death

But the BSoD says it is "tvalz_o.sys"

Thank you for the quick response

 

BSOD MEMORY_MANAGEMENT Help with Analysis

Hello, i've been getting frequent BSOD crashes under the error code mem_management so I did a driver test with CMD, followed the steps and upon startup it kept crashing. I booted into safe mode to extract the minidump files and i've uploaded the latest 3
dmp files into this onedrive link. https://onedrive.live.com/?auth=1&id=root&cid=313D8B7743649D11

Would appreciate some help with figuring out which driver is causing me issues, so I can update it and get on with my BSOD free life. THANKS!!!

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks