Issues with Assassin's Creed Origins due to frequent GPU 3D spikes
Issues with Assassin's Creed Origins due to frequent GPU 3D spikes
Not sure whether this is better listed under games or GPUs, but the issue has been driving me crazy.
After launching Ass Creed Origins, somewhere between 1 and about 20 minutes into gameplay, the game constantly crashes. Usually, the music keeps playing, but the screen itself is frozen, with no cursor to move around. If I'm able, I have to use Task Manager to end the AC Origins process to get control of my computer back. When it won't open TM, I have to do a reset.
Now, I've searched all the forums and done all the things that a mid-tech competent person can do, and nothing helps. The
one
telltale error that (I hope) leads to a solutions is this: In looking at Task Manager after a crash, under the 'Performance' tab, every crash is directly preceeded by two spikes in the 3D graph associated with my 3060ti GPU - the first is usually about 80, then a very brief dip to 0, followed by a quick spike to 100, followed by a quck return to 0, indicating the post-crash value. . I don't know what this is indicative of, but it occurs without fail in these crashes. I might add that aside from these 3D spikes associated with the crash, there seems to be no other 3D activity that preceeds a crash during gameplay.
Yes, all my drivers are up to date (including Nvidia - clean boot of GPU drivers), and the things I've tried are far too long to list.
My rig is a Win 11 Gigabyte Aorus Pro DDR5 Z690 mobo, Intel 12700K CPU, Asus LHR 3060ti OC GPU, 16gb x 2 Kingston Fury DDR 6000 RAM which works fine with XMP profile for everything else, and a Gigabyte G2 850w gold PSU. No component is overclocked by me, it's all factory settings. I have seen this crashing issue, on so many forums, and with so many games (including others playing Ass Creed Origins), with so many supposed 'fixes' that it's so clearly a widespread problem. But none of the fixes proposed has any effect on this problem.
I'm not super-tech savvy, so an 18-step list of technical things isn't going to help me. If someone has an idea that I can carry out, particularly given that suspicious 3D graph spike, I'd be very grateful. Thanks in advance.
I often see several mistakes and different kinds of errors as a hint of PSU or power issues.
Not a guaranteed certainty at all.
Actions to take:
Execute the built-in Windows troubleshooters, "sfc /scanno", and "dism" to check if Windows can locate and resolve problems.
References: https://www.lifewire.com/how-to-use-sfc-...es-2626161
Learn how to use the DISM command tool for repairing Windows 10 image | Windows Central
Make sure all drivers are current, particularly the GPU. Download drivers directly from the manufacturer's site, reinstall if needed, and reconfigure accordingly. Avoid third-party installers or tools.
Ralston - Thanks for your reply! I wasn't familiar with those two programs, but I reviewed each one. While I can't really understand which categories are most important or what the different labels mean, there are many warnings and errors. Some of them are pretty clear to me—like sudden system shutdowns (which seem to be the frequent crashes from Origins). I also experience occasional hardware or software issues. If possible, would it help to share some of these here? Thanks. (I'm actually writing this from another computer, otherwise I'd just post what I might be able to copy and paste now.)
Ralston - In the event viewer and reliability history, could you specify exactly what you're searching for? This way I might suggest something useful. I'm encountering numerous warnings, errors, and information that aren't clear on which would be most relevant. For example, in the event viewer under administrator events, I see entries like:
Warning - 11/11/2022 4:39:01 PM DNS Client Events (Microsoft-Windows-DNS-Client) 1014 (1014)
Error - 11/11/2022 3:30:44 PM System Restore 8193 None
Error - 11/11/2022 3:29:36 PM Kernel-EventTracing 3 Session
Warning - 11/11/2022 3:29:36 PM Kernel-EventTracing 4 Logging
Warning - 11/11/2022 2:19:14 PM DistributedCOM 10016 None
Error - 11/11/2022 2:19:01 PM Server 2505 None
Warning - 11/11/2022 2:18:57 PM User Device Registration 360 None
Warning - 11/11/2022 2:18:57 PM DistributedCOM 10016 None
Warning - 11/11/2022 2:18:55 PM e2fexpress 27 None
For reliability history, there are several events daily—some indicate unexpected shutdowns. The latest entry on November 10th mentions:
Description
The system restarted due to a bugcheck. The issue was identified as 0x000001aa (details in the dump at C:\Windows\MEMORY.DMP). A file was saved with ID 00000000-0000-0000-0000-000000000000.
However, I'm facing an access problem: the memory dump file in C:/Windows/MEMORY.DMP is marked as read-only for me, even though I'm the administrator. This prevents me from opening it or sharing it with you.
I feel a bit embarrassed about this technical shortcoming. If you or someone else could clarify what would help and how to proceed, I'd really appreciate your guidance.
I often see several mistakes and different kinds of errors as a hint of PSU or power issues.
Not a definitive sign at all.
Actions to take:
Execute the built-in Windows troubleshooters, "sfc /scanno", and "dism" to check if Windows can locate and resolve problems.
References:
https://www.lifewire.com/how-to-use-sfc-...es-2626161
Learn how to use the DISM command tool for repairing Windows 10 image | Windows Central
Make sure all drivers are current, particularly the GPU. Download drivers directly from the manufacturer's site, reinstall if needed, and reconfigure as required. Avoid third-party installers.
Next: power off, unplug, and open the case.
Remove dust and debris.
Confirm that every connector, card, RAM, jumper, and case connection is securely placed.
Keep reviewing Reliability History and Event Viewer for more errors, shifting error codes, or identifying any recurring patterns.
Ralston, thanks for all the ideas. It might take some time to go through everything, but I hope it helps. I have a few questions: Is the 3D spike found after every crash probably linked to the PSU issue you mentioned, or could it be caused by other factors? Also, do you think the DISM command tool should work on Windows 11, besides the 'repair Windows 10 image' option you talked about? Additionally, I have an older but still functional Windows 10 machine. I’m considering setting up Origins there to check if the same issues appear. Many users on forums report similar problems with both Windows 10 and 7. I suspect it could point to a software issue from Ubisoft. On one of their developer forums, someone mentioned Ubisoft took responsibility and a fix is coming soon—but so far nothing has been released. Appreciate your time and assistance!
3D spike versus PSU, software versus hardware.
When I review it again, I’d lean slightly toward the PSU for now. This might be due to reported issues in Origin. It could require a high peak power level that triggers crashes.
I don’t know of any problems using DSM with Windows 11.
Don’t worry about feeling "technically lacking." None of this is straightforward, and many products leave consumers at a disadvantage when troubleshooting.
DIY solutions are increasingly difficult because of limited information (like the "Check Engine" code) and various manufacturer restrictions that hinder repairs.
You might want to try an older Windows 10 system. But it will probably need several updates before it’s fully compatible, and stability isn’t guaranteed.
A few members here have experience with memory dumps, and if needed, a dump can be shared.
In the meantime: could you check inside the case? If you’re unsure, ask a family member or friend who knows more.
Just proceed slowly and carefully.