ntdll.dll - Swat 3 Crash

Once I get the new beta copy out I may take you up on your offer after Christmas. I have 2 laptops that I don't really play the game on so would be interesting to try.

Could the crash be causing Windows to turn on some sort of compatibility mode that continues to mess with the game?

Comparing the Windows registery before and after the crash would be interesting.

Usually when the game crashes only the swat.cfg file can get mangled. Could it be something as simple as that? Delete the file and the game will auto regenerate a new one.

update: On second though since you have the Steam version try turning off the Last Resort mod with the toggle switch at the top right of the launcher and then use Steam's "VERIFY INTEGRITY OF GAME FILES". This will confirm that it isn't the game files that are corrupted.

I have tried that, the problem persists. I have tried completely uninstalling the game from steam, deleting the folder, re-download and install, and I still have the ntdll.dll error.

Could be some compatibility mode that is causing the crash. I also tried deleting the cfg and no go.

I suspect maybe since the character is so glitchy because it is at the limits of the game that it is causing a memory leak, and windows is detecting it and killing all further instances of the Swat3.exe, Some sort of fail safe that is unknown , and unexplored.

The funny thing is I knew once I ran the map it was going to break.

There seems to be a correlation to run as administrator as opposed to running it with out Admin Privledges. This means you will have 2 chances to run your tests per install. One without Run as Admin, and another with admin.

This problem if solved could be the answer to so many other games people around the world have had with their game crashing due to ntdll,dll.

I have never heard of this error being a problem before this thread.

Once you get this error does it interfere with other games or just Swat 3?

I take it you have looked at this page?
www.lifewire.com/how-to-fix-ntdll-dll-errors-2624474

Another suggestion is uninstall Swat 3, reboot, and then run a registry cleaner app like CCleaner. Other option is backup the Windows registry and then manually search and delete any reference to Swat 3.

installed Virtual Box and setup Windows 8.1
installed game and Last Resort Mod
installed map to cause the ntdll.dll crash.

Load game and played missiona. Exited game using over and out button.
No Crash.

Created a restore point.
Took a Virtual Machine Snapshot.

Loaded game and launced the map to cause crashes.
The Sound was garbled, skybox missing, spikes everywhere, and Swat team twisting and moving erratically, almost looks like the where dancing. The command overlay was overlaying over each menu.
Everytime I quit the game it crashed, but the game loaded the game and the map again.
After 10 attempts it crashed on startup with ntdll.dll crash.
No longer functioning game....

Used the restore point before crash. The game still crashes.
Used the VM snapshot and the game loads again.

I now I have a test machine that I can tinker with.
I will be revisiting this soon.

Merry Christmas!

Update:
The game folder file size does not change as a result of the crash.
It crashes and will not start after first crash.

Windows Prefetch folder created a few files at the time of crash. 2 of which i am interested in.
WERFAULT.EXE-E69F695A.pf
SWAT.EXE-83DFDD9A.pf

Deleted those and a few others, no change.

Cleared Event Logs for Applications.
Crashed the game -

2 events noted that are related to crash
FaultTolerantHeap - Swat3
ntdll.dll - Swat3

Deleting the fthempty.txt that was created and including clearing the logs. - No Change

Researched The Fault Tolerant Heap (FTH) is a subsystem of Windows 7 responsible for monitoring application crashes and autonomously applying mitigations to prevent future crashes on a per application basis.

After 5 Crashes within an hour the FTH is applied to the exe.

Watch the Explanation video from Microsoft

O_O WTF!

Gonna turn off and test..
Resetting the list of applications tracked by FTH

Restarted VM with Snapshot
Modified the registry to manually remove FTH from being applied to Swat3.
Modified the Registry to turn off FTH from being applied to further Crashes of Swat3.

No Change - Game will crash and stay broken, FTH may not be the culprit.

Restarted VM with Working Game Snapshot
Backup registry - Loaded and Crashed game, imported registry and certain items could not be overwritten.
Cleared event log
Restarted - No Change

Found another generated file
AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_swat.exe_a4c573a8c48793a9e6ea4d832bfebd5897a2b841_ae75fd6b_055a4f6e

Deleted - No Change

Some really weird shit, lol.