Home Trending Latest threads New posts Developer diaries

Game crashes to desktop

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Show only dev responses
unmerged(17298)

unmerged(17298)

Second Lieutenant
May 28, 2003
160
0
Visit site
Okay I fixed one problem but now got another :)

Here are my PC specs:

MSI Nforce K7N2 Delta-ILSR Motherboard
AMD XP2500+ 333FSB Barton 512kb @2.21+Ghz (XP3200+)
Sapphire Radeon 9800 128MB DDR AGP 8X Lite
WXP Pro (Fully updated)

Pretty sure all drivers and stuff are up to date as I just built the system.

HOI 1.05c

Basically every now and again the game just crashes to the desktop. I have auto save on every month so it is not a total disaster every time but quite annoying none the less. I had a quick read through the posts and can't find anything really help full.
 
Last edited:
Two possible problems.
1) Bink player conflict: Solution is to rename the AVI folder to AVI_back

2) VIA drivers. These are known to be buggy. With XP not much you can do about it right now, except bug them to fix it.
 
Originally posted by Castellon
Two possible problems.
1) Bink player conflict: Solution is to rename the AVI folder to AVI_back

2) VIA drivers. These are known to be buggy. With XP not much you can do about it right now, except bug them to fix it.
Click to expand...

Thanks for the reply, what is the Bink Player??? So I have to permananty rename the folder to AVI_back or just when i want to play HOI???

If it is 2 then I guess I will just have to wait :)

Cheers
 
The Bink player is the program that runs the intro movies, it has been known to cause some conflicts on certain systems. Renaming the HOI AVI folder will only effect HOI, so no problem to do it.
 
Are you sure you are using the VIA drivers?
 
PM jpd, he is my resident expert on VIA drivers.
 
Originally posted by epscilon
No I am not sure how do i check? it just happened again though :(
....
MSI Nforce K7N2 Delta-ILSR Motherboard
Click to expand...
Since you are using an NVidia nForce based mobo, you won't have any VIA drivers installed. Those are for VIA chipset based mobo's. Instead, you will have the NVidia unified driver set.

What version of DirectX do you have installed? (If it's 9.0, make sure you upgrade to 9.0b, as the original distribution is somewhat buggy)

Jan Peter
 
I am running DX 9.0b. Has anyone got any more suggestions?

I will try swapping my G card for an older one and see what happens.... I did this for the problems I have been having in other games but still got those problems but it may be a g card error???
 
So You are have problems with other games as well?
 
Originally posted by epscilon

AMD XP2500+ 333FSB Barton 512kb @2.21+Ghz (XP3200+)
Click to expand...
Do I interpret this correctly as you having an overclocked system?

If so, restore the original timing settings of your Athlon and see if that resolves the problem. Overclocking can cause all sorts of nasty problems if pushed to or just beyond the limit, especially if the increased timing also applies to the AGP/PCI bus. Overclocking increases the temp of a lot of system components and also increases power consumption. Both can cause systems to crash if pushed beyond tolerance.

Also make sure your memory interface is clocked in sync with your processor's FSB. Not only will this increase performance (slightly), but also decreases the potential for trouble. So, no processor FSB at 333, and DDR at 400, for example.

Also, how much RAM do you have installed? WinXP likes a lot of that for a smooth running system. 512 MB or more would be advisable.

Jan Peter
 
Last edited:
I have not really overclocked my system to my liking yet I have had it running briefly at 2200MHz but at the moment it is running nornally 1.8Ghz.

I have also been having problems with AAO (amercas army) however swapping the G Card out for the older one did not stop that error so i came to the conclusion that the card was not at fault.

The guys there recon it is my net connection which i am changing over to Ethernet tonight to see if it fixes that.

I have 512 of dual DDR 400Mhz Ram. Currently at 200MHz (which is the default) while my FSB is at 166 which is also default? Should I try and slow my Ram down?

I only wish for an easy gaming life :) it seems I spend more time browsing forums looking for answers to my various problems than having fun playing games :(
 
Yes, you definately should slow down your RAM.

You said yourself, your Athlon runs at 333 (166 clock). Set your RAM at sync timing, thus also at 333 (166 clock). It may sound odd, but your system will actually perform better that way.

The north bridge of your chipset doesn't have to deal with out-of-sync memory request when you set it at synchronous operation. That ensures that no wait states are inserted, and no requests need to be buffered. Both can cause problems if there are bugs inside the system (either hardware or the mobo driver software)

Jan Peter
 
Right, I have reseated my Graphics card, installed teh drivers again, turned off fast writing in the bios, reduced my ram to 166 rather than 200 like my fsb and made sure everything looks correct.

I will test tonight and post back. Fingers crossed...
 
Good luck. Let us know how it turns out.

Jan Peter
 
Well something seems to have fixed itself!!! I played for an hour last night and while getting hammered by the Soviet AI (must qualify me for the worst player club!) I did not get one crash.

Just want to say thanks for the help guys!!

I really think it may have been the memory timings that was messing me up. Everyone make sure they are the same Mhz as your FSB!!!
 
Now you know why Intel has desided to leave out the async memory timing from their DDR chipsets :D

Anyway, congrats with finally resolving the problem, and good hunting :p

Jan Peter
 
Glad you are back and up and running.!
 
You must log in or register to reply here.
Top Bottom
Back