When last bugged version of SRO was released, Gameguard started to report a speedhack error, at last I found how to solve thius, but at the cost of worst performance and cooling.
Just turned off the AMD Cool'nQuiet feature in the BIOS setup and no more speedhack by now.
AMD 64 3200+ and Speedhack error
-
Mereghost
- Common Member
- Posts: 199
- Joined: Tue Apr 25, 2006 11:45 am
- Quick Reply: Yes
- Location: Xian
- Contact:
Tronak:
Errr... I have a AMD64 3200+ (core at 2200) running on a K8V-SE Deluxe with cool'n'quiet active and never had that kind of trouble.
Try updating your processor "driver" and reactivating it.
Errr... I have a AMD64 3200+ (core at 2200) running on a K8V-SE Deluxe with cool'n'quiet active and never had that kind of trouble.
Try updating your processor "driver" and reactivating it.
"If I should die before I wake, I pray in Hell my soul won't bake."
Lian _Xiao: Glaive Str Hybrid 2.5:1
Level: 4X
Please correct my engrish. Thanks.
Mereghost, I have a similar rig (asus k8v se deluxe + ADMD64 3200+) but can't get the game running; it crashes windows (I'm running XP SP2) to a blue screen of death. Would you be so kind as to give some details about your rig and your game config?
I have a SB Audigy 2 ZS as a soundcard, and 1 GB of RAM. I'm also able to run Oblivion quite smoothly. (more details here: http://www.silkroadforums.com/viewtopic.php?t=8365)
I have a SB Audigy 2 ZS as a soundcard, and 1 GB of RAM. I'm also able to run Oblivion quite smoothly. (more details here: http://www.silkroadforums.com/viewtopic.php?t=8365)
My BSoD says windows found a problem and windows was shut down to prevent damage to the computer (I think it's generic stuff).
Then the message goes on and explains I should try some basic things such as upgrading BIOS (something I've already tried; I've upgraded BIOS, chipset drivers, processor drivers, graphics drivers, direct X, to no effect), or disabling some BIOS options such as cache or "vigilancy".
Then it posts a "**STOP: (hex numbers)" final line, where hex numbers vary from time to time.
The machine crashes right after the NCSoft thing loads.
EDIT: I'm using the Spanish version of Windows XP. I hope the problem isn't there...
Then the message goes on and explains I should try some basic things such as upgrading BIOS (something I've already tried; I've upgraded BIOS, chipset drivers, processor drivers, graphics drivers, direct X, to no effect), or disabling some BIOS options such as cache or "vigilancy".
Then it posts a "**STOP: (hex numbers)" final line, where hex numbers vary from time to time.
The machine crashes right after the NCSoft thing loads.
EDIT: I'm using the Spanish version of Windows XP. I hope the problem isn't there...
-
Mereghost
- Common Member
- Posts: 199
- Joined: Tue Apr 25, 2006 11:45 am
- Quick Reply: Yes
- Location: Xian
- Contact:
fedejico:
Hmmm... ever ran a RAM tester? Try googling Memtest and give it a try.
Most of the misterious BSoD error are caused by defective RAM sticks.
And 'bout the WinXP version: no it isn't the problem, I'm using the brazilian portuguese one.
Hmmm... ever ran a RAM tester? Try googling Memtest and give it a try.
Most of the misterious BSoD error are caused by defective RAM sticks.
And 'bout the WinXP version: no it isn't the problem, I'm using the brazilian portuguese one.
"If I should die before I wake, I pray in Hell my soul won't bake."
Lian _Xiao: Glaive Str Hybrid 2.5:1
Level: 4X
Please correct my engrish. Thanks.