Update: I seem to have resolved the issue a little. I still get crashing but I can get at least two-three save-states working in just my preliminary testing (it used to straight up crash immediately after). So I might be able to continue on this.
Here is new error log from a sample crash though, just in-case this is fixable too...
Edit: insane_coder from IRC offered an insight.
<Ilari> DDRKhat: The game allocates a memory area for some purpose. Then it decides it doesn't need it anymore and frees it. But then, it actually needs it, and uses it, reading a memory address from there. Then it uses that memory address and things blow up.
<insane_coder> Ilari: Older versions of windows don't actualy free right away <insane_coder> so setting compatibility mode way back may fix it
There was more discussion later about how that came about but either way setting it to Windows 2000 compatibility has given me a significant stability in the save-states (Note these errors do not occur outside of trying to save-state) it's not perfect, still happens, but as long as I don't spam my save-states and such it's MUCH more tolerable, Thanks to him!
Writing this here just in-case it might help others.
2nd Edit, turska did some testing for me whilst I was AFK.:
<turska> DDRKhat-AFK: it can be somewhat unstable if you keep "wrap" on when loading states - start the movie with "wrap" and set it to "disabled" once you enter the stage and start using savestates. the movie should still sync with "wrap" - of course, you should test often and you'll need to play back the movie from the start with wrap on if you ever need wrap re-enabled at some point for the game to not lock up