Crash to unresponsive black screen

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Reposting this bug / Fault here to see if I can get to the bottom of this.

Originally posted by oOOOoeAaaAAaAAaaAAAhHHHhhHhee...:

I have submitted a bug report on this already but I am getting a very strange crash after a few minutes of play. I believe the nvidia driver is crashing as the screen goes black (no signal at all from the graphics card output). It does not recover and requires a manual hard reset of the system to recover. Radio music is often still playing in the background but Its hard to say if the game is still responding to input.

I found suggestions on other unreal related content that it might be a corrupted cache to do with the engine and reinstalling the game before a play session seems to help. I can usually (but not always) get through a single play session without crashing after a reinstall.

CPU + GPU Temps, and RAM usage seem fine shortly before crashing.
System: 5800x3d, rtx 3080, 32GB ram.

This is the only unreal engine game I have this problem with.

wondering if anyone else has experienced this.

I am currently doing some dev work in Unreal Engine 5 myself, so it would be very interesting to find out whats causing this. Any ideas or help is much appreciated.

Specific hardware:

CPU: Ryzen 7 5800x3d
GPU: ASUS ROG Strix 3080 10GB
RAM: KLEVV BOLT X 32GB (16GB x 2) 3200MHz
MOTHERBOARD: ASROCK X570 PHANTOM GAMING X

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

I agree with the assessment that this looks like a hardware issue, but this is the only game I have had anything like this problem with.

This thread sounds similar although there's not much info there:
https://steamcommunity.com/app/1458140/discussions/0/4211498059467350111/

[Aluvard]

Try to turn off MFAA in Nvidia Control Panel (it should be in Manage 3D Settings).

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

MFAA is set to Off already

[animal_PLANET]

Yea, I would check on BIOS as well.

What version/build of windows are you running?

What is your CPU cooler?

PSU?

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Not running EXPO
Windows 11
Cooler: EK-AIO Basic 360
PSU: Corsair HX Series HX1000

Will check my BIOS, I don't recall when I last updated

[animal_PLANET]

Is win 11 fully up to date on latest public build?

When installing win 11, did you use the upgrade process or clean install?

Are you OC CPU and or GPU? Try default clocks/voltages?

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Just Flashed to latest BIOS, no change. game Still causes gpu to fail after a few minutes. reset all nvidia control panel settings too, no change.

Win 11 was a clean install, possibly not totally up to date but shouldn't be far off, I will force the updates. CPU and GPU are running stock

[animal_PLANET]

Did you let windows install chipset and system drivers for motherboard? Or did you do so and DL them from ASrock?

Have you checked your GPU BIOS? ASUS released V6 to help with other issues from previous update including re-bar. Check their support site on that.

Are you using Re-bar or GPU scheduling?

Have you tried running DDU and do a clean boot?

Running DDU will remove previous driver completely and ensure a clean install of newest display driver. Like its being done for the first time on a newly installed OS.

Here is link to DDU. Make sure to read/follow guide if unfamiliar. https://www.wagnardsoft.com/forums/viewtopic.php?t=4876

A clean boot will remove any potential conflicts with other software running in background. Disable all non essential services, programs and tasks from starting with PC. So use services (services app or system configuration app), tasks (task scheduler app), and startup items (task manager) to disable them. Check all 3 areas. If anyone is enabled that software will run and could be causing conflicts with games. This will also help free up system resources in general.

I would also check event viewer. See if a crash report is being logged. So open event viewer app. Go to windows logs>application. Look for Pacific Drive at time and date of crash. If a report is even being made. Look for faulting module name and path. Its at bottom of page under the general tab. As well as checking system logs at time and date of system failure.

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Ok, I've been through your list there. Updated my BIOS and VBIOS; Enabled Rebar; Cleaned drivers with DDU and reinstalled. Looking at event viewer, I have this event:

Faulting module name: ntdll.dll, version: 10.0.22621.3235, time stamp: 0xa2c4352c
Exception code: 0xc0000374
Fault offset: 0x000000000010c1a9
Faulting process ID: 0x0x48C0
Faulting application start time: 0x0x1DA772CABF0D8D9
Faulting application path: D:\SteamLibrary\steamapps\common\Pacific Drive\PenDriverPro\Binaries\Win64\PenDriverPro-Win64-Shipping.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 30cfef22-420f-4e9c-b9a5-c7bd73fb4176
Faulting package full name:
Faulting package-relative application ID:

But it doesn't seem to appear with as much frequency as the black screen crashes, so I'm not sure if it is a related failure.

I booted the game for about 10 minutes just now and no crash so far, but I'll try to have a session tonight and see what happens. Cheers for the suggestions so far!

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

This looks like the same Issue here:

https://answers.microsoft.com/en-us/windows/forum/all/laptop-screen-going-black-randomly-after-update-my/0347d338-5f3c-4862-9d97-74faae480d76

[Deja Vu]

That exception code (0xc0000374) is the important bit I believe. Googling it shows something called STATUS_HEAP_CORRUPTION.

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Yeah, Looks like people are having similar non-recoverable black screen GPU output failures along side it too. But Im not sure that it actually narrows down the problem beyond that. I am still hopeful that DDU has purged the problem. I'll find out tonight

[animal_PLANET]

Let us know how those other steps worked for you. If you played again for a bit and it didnt crash yet. Hopefully that is good sign. GL!

Just to add. There maybe some system corruption here if running DDU and installing new drivers does not help along with the other suggestions.

Next step would be to do an sfc scan for windows. See this video for more on how to do that.

https://www.youtube.com/watch?v=BWqPjSg5IYM

However, I would make sure you update windows first to latest public build. No insider, preview, or optional updates.

Since this is a system file error. It could mean windows file structure is bad. You have possible bad memory, and or bad storage drive. Or just a bad install of windows.

If you still have the issue after doing an sfc scan and restore. Unfortunately the next step is installing windows again clean. Which means. Save any data you want to backup first. When running the install you want to completely delete all partitions on the drive. If only one partition the better. Than just select that drive without creating a new partition and windows will take care of the rest. This will ensure a clean install.

If the issue still persists, than that is were things get more complicated as it than may be a memory or drive issue. Hopefully it doesnt get that far.

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Ok so thought I would just have a cheeky mid afternoon drive. Crashing is still persisting. This crash was after a fresh boot of the PC, crashing about 8 minutes into a game, just walking around and interacting with parts and stations in the garage. Nothing of note at the time of the crash other than the rainstorm weather.

I have referred this user here as it sounds like a very similar issue:
https://steamcommunity.com/app/1458140/discussions/0/4288062617425861458/

This still remains as the only application I have any trouble with. Will continue to try fixes as and when I have time and keep you updated, cheers!

[oOOOoeAaaAAaAAaaAAAhHHHhhHhee...]

Originally posted by zen:

anything relevant in "C:/Users/Your Username/AppData/Local/PenDriverPro/Saved/Logs"?

Just looks like the engine is reporting loss of access to the gpu.

https://pastebin.com/g8WNvmvQ