Crash log:
5/23/2007 8:20:48 PM: Initializing
5/23/2007 8:20:48 PM: Reading Settings
5/23/2007 8:20:48 PM: Logging Option: SIMPLE
5/23/2007 8:20:48 PM: Loading MRU Callsigns
5/23/2007 8:20:48 PM: Loading Form Position
5/23/2007 8:20:48 PM: Checking Installation
5/23/2007 8:20:48 PM: Checking OOBE
5/23/2007 8:20:48 PM: Ready
5/23/2007 8:20:53 PM: Checking for system updates
5/23/2007 8:20:53 PM: Checking for existing processes
5/23/2007 8:20:53 PM: Saving Settings
5/23/2007 8:20:53 PM: Saving MRU Callsigns
5/23/2007 8:20:54 PM: Checking connectivity
5/23/2007 8:20:54 PM: Using Port: DirectPlay
5/23/2007 8:20:54 PM: Checking ASGS Client Version
5/23/2007 8:20:54 PM: Client Version: 155
5/23/2007 8:20:54 PM: Server Version: 155
5/23/2007 8:20:54 PM: Securing Installation
5/23/2007 8:20:54 PM: Validating Installation
5/23/2007 8:20:55 PM: Preparing Key
5/23/2007 8:20:55 PM: Key Generated
5/23/2007 8:20:55 PM: Connecting to ASGS Server
5/23/2007 8:20:55 PM: Authenticating
5/23/2007 8:20:56 PM: Ticket Received
5/23/2007 8:20:56 PM: Return Value: 0
5/23/2007 8:20:56 PM: Callsign: GibGezr(0)
5/23/2007 8:20:56 PM: Authenticated successfully
5/23/2007 8:20:56 PM: Checking messages
5/23/2007 8:20:56 PM: Return Value: 0
5/23/2007 8:20:57 PM: No messages
5/23/2007 8:20:57 PM: Checking polls
5/23/2007 8:20:57 PM: Return Value: 0
5/23/2007 8:20:57 PM: No polls
5/23/2007 8:20:57 PM: Logged In
5/23/2007 8:20:57 PM: Launching Allegiance
5/23/2007 8:21:20 PM: Unable to launch Allegiance.
5/23/2007 8:21:20 PM: Allegiance did not launch in the time allotted.
5/23/2007 8:21:20 PM: Beginning Logout
5/23/2007 8:21:20 PM: Closing processes
5/23/2007 8:21:20 PM: Sending Logout Request
5/23/2007 8:21:20 PM: Allegiance exited with code: EXCEPTION_ACCESS_VIOLATION
5/23/2007 8:21:20 PM: Creating Crashfile
It worked this afternoon, but when I shut my system down it installed a Windows update...now Allegiance crashes when I run it. If I run Allegiance directly (not from ASGS) it invokes Microsoft Crashgaurd.
Any ideas?
Allegiance crashes after latest Windows update
Not sure off-hand. Maybe if you post using the template located here it'll give the guys some additional information to work with. Thanks!
Ah...found that...
Windows Version (and Service Packs): XP Pro SP2
Processor Speed: Intel Pentium M 2GHz
RAM: 2 GB
Video Card (Make and Model#): NVidia Geforce Go 7800 GTX
Sound Card (Make and Model#): Sigmatel C-Major
Connection Type (Dialup, Cable, DSL, other): DSL
Modem (Make and Model#):
Router (Make and Model#): Siemens SPeadstream 6520
Internet Service Provider(company name): Aliant
Location(State/Province/Locality, and Country): Miramichi, Nnew Brunswick, Canada
Installed Mods: None
Windows Version (and Service Packs): XP Pro SP2
Processor Speed: Intel Pentium M 2GHz
RAM: 2 GB
Video Card (Make and Model#): NVidia Geforce Go 7800 GTX
Sound Card (Make and Model#): Sigmatel C-Major
Connection Type (Dialup, Cable, DSL, other): DSL
Modem (Make and Model#):
Router (Make and Model#): Siemens SPeadstream 6520
Internet Service Provider(company name): Aliant
Location(State/Province/Locality, and Country): Miramichi, Nnew Brunswick, Canada
Installed Mods: None
Uninstall, re-install...still the same.
Safe mode and windowed same thing.
DX is installed & latest version, ASGS updates fine to 1.55, can connect...but Allegiance itself no longer will run.
I wonder what the latest Windows update was....hmmm.
Safe mode and windowed same thing.
DX is installed & latest version, ASGS updates fine to 1.55, can connect...but Allegiance itself no longer will run.
I wonder what the latest Windows update was....hmmm.
Last edited by GibGezr on Thu May 24, 2007 2:10 am, edited 1 time in total.
Miramichi! Cool. We're neighbours. Salmon running yet? /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />
Unfortunately, that particular error code that you posted doesn't help us much - not your fault, of course - it's just the way it is. Basically it means "something did something that it shouldn't have". /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />
Just for fun... did you try a hard reset? (ie... shut down the computer completely, not just a reboot) Sometimes after an update the hardware needs to be re-initialized. This might be the case after a Windows update. A simple thing to do and worth trying.
Hopefully others will chime in - at this point it could be just about anything.
Unfortunately, that particular error code that you posted doesn't help us much - not your fault, of course - it's just the way it is. Basically it means "something did something that it shouldn't have". /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />
Just for fun... did you try a hard reset? (ie... shut down the computer completely, not just a reboot) Sometimes after an update the hardware needs to be re-initialized. This might be the case after a Windows update. A simple thing to do and worth trying.
Hopefully others will chime in - at this point it could be just about anything.