AC Origins Black Screen Reboot

[Lord Stirling]

Hey guys,

I'm having a consistent issue with a brand new PC build and AC Origins.

After 15 minutes or so of gameplay the screen will suddenly go black and the whole computer reboots.

My rig:

GTX 1080 FTW2
Ryzen 7 1800
Asus STRIX ROG X370-F

I brought the PC to some specialists who stress tested all aspects of the system. The CPU, GPU, RAM are all fine and do not overheat.

I run FurMark on 4k for 20 minutes with no issue, but play AC Origins for 15 minutes at 144hz 1080p and the whole PC crashes and reboots.

Is this a known issue? It seems to be the game, not the PC. Is there any hope of a patch to stabilize this?

As a fanatic regarding ancient Egypt, I reeeeeeaaaaallllly want to play this game and explore the pyramids and tombs, etc...

Any help would be greatly appreciated.

In Liberty,
Duncan aka Lord Stirling

[_onyx_]

What do you windows crashlog/eventlogs say?

[Lord Stirling]

Originally posted by _onyx_:

What do you windows crashlog/eventlogs say?

Got this one, 16 of them? Seems to line up with the number of times the processor shows up in Device Management.


I think these are the error logs resulting from the reboot.

"Performance power management features on processor 15 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware."

It's Error "35"


These 16 errors appear immediately following Error 41:
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

[Lord Stirling]

I found the following suggestion on a Microsoft forum. Not sure if it will make a difference...:


I would suggest you to change the settings of System cooling policy from active to passive under Processor Power Management. To do so, follow the steps below.
1. Click onStart; Go to Control Panel.
2. Click onPower Options.
3. Click onchange plan settings.
4. Click onChange advanced power settings.
5. In the window that is open, scroll down toProcessor Power Management.
6. Expand theProcessor Power Management.
7. ExpandSystem Cooling Policy.
8. Click onActive to make turn the option to Passive.
9. Click onApply and Ok.

Now check if the system crashes.

Hope this information is helpful.
Mouneshwar R – Microsoft Support

https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-7-random-restart-event-error-35-some/091b9859-ad06-4925-af3f-dff3eed90fab

Edit: This just says it will slow the processor before increasing the fans... So I don't see how that would help...

[_onyx_]

Originally posted by Lord Stirling:

Originally posted by _onyx_:

What do you windows crashlog/eventlogs say?

Got this one, 16 of them? Seems to line up with the number of times the processor shows up in Device Management.


I think these are the error logs resulting from the reboot.

"Performance power management features on processor 15 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware."

It's Error "35"


These 16 errors appear immediately following Error 41:
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost after"

Could be Bios related. See if problem persist after flashing Bios with an older version if you have the latest bios. Or with a newer Bios if you have an older.

[Lord Stirling]

Originally posted by _onyx_:

Originally posted by Lord Stirling:

Got this one, 16 of them? Seems to line up with the number of times the processor shows up in Device Management.


I think these are the error logs resulting from the reboot.

"Performance power management features on processor 15 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware."

It's Error "35"


These 16 errors appear immediately following Error 41:
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost after"

Could be Bios related. See if problem persist after flashing Bios with an older version if you have the latest bios. Or with a newer Bios if you have an older.

The BIOS I have if from last August. Haven't tried to update it yet. This is a replacement motherboard because I tried to update the BIOS last week on the first STRIX X370-F I received and it froze part way through the flash... I ended up resetting it and it corrupted the BIOS, rendering the mobo unusable. There's no way to flash an old BIOS on this mobo once its corrupted, so I've been nervous to try it again.

You think it's likely BIOS related?

[The Father]

BSODS and reboots are caused by hardware/drivers failure, since most of players can play with similar hardware then drivers are not an issue unless if you have old drivers.

so have you installed latest Nvidia drivers??

if yes, then stress test your system with prime95 using blend test for several hours and post back the results.

[Lord Stirling]

Originally posted by Abook:

BSODS and reboots are caused by hardware/drivers failure, since most of players can play with similar hardware then drivers are not an issue unless if you have old drivers.

so have you installed latest Nvidia drivers??

if yes, then stress test your system with prime95 using blend test for several hours and post back the results.

Thanks for responding. I appreciate the advice and info. Turns out that it was in fact the BIOS. I overcame my anxiety about flashing the latest BIOS and gave it a shot. Luckily this time it worked seamlessly. That also makes me feel more confident for future updates. Been playing Origins to test stability for a couple hours now and its been nothing but incredibly smooth at this point.

What a relief!

[Lord Stirling]

Originally posted by _onyx_:

Originally posted by Lord Stirling:

Got this one, 16 of them? Seems to line up with the number of times the processor shows up in Device Management.


I think these are the error logs resulting from the reboot.

"Performance power management features on processor 15 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware."

It's Error "35"


These 16 errors appear immediately following Error 41:
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost after"

Could be Bios related. See if problem persist after flashing Bios with an older version if you have the latest bios. Or with a newer Bios if you have an older.

You were right! Running very smoothly now as it should be. Thanks for your help!

[Lord Stirling]

Ohhhhh man. Well, I guess I jinx'ed myself, because now after a couple of hours it just black screened and restarted on me again!

Wth!

[The Father]

just stress test your system as i said for at least 8 hours straight, i bet it would do the same, something is not stable. might be RAM timings as well.