| Symptom | First useful check | Do not assume |
|---|---|---|
| Black screen before the title menu; mods installed | Identify and temporarily disable your installed loader. | That fixing startup also fixes in-game crashes. |
| Startup crash; never used mods | Verify Steam files, then record the error and driver version. | That you need to download REFramework. |
| Crash when changing a setting or opening inventory | Record the exact menu and whether frame generation is involved. | That an old menu fix applies to this update. |
| Fatal D3D error during exploration | Capture the full code and compare one reversible setting change. | That the code alone proves a defective GPU or one engine bug. |
Startup black screen with mods
Close the game and record your mod manager, loader version and installed tools. REFramework’s author documentation [1] identifies dinput8.dll in the game directory as its non-VR loader. If you knowingly installed that file, temporarily move that specific copy to a backup folder outside the game directory, or use the tool’s uninstall procedure. Do not remove similarly named Windows files or unfamiliar DLLs.
Launch once without the loader. If you reach the menu, record that result before restoring anything. Only reintroduce a loader or mod when its author supports your game version. If the same crash remains, keep the original files backed up and move to the unmodded checks; repeatedly swapping loaders will not establish a diagnosis.
One DLSS5-Swapper issue [2] reports that updating REFramework to nightly 01408 (external) fixed a startup problem. That is a tool-specific, single-reporter outcome, not a recommended download for every DD2 player. The linked release predates the October expansion window; this page does not claim it is the latest or universally compatible build.
No mods, or the crash survives their removal
Run the standard Steam file verification [3]: Library → Dragon’s Dogma 2 → Properties → Installed Files → Verify integrity of game files. Let it finish, then retest the same action. Verification is an installation check, not evidence that a game update has no bugs.
For further baseline checks, Capcom’s Steam troubleshooting guidance [4] recommends checking requirements, graphics drivers and Windows updates. Record the existing driver version before changing it, use your hardware vendor’s supported installer, and restart afterward. Change one thing at a time so a working or failing result can be interpreted.
In an October 11 PC report [5], disabling mods got the player past a startup black screen, but walking outside town still crashed the game. Verification, reinstalling and updating drivers had already failed for that later symptom. A second commenter reported recurring crashes in Norgan. This is why reaching the menu is only the first test, not proof that the whole problem is solved.
Fatal D3D errors: compare outcomes, not promises
Save the complete error text, including the number and any DXGI_ERROR or DeviceRemovedReason value. Reports that share the phrase “Fatal D3D” may differ in timing, hardware and installed software. The following counts describe visible individual reports, not controlled tests.
| Reported change | Observed outcome | Scope |
|---|---|---|
| Texture Quality → Medium (0.25 GB) | One temporary success; one explicit failure on retest | Success reporter had tested the base-game area, not the DLC zone. |
| Reinstall drivers plus verify files | One poster thought this resolved their crashes | Two changes together; no isolated cause or long-term follow-up. |
| Remove mods, verify and reinstall | One in-game CTD case remained unresolved | Startup had improved, exploration had not. |
The texture outcomes come from the October 10 crash discussion [6]; the driver-and-verification report comes from a separate Fatal D3D thread [7]. If you can open settings, a lower texture setting is a reversible comparison: record the old value, repeat the same route, and restore it if it offers no useful improvement. A short crash-free session cannot establish a fix when the original failures were intermittent.
Menu crashes need their own reproduction steps
Write down whether opening inventory crashes, changing resolution crashes, or enabling frame generation crashes. An older menu-crash report [8] described both graphics-settings and inventory failures, with several attempted changes unsuccessful. It is historical evidence of a distinct symptom, not confirmation of an October 2026 fix. Avoid applying a 2024 procedure solely because its headline matches.
If the whole PC resets, or the GPU disappears from Windows, stop repeatedly provoking the same failure and include that system-level behavior in your support report. It is materially different from DD2 closing to the desktop.
What to send when the next test still fails
Keep the crash reporter and your saves. This guide has not established save deletion, deleting CrashReport.exe, or adding -dx11 as a current remedy. One unresolved report had already tried the latter two without success.
Capcom requests [4] hardware specifications, driver and OS versions, graphics settings, reproduction steps and crash-report files. Add the game version, mod status, exact location or menu, time until failure, and the result of each individual change. Send these through Capcom’s support form (external); avoid posting account information in a public thread. A precise unresolved report is more useful than another untracked reinstall.
Common questions
Does verifying Steam files fix every crash?
No. It checks the installation, and the reports include crashes that continued afterward. Record whether the failure changes.
Do I need REFramework if I never used mods?
No. The loader-specific reports apply to players who installed that tool. Follow the unmodded checks when no loader is present.
Does a short crash-free test mean it is fixed?
Not when the original error was intermittent. Note the route and test duration, then compare them with how the crash normally occurred.
Sources & verification
The notes above link to these sources. External originals open in a new tab.
- GitHub · praydog / REFramework (external, opens in a new tab)Checked 14 October 2026
Author documentation identifying the loader and installation file; relevant only when this tool is installed.
- GitHub · DLSS5-Swapper issue 314 (external, opens in a new tab)Checked 14 October 2026
One tool-specific startup report and linked nightly; not a universal fix or a current-version recommendation.
- Steam Support (external, opens in a new tab)Checked 14 October 2026
Official game-file verification procedure; checking files does not establish that game bugs are fixed.
- CAPCOM Support (external, opens in a new tab)Updated 22 July 2026; checked 14 October
General Steam troubleshooting and information required for support; not an October DD2-specific hotfix.
- Reddit · crashes after adding DLC (external, opens in a new tab)Checked 14 October 2026
Startup improved after disabling mods, but the original reporter still had in-game crashes; a second reporter described Norgan crashes.
- Reddit · random crashes after DLC (external, opens in a new tab)Checked 14 October 2026
Texture-setting change: one limited improvement and one failure; intermittent errors complicate short tests.
- Reddit · Fatal D3D discussion (external, opens in a new tab)Checked 14 October 2026
A combined driver/file-verification improvement and an unresolved report; long-term success not established.
- Reddit · older menu-crash discussion (external, opens in a new tab)2024 report; checked 14 October 2026
Earlier symptom comparison for menu crashes; does not prove that the current expansion has the same cause.