Windows 10: Need help understanding a crash report

I've never used these online forums before and I'm not sure how to go about asking for help but my windows has been crashing a lot lately and I have updated all my drivers, factory reset the system, and I think i may have a faulty cpu or motherboard. To my knowledge I have not overclocked my system and I am wondering if i can get some help here. Below is the minidump report from windows debugger of how my system crashed this morning. If i am not wrong it says that my cpu is at fault here correct?




Microsoft R Windows Debugger Version 10.0.18362.1 X86

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\042820-39859-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 18362 MP 16 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff807`5be00000 PsLoadedModuleList = 0xfffff807`5c248150

Debug session time: Tue Apr 28 11:44:07.054 2020 UTC - 6:00

System Uptime: 1 days 1:46:46.672

Loading Kernel Symbols

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

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

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

.....

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

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

WHEA_ERROR_RECORD structure that describes the error conditon.

Arguments:

Arg1: 0000000000000000, Machine Check Exception

Arg2: ffff8f8fb2206028, Address of the WHEA_ERROR_RECORD structure.

Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000070005, 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



SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.



SYSTEM_PRODUCT_NAME: X299 AORUS Gaming 7



SYSTEM_SKU: Default string



SYSTEM_VERSION: Default string



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: F7



BIOS_DATE: 09/14/2017



BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.



BASEBOARD_PRODUCT: X299 AORUS Gaming 7



BASEBOARD_VERSION: x.x



DUMP_TYPE: 2



BUGCHECK_P1: 0



BUGCHECK_P2: ffff8f8fb2206028



BUGCHECK_P3: b2000000



BUGCHECK_P4: 70005



BUGCHECK_STR: 0x124_GenuineIntel



CPU_COUNT: 10



CPU_MHZ: e10



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 55



CPU_STEPPING: 4



CPU_MICROCODE: 6,55,4,0 F,M,S,R SIG: 200004D'00000000 cache 200004D'00000000 init



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: chrome.exe



CURRENT_IRQL: f



ANALYSIS_SESSION_HOST: DESKTOP-21O5S9I



ANALYSIS_SESSION_TIME: 04-28-2020 12:02:13.0614



ANALYSIS_VERSION: 10.0.18362.1 x86fre



STACK_TEXT:

ffffb780`a214cd58 fffff807`5c8ff188 : 00000000`00000124 00000000`00000000 ffff8f8f`b2206028 00000000`b2000000 : nt!KeBugCheckEx

ffffb780`a214cd60 fffff807`5f981920 : ffff8f8f`ac0f2940 00000000`00000000 ffff8f8f`b2206028 00000000`00000000 : hal!HalBugCheckSystem+0xd8

ffffb780`a214cda0 fffff807`5c141072 : ffff8f8f`ac0f2940 ffffb780`a214ce29 00000000`00000000 ffff8f8f`b2206028 : PSHED!PshedBugCheckSystem+0x10

ffffb780`a214cdd0 fffff807`5c900ae6 : ffffb780`a214cef0 00000000`00000002 ffff8f8f`ac0f2990 ffff8f8f`ac0f2940 : nt!WheaReportHwError+0x382

ffffb780`a214ce90 fffff807`5c900f7a : 00000000`00000010 ffff8f8f`ac0f2990 ffffb780`a214d048 ffffb780`a214d290 : hal!HalpMcaReportError+0x72

ffffb780`a214cff0 fffff807`5c900e54 : ffff8f8f`aacac160 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2

ffffb780`a214d040 fffff807`5c9010c0 : 00000000`00000010 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0

ffffb780`a214d080 fffff807`5c900168 : 00000000`00000000 ffffb780`a214d310 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4

ffffb780`a214d0b0 fffff807`5c901347 : ffff8f8f`aacac160 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c

ffffb780`a214d0e0 fffff807`5c0a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37

ffffb780`a214d110 fffff807`5bfd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10

ffffb780`a214d140 fffff807`5bfd106f : 00004c90`00000000 fffff807`5bfd0fac 00000000`00000045 00000000`00000000 : nt!KxMcheckAbort+0x7a

ffffb780`a214d280 fffff807`5c151800 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f

ffffb780`a21571d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFaultShadow





THREAD_SHA1_HASH_MOD_FUNC: 9e0f0a7ea668ca23d1fa72ce2624aac7570b7ffa



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 862f7206415a6dceb5c0c2942a10aa65d56e9f4d



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_UNKNOWN



BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN



PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN



TARGET_TIME: 2020-04-28T17:44:07.000Z



OSBUILD: 18362



OSSERVICEPACK: 778



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: 2015-10-23 00:39:54



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



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



ANALYSIS_SESSION_ELAPSED_TIME: 1c83



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae_unknown



FAILURE_ID_HASH: {d1b54118-491d-1f97-b145-f80457d2955b}



Followup: MachineOwner

---------

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

Help understanding log file and game crash.

You are welcome! Glad my suggestion was helpful. *Smile

 

[HELP] Minecraft crash because OpenGL error

Hi,

Thank you for posting your query on Microsoft Community.

I understand that the game crashes. We will assist you to resolve the issue.

This issue may arise se due to compatibility issues.

I suggest you to run the game in compatible mode and check if it helps to resolve the issue.

Run the program in Compatibility mode, please follow the below steps:

• Right click on the Program
• Click on Properties
• Click on Compatibility tab
• Select Run this program in compatibility mode and select the operating system accordingly from the drop down list.

Hope the information helps. Let us know if you need further assistance. We will be happy to help.

Thank you.