iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Most problems in the unofficial native Windows port of Shadow of the Colossus have a specific cause: an incorrectly identified CUSA08809 dump, missing user-owned sound modules, an outdated build, a shader cache being rebuilt after an update, Vulkan/GPU incompatibility, or an input layer outside the game. Verify the game folder first, install the required firmware modules for audio, update the port, allow the first shader rebuild to finish, and then troubleshoot graphics or controllers according to the symptom.
This guide covers the native Windows port of the PS4 version and separates those fixes from documented RPCS3 and PCSX2 emulator workarounds. The emulator steps are not interchangeable with the native-port steps.
![ICO and Shadow of the Colossus [Limited Edition] [Japan Import]](https://m.media-amazon.com/images/I/51LoyTA6T7L._SL160_.jpg)
Identify which version you are troubleshooting
There are three different setups commonly described as “the PC version,” and each has different failure points:
Recommended Free Tools
| Setup | What runs on the PC | Renderer and files that matter | Typical first checks |
|---|---|---|---|
| Unofficial native Windows port | The game’s x86-64 code runs directly on the PC CPU. | PS4 GPU work is translated through Vulkan. The launcher expects a CUSA08809 game folder containing eboot.bin, sce_module, and sce_sys. |
Confirm the dump, Vulkan driver, release version, shader rebuild, and sound modules. |
| RPCS3 PS3 Classics HD release | The PS3 game runs through an emulator. | The emulator’s Vulkan backend can report a device-lost error before the main menu. | Try the game’s custom “High precision Z buffer” setting and record the RPCS3 build and GPU. |
| PCSX2 setup | A PlayStation 2 title runs through an emulator. | Controller software, Steam Input, and third-party vibration drivers can interfere with the emulator. | Test without Steam Input and check for EZFRD64.dll. |
The rest of this article labels the path being discussed. Do not copy a PCSX2 driver fix into the native port, or use a native-port file layout to diagnose RPCS3.
Check the native port’s prerequisites before changing settings
The documented baseline for the native Windows port is Windows 10 or Windows 11, 64-bit, with a recent graphics driver and a Vulkan 1.3-capable NVIDIA, AMD, or Intel GPU. Vulkan is the supported renderer. The project does not use DirectX 11 or DirectX 12 for this port, so installing a DirectX runtime will not correct a Vulkan startup failure.
Confirm the game identity and directory structure
The launcher searches for a folder for the PS4 title ID CUSA08809. Inside that game folder, it must be able to find all three of these items:
eboot.binsce_modulesce_sys
If even one is absent, point the launcher at the correct root of your dump rather than at a parent folder, an extracted archive’s outer folder, or a subdirectory such as sce_sys. A folder with similarly named files from another region or title ID is not a valid substitute.
Prefer the documented EU 1.01 dump when available
The project recommends the EU 1.01 dump for its 60 FPS and 16x filtering modes. That recommendation does not mean every other dump will fail to boot; it means those modes are documented against that build. When a feature is missing or a crash appears only after enabling one of those options, record the exact region and game version before assuming the graphics setting is defective.
Use a current Vulkan driver
Update the driver supplied for the installed GPU, then restart Windows before retesting. Vulkan behavior is highly dependent on the GPU and driver combination. Keep the exact GPU model and driver version in your notes; those details are needed if the issue remains after the file and release checks.
Resolve missing sound files and a silent game
The native port does not redistribute Sony firmware. A silent installation usually means the two required sound modules are missing, not that another generic redistributable package needs to be downloaded.
Provide the two required modules
Supply your own decrypted copies of:
libSceNgs2.sprxlibSceUlt.sprx
The launcher can copy these modules from an existing shadPS4 installation’s user/sys_modules directory, or you can provide modules obtained from your own console. The distributed port ZIP intentionally does not contain them because they are Sony firmware.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use this audio diagnosis
- Close the game and launcher.
- Check whether both
.sprxfilenames are present in the location from which the launcher imports system modules. - If you use shadPS4, verify that the files are in its
user/sys_modulesdirectory and use the launcher’s copy/import function. - Start the game and test a scene with voice, music, or effects rather than relying only on the title screen.
- If the game is still silent, keep the modules in place and continue with the release and log checks; do not download a replacement firmware archive from an unofficial source.
Missing modules explain absent audio. They do not normally explain a missing eboot.bin, a Vulkan device failure, or a controller that is not detected.
Also popular on Amazon
Update before diagnosing an old crash
Install the current port release before changing a large number of options. Several crashes in older builds already have recorded fixes:
| Port version | Historical problem addressed | What to do |
|---|---|---|
| 0.0.13 | An intro/menu crash caused by requesting more textures than the available pool could hold. | Update rather than trying to work around the intro with random texture or memory settings. |
| 0.0.12 | Memory corruption that could close the game after loading a save. | Update, then retest the same save. Make a backup of saves before repeated troubleshooting. |
| Current release | Later fixes and hardware-specific changes, including the AMD color-path change documented in version 0.57. | Use the newest release you can obtain, and record its exact version when reporting a failure. |
These version notes explain why an old crash report may not match current behavior. If a failure disappears after updating, avoid retaining obsolete launch flags or workarounds unless the current release still needs them.
Allow the first shader rebuild to finish
After an update, the first launch can be slow and may stutter while shaders are rebuilt. That delay is expected cache work, not proof that the installation is frozen or corrupt. Let the game continue for a reasonable period before terminating it, especially immediately after changing the executable or graphics driver.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →If the window eventually reaches the menu, close and relaunch once more. Later launches should use the rebuilt cache and provide a better indication of the port’s normal performance. Do not judge a new driver or release solely from the first shader-compilation run.
What to do when the game still closes
Separate a missing-file failure from a runtime crash
- If the launcher cannot find the game, return to the CUSA08809 folder check and verify
eboot.bin,sce_module, andsce_sys. - If the game opens but has no sound, check
libSceNgs2.sprxandlibSceUlt.sprx. - If it closes after an update or at the first launch, allow shader rebuilding before changing settings.
- If it reaches the menu and closes while loading a save, update past the memory-corruption fix in 0.0.12 and retest a backed-up save.
- If it closes in the intro or menus, update past the texture-pool fix in 0.0.13.
Collect the log instead of guessing
When the program still exits by itself, preserve the run information at user/last_run.log. The project’s explicit guidance is: “The game closed by itself? Open an issue with user/last_run.log.” Attach that file to the project’s issue report along with the port version, Windows version, GPU model, graphics-driver version, game region/build, and the exact point of failure.
Describe a reproducible sequence rather than writing only “it crashes.” For example, state whether the crash occurs before the title screen, after selecting “Continue,” when entering a particular colossus arena, or immediately after changing an Image and FPS option. If the failure stopped after removing a setting, include the old and new values.
Fix green, pink, black, or incorrectly colored characters
Version 0.57 documents an AMD-specific rendering change for green or pink fog and for characters that appear incorrectly colored or black. AMD cards now use the same 32-lane path as NVIDIA. The release notes also state that the change had not yet been tested on an AMD card, so it is a documented fix, not a universal compatibility guarantee.
Use this graphics sequence
- Update the port to a release containing the version 0.57 AMD change.
- Install a current driver for the exact GPU.
- Launch with the default Vulkan settings first, without stacking several experimental options.
- Reproduce the color artifact and note whether it affects fog, characters, the title demo, or every scene.
- If it remains, save
user/last_run.logand report the GPU model, driver version, port version, and a description of the colors or black surfaces.
On NVIDIA, AMD, and Intel hardware, the same symptom can have different causes. Do not describe the AMD fix as proof that every driver has been tested; the release’s own testing qualification matters when you decide whether to report the result.
Also popular on Amazon
- Action-Packed Battles - Players will switch between using melee and ranged attacks in battle against hordes of enemies and challenging bosses across a variety of open field maps.
- Beautifully Desolate Open-World - The game seamlessly joins together hauntingly beautiful vistas and locations with no area loading.
- Masterfully Crafted Story and Characters - NieR: Automata tells the story of androids 2B, 9S and A2 and their ferocious battle to reclaim a machine-driven dystopia overrun by powerful weapons known as machine lifeforms.
- Elements of an RPG - Players will obtain a variety of weapon types, level up in battle, learn new combat skills, and customise a loadout that caters to their playstyle.
- Utilise the Pod Support System to Assist In and Outside of Battle - Pods can attack the enemy in both manual and lock-on modes.
Handle GPU-work-submission options carefully
The launcher exposes GPU-work-submission controls for AMD and Intel hardware. The README also documents NVIDIA-only submission options under the Image and FPS settings for cases where the normal path is not working.
- Start with the submission setting at Automatic.
- If a documented GPU-work problem persists, test the NVIDIA-only submission option described by the launcher.
- Restart the game after changing the option so the new submission path is actually used.
- If the screen becomes black, return the setting to Automatic immediately and retest.
A black screen after changing a submission option is a reason to undo that option, not evidence that the game dump is missing. Change one graphics setting at a time so the resulting log and symptom remain meaningful.
Improve performance without confusing it with a crash fix
The port includes a full-water-reflections/direct-memory-access option. The documented title-demo result rises from about 54 FPS to about 59 FPS—approximately 10 percent—when the option is disabled. The trade-off is flatter-looking distant water.
Use that setting only as a performance choice. It does not repair a startup crash, missing sound, a Vulkan device failure, or controller mapping. Record whether the measurement is from the title demo or normal gameplay; the cited figures are title-demo results, not a universal frame-rate guarantee for every scene, GPU, or driver.
RPCS3: fix the documented Vulkan device-lost case
If you are running the PS3 Classics HD release in RPCS3 rather than the native Windows port, issue #7774 documents a different failure: Vulkan reported “device lost” before the main menu.
Enable High precision Z buffer
- Open RPCS3 and locate the Shadow of the Colossus game entry.
- Open the game’s custom configuration, not only the global emulator settings.
- Find the graphics option named High precision Z buffer and enable it.
- Save the per-game configuration and boot the title again.
The reporter in that case confirmed that the game then booted smoothly. This is a documented workaround for that issue, not proof that the same toggle resolves every Vulkan failure.
If Vulkan still fails
Test another renderer to isolate whether the failure is specific to Vulkan. In the original report, OpenGL worked without crashes at that time. Emulator builds and GPU drivers change, so treat that result as historical evidence. Write down the current RPCS3 build, GPU, driver, renderer, and whether the failure happens before or after the main menu.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchNative-port controller troubleshooting
The native port lists support for DualShock 4, DualSense, and Xbox controllers, along with key remapping and mouse camera controls. The fastest way to determine whether input is the problem is to test the game independently of the controller.
Also popular on Amazon
- Video Game Cover Art design. Officially licensed PlayStation video game merch. Play has no limits in this cool gamer gear that features the iconic video gaming console brand. Greatness awaits in this awesome apparel.
- Perfect graphic merchandise for fans of Video Games, Gaming, Merch for Gamers, Wander and Mono, and Gamer fashion. Our PlayStation merch is made with gamers in mind. You'll be ready to play all day in this fun apparel.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Use a keyboard test to classify the failure
- Start the port without the controller connected.
- Use the keyboard mapping shown on the port’s own mapping page to reach the title screen and navigate a menu.
- If keyboard input works, the game has booted and the remaining problem is the controller or its driver layer.
- If keyboard input also fails, return to the dump, release, shader, Vulkan, and log checks; changing a controller will not repair a startup crash.
Remap and isolate the physical device
Connect one controller at a time and use the port’s key-remapping controls rather than relying on a third-party profile. Check that the left and right sticks, triggers, face buttons, and menu buttons produce the intended actions. If buttons are shifted, remove other virtual gamepads and remapping tools temporarily, reconnect the controller, and map it again.
A wired Xbox-compatible USB controller is a practical test accessory when a wireless pad is not detected or maps incorrectly. It is useful as an isolation step, not a requirement for the port. If the wired device works, compare connection mode, firmware, and driver layers on the original controller.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.PCSX2: remove Steam Input interference
PCSX2’s official controller documentation describes a separate Windows conflict: Steam’s built-in controller support can send unintended keyboard input. The emulator may appear to press keys by itself, trigger hotkeys, or navigate menus unpredictably even though the controller is functioning.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use one of the documented remedies:
- Exit Steam completely before launching PCSX2.
- Disable controller support in Steam.
- Change Steam’s desktop layout and emulator hotkeys so the controller is not mapped to random keyboard commands.
Retest after each change. If the unexpected keyboard input disappears when Steam is closed, the emulator and controller are not necessarily defective; the conflict is in the input layer above PCSX2.
PCSX2: remove the EZFRD64.dll driver conflict
PCSX2 also warns that many third-party controllers and adapters use a buggy driver commonly identified as EZFRD64.dll. According to the documentation, that driver can corrupt memory and crash the emulator whenever the controller is plugged in.
Clean removal procedure
- Close PCSX2 completely.
- Unplug the affected controller or adapter.
- Check for the driver directory
C:WindowsUSB_Vibration. - Remove that directory, or uninstall the related driver through Windows Control Panel.
- Reboot Windows.
- Start PCSX2 with the controller disconnected, confirm the emulator is stable, and then reconnect a known-good controller for testing.
Do not perform this PCSX2 cleanup as a native-port fix unless you have independently confirmed that the same driver is interfering with your Windows input stack. The documented crash behavior belongs to the emulator/controller-driver case.
A symptom-to-action checklist
| Symptom | Most useful first action | Evidence to retain |
|---|---|---|
| Launcher cannot find the game | Point it to the CUSA08809 root and verify eboot.bin, sce_module, and sce_sys. |
Region, game version, and folder layout. |
| Game starts with no audio | Provide decrypted libSceNgs2.sprx and libSceUlt.sprx from an authorized source or shadPS4’s user/sys_modules. |
Module names and the import location used. |
| Slow, stuttering first launch after update | Wait for shader rebuilding to finish. | Whether later launches improve. |
| Intro/menu crash | Update past 0.0.13. | Port version and user/last_run.log. |
| Crash after loading a save | Update past 0.0.12 and retest a backed-up save. | Save location, action that triggers the close, and log. |
| Green/pink fog or black characters on AMD | Use a release containing the version 0.57 AMD path change, then retest with current drivers. | GPU, driver, release, scene, and log. |
| Black screen after a submission-option change | Restore Automatic. | Previous and current submission setting. |
| RPCS3 Vulkan “device lost” before menu | Enable High precision Z buffer in the game’s custom configuration. | RPCS3 build, renderer, GPU, and driver. |
| Native port ignores a controller | Test keyboard input, then connect one supported controller and remap it. | Connection type, controller model, and mapping result. |
| PCSX2 receives random key presses | Exit or reconfigure Steam Input. | Steam state and desktop-layout settings. |
| PCSX2 crashes when a controller is plugged in | Remove or uninstall the EZFRD64.dll-related driver and reboot. |
Driver path and whether the crash depends on plugging in the device. |
What to include in a useful bug report
No published compatibility matrix guarantees a crash-free result for every GPU, driver, dump, or emulator build. A complete report lets maintainers distinguish a missing file from a regression or an untested hardware path.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors- Exact native-port or emulator version.
- Windows version and whether it is 64-bit.
- GPU model and graphics-driver version.
- Game region and build, including whether it is EU 1.01 for the native port.
- Renderer and any non-default graphics options.
- Controller model, wired or wireless connection, and any active remapping software.
- The precise reproduction steps and whether keyboard input works.
user/last_run.logfor native-port exits, attached without editing its contents.
That information is more valuable than repeatedly changing unrelated settings. It also makes clear whether a fix is already present in a release, a configuration workaround, or an unresolved hardware-dependent symptom.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
