Spam Prevention - PLEASE READ !! (23 Apr 2021)
Due to a problem with spammers the rules for posting in the forums have changed for new users.
Newly registered users won't have their posts published until a moderator approves them.
Start up crash with error code 58
Yes I have both 640x480 and 800x600 in 32bpp. Hum.. something that may interest you is when I untick "List 32 bit color modes instead" I get the following warning "Warning: 640x480 is needed by Swat3". So may be the issue is related to 16bpp mode?
I tried your tuto, I made swat 3 crash at startup but can't see the log of desired crash. I tried several times.
Any chance you can look in the Windows event log for errors:
Basically you will want to re-enable the movies and cause the game to crash at startup. Then follow the link above to see if Windows 10 recorded the cause of the crash.
Btw I can see older crashes (several days older) but with no interesting info:
May be the log will appear later, I will retry tomorrow.
Faulting application name: Swat.exe, version: 126.96.36.199, time stamp: 0x74617773
Faulting module name: ntdll.dll, version: 10.0.19041.1466, time stamp: 0x9012d056
Exception code: 0xc0000005
Fault offset: 0x00044319
Faulting process id: 0x25e0
Faulting application start time: 0x01d80eeb276376e5
Faulting application path: C:\Sierra\SWAT3\Swat.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 931ea823-7715-4ee4-b917-7ac039aee77b
Faulting package full name:
Faulting package-relative application ID:
That is good that both are listed in 32-bit colour because the launcher checks with Windows what resolutions are available. From my understanding of the query method used it cross checks with both your video card and your monitor what it can do.
If you untick the 32-bit colour box you won't see any available resolutions. Windows 10 can only emulate 16-bit colour unfortunately and is why we need dgVoodoo to help speed the process back up.
Faulting application name: Swat.exe, version: 188.8.131.52, time stamp: 0x74617773 Faulting module name: ntdll.dll, version: 10.0.19041.1466, time stamp: 0x9012d056 Exception code: 0xc0000005 Fault offset: 0x00044319 Faulting process id: 0x25e0 Faulting application start time: 0x01d80eeb276376e5 Faulting application path: C:\Sierra\SWAT3\Swat.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 931ea823-7715-4ee4-b917-7ac039aee77b Faulting package full name: Faulting package-relative application ID:
Hopefully those are just old crashes from when you had issues with dgVoodoo. Trying to discover the source of the ntdll.dll error may prove difficult.
Any chance you can re-store the original Indeo codec movies to see if they give an error that shows up in the logs?
- Posts: 181
I think this is the dreaded crash, that I experienced with the VM ware, and my gaming rig.
Setting the Exe's to run as administrator could temporarily allow him to continue troubleshooting.
If you crash the game a number of times within an hour this error will pop up. Unfortunately there is no fix.
These are the errors in his log possibly from movie crash.
I installed last intel drivers. It comes with an utility, it seems to accept custom resolutions so I tried to add 640x480 (screen shot added). But crashes as well.
I desinstalled mod and swat3, and reinstalled swat3 only. I now I get a log after crash:
Fault bucket 107633515279, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Swat.exe P2: 184.108.40.206 P3: 39660360 P4: Swat.exe P5: 220.127.116.11 P6: 39660360 P7: c0000005 P8: 0000e416 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1EA.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA258.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA278.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA280.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA2B0.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Swat.exe_fae18cec404ede8915495be121d2be72289da_e665ac9e_7e78e52f-e9f1-4d3c-8946-4a1dca0ec2e8 Analysis symbol: Rechecking for solution: 0 Report Id: 64c5b136-30e2-4498-a6e5-d8913f894d8a Report Status: 268435456 Hashed bucket: 2b3f2070de72cc0c6db1b4871559015a Cab Guid: 0
But no mention on video
Sadly that crash report doesn't tell us anything.
Please also make sure that 800x600 is enabled in the driver.
If nothing else works I am tempted to send you my 1920x1080 versions of the movies and the temporary hack just to test the crash is indeed because your system doesn't like the old smaller resolutions.