Windows 10: MACHINE_CHECK_EXCEPTION 9c A fatal Machine Check Exception has occurred.

Hey there I am so anoyed about this Blue screen It all began when I updatede my 1809 to 1909 since that I have installed windoes 10 pro on a new ssd and I got the newest windows from Microsofts site :- this is what I have found out but dont understand.

Oh yeah my hardware is Asus motherbord Z370-AII Prime Rev. X.0x Bios version 1001 from 05/24/2019 16 GB ram G.skill Nvidia GTX 1070TI 8 GB ram


and here are all that I dont understand ;-





Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 6 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`33200000 PsLoadedModuleList = 0xfffff801`33648150Debug session time: Mon Apr 27 12:24:27.471 2020 UTC + 2:00System Uptime: 1 days 0:48:40.190Loading Kernel Symbols....................................................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 0000005d`3164e018. Type ".hh dbgerr001" for detailsLoading unloaded module list................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`333c2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb100`c098cca0=000000000000009cLoading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Can't set dump file contextsMachineInfo::SetContext failed - Thread: 00000256899C91F0 Handle: 4 Id: 4 - Error == 0x8000FFFF************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 6 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`33200000 PsLoadedModuleList = 0xfffff801`33648150Debug session time: Mon Apr 27 12:24:27.471 2020 UTC + 2:00System Uptime: 1 days 0:48:40.190Loading Kernel Symbols....................................................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 0000005d`3164e018. Type ".hh dbgerr001" for detailsLoading unloaded module list................nt!KeBugCheckEx:fffff801`333c2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb100`c098cca0=000000000000009c1:3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************MACHINE_CHECK_EXCEPTION 9cA 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 If Param 1 is < 0x80000000 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 AMD64 Processors If Param 1 is > 0x80000000 1 - Failure Type VALUES: 0x80000001: Spurious MCE 2 - Address of MCA_EXCEPTION structure 0x80000002: Rendezvous failure 2 - Address of MCA_EXCEPTION structure END_VALUESArguments:Arg1: 0000000000000000Arg2: ffffb100c098ccd0Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on FARS-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 8 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 9cBUGCHECK_P1: 0BUGCHECK_P2: ffffb100c098ccd0BUGCHECK_P3: 0BUGCHECK_P4: 0BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: chrome.exeBAD_STACK_POINTER: ffffb100c098cc98STACK_TEXT: ffffb100`c098cc98 fffff801`331a5b91 : 00000000`0000009c 00000000`00000000 ffffb100`c098ccd0 00000000`00000000 : nt!KeBugCheckExffffb100`c098cca0 fffff801`331a611d : 00000000`00000006 ffffb100`c098d010 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0x11dffffb100`c098ce00 fffff801`331a5168 : 00000000`00000000 ffffb100`c098d090 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131ffffb100`c098ce30 fffff801`331a6347 : ffffe687`47adab20 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5cffffb100`c098ce60 fffff801`334a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37ffffb100`c098ce90 fffff801`333d13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10ffffb100`c098cec0 fffff801`333d106f : ffffb100`00000000 fffff801`333d0fac fffffc84`c5acf690 00000000`00000000 : nt!KxMcheckAbort+0x7affffb100`c098d000 fffff801`332b523b : 00000000`00000000 ffffb100`c0980180 ffffb100`c0980180 00000000`00000002 : nt!KiMcheckAbort+0x26ffffffc84`c5acf630 fffff801`33314343 : ffffe687`55ad80c0 fffff801`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1bfffffc84`c5acf660 fffff801`33317dbe : ffffe687`000000be ffffe687`00000000 ffffe687`5acf1d01 ffffe687`55ad8200 : nt!KiCommitThreadWait+0x583fffffc84`c5acf700 fffff801`333178b9 : ffffe687`00000002 fffff801`3330a901 ffffe687`5acf1d00 00000183`9e1eb1b0 : nt!KeRemoveQueueEx+0x27efffffc84`c5acf7b0 fffff801`337f38f0 : fffffc84`c5acf920 0000005d`35fffb18 00000000`00000001 00000000`00000000 : nt!IoRemoveIoCompletion+0x99fffffc84`c5acf8d0 fffff801`333d3c15 : ffffe687`55ad80c0 0000005d`35fffaf8 fffffc84`c5acf9a8 00000183`9e1eb1b0 : nt!NtRemoveIoCompletion+0x140fffffc84`c5acf990 00007ffa`480fc194 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x250000005d`35fffad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`480fc194SYMBOL_NAME: nt!KiHandleMcheck+10MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 10FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheckOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f10d6786-a78f-4993-4f62-7de145ea1ce2}Followup: MachineOwner---------PLZ help me im going NUTS :

:)

 

Windows 10 - blue screen MACHINE CHECK EXCEPTION and srttrail.txt

Hi, Chanel.

Thank you for posting your query in Microsoft Community.

I understand your concern, and we in Community will try to help you in the best possible way.

The MACHINE_CHECK_EXCEPTION bug check has a value of 0x0000009C. This bug check indicates that a fatal machine check exception has occurred.

I suggest that you perform the steps below and check if it resolves your issue:

1. On the Lock Screen press on Shift Key + power icon located on the right bottom corner of the screen.

2. Press on " Restart Anyway" this will take you to the Recovery Environment.

3. Click on "Troubleshoot" and the "Advanced Option" and the "Startup Repair."

Your reply is very important for us to ensure a proper resolution. Please get back to us with the above information in order to assist you accordingly.

For further assistance, you can post your query in Microsoft Community.

 

BSOD when playing CSGO - Machine Check Exception

The dumpfiles are
Code:

Usual causes:* Hardware, Incompatibility, Maybe driver corruption

Are you overclocking your system, stop it.

old drivers
speedfan Sat Dec 29 21:59:35 2012, update to the latest version or uninstall

TeeDriverx64 Tue Sep 23 22:01:14 2014 = intel manegement engine interface
iaStorA Sat May 03 01:06:56 2014 = intel storage driver
RTKVHD64 Tue Sep 30 14:02:07 2014 = Realtek High definition audio

Update these drivers from the supportpage of your mobo https://www.asus.com/Motherboards/Z9...Desk_Download/

Also your BIOS is from 2014, update tot he latest version (Improve system stability )

 

BSOD MACHINE CHECK EXCEPTION

Hi,

Machine Check Exception Freeze and Blue Screen Error is a bug check that indicates that a fatal machine exception has occurred on your system. Try running the blue screen error troubleshooter and follow the instructions on this
article.

If the issue still persists, check the answer of SpiritX MS MVP, one of our community MVPs, and follow the steps he provided on this
thread which were found helpful in resolving the issue.

Should you need further assistance, feel free to post your query anytime.