Bloodborne PC Windows Port v0.6.1

This update fixes several startup crashes, mid-game memory faults, and high-FPS boss fight crashes reported in v0.6.0 and previous versions.

Changelog

• Fixed Startup Crash on Certain Systems (#134)

  • Fixed an early initialization crash (0xc0000005 at 0x207de26) where the engine attempted to read from an unallocated thread memory heap during startup.

• Fixed Crash When Applying Launcher Patches (#136)

  • Fixed an issue where enabling certain patches (such as heap size or resolution adjustments) caused the game to fail to boot (0xc0000005 write violation at 0x443025). Memory pools now safely handle custom allocation sizes.

• Fixed Mid-Game Crash During Heavy Texture Streaming (#135)

  • Fixed a crash in msvcrt.dll (memcpy) triggered when the game streamed new areas under high memory pressure. All internal memory transfer functions now safely validate memory addresses before copying.

• Fixed GPU "Device Lost" Crash in Central Yharnam (#129)

  • Resolved a Vulkan driver crash (VK_ERROR_DEVICE_LOST) that occurred in busy scenes with torches and mobs (especially at uncapped frame rates). Texture tiling compute dispatches now properly synchronize with the GPU queue, preventing Windows driver timeouts (TDR).

• Fixed Ebrietas Boss Fight Crash at High Frame Rates (#127)

  • Extended vertex and particle generator protection across worker threads. Cosmic charge attacks, spit projectiles, and aura effects no longer trigger crashes when playing at 60 FPS, 90 FPS, or above.

• Clear Diagnostics for Incomplete Game Dumps

  • Added validation in the preparation pipeline to detect empty (0-byte) or truncated eboot.bin files upfront with a clear message explaining that the dump file is incomplete, replacing cryptic out of bounds errors.

Issues Tackled

• Closes #127: Boss Fight Crash (Ebrietas at >60 FPS)
• Closes #129: GPU crash in Central Yharnam (vk_scheduler.cpp:516 SubmitExecution: Device lost)
• Closes #134: Startup Crash (0xc0000005 at 0x207de26)
• Closes #135: Mid-Game Crash in msvcrt.dll (memcpy NULL pointer)
• Closes #136: Startup Crash with Launcher Patches (0xc0000005 at 0x443025)
• Fixes prepare failed: out of bounds: 0x0+0x4 / 0x0 on empty/corrupted game binaries

Requirements

• OS: Windows 10 or Windows 11 (64-bit)
• GPU: Vulkan 1.3 capable graphics card (NVIDIA GTX 10-series+, AMD RX 400-series+, Intel Arc)
• CPU: x86-64 processor supporting AVX / SSE4.2 (AVX2 no longer required)
• Game Dump: Decrypted Bloodborne PS4 dump (CUSA03173, version 1.09) with eboot.bin

Fresh Installation

1. Extract the release archive to a dedicated folder.
2. Run BloodborneLauncher.exe (or run.bat).
3. Select your decrypted 1.09 eboot.bin path.
4. Set your graphics, framerate cap, and keybinds.
5. Click Launch Bloodborne.

Updating Existing Installation

1. Extract the new release archive.
2. Copy the new out and scripts folder.
3. Paste it into your existing bloodborne_pc_windows_port_v0.6.0_release folder, replacing the old out and scripts folder and overwriting all files when prompted.
4. Run BloodborneLauncher.exe.

In-Game Hotkeys

• F1 to capture/release mouse
• Insert or L3 + R3: Open the in-game settings overlay.
• F11: Toggle performance telemetry HUD.

Troubleshooting

If you get crashes, stuttering, or launch failures, try these before opening an issue:

• If the game crashes during area transitions or freezes on startup, set prep_workers=1 or prep_workers=2 in bbport.ini instead of auto. Higher values use more CPU threads at once, which can cause race conditions or driver timeouts on 4-core and 6-core CPUs.

• If it crashes during heavy boss fights or in areas with lots of enemies, set the target FPS to 60 in the launcher and see if it holds. 90+ FPS and uncapped modes work on high-end hardware, but higher frame rates mean a lot more particle and cloth physics calculations.

• Don't stack multiple frame rate or resolution patches. Combining "Uncap FPS++" with "60 FPS++", or running several heap mods together, can stop the game from booting. If that happens, start with only the essentials (like "Skip Intro") and add the rest back one at a time.

• If you see a GPU crash or visual corruption, delete the cached pipeline files in user/cache/CUSA03173/. The game regenerates them on the next launch.

Note

• When opening an issue about a crash or a bug you're experiencing, please make sure to attach the crash log from the out folder
  and the bblauncher.log

Discord Server

Join the Discord for updates, bug reports, and discussions about the Bloodborne PC Windows Port.
discord.gg/xHFkvtssuV