Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: memnon on August 20, 2004, 04:00:40 PM

Title: computer lockup since patch 8
Post by: memnon on August 20, 2004, 04:00:40 PM

Has anyone else encountered this problem. My computer will just lock up it has happened to me five times since patch 8. It only happens while i'm online and four out of the five have been while i was in battle. I will have to display my operating system info when i return home but in the mean time i wanted to find out if anyone else was experiencing the same problem that i am.

Title: computer lockup since patch 8
Post by: Skuzzy on August 20, 2004, 05:02:39 PM

That is typically heat or ram timing problems.

I recently experimented with an AMD system on a NForce2 chipset and found I could get it to run everything reliably, then fire up Aces High II and it would either reboot the system or lock up.
I then reset the timings for the RAM using the "By SPD" option and everything was rock solid.

Just a thought.

Title: computer lockup since patch 8
Post by: memnon on August 20, 2004, 09:38:17 PM

How about in laymens terms please:D

What is "by SPD" option and where can i find it and what should i set it to.

It will be a couple of days before i get back home.

Title: computer lockup since patch 8
Post by: CurtissP-6EHawk on August 20, 2004, 10:59:44 PM

Try RGK.
Remove Girlfriend from Keyboard!

Title: computer lockup since patch 8
Post by: memnon on August 23, 2004, 05:07:14 PM

i'm at home now here is what my system has:

HP pavilion
AMD athlon xp 2800+
2.08 ghz
768 MB of ram
WIN XP version 2002 SP1
Radeon 9800 pro 128MB



If you need more info let me know please because my computer locked up on me again last night.


What is "by SPD" option and where can i find it and what should i set it to.

Title: computer lockup since patch 8
Post by: Skuzzy on August 23, 2004, 05:37:03 PM

Disregard that.  The HP system will not allow a user that type of control.

Instead, if you could send me the output from a DXDIAG, I would be happy to see if any is suspect.  See the bottom of the "Hints and Tips" post at the top of the forum for instructions.