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

Sorry what? Without proper justification I can not just remove it.

 

AC Origins is a game. What indication is there that the AV has anything to do with the BSOD issue?

Do you have BSODs with any other game or application? If not, it could have some bearing on the fact that your hardware is real close to the minimum required to run the game. ACOrigins Minimum Specs.

Have you monitored your CPU and GPU temps and usage?

 

If You Google assassin's creed origins bsod - Google Search You'll find a lot of complaints about that problem. The DRM causes BSODs on Legit Purchased Versions and it's even worse on "Shared" copies. As posted above, Your CPU might just not be powerful enough ?

 

No I did not have issues with other applications and I heavily doubt it is because of the "requirements". Having older CPU should cause performance bottlenecks not major instabilities and blue screens.

I did monitor both the temps and the usage (I can not believe that this is the number one suggested problem AT ALL TIMES) and they are more than nominal. I barely go above 40C

I am aware of the reports and I browsed through all of them. I posted this hoping analytics would specify the problem.

 

eric, an 0x124 is generally a hardware error, as is a WHEA (Windows Hardware Error Architecture) error.
I didn't make up the Minimum Requirements, the game developers did.
Typically when the CPU detects a hardware error or fault it will call for a BSOD or shutdown to protect the computer from permanent damage. Therefore in many cases the dumps will blame the CPU because it called for the shutdown, but in the majority of cases is not the cause of the error. A bad driver can cause the relevant piece of hardware to act as though it is failing. However a bad driver or piece of hardware should cause the BSODs in many games or applications. If a game or application is requiring more resources from a piece of hardware than it is capable of, it will fail or act as if failing. It is out of resources, but the game/app is requiring more, so it fails.

Given all of that, and the fact that you only have issues with one application, AC, it would lead one to believe that there is either a problem with the game or game files or it is requiring more resources than your hardware can give it.

Have you tried to lower the game settings as low as possible and see if the game plays without a crash? If not, I would lower them as much as possible and see. If it works, you could then increase them one at a time until you start crashing again. That would tell you which setting is causing you the problem or how high you can set them without crashing.

This is @Ztruker's thread, so it is best to let him handle it.

 

I tried that without any luck. The frequency of bluescreens did not change.

I think that too. There are way too many people on the internet complaining that it is a game related problem, most likely caused by an incompatibility with systems running on fx bulldozer or pile driver architecture paired with gigabyte motherboards.
All of the reports have the same bugcheck errors.

I just never encountered a blue screen problem that would be caused by something literally running on the application layer. Unless they are seriously messing with the drivers, there is no way it could crash the whole system like that.

 

You might want to check the refund policies to see if You qualify ?
Steam Refunds
Returns Cancellations - Ubisoft Support
GameStop Returns and Refund Policies

Or wherever You purchased if not one of the above

 

I simply wanted to play the game. I will keep it and when I will have time simply switch my CPU and board for something that is not 50 bucks cheap and 6 years old.

 

We gave up Gaming for the most part because the requirements got so high with Denuvo as well as always online Games on a Crap Internet connection. Pretty sure my old Dozer on a ASUS M5A 99X EVO could run it IF I had a decent GPU *cry

 

Yeah, well I was having solid frame rate too, if it was not for the constant crashes. My first guess was the anti-consumer DRM.
God knows what routines it performs in the background.

 

Please run this version of the log collector and post a zip into this thread:
log collector v2-beta08.zip

Whenever there is a new BSOD please run this version of the log collector and post a new zip into the thread.

 

Here are the files.
For some reason the dmps were not found? Should I copy them manually?

No problem. I will run AC origins and have a blue screen in 5 minutes.

 

The event logs start on 2/4/2018.
The last BSOD was one week ago on 2/4/2018: WHEA 0x124.
The last crash was one week ago on 2/4/2018.


There were no BSOD files to debugg.
The computer has displayed stability for 1 week.
The logs were unremarkable.
The RAM modules are mismatched: There are 4 RAM modules and they are in pairs of matching SKU but all 4 SKU do not match.


Perform the following steps:
1) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread







Code: 4. 2. 2018 19:52 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9d00ae66a028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-31687-01.dmp \\?\C:\Windows\TEMP\WER-252515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C00.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C3F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C8E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_812eef2c19198d49467122676a8337c596a16547_00000000_cab_25301d0a Analysis symbol: Rechecking for solution: 0 Report Id: 6a4931ab-2628-413d-9273-6c58f88ca494 Report Status: 2049 Hashed bucket:4. 2. 2018 19:52 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9d00ae66a028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-31687-01.dmp \\?\C:\Windows\TEMP\WER-252515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C00.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C3F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C8E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_812eef2c19198d49467122676a8337c596a16547_00000000_034c1c8d Analysis symbol: Rechecking for solution: 0 Report Id: 6a4931ab-2628-413d-9273-6c58f88ca494 Report Status: 4 Hashed bucket:4. 2. 2018 20:22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9f8757752028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-26859-01.dmp \\?\C:\Windows\TEMP\WER-182765-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFDF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER107C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER109C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_a4c59d6cda106b51b3ce5ce1979de84fc1e58_00000000_cab_24d71936 Analysis symbol: Rechecking for solution: 0 Report Id: 8b5fe748-2761-4e4f-9f50-059db0bc677d Report Status: 2049 Hashed bucket:4. 2. 2018 20:22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff9f8757752028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-26859-01.dmp \\?\C:\Windows\TEMP\WER-182765-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFDF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER107C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER109C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_a4c59d6cda106b51b3ce5ce1979de84fc1e58_00000000_02f710d9 Analysis symbol: Rechecking for solution: 0 Report Id: 8b5fe748-2761-4e4f-9f50-059db0bc677d Report Status: 4 Hashed bucket:4. 2. 2018 20:09 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb587be267028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-32031-01.dmp \\?\C:\Windows\TEMP\WER-181781-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_78cac8cbdfb629dfef33b7f6bbd4bc1c3b422dbf_00000000_cab_27230706 Analysis symbol: Rechecking for solution: 0 Report Id: 71d63e81-3f33-48d8-9075-97ac1613de26 Report Status: 2049 Hashed bucket:4. 2. 2018 20:09 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb587be267028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-32031-01.dmp \\?\C:\Windows\TEMP\WER-181781-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_78cac8cbdfb629dfef33b7f6bbd4bc1c3b422dbf_00000000_02fb063b Analysis symbol: Rechecking for solution: 0 Report Id: 71d63e81-3f33-48d8-9075-97ac1613de26 Report Status: 4 Hashed bucket:4. 2. 2018 21:20 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb68e9a06d028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-25796-01.dmp \\?\C:\Windows\TEMP\WER-258640-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2603.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2651.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2671.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_595a89797bc27c3286d99e92829b0a986b33df8_00000000_cab_2698270c Analysis symbol: Rechecking for solution: 0 Report Id: bacb9200-fc35-4906-b9dc-9ef52b65a800 Report Status: 2049 Hashed bucket:4. 2. 2018 21:20 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffb68e9a06d028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-25796-01.dmp \\?\C:\Windows\TEMP\WER-258640-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2603.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2651.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2671.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_595a89797bc27c3286d99e92829b0a986b33df8_00000000_02f4268f Analysis symbol: Rechecking for solution: 0 Report Id: bacb9200-fc35-4906-b9dc-9ef52b65a800 Report Status: 4 Hashed bucket:4. 2. 2018 20:59 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffd482eda67028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-26343-01.dmp \\?\C:\Windows\TEMP\WER-182140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB3E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB6D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB8D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_66a26125b53db5e2afab6ccb217597e927342693_00000000_cab_272efc19 Analysis symbol: Rechecking for solution: 0 Report Id: e0388270-10b2-4157-807a-e1ea4ad78f8c Report Status: 2049 Hashed bucket:4. 2. 2018 20:59 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffd482eda67028 P4: b0800000 P5: 60151 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020418-26343-01.dmp \\?\C:\Windows\TEMP\WER-182140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB3E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB6D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB8D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_66a26125b53db5e2afab6ccb217597e927342693_00000000_02f6fbac Analysis symbol: Rechecking for solution: 0 Report Id: e0388270-10b2-4157-807a-e1ea4ad78f8c Report Status: 4 Hashed bucket:[/quote]

 

erik9631
You can install ESET again, but let's check if the BSOD will occur after removing the anti-virus

 

1) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials