Skip to content
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

Open
Darkhost1999 opened this issue Apr 1, 2023 · 20 comments
Open

Call of Duty: Black Ops II [BLUS31011] Fatal Device Lost Error #13602

Darkhost1999 opened this issue Apr 1, 2023 · 20 comments
Assignees
Labels
Bug Driver: NVIDIA Proprietary NVIDIA OpenGL or Vulkan driver Render: Vulkan

Comments

@Darkhost1999
Copy link
Contributor

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.

·F 0:00:58.200436 {RSX [0x80558bc]} SIG: Thread terminated due to fatal error: Assertion Failed! Vulkan API call failed with unrecoverable error: Device lost (Driver crashed with unspecified error or stopped responding and recovered) (VK_ERROR_DEVICE_LOST)
(in file C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\rpcs3\Emu\RSX\VK\VKQueryPool.cpp:45[:4], in function poke_query)
(in file C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\rpcs3\Emu\RSX\VK\vkutils\shared.cpp:107[:24], in function die_with_error)

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

@kd-11
Copy link
Contributor

kd-11 commented Apr 2, 2023

If it's consistent on your system you can install SDK and capture a log with debug output enabled.
Also missing steps to reproduce, it's a large game, I don't know if it crashes in the menus or a specific level, etc.

@Darkhost1999
Copy link
Contributor Author

Darkhost1999 commented Apr 2, 2023

If it's consistent on your system you can install SDK and capture a log with debug output enabled.

Debug.log

Also missing steps to reproduce, it's a large game, I don't know if it crashes in the menus or a specific level, etc.

When booting BLUS31011 updated to 1.19 the game crashes at the press start screen if using 100% default configuration.

@Darkhost1999
Copy link
Contributor Author

The press start screen being the main menu before you can even start a new game.

@kd-11
Copy link
Contributor

kd-11 commented Apr 2, 2023

I'm unable to reproduce on RTX 3050. The debug output also has no information about any violation that could cause a crash.
There is some log spam about use of barycentrics, but that shouldn't crash and has nothing to do with zcull accuracy. You can easily prove that this is not the culprit by setting shader quality to low.

@kd-11
Copy link
Contributor

kd-11 commented Apr 2, 2023

I have an idea - try this build: https://cirrus-ci.com/task/5489746785337344
Let's see if it solves the nvidia silent crash problem.

@Darkhost1999
Copy link
Contributor Author

There was a change. The fatal error is now before the intro cutscene rather than after.
Debug.log
RPCS3.log

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.

@kd-11
Copy link
Contributor

kd-11 commented Apr 3, 2023

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.

@kd-11 kd-11 added the Driver: NVIDIA Proprietary NVIDIA OpenGL or Vulkan driver label Apr 11, 2023
@Darkhost1999
Copy link
Contributor Author

Darkhost1999 commented May 17, 2023

Tested 13875
RPCS3.log
image
No change. And what's odd is if you don't press start on the title screen then that CELL_NET_CTL error is the last thing seen before the game freezes without that device lost error.

@kd-11
Copy link
Contributor

kd-11 commented May 17, 2023

Try with #13875

@Darkhost1999
Copy link
Contributor Author

Darkhost1999 commented May 17, 2023

This is using bc96333
image
RPCS3.log
-Edit add debug output log-
RPCS3.log

@Shoegzer
Copy link

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
CPU: Intel i7-10870H
GPU: Nvidia GTX 3070 / driver 530.41
Commit tested: 1371bf8
Log: RPCS3.log.zip

@Shoegzer
Copy link

Update: Gave this a closer look. As I mentioned I don't see the VK_ERROR_DEVICE_LOST exception in the log, though I do see CELL_NET_CTL_ERROR_NOT_CONNECTED as @Darkhost1999 has reported:

19386, spu:0]; [soft:665 hard:727]; Switches:[vol:187178 unvol:14150]; Wait:[9.577s, spur:131010]
·E 0:21:02.668006 {PPU[0x1000000] main_thread} SYS: Stat: 'cellNetCtlGetInfo' failed with 0x80130108 : CELL_NET_CTL_ERROR_NOT_CONNECTED [x2012]

This is soon followed by other entries that seem to reflect a problem, for example:

·W 0:21:02.668038 {PPU[0x100000a] Thread (hang detect) [0x0033d844]} PPU: 'sys_timer_usleep' aborted (9.539612s)

Failed attempts to resolve include:

  • SPU Decoder: ASMJIT
  • Framelimit: 30
  • Sleep timers accuracy: [all settings]
  • Driver wake-up delay: 200us
  • RSX FIFO accuracy: Atomic&Ordered
  • Accurate PPU 128 Reservations: Always Enabled
  • PPU Thread Count: 1

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).

@Darkhost1999
Copy link
Contributor Author

Issue not occurring on RPCS3 v0.0.29-15463-edf4f7ea Alpha
RPCS3.log
I used new caches and boot with default configuration. Did not skip any intro cutscenes. Request reopen if others can still reproduce.

@Shoegzer
Copy link

Shoegzer commented Aug 7, 2023

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.

·E 0:25:41.404741 {Emulation Join Thread} SIG: Thread [rsx::thread] is too sleepy. Waiting for it 4226396.399µs already!

Log: RPCS3.log.zip

@Darkhost1999
Copy link
Contributor Author

Looks like what I had when trying just today. Reinstall your game update files and try again.
Here is how to remove them
https://wiki.rpcs3.net/index.php?title=Help:Installing_Game_Updates#Removing_game_updates/game_data

@Darkhost1999 Darkhost1999 reopened this Aug 7, 2023
@Shoegzer
Copy link

Shoegzer commented Aug 8, 2023

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

@Asinin3
Copy link
Contributor

Asinin3 commented Sep 19, 2023

Test with #14657 (if its merged when you're reading this, just test latest RPCS3 build instead)

@Shoegzer
Copy link

Thanks, still freezes after 5-15 minutes after going ingame in testing a build with #14657. Again I do not see VK_ERROR_DEVICE_LOST in the logs but rather the others as I noted above.

New log in case it helps: RPCS3.log.zip

@Darkhost1999
Copy link
Contributor Author

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.

@Shoegzer
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Driver: NVIDIA Proprietary NVIDIA OpenGL or Vulkan driver Render: Vulkan
Projects
None yet
Development

No branches or pull requests

4 participants