Windows 10: BSOD Issue!

Hello! I am experiencing recurring BSOD crashes on a fairly new system. The BSOD and attatched errors usually only occur when the system is under heavy load Gaming.


This is the Dump Log that has been generated.




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: ffffd30587ff0028, Address of the WHEA_ERROR_RECORD structure.

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

Arg4: 0000000000000014, 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: System manufacturer



SYSTEM_PRODUCT_NAME: System Product Name



SYSTEM_SKU: ASUS_MB_CNL



SYSTEM_VERSION: System Version



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: 0805



BIOS_DATE: 09/21/2018



BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



BASEBOARD_PRODUCT: TUF Z390-PLUS GAMING WI-FI



BASEBOARD_VERSION: Rev X.0x



DUMP_TYPE: 2



BUGCHECK_P1: 0



BUGCHECK_P2: ffffd30587ff0028



BUGCHECK_P3: b2000000



BUGCHECK_P4: 14



BUGCHECK_STR: 0x124_GenuineIntel



CPU_COUNT: 6



CPU_MHZ: e70



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: c



CPU_MICROCODE: 6,9e,c,0 F,M,S,R SIG: 9E'00000000 cache 9E'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: NVDisplay.Container.exe



CURRENT_IRQL: f



ANALYSIS_SESSION_HOST: DESKTOP-MUGK23C



ANALYSIS_SESSION_TIME: 11-17-2020 16:11:13.0360



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



STACK_TEXT:

ffffe480`abdd1af8 fffff802`634fd178 : 00000000`00000124 00000000`00000000 ffffd305`87ff0028 00000000`b2000000 : nt!KeBugCheckEx

ffffe480`abdd1b00 fffff802`65781920 : ffffd305`8089e830 00000000`00000000 ffffd305`87ff0028 00000000`00000000 : hal!HalBugCheckSystem+0xd8

ffffe480`abdd1b40 fffff802`62d40062 : ffffd305`8089e830 ffffe480`abdd1bc9 00000000`00000000 ffffd305`87ff0028 : PSHED!PshedBugCheckSystem+0x10

ffffe480`abdd1b70 fffff802`634fead6 : ffffe480`abdd1c90 00000000`00000003 ffffd305`8089e880 ffffd305`8089e830 : nt!WheaReportHwError+0x382

ffffe480`abdd1c30 fffff802`634fef6a : 00000000`00000010 ffffd305`8089e880 ffffe480`abdd1de8 ffffe480`abdd2030 : hal!HalpMcaReportError+0x72

ffffe480`abdd1d90 fffff802`634fee44 : ffffd305`804a5b30 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2

ffffe480`abdd1de0 fffff802`634ff0b0 : 00000000`00000006 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0

ffffe480`abdd1e20 fffff802`634fe158 : 00000000`00000000 ffffe480`abdd20b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4

ffffe480`abdd1e50 fffff802`634ff337 : ffffd305`804a5b30 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c

ffffe480`abdd1e80 fffff802`62ca42e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37

ffffe480`abdd1eb0 fffff802`62bd2afa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10

ffffe480`abdd1ee0 fffff802`62bd27af : 00000000`00000000 00000000`00000000 00000000`0000000f 00000000`00000000 : nt!KxMcheckAbort+0x7a

ffffe480`abdd2020 00007ffa`4b85d368 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f

00000038`e6afec60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`4b85d368





THREAD_SHA1_HASH_MOD_FUNC: 4de11a045a075685c6206f99f334fdcf81e00201



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 52bc5bbdfdfeb50262bd4e22a6b4ce3d3d5996e4



THREAD_SHA1_HASH_MOD: e68de900930b6f9798c6a02efd69edc806b33cb0



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_TLB



BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_TLB



PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_TLB



TARGET_TIME: 2020-11-16T21:08:09.000Z



OSBUILD: 18362



OSSERVICEPACK: 1198



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: 1981-09-10 17:55:31



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



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



ANALYSIS_SESSION_ELAPSED_TIME: 70b5



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_tlb



FAILURE_ID_HASH: {03e060e2-37bb-3e02-4bd4-77932f0be153}

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast:

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.