-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call of Duty: Black Ops II [BLUS31011] Fatal Device Lost Error #13602
Comments
If it's consistent on your system you can install SDK and capture a log with debug output enabled. |
When booting BLUS31011 updated to 1.19 the game crashes at the press start screen if using 100% default configuration. |
The press start screen being the main menu before you can even start a new game. |
I'm unable to reproduce on RTX 3050. The debug output also has no information about any violation that could cause a crash. |
I have an idea - try this build: https://cirrus-ci.com/task/5489746785337344 |
There was a change. The fatal error is now before the intro cutscene rather than after. I want to just ship my graphics card to you if I had a replacement/upgrade. Is there anything I can do here to obtain useful information and help the silent speak? I am willing to learn something new if it helps. |
We just have to wait for nvidia to implement VK_EXT_device_fault then. AMD already ships that extension, basically whenever the driver crashes it should give some more information to us about why it did so. Until then I think it's not very useful to keep fighting the NVIDIA driver. |
Tested 13875 |
Try with #13875 |
Getting something similar here, though not quite the same. The game doesn't crash at the start screen on default settings, but rather freezes ingame after a while (between 3-15 minutes), usually in the "zombies" mode. Using default settings except for Approximate ZCull accuracy and Ordered&Atomic RSX FIFO accuracy. Note though, the "device lost" message isn't thrown to the log file. The log below is quite large as it took about 15 minutes of play to trigger the freeze. OS: Linux Mint 21.1 / kernel 5.15 |
Update: Gave this a closer look. As I mentioned I don't see the
This is soon followed by other entries that seem to reflect a problem, for example:
Failed attempts to resolve include:
Note that I cannot test OpenGL as rpcs3 hangs during the initial shader build process (though this happens with all titles, not just this one). |
Issue not occurring on RPCS3 v0.0.29-15463-edf4f7ea Alpha |
Still freezing here unfortunately, after several single-player zombie mode games. Tested against commit edf4f7e with new cache and default configuration as well. Please re-open.
Log: RPCS3.log.zip |
Looks like what I had when trying just today. Reinstall your game update files and try again. |
Thanks for reopening. I tried what you suggested but it still froze. Update path was from 1.00 > 1.09 > 1.19, was that yours? Log: RPCS3.log.zip |
Test with #14657 (if its merged when you're reading this, just test latest RPCS3 build instead) |
Thanks, still freezes after 5-15 minutes after going ingame in testing a build with #14657. Again I do not see New log in case it helps: RPCS3.log.zip |
Yea freezes for me as well. However, I believe that branches this issue into a new issue entirely. I also know I don't obtain freezes with zcull accuracy is changed from precise and can play to the end game. |
Well I can certainly create a new issue for this, as this one's title may be misleading assuming the fatal device error isn't a cause of freezing any more. With regards to zcull accuracy, I've tested using precise and approximate and freezing occurs with either (though perhaps not as frequent with approximate). Play in zombie survival mode, specifically starting in the bus station, and you should see the same thing? |
Quick summary
Note this issue is resolved/bypassed by using Approximate Zcull Accuracy.
The wiki does mention improved performance with Approximate Zcull Accuracy.
https://wiki.rpcs3.net/index.php?title=Call_of_Duty%3A_Black_Ops_2
However, The use of accuracy settings should not cause a fatal error
Details
When booting BLUS31011 updated to 1.19 the game crashes at the press start screen if using 100% default configuration.
But by changing zcull to approximate or relaxed we can actually play the game. This same fatal error and device lost affects so many of my games that I am glad to have obtained this game and am able to make a replicable debug output log.
Attach a log file
Debug.log
Crash.log
Working-Approximate Zcull Accuracy.log
Attach capture files for visual issues
Not a visual issue
System configuration
Ryzen 5 3600
Gtx 1660S
Windows 11 beta insider
Other details
I hope this helps end the device lost errors. I know there is a workaround but it's not a proper fix
The text was updated successfully, but these errors were encountered: