Programmer and I have been going back and forth for almost a week trying to figure out why something in development was crashing. It turns out.. its the name of the exe. This system does not like "fatalgs" as a exe name. I attempted renaming other exes to it, and they failed to start as well with a 0x80000003. so something in that name is trying to address a part of the system that's being used.
I attempted a fresh install with same results. So that leaves either the drivers for my hardware, XP Pro SP3, or my chip since this is the only system thus far to encounter it.
I know a friend who knows someone whom is on the windows development team. I really want to try to see if this can be narrowed down to give them more data if this is something OS/hardware config based.
So, those of you with..
xp pro sp3
nvidia 6000 series
nforce 2 motherboard
athlon XP
Any combination's of the above, or hell, it you want, something completely different. Can try renaming a exe.. again ANY exe to "fatalgs" (without quotes of course), and see if it fails to start.
Replies
XP Home SP3
nVidia 7000 series
Asus p5k-e mobo
Intel Quad Core
Good luck. :P
A search for "fatalgs.exe" (to see if there was a process out there that is named that...) brought me back to this: http://www.bleepingcomputer.com/startups/algs.exe-10289.html so maybe it is being blocked by a system patch as a virus?
I know, I'm reaching. Points for trying?