Error running the EXE
by Glen Farrell · in Torque Game Engine · 03/10/2004 (4:55 pm) · 10 replies
This might be a Microsoft bug, but I thought I'd try here first ... probably get a better response! In case it makes a difference, I'm using Visual C++ 6.0 in Windows XP Professional.
I've had Torque for almost two months now, and it's been working well up until the past week or so. Since then I've started having problems with the compiled exe, and they've been progressively getting worse.
What'll happen is I'll compile the EXE as usual, without any problems. But then when I try to run it, I get a generic windows error:
torqueDemo_DEBUG.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
If I do a Clean and Rebuild All a few times, it usually starts working again. Given how long it takes to do a Rebuild All though, this really isn't a good solution!
At first it was just cropping up occassionally, now I'll only get one or two good builds before it dies again. And likewise it takes more Clean/Rebuild cycles to fix it now.
Anyone have any ideas?
I've had Torque for almost two months now, and it's been working well up until the past week or so. Since then I've started having problems with the compiled exe, and they've been progressively getting worse.
What'll happen is I'll compile the EXE as usual, without any problems. But then when I try to run it, I get a generic windows error:
torqueDemo_DEBUG.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
If I do a Clean and Rebuild All a few times, it usually starts working again. Given how long it takes to do a Rebuild All though, this really isn't a good solution!
At first it was just cropping up occassionally, now I'll only get one or two good builds before it dies again. And likewise it takes more Clean/Rebuild cycles to fix it now.
Anyone have any ideas?
#2
I can e-mail to anyone if they want to have a look. The last few lines are:
Entering [demo]onExit()
Entering [common]onExit()
Leaving [common]onExit() - return
Leaving [demo]onExit() - return
Shutting down the OpenGL display device...
Making the GL rendering context not current...
Deleting the GL rendering context...
Releasing the device context...
As for the version, it's a mix of the Head as of 2/18 (shortly before they cut 1.2.1 as it turned out), plus my own additions. But it's not like coding changes are causing the error (at least not consistently ...). As I said, I do a Clean and Rebuild All a few times, and it starts working - same code as before ...
03/10/2004 (5:20 pm)
Well, it doesn't tell me anything ... ;-)I can e-mail to anyone if they want to have a look. The last few lines are:
Entering [demo]onExit()
Entering [common]onExit()
Leaving [common]onExit() - return
Leaving [demo]onExit() - return
Shutting down the OpenGL display device...
Making the GL rendering context not current...
Deleting the GL rendering context...
Releasing the device context...
As for the version, it's a mix of the Head as of 2/18 (shortly before they cut 1.2.1 as it turned out), plus my own additions. But it's not like coding changes are causing the error (at least not consistently ...). As I said, I do a Clean and Rebuild All a few times, and it starts working - same code as before ...
#3
This seems to be the problem here, since it goes away with a complete rebuild.
I think you'll have to bite the bullet and settle for complete rebuilds when you change your sourcecode, just like we do :)
03/11/2004 (7:17 am)
Well, it's because if you change stuff in your source files and don't do a complete rebuild, you'll probably end up with problems in the long run.This seems to be the problem here, since it goes away with a complete rebuild.
I think you'll have to bite the bullet and settle for complete rebuilds when you change your sourcecode, just like we do :)
#4
That was the case at first, but now it can take three or four complete rebuilds (and usually I reboot the PC somewhere in there too ...) before it starts working again.
I'm thinking it might be a corruption in my Visual Studio files ... last night I couldn't even shut down VC++ normally, and had to use End Task ...
I'm going to see if I can do a Repair on VS, or failing that a complete uninstall/reinstall ...
03/11/2004 (8:22 am)
If that was all, then wouldn't a complete rebuild always fix it?That was the case at first, but now it can take three or four complete rebuilds (and usually I reboot the PC somewhere in there too ...) before it starts working again.
I'm thinking it might be a corruption in my Visual Studio files ... last night I couldn't even shut down VC++ normally, and had to use End Task ...
I'm going to see if I can do a Repair on VS, or failing that a complete uninstall/reinstall ...
#5
There are two very good programs you can use to stress test/verify hardware inconsistancies. I would run them and see if anything turns up. Let me dig them up...
Memtest86 from http://www.memtest86.com
Prime95 (Use the stress test option) from http://www.mersenne.org/prime.htm
There are other good stress testing programs, but those two used in conjuntion do a VERY good job of revealing any possible hardware pronlems. Give them a try and see what you see.
03/11/2004 (8:44 am)
Sounds to me like possible hardware failures. I've had similiar odd problems when hardware starts to go flaky.There are two very good programs you can use to stress test/verify hardware inconsistancies. I would run them and see if anything turns up. Let me dig them up...
Memtest86 from http://www.memtest86.com
Prime95 (Use the stress test option) from http://www.mersenne.org/prime.htm
There are other good stress testing programs, but those two used in conjuntion do a VERY good job of revealing any possible hardware pronlems. Give them a try and see what you see.
#6
03/11/2004 (8:46 am)
Hmm, assuming the symptoms you're seeing are actually what's going on I'd do a complete uninstall/reinstall of VS if for no other reason than to eliminate that as a cause for the error. Let us know how it goes, and good luck to you.
#7
One of the files containing the system's registry data had to be recovered by use of a log or alternate copy. The recovery was successful.
'Successful' or not, that can't be good ... in any case I couldn't compile at all after that.
@John - I ran the Memtest86, and it didn't find any problems. Tried Prime95, and it died pretty much right away with this:
Test1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Resulting sum was -4.719083819393627e+132, expected: 93342471491.39105
Hardware failure detected, consult stress.txt file.
Stress.txt advises I try running Motherboard Monitor, so I'm going to take a look at that next ... if you have any other ideas, let me know!
03/11/2004 (1:22 pm)
Well the uninstall/reinstall just made things worse ... after the reinstall (and corresponding reboot), I got the following error starting windows:One of the files containing the system's registry data had to be recovered by use of a log or alternate copy. The recovery was successful.
'Successful' or not, that can't be good ... in any case I couldn't compile at all after that.
@John - I ran the Memtest86, and it didn't find any problems. Tried Prime95, and it died pretty much right away with this:
Test1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Resulting sum was -4.719083819393627e+132, expected: 93342471491.39105
Hardware failure detected, consult stress.txt file.
Stress.txt advises I try running Motherboard Monitor, so I'm going to take a look at that next ... if you have any other ideas, let me know!
#8
Try cleaning your system, too. Sometimes gunk in the system can break things.
03/11/2004 (8:05 pm)
Get new hardware! :)Try cleaning your system, too. Sometimes gunk in the system can break things.
#9
I ran a Chkdsk, and it found a few bad data clusters, but they were all under system/restore, so shouldn't have been a problem (except for restoring ...)
In the meantime though I've had two blue screens, and three registry errors, so something is seriously wrong!
Anyone know if XP has a Repair option? I haven't been able to find it ... not sure if it's because I only have a "New Installation" CD instead of a full version of it ...
I'm thinking I'll have to try reinstalling XP, but I'm not looking forward to that!
P.S: Motherboard Monitor turned out to be useless - it doesn't support my motherboard, and the only 'sensor' it could find seems to always read 0 degrees ...
03/12/2004 (8:09 am)
It's only a year old! :(I ran a Chkdsk, and it found a few bad data clusters, but they were all under system/restore, so shouldn't have been a problem (except for restoring ...)
In the meantime though I've had two blue screens, and three registry errors, so something is seriously wrong!
Anyone know if XP has a Repair option? I haven't been able to find it ... not sure if it's because I only have a "New Installation" CD instead of a full version of it ...
I'm thinking I'll have to try reinstalling XP, but I'm not looking forward to that!
P.S: Motherboard Monitor turned out to be useless - it doesn't support my motherboard, and the only 'sensor' it could find seems to always read 0 degrees ...
#10
The repair option just killed windows completely. Resorted to reformating the harddrive, but even that didn't work - it would just die in the middle of the Windows install.
I'm just glad I splurged for the extended warranty! I have a new harddrive being shipped out to me now. In the meantime, I'm borrowing my wife's computer ...
Anyway, thanks for the help!
03/12/2004 (2:11 pm)
Well looks like I'm getting new hardware after all ...The repair option just killed windows completely. Resorted to reformating the harddrive, but even that didn't work - it would just die in the middle of the Windows install.
I'm just glad I splurged for the extended warranty! I have a new harddrive being shipped out to me now. In the meantime, I'm borrowing my wife's computer ...
Anyway, thanks for the help!
Torque Owner Dan -