[GTA SA] Game doesn't start

[Alyxsqrd]

The new widescreen fix update for San Andreas (I'm guessing after you guys ditched wshps.asi) makes gta_sa.exe not start at all on Windows 10 (1903/1803). Here's what I collected from Windows Event Viewer:

Faulting application name: gta_sa.exe, version: 0.0.0.0, time stamp: 0x427101ca
Faulting module name: vorbisfile.dll, version: 1.2.0.0, time stamp: 0x5d0e48a8
Exception code: 0xc0000005
Fault offset: 0x0000134a
Faulting process id: 0x1a40
Faulting application start time: 0x01d538e1e4eb0f96
Faulting application path: C:\Users\<my username>\Desktop\GTA San Andreas\gta_sa.exe
Faulting module path: C:\Users\<my username>\Desktop\GTA San Andreas\vorbisfile.dll
Report Id: cbb07ce9-1c02-4bda-a9b4-b0c79507ede8
Faulting package full name: 
Faulting package-relative application ID: 

I can run the game just fine without Widescreen Fix (using the original vorbisfile.dll from the game.)

Help! D:

[Alyxsqrd]

Update: All my drivers are updated, I ran sfc /scannow and DISM commands to fix my system files, but no luck...

[ThirteenAG]

Please provide a crash dump. And try to move the game away from program files.

[BusyOne]

@ThirteenAG Same problem, moving away didn't help. Here is a crash dump: gta_sa.exe.9204.zip (Sorry for bad English if it is.)

[Alyxsqrd]

I don't know how to make a crash dump. Also the game was never in the Program Files folder in the first place. For now I have temporarily replaced the Widescreen Fixes vorbisfile.dll with Silent's ASI Loader (but keeping the Widescreen Fix ASI) and now the game works fine.

[ThirteenAG]

Well, I see a crash inside vorbisfile.dll, but it's hard to debug it because I can't reproduce the problem. It happens here. So it seems like original vorbisfile.dll wasn't loaded for some reason.

If you rename vorbisfile.dll to vorbisHooked.dll, and then use vorbisfile.dll from widescreen fix, does it work that way?

[BusyOne]

Well, I see a crash inside vorbisfile.dll, but it's hard to debug it because I can't reproduce the problem. It happens here. So it seems like original vorbisfile.dll wasn't loaded for some reason.

If you rename vorbisfile.dll to vorbisHooked.dll, and then use vorbisfile.dll from widescreen fix, does it work that way?

@ThirteenAG For me it is worked! (Sorry for bad English if it is.)

[ThirteenAG]

Yeah, weird. It should work in both cases. :/

[BusyOne]

For me on Windows 10 build 1909, it is working now! (Sorry for bad English if it is.)

[CrezyDud]

-n- (Sorry for bad English if it is.)