Question Bsod on super simple games

Jan 11, 2020
8
0
10
0
Hello everyone,

I had multiple BSOD's before but i was able to solve them all except now I get multiple different types of bsods only when playing super easy to run games. Things such as a new game called TemTem, another game called Legend of Keepers: Prologue. I can play PUBG, Hunt Showdown, Monster Legends, Black Desert, Modern Warfare, Apex Legends, League of Legends, Divinity 2, and tons more without any issues so it's very very confusing. I can and I did play 4 days without a single bsod until trying to play a super simple pixelated game. Anyway, I have tons of dump files but this one was the most recent.

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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9a0466753028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9a0466753028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 10

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: Discord.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-SOCFDQI

ANALYSIS_SESSION_TIME: 01-22-2020 05:13:54.0986

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT:
ffffda8010cecd78 fffff8064dcfdfe8 : 0000000000000124 0000000000000000 ffff9a0466753028 00000000be000000 : nt!KeBugCheckEx
ffffda8010cecd80 fffff80651781920 : ffff9a0462242600 0000000000000000 ffff9a0466753028 0000000000000000 : hal!HalBugCheckSystem+0xd8
ffffda8010cecdc0 fffff8064d540952 : ffff9a0462242600 ffffda8010cece49 0000000000000000 ffff9a0466753028 : PSHED!PshedBugCheckSystem+0x10
ffffda8010cecdf0 fffff8064dcff946 : ffffda8010cecf10 0000000000000005 ffff9a0462242650 ffff9a0462242600 : nt!WheaReportHwError+0x382
ffffda8010ceceb0 fffff8064dcffdda : 0000000000000010 ffff9a0462242650 ffffda8010ced068 ffffda8010ced2b0 : hal!HalpMcaReportError+0x72
ffffda8010ced010 fffff8064dcffcb4 : ffff9a0461ae67c0 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xf2
ffffda8010ced060 fffff8064dcfff20 : 0000000000000010 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xe0
ffffda8010ced0a0 fffff8064dcfefc8 : 0000000000000000 ffffda8010ced330 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffda8010ced0d0 fffff8064dd001a7 : ffff9a0461ae67c0 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffffda8010ced100 fffff8064d4a4a20 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffffda8010ced130 fffff8064d3d04ba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x10
ffffda8010ced160 fffff8064d3d0171 : 0000000000000000 fffff8064d3d00ae 000000000ee51a01 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffda8010ced2a0 fffff8064d2fca55 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x271
fffffd863173ef50 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxSetTimeStampBusy+0x35


THREAD_SHA1_HASH_MOD_FUNC: b6525ded3827a37d0ee6e80d89f5fe0ddf74426b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 980db832682eabebfd45cff53afba12ede57c766

THREAD_SHA1_HASH_MOD: 2e7aa506b46de331baac28a574c338764f2697af

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

TARGET_TIME: 2020-01-22T13:11:35.000Z

OSBUILD: 18362

OSSERVICEPACK: 592

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: 1972-08-21 17:24:00

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 9ce

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae_internal_timer

FAILURE_ID_HASH: {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

Followup: MachineOwner
---------
 
Jan 11, 2020
8
0
10
0
Are you using intel hd video when playing games? It is a cpu error report not software.
So I went in to Nvidia Control Panel and ensured that the programs were added and using the video card. After doing so I started up one of the games and got this dump.


SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8025563638b, Address of the instruction which caused the bugcheck
Arg3: ffffc580ea3ba930, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8025563638b

BUGCHECK_P3: ffffc580ea3ba930

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
nt!KeDelayExecutionThread+44b
fffff8025563638b 450fb6cc movzx r9d,r12b

CONTEXT: ffffc580ea3ba930 -- (.cxr 0xffffc580ea3ba930)
rax=0000000000000000 rbx=ffffa807bffc9080 rcx=ffffa807bffc9080
rdx=ffffb808e13cfa10 rsi=0000000000000001 rdi=0000000000000000
rip=fffff8025563638b rsp=ffffb808e13cf950 rbp=ffffb808e13cfa80
r8=ffffb808e13cfa01 r9=ffffb808e13cf988 r10=0000000000000000
r11=00000000001c6550 r12=0000000000000001 r13=0000000000000001
r14=0000000007bafd60 r15=0000000077033620
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nt!KeDelayExecutionThread+0x44b:
fffff802
5563638b 450fb6cc movzx r9d,r12b
Resetting default scope

BUGCHECK_STR: 0x3B_c0000005

CPU_COUNT: 10

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: LegendOfKeepersPrologue.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-SOCFDQI

ANALYSIS_SESSION_TIME: 01-22-2020 08:49:19.0738

ANALYSIS_VERSION: 10.0.18362.1 x86fre

BAD_STACK_POINTER: ffffc580ea3b9ff8

LAST_CONTROL_TRANSFER: from fffff80255beb1bf to fffff8025563638b

STACK_TEXT:
ffffb808e13cf950 fffff80255beb1bf : ffffa807bffc9080 ffffa807c1013fe0 ffffb808e13cfa10 0000000000000001 : nt!KeDelayExecutionThread+0x44b
ffffb808e13cf9d0 fffff802557d2d15 : ffffa807bffc9080 0000000000000001 0000000000000000 0000000000000000 : nt!NtDelayExecution+0x5f
ffffb808e13cfa00 0000000077031cbc : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
0000000007aaecb8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77031cbc


THREAD_SHA1_HASH_MOD_FUNC: 1466b3bc52dbc9ec0ce08795306a99aaa4848cfd

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: cbecbfbc03b3b08ae66eb4e3b238f2438404f408

THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:
nt!KeDelayExecutionThread+44b
fffff802`5563638b 450fb6cc movzx r9d,r12b

FAULT_INSTR_CODE: ccb60f45

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KeDelayExecutionThread+44b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4f6eba0

IMAGE_VERSION: 10.0.18362.592

STACK_COMMAND: .cxr 0xffffc580ea3ba930 ; kb

BUCKET_ID_FUNC_OFFSET: 44b

FAILURE_BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KeDelayExecutionThread

BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KeDelayExecutionThread

PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_STACKPTR_ERROR_nt!KeDelayExecutionThread

TARGET_TIME: 2020-01-22T16:47:10.000Z

OSBUILD: 18362

OSSERVICEPACK: 592

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: 1972-08-21 17:24:00

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 9ca

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_c0000005_stackptr_error_nt!kedelayexecutionthread

FAILURE_ID_HASH: {101087e3-2714-2191-e17a-21ec0f3254ab}

Followup: MachineOwner
 
Try uninstalling all of your Nvidia gpu drivers nad reinstalling the newset ones for your card. Also try pullng out gpu card and reseating it. Do this with your memory sticks too. If none of this works, try using only one memory stick at a time when starting up your pc and using it, and then repeat with the other stick/s.
 
Jan 11, 2020
8
0
10
0
Try uninstalling all of your Nvidia gpu drivers nad reinstalling the newset ones for your card. Also try pullng out gpu card and reseating it. Do this with your memory sticks too. If none of this works, try using only one memory stick at a time when starting up your pc and using it, and then repeat with the other stick/s.
Hey man! just wanted to inform you that i was able to fix my issue. Turns out even tho my motherboard read as updated it actually wasn't when i was viewing it in system information. Once I updated the BIOS I have had a BSOD in almost 3 days! Just wanted to stop by and say thank you for taking the time out of your day to help! Have a good one!
 

ASK THE COMMUNITY