New
#1
BSOD playing Assassins Creed Origins, error 0x00000124
Hello!
Only when I play Assassins Creed Origins this happens. I've attached the required files. Please tell me if I need to give any other information.
Thank you in advance!
Hello!
Only when I play Assassins Creed Origins this happens. I've attached the required files. Please tell me if I need to give any other information.
Thank you in advance!
Only one dump. It shows:
Code: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: ffff8603ba540028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000060151, Low order 32-bits of the MCi_STATUS valueIdentical error here: BSODs - Not sure why they're happeningCode:!errrec ffff8603ba540028 =============================================================================== Common Platform Error Record @ ffff8603ba540028 ------------------------------------------------------------------------------- Record Id : 01d40bcdef19b920 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 6/24/2018 15:36:33 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff8603ba5400a8 Section @ ffff8603ba540180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Instruction Execute Flags : 0x00 Level : 1 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff8603ba5400f0 Section @ ffff8603ba540240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : 20 0f 60 00 00 08 08 06 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff8603ba540240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff8603ba540138 Section @ ffff8603ba5402c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 6 Bank 1) Status : 0xb080000000060151
The advice given there also applies in your case. If over clocking, stop. Check heat sink, make sure it's seated well. Apply new thermal paste. Clean out inside of case and all vents.
Comeback if none of that seems to help. We can try running Driver Verifier, see if that shows anything useful.
Cleaned all the fans, applied thermal paste.
P.S.- I never overclocked.
Have you added any new hardware or updated any drivers around the time this started happening?
Let's give Driver Verifier a try, see if that shows us anything:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.
Driver Verifier - Enable and Disable in Windows 10
Pay close attention to PART TWO and make sure the correct boxes are checked.
Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.
Always create a Restore Point prior to enabling Driver Verifier.
What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.
No, I didn't get any new hardware, i updated my gpu driver but the BSOD also happened with my previous version driver too.
Also there was a BSOD when i ran driver verifier. It's attached.
P.S.- this only happens when I play Assassins Creed Origins only and nothing else.
No dump from yesterday, shows length of 0.
Are you running any hard drive cleaning programs like CCleaner? There should be a lot more dumps than the one from the 24th.Code:Directory: C:\WINDOWS\Minidump Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 6/29/2018 11:51 AM 0 062918-42953-01.dmp
I'm using advanced systemcare. Should I uninstall it?
Yes, it is probably the cause of the loss of the dump files. Uninstall it and leave i uninstalled.