What should I do if the game won't launch? There are no error messages, and the log shows nothing. I'm using version DownpourRecomp-v1.1.8. Essentially, it only runs for the first 5 seconds: I see a black screen, and then it shuts down abruptly.
In log only 1 error:
[2026-09-17 20:11:36.027] [warning] [core] [t23248] present_effect=fsr2/fsr3 uses an experimental temporal upscaler path with synthesized depth/motion inputs and may fall back to spatial FSR
The event viewer shows this log:
№1
Faulting application name: downpour.exe, version: 0.0.0.0, time stamp: 0x6a98a09c
Faulting module name: TracyClientrd.dll, version: 0.0.0.0, time stamp: 0x6a2f4737
Exception code: 0xc000001d
Fault offset: 0x000000000002c139
Faulting process ID: 0x55c
Faulting application start time: 0x01dd46ca9c85ca64
Faulting application path: D:\Games\DownpourRecomp-v1.1.8\downpour.exe
Faulting module path: D:\Games\DownpourRecomp-v1.1.8\TracyClientrd.dll
Report ID: 42b91c5e-3621-4c7a-84e3-f033282af24e
Full faulting package name:
Application ID associated with faulting package:
№2
Fault bucket 1542266835924882611, type 4
Event Name: APPCRASH
Response: Not available
CAB Id: 0
Problem signature:
P1: downpour.exe
P2: 0.0.0.0
P3: 6a98a09c
P4: TracyClientrd.dll
P5: 0.0.0.0
P6: 6a2f4737
P7: c000001d
P8: 000000000002c139
P9:
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBDD9.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBED4.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFB0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFBF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFFF.tmp.txt
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_downpour.exe_f734e8801fd8cb62fcb1be917599e4f8db6694b7_6400d8eb_c619cb79-5cd7-44c3-9a58-97168d207af1
Analysis symbol:
Recheck for solution: 0
Report Id: 42b91c5e-3621-4c7a-84e3-f033282af24e
Report Status: 268435456
Hashed container: 0541c18a45f0c97d25673b84182b14b3
CAB GUID: 0
P.S. You say that the AVX2 issue was resolved starting with version 1.1.8, but in reality, the error
Exception code: 0xc000001d
indicates precisely an AVX2 requirement. Therefore, the problem has NOT been resolved.
What should I do if the game won't launch? There are no error messages, and the log shows nothing. I'm using version DownpourRecomp-v1.1.8. Essentially, it only runs for the first 5 seconds: I see a black screen, and then it shuts down abruptly.
In log only 1 error:
[2026-09-17 20:11:36.027] [warning] [core] [t23248] present_effect=fsr2/fsr3 uses an experimental temporal upscaler path with synthesized depth/motion inputs and may fall back to spatial FSR
The event viewer shows this log:
№1
Faulting application name: downpour.exe, version: 0.0.0.0, time stamp: 0x6a98a09c
Faulting module name: TracyClientrd.dll, version: 0.0.0.0, time stamp: 0x6a2f4737
Exception code: 0xc000001d
Fault offset: 0x000000000002c139
Faulting process ID: 0x55c
Faulting application start time: 0x01dd46ca9c85ca64
Faulting application path: D:\Games\DownpourRecomp-v1.1.8\downpour.exe
Faulting module path: D:\Games\DownpourRecomp-v1.1.8\TracyClientrd.dll
Report ID: 42b91c5e-3621-4c7a-84e3-f033282af24e
Full faulting package name:
Application ID associated with faulting package:
№2
Fault bucket 1542266835924882611, type 4
Event Name: APPCRASH
Response: Not available
CAB Id: 0
Problem signature:
P1: downpour.exe
P2: 0.0.0.0
P3: 6a98a09c
P4: TracyClientrd.dll
P5: 0.0.0.0
P6: 6a2f4737
P7: c000001d
P8: 000000000002c139
P9:
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBDD9.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBED4.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFB0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFBF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFFF.tmp.txt
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_downpour.exe_f734e8801fd8cb62fcb1be917599e4f8db6694b7_6400d8eb_c619cb79-5cd7-44c3-9a58-97168d207af1
Analysis symbol:
Recheck for solution: 0
Report Id: 42b91c5e-3621-4c7a-84e3-f033282af24e
Report Status: 268435456
Hashed container: 0541c18a45f0c97d25673b84182b14b3
CAB GUID: 0
P.S. You say that the AVX2 issue was resolved starting with version 1.1.8, but in reality, the error
Exception code: 0xc000001d
indicates precisely an AVX2 requirement. Therefore, the problem has NOT been resolved.