PDA

View Full Version : Consistant crashes when clicking the UI


Rodago
02-08-2007, 10:03 AM
Hi! I've posted this on the tech support forums, but I haven't gotten any good answers there, so I thought I'd try the kind people at Silky Venom!

I've been having a particular sort of crash happen to me since I started playing. Depending on what I'm doing, it has started every 20 to 60 minutes of play, but last night, it got much worse, happening every 15 minutes or so.

First, I'll start getting a decreasing frame rate. Then after a few minutes, the user interface buttons and graphics will turn black. Then the target selection circle will turn a solid color, and after that happens, the next time I click my mouse, the game crashes.

Initially, I (and others) suspected a video card overheat. But I added some cooling to my case, got the card down to a consistent 40 degrees, and there was little change in the nature of the crash. Then I realized that if I just run around all the time and don't use my mouse, I never crash. When I'm doing diplomacy, which requires constant clicking on the interface, I crash constantly. Lowering graphics to the minimum does not help. I have almost nothing but Windows and Vanguard installed on my machine; no antivirus or firewalls. I suspect a bug in the user interface, but I can't be sure.

The guys in the tech support forums suggested that I clear the cache or use the /flush command, and I thought that was working, but the problem has now gotten worse, and no amount of cache clearing or using of the /flush command helps.

My system specs look like this:

CPU: AMD Athalon 64 3200+, 2 GHz

Ram: 2x 512 MB DDR 400 SDRAM

Video Card: ATI Raedon X1600 PCI Express with 512 MBs DDR2

Motherboard: ASRock 939Dual-SATA2



Does anyone have any ideas on this?

-Jacob

Rodago
02-09-2007, 11:07 AM
I have a bit of new information about this issue... I found someone who had a similar issue who managed to fix it by using /reloadui. Not only does this not work for me, but it crashes me half of the time. If anyone else out there is having the same issue as I am, I would love to hear from you!

Rodago
02-13-2007, 12:18 PM
Just letting you guys know (in case anyone is having the same issue) that I fixed the problem! It turns out that I had a bad DirextX file.
I had considered this possibility a week ago and ran the DirectX installer, not realizing that the installer checks to see if the files are the latest version and only overwrites files that are not. I had a broken, but current file.
Of course, there is no way to uninstall DirectX and reinstall it to fix a broken file (thanks to the incredibly wise decision makers at Microsoft).
What I ended up having to do is to get into the registry and manually lower the listed DirectX version number so that the installer would think that it's a very old version and replace the whole thing. You can search for instructions on this at Google. Use at your own risk.

The moral of the story? Microsoft is my arch nemisis! I apologize for all negative thoughts that I may or may not have expressed vehemently about Sigil. ;)

Lithran
02-13-2007, 12:50 PM
Just letting you guys know (in case anyone is having the same issue) that I fixed the problem! It turns out that I had a bad DirextX file.
I had considered this possibility a week ago and ran the DirectX installer, not realizing that the installer checks to see if the files are the latest version and only overwrites files that are not. I had a broken, but current file.
Of course, there is no way to uninstall DirectX and reinstall it to fix a broken file (thanks to the incredibly wise decision makers at Microsoft).
What I ended up having to do is to get into the registry and manually lower the listed DirectX version number so that the installer would think that it's a very old version and replace the whole thing. You can search for instructions on this at Google. Use at your own risk.

The moral of the story? Microsoft is my arch nemisis! I apologize for all negative thoughts that I may or may not have expressed vehemently about Sigil. ;)

Hmm good to know. Wonder if that is one of the new steps we should add for folks having issues. Uninstall DirectX and reinstall it.