Windows 10: BSOD when playing Assassins creed Origins error 0x00000124

When playing AC origins I get a blue screen error. I uploaded the DMP file.
Any help would be appreciated. Thanks

:)

 

BSOD Playing Assassins Creed: Origins

So I went down the list and basically started trying everything in order. Updating my BIOS and uninstalling NVIDIA HD Audio seems to be the fix for me! Thank you for the speedy, detailed, and helpful response, now I can finally play this game. Also, updating
my BIOS seems to have come with many other benefits too.

Thanks

 

BSOD Playing Assassins Creed: Origins

My basic mini-dump analyser points in the direction of, but not necessarily limited to a hardware issue.

- WHEA Uncorrectable Error , HAL (Windows Hardware Abstraction layer ).

- As you have just installed the new gpu I would first pull and reseat the 1050ti (clean the slot with a soft brush too) .

Also pull and re-seat your RAM as you may have bumped the RAM while installing the gpu, which can sometimes

cause a flaky connection.

---------

[EDIT: Finally got around to the sysinfo errors (got lost in the mix) - AMD processor cache errors leading to BSOD... Significant ? I don't know.

- Also see some Windows Update fail errors. Try running Windows Updates manually. WU may be trying to do an update while you

are gaming. If you have not installed the 1709 version update this would consume a lot of your cpu and RAM if you allow

Windows updates to handle it.

The safer way to do the version updates is to download the update tool and do the update 'manually' before WU starts in,

and don't do anything on the machine other than simple tasks while a version update is downloading.

- Can you enlighten us what UE4 - KiwiGame...... is ? This shows in great long string of App Crashes. Failed server connections or somethin' ?

- There are also the Wacom tablet and pen errors. Outdated software or Wacom driver conflicting, maybe ?

Also try disabling the stuff in Startup , at least while troubleshooting.

No need to run the main CCleaner program in the background all the time ever (btw - People still post here now and then who have borked their Windows after using a Registry 'cleaner' ). ]

---------------

- Did you have another Nvidia card previously or AMD ? If it was AMD did you use Display Driver Uninstaller (DDU) orDriver Fusion (free version is adequate) to fully uninstall the old drivers ?

Display Driver Uninstaller Download version 14.1.0.0

Treexy | Download free driver and device software

- A BIOS update (if Gigabyte has a more recent one available), sometimes helps when installing a new gpu

that is several generation newer than the original.

- If you have changed any RAM or cpu settings in BIOS, reverting to default may help.

- There is potential for conflict between Nvidia HD Audio and your Sound Blaster drivers. If you don't need

the Nvidia driver for HDMI/DisplayPort audio you can uninstall them.

"I never see the temp rise over 50-60 degrees before BSOD."

- Are you creating log files so you know the exact temp at the time of BSOD ?

I wouldn't think this game would put full 100% load on your cpu. Do you have other things running in the backgroundthat may be stealing cpu cycles ?

Have you enabled Game Mode (and other options is that section) ? If so, this may be the culprit, and it may be

shifting load from gpu to cpu ?

I haven't heard much about Game Mode lately, but it has been know to be counterproductive with some games.

- Generally running the gpu @100% should not cause TDR or BSOD, but I have one game that would get a TDR error( with decent fps ) now and then if the gpu had 100% use, but when I changed game settings so it only ran at 99% the

game never had a problem.

- If you still have another functioning card and the problem persists try the old card again to verify the new is not faulting.

.

 

Use this to learn how to post your system specs: System Specs - Fill in at Ten Forums Site Use Tutorials

Then go here to download the log collector, to upload what's needed: BSOD - Posting Instructions - Windows 10 Forums

Once You've done that then one of the BSOD Gurus will be able to help. Just be patient cause they get real busy at times.

 

First of all thanks for the reply. I appreciate the help.
I am sorry for not adding the necessary information beforehand. Here are the required files.

 

The info in your System Specs under My Computer do not match what I see in the dump. Can you please fill out your system specs following the directions at the link Bat 1 gave you above.

Need to know what the make and full model number of the mother board is. Looks like you have 16GB of RAM (4 x 4GB DIMMs).
Dump shows:
Code: Vendor American Megatrends Inc. BIOS Version FD BIOS Release Date 01/25/2013[/quote] All 3 dumps indicate a fatal machine check :
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: ffff9f8757752028, 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 value[/quote] Code: 4: kd> !errrec ffff9f8757752028 =============================================================================== Common Platform Error Record @ ffff9f8757752028 ------------------------------------------------------------------------------- Record Id : 01d39df395a7a05c Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/4/2018 20:18:23 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff9f87577520a8 Section @ ffff9f8757752180 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 : 0x0000000000000004 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff9f87577520f0 Section @ ffff9f8757752240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000004 CPU Id : 20 0f 60 00 00 08 06 04 - 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 @ ffff9f8757752240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff9f8757752138 Section @ ffff9f87577522c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 4 Bank 1) Status : 0xb080000000060151[/quote] 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: ffff9d00ae66a028, 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 value.[/quote] Code: 2: kd> !errrec ffff9d00ae66a028 =============================================================================== Common Platform Error Record @ ffff9d00ae66a028 ------------------------------------------------------------------------------- Record Id : 01d39dc21baada9a Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/4/2018 19:46:53 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff9d00ae66a0a8 Section @ ffff9d00ae66a180 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 : 0x0000000000000002 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff9d00ae66a0f0 Section @ ffff9d00ae66a240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : 20 0f 60 00 00 08 06 02 - 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 @ ffff9d00ae66a240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff9d00ae66a138 Section @ ffff9d00ae66a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 2 Bank 1) Status : 0xb080000000060151[/quote] 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: ffffb587be267028, 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 value.[/quote] Code: 0: kd> !errrec ffffb587be267028 =============================================================================== Common Platform Error Record @ ffffb587be267028 ------------------------------------------------------------------------------- Record Id : 01d39df104373e89 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/4/2018 20:05:09 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffb587be2670a8 Section @ ffffb587be267180 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 : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffb587be2670f0 Section @ ffffb587be267240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 20 0f 60 00 00 08 06 00 - 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 @ ffffb587be267240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffb587be267138 Section @ ffffb587be2672c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 0 Bank 1) Status : 0xb080000000060151[/quote] The only difference is the address of the WHEA error record and processor (Arg2).

If you are over clocking or running at anything but nominal voltages, set everything back to nominal and see if that helps.
Check voltages in BIOS, make sure they are correct.

Also, the event log shows you had 10 BSODs on 2/4/2018 between 19:52 and 21:20 and all of them were WHEA 124 errors, the same as the 3 dumps I looked at.

What did you change on February 4th around that time? Did you install anything new, add or remove any hardware?

 

The logs displayed possible piracy with software to bypass the activation of Windows products.
Please explain the use of this software.
Code:

• No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.

[/quote] Forum Rules - Windows 10 Forums

 

All 3 dumps indicate a fatal machine check :
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: ffff9f8757752028, 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 value[/quote] Code: 4: kd> !errrec ffff9f8757752028 =============================================================================== Common Platform Error Record @ ffff9f8757752028 ------------------------------------------------------------------------------- Record Id : 01d39df395a7a05c Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/4/2018 20:18:23 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff9f87577520a8 Section @ ffff9f8757752180 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 : 0x0000000000000004 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff9f87577520f0 Section @ ffff9f8757752240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000004 CPU Id : 20 0f 60 00 00 08 06 04 - 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 @ ffff9f8757752240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff9f8757752138 Section @ ffff9f87577522c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 4 Bank 1) Status : 0xb080000000060151[/quote] 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: ffff9d00ae66a028, 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 value.[/quote] Code: 2: kd> !errrec ffff9d00ae66a028 =============================================================================== Common Platform Error Record @ ffff9d00ae66a028 ------------------------------------------------------------------------------- Record Id : 01d39dc21baada9a Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/4/2018 19:46:53 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff9d00ae66a0a8 Section @ ffff9d00ae66a180 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 : 0x0000000000000002 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff9d00ae66a0f0 Section @ ffff9d00ae66a240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : 20 0f 60 00 00 08 06 02 - 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 @ ffff9d00ae66a240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff9d00ae66a138 Section @ ffff9d00ae66a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 2 Bank 1) Status : 0xb080000000060151[/quote] 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: ffffb587be267028, 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 value.[/quote] Code: 0: kd> !errrec ffffb587be267028 =============================================================================== Common Platform Error Record @ ffffb587be267028 ------------------------------------------------------------------------------- Record Id : 01d39df104373e89 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/4/2018 20:05:09 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffb587be2670a8 Section @ ffffb587be267180 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 : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffb587be2670f0 Section @ ffffb587be267240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 20 0f 60 00 00 08 06 00 - 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 @ ffffb587be267240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffb587be267138 Section @ ffffb587be2672c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : ICACHEL1_IRD_ERR (Proc 0 Bank 1) Status : 0xb080000000060151[/quote] The only difference is the address of the WHEA error record and processor (Arg2).

If you are over clocking or running at anything but nominal voltages, set everything back to nominal and see if that helps.
Check voltages in BIOS, make sure they are correct.

Also, the event log shows you had 10 BSODs on 2/4/2018 between 19:52 and 21:20 and all of them were WHEA 124 errors, the same as the 3 dumps I looked at.

What did you change on February 4th around that time? Did you install anything new, add or remove any hardware?[/quote] I am sorry, i have 4x4gb ram not 4x8gb. I made a typo.

CPU used to be overclocked but i did a cmos reset a while back.

The other bluescreens were Assassins creed related too. There are more people complaining about it so i thought it is game related. So i was doing different tests hoping to find out the reason behind it.

Did not install any new hardware.

Actually that is college related reverse engineering project. Had to chose a random virus and do a list of tasks. I chose kms

Our school gives licenses for Microsoft products to students. I have no reason to resort to piracy

 

What about board voltages? Are they where they should be? Any over/under valued?

The 3 dumps showed the Machine check was due to 3 different processors which to me makes it less likely the CPU is actually defective. That's whay I'm looking for another cause, like over/under clocking or voltages.

 

The board has been acting weird ever since I bought it. My CPU was clocked, and there was a bug that I had to press the power button twice in order the turn the computer on. It was like button press, fans turned on for a second, PC turned off and button press again, everything works fine.
I have been on a lot of forums 6 - 5 years back when I built this PC hoping someone would tell me what the issue is but nobody could figure out. I eventually forgot about it and just pressed the button twice in a row.
What I managed to figure out however is that it was not related to overclocking, but to turning off the turbo mode of my CPU. Everything would work fine had I kept it on.

The computer has been working like this flawlessly until now (Well except the power bug).
I am saying that because it might be a relevant information.

To shortly answer your question: No, I did not mess with the board in any way. No overclocking, no changes in voltages. Everything on the board in stock.

 

Let's try turning off Hibernate and by association, Fast Startup, see if that makes any difference.

Open a Elevated Command Prompt.

• Click Start
• Type cmd
• Right click on Command Prompt at top of window and select Run as Administrator

Type powercfg -h off and press Enter.

Shutdown (nor Restart) then power on after 10 seconds or so. See how it runs.

 

Hybernation has been causing problems as well. I back tracked it a while ago, therefore I already had it turned off and it is the first thing I switch off after formatting my drive. (I did not use the CMD however, I turned it off in the power options and turned off fast startup)

All the mentioned problems are with these settings off. I will use the console command just to be sure but I doubt it will make any difference.

Do you believe the blue screens are caused by a faulty motherboard?

EDIT: I tried the console solution, but no difference so far.

 

I don't know for sure what is causing the problem. As I mentioned earlier, I don't think it's the CPU because of the different processors showing as failing but that could be wrong. System board is possible but that's all I can say, possible.

 

Do you have any tips how I could narrow down the cause of the error?
And may I ask what tools you used that outputted the DMPs in such a detailed manner? I used bluescreenview but that is far from being as readable as what you posted.

 

PROCESS_NAME: ACOrigins.exe may cause errors
First, remove ESET