Windows 10 Windows 10 BSOD

  • Thread starter Thread starter KennHerzler
  • Start date Start date
K

KennHerzler

Guest
I've been experiencing multiple BSOD conditions, and I'm struggling to figure out why. Here's a dmp file:

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


Loading Dump File [C:\Users\kennh\Downloads\080819-25078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Unable to load image Unknown_Module_66db3961`813a98cd, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_66db3961`813a98cd
Debugger can not determine kernel base address
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805`54600000 PsLoadedModuleList = 0xfffff805`54a432f0
Debug session time: Thu Aug 8 11:31:14.831 2019 (UTC - 5:00)
System Uptime: 0 days 0:42:47.597
Unable to load image Unknown_Module_66db3961`813a98cd, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_66db3961`813a98cd
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8055a684b10
Arg3: 0000000000000000
Arg4: 0000000000000000

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: fffff8055a684b10

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x9C_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: bb8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT: 1

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: AMAZINGIT-PC

ANALYSIS_SESSION_TIME: 08-08-2019 13:51:10.0346

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff805545a61f1 to fffff805547bc900

STACK_TEXT:
fffff805`5a684ad8 fffff805`545a61f1 : 00000000`0000009c 00000000`00000000 fffff805`5a684b10 00000000`00000000 : 0xfffff805`547bc900
fffff805`5a684ae0 00000000`0000009c : 00000000`00000000 fffff805`5a684b10 00000000`00000000 00000000`00000000 : 0xfffff805`545a61f1
fffff805`5a684ae8 00000000`00000000 : fffff805`5a684b10 00000000`00000000 00000000`00000000 00000000`00000000 : 0x9c


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID: CORRUPT_MODULELIST_0x9C_GenuineIntel

DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0x9C_GenuineIntel

PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0x9C_GenuineIntel

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x9C_GenuineIntel

TARGET_TIME: 2019-08-08T16:31:14.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

ANALYSIS_SESSION_ELAPSED_TIME: 2e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0x9c_genuineintel

FAILURE_ID_HASH: {86f63a57-0ca5-51f6-b043-4ec5fad73882}

Followup: MachineOwner


I've run every hardware test I can locate on memory, cpu, and gpu. The failure never happens during the testing, and I think it may have something to do with Steam. Any ideas?

Stop code is normally: Machine Check Exception

Thanks,


Kenn

More...
 
Back
Top