Silent Hill: Townfall Crashing on Launch: PC Display Checks
Townfall crashes before the menu or opens to a black screen? Check the reported display-scaling workaround, a limited 60 Hz test and Steam file verification.
Quick answer
For a Townfall PC startup crash with DXGI_ERROR_INVALID_CALL, several Steam players report that setting Windows display scale to 100% let the game launch. This is a community workaround, not a confirmed patch. A separate black-screen report improved at 60 Hz. Test one display setting at a time and restore it if it does not help.
On this page
Match the failure before changing settings
Use these checks when the PC game begins launching but closes or stays black before you can play. The Steam thread includes a D3D12Viewport error with DXGI_ERROR_INVALID_CALL; a later reply asks where to find the scaling setting. Different startup errors can have different causes. Record the full error, game version, GPU and driver version before testing.
A grey Play button after preloading is an access question. If the game already runs but hitches during movement, follow the frame-pacing guide instead.
Test Windows display scale at 100%
The September 22 Steam discussion contains a suggestion to use 100% scaling and three follow-up success reports, including the original poster. Fullscreen-optimization changes had mixed results in the same thread. These observations justify a reversible scaling test; they do not establish the underlying cause.
- Close Townfall. Note your current display scale so you can restore it.
- Open Windows Settings, then System, then Display. Select the display used for the game if more than one is connected.
- Under Scale & layout, set Scale to 100% using the available dropdown. This is desktop scaling, not the game’s render-resolution percentage or the separate Text size slider.
- Launch Townfall again without changing another setting. If the same error remains, restore your previous scale. If it works, record the result and reassess the workaround after a game update.
For a black screen, compare a supported 60 Hz mode
In a separate September 22–23 Reddit exchange, a player suggested 60 Hz in NVIDIA settings and the original poster reported success. That is one confirmed follow-up, weaker evidence than the scaling reports. It does not show that every high-refresh display is affected.
If your display offers 60 Hz, close the game and note its current rate. In NVIDIA Control Panel, open Display, then Change resolution, choose the gaming display and select 60 Hz from the Refresh rate list. Windows also exposes supported rates under Settings, System, Display, Advanced display. Select the correct display before changing it. Do not create a custom timing to force a missing option.
Try launching once, then restore the previous rate if there is no improvement. Refresh rate is measured in Hz and is separate from an in-game FPS limit. Lowering it can make the rest of the desktop feel less smooth.
Verify the installation and keep a useful failure record
If the display comparisons do not help, use Steam’s official file check: restart the computer, open Steam, select Townfall in Library, open Properties, then Installed Files, and choose Verify integrity of game files. Let verification finish before retrying. This checks the installation; it is not a promised solution to the reported display error.
For a continuing failure, retain the error text, whether you reached the menu, display resolution/scale/refresh rate, hardware and driver details, and the result of each separate test. Send that information through the game’s support route. This guide does not reproduce advice to disable Windows security controls or install replacement DLLs from a forum.
Common questions
Is this an official Townfall crash fix?
No. The game-specific results are dated community observations checked September 23, 2026. Microsoft, NVIDIA and Steam documentation support the settings and verification procedures, not a Townfall-specific cure.
Will these steps fix a crash later in the story?
The evidence concerns startup failures. A repeatable crash at a particular scene should be reported with that location and error; do not assume it has the same cause.
REFERENCE RECORD

