Still Wakes the Deep - Fatal Error Crash and Black Screen
Some Still Wakes the Deep players have reported a Fatal Error followed by a black screen. We'll investigate the potential causes of the game's crashes and possible solutions to fix this issue.
Still Wakes the Deep is a first-person narrative horror game set in 1975 on a North Sea oil rig. Developed by The Chinese Room, also known for Amnesia: A Machine for Pigs, the game attracted a large number of players, but some encountered a “Fatal Error” resulting in a black screen and a crash. Read on if you want to know what can cause this issue and how to fix it to get you back into the game.
Fatal Error and Black Screen in Still Wakes the Deep Explained & How to Fix it
Some players have stumbled upon a Fatal Error with a ‘UE-Habitat Game has crashed and will close’ notification while launching Still Wakes the Deep or during the game’s cutscenes. Here’s what may help:
- Verify game files: Both Steam and Game Pass offer options to verify the integrity of the game files. This checks for any corrupted data that might be causing the crash.
- Update drivers: Outdated drivers can sometimes cause crashes. Make sure you have latest drivers for your graphics card.
- Reinstall the game: If nothing else works, you can try reinstalling Still Wakes the Deep. This will ensure all the game files are installed correctly.
If none of the above helped, there might be another reason for the Fatal Error problem. Apparently, a compatibility issue between Intel's 13th and 14th gen CPUs and certain games, including Still Wakes the Deep, is causing shader problems. Here’s a breakdown:
- Overvoltage: The motherboard might be supplying too much voltage to the CPU.
- Auto-overlocking: Some motherboards might be automatically overclocking 13th and 14th Intel CPUs, causing instability.
- Solutions: Updating the motherboard’s BIOS might have fixes from the manufacturer or manually reducing the CPU’s clock speed can help. However, downclocking is recommended for advanced users who understand the potential risks involved.
You can read more about this issue on Intel official forum discussion.