New
#11
Hi Haza.
Your 2 latest dump files have atop error 0x124. Usual causes: Hardware, Incompatibility, May be driver corruption
A stop0x124 means blame the hardware. See: Stop 0x124 - what it means and what to try
Old or incompatible drivers will not help the issue either so I'll have a look at your latest dump file to see what's in there.
Bugcheck AnalysisCode: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: 00000000, Machine Check Exception Arg2: 859f1314, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000, High order 32-bits of the MCi_STATUS value. Arg4: 00000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: 8a91fcc4 82924fc5 859f12f8 829bdc28 829bdc20 nt!WheapCreateTriageDumpFromPreviousSession+0x32 8a91fce4 82925def 829bdc20 859f12f8 829bdc50 nt!WheapProcessWorkQueueItem+0x56 8a91fd00 828c3f3b 829bdc20 00000000 848cca70 nt!WheapWorkQueueWorkerRoutine+0x1f 8a91fd50 82a646d3 00000001 9443f03a 00000000 nt!ExpWorkerThread+0x10d 8a91fd90 829160f9 828c3e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV Followup: MachineOwner