Supermium gives "STATUS_ACCESS_VIOLATION" error then crashes on windows XP (SP3 & SP4)

[madeforlosers]

Describe the bug
Fresh install of Windows XP SP3 (Then to SP4 after the bug started).
Every time I run Supermium, after maybe half a minute, all the webpages show up with an "Aw Snap!" message and give the ambiguous "STATUS_ACCESS_VIOLATION" error before crashing.
Nothing else is given in terms of information when this happens, and all solutions I have found have been unsuccessful. I have tried re-installing Supermium, re-installing Windows, updating to the unofficial Service Pack 4, and many others. I can't disable hardware acceleration in Supermium because I can't get there in time before it crashes.

Nothing else happens after the crash, not even a send error report prompt.

To Reproduce
Steps to reproduce the behavior:

1. Open Supermium.
2. Just browse for maybe half a minute. I usually open google, a new tab, and a personal website to test if it will crash (and it does). On occasion it will only crash after you press "Reload" a few times.

Expected behavior
I expect it to work properly.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows XP Professional x86 (SP3 and SP4)
• 32-bit
• Pentium 4 @ 2.66GHz
• 1.00 GB of RAM

Additional context
As stated before, this problem started before I installed SP4, and it still persists after.

It is probably good to note that this is the first time i've had this happen to me. On a previous install of windows XP (on a seperate hard drive), superium worked completely fine.

Supermium was the first program installed on this computer after Windows XP was installed.

I'm not sure if this is because of the CPU being slow, but i will say the CPU hits 100% right before it crashes.

let it also be known that I have no idea how to get a dump file from Supermium.

edit again: Here is a debug log from WinDbg running chrome.exe: pastebin.com/U1TcMTnC

[win32ss]

I recognize the crashing instruction. This type of crash is in some CPU capability checking code, and has only occurred on systems of that era. Some changes to synchronization code did not help. I'll think of another way to approach this issue.