I've experienced a couple of crashes where rather than my empires crashing, my whole computer will simply turn off and restart itself. Would this problem be empires or the source engines? It showed me that it saved a couple files regarding the crash. C:\DOCUME~1\Owner\LOCALS~1\Temp\WERac6b.dir00\Mini080908-01.dmp C:\DOCUME~1\Owner\LOCALS~1\Temp\WERac6b.dir00\sysdata.xml and system stuff: AMD Athlon 64 Processor 3200+ 1.99 GHz 2.37 GB Ram ATI RADEON Xpress 200 Series integrated vid card. It also gave me this: BCCode : 10000050 BCP1 : EC0AA280 BCP2 : 00000000 BCP3 : BF1AC34A BCP4 : 00000001 OSVer : 5_1_2600 SP : 2_0 Product : 768_1 anyhow, this has happened a few times before, and it's hard to figure out exactly when it happens. The most recent time I was jumping out of my com vehicle on Canyon. There was an enemy near by building walls trying to wall it in, but he was on the opposite side of the VF. Not sure what else to add.
Symptoms as well as a quick Google search for the BCCode point to a problem with the computer rather than the engine or the game. I suggest you google the BCCode and read a couple of the posts. Disclaimer: I am not a computer expert. Not even close.
On windows XP, only a driver or a hardware problem could cause that. There is no game made for windows XP that will make your computer suddenly restart.
thanks. I need to find our old win 2k disk and load that up onto my computer. It never had so many driver issues as xp. Used to have an issue with drivers freezing up in cs as well, regardless of how up to date the driver was.
That could be some broken hardware. If you have some more knowledge about computers and if you can follow a tutorial this might help: http://www.thomaskoetzing.de/index.php?option=com_content&task=view&id=121&Itemid=195&lang=en What i need is the stuff that program will returns after the !analyze –v. Post that on the forums and we will know where the problem is and which driver is causing it.
alright, i got dr. watsons up and I'm skimming through some of it. I'd need to take some time to read through all this stuff and get a debugger and reproduce this crash, etc. But I do have 3 dumps. looking at it, these two lines are directly before the crash, in the back tracking part of the dump. *----> Stack Back Trace <----* WARNING: Stack unwind information not available. Following frames may be wrong. *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\userenv.dll - ChildEBP RetAddr Args to Child 0f62ff68 7c809c86 00000003 76a60310 00000000 ntdll!KiFastSystemCallRet I haven't really looked at dump files, so I don't know if those lines are significant. There is only one stack back trace with any significant amount of source file paths in it: Dunno if any of that helps.
It doesn't help. Stacktrace might be useful. (I don't want 2.12 dumps because I don't have VS 2003 installed)
