Kyro II system hangs/reboots in 3-d games - Fixed! Thanks

[aviris]

Okay - I've got a Hercules 4500 on a Abit K7A-raid with 512 (2 x 256) Crucial PC133 CL2 with an Athlon 1.33 (@1.33) running a fresh install of WinXP-pro. The card works like a champ in all 2-d apps. Works great with some 3-d games, but only for awhile. When playing Mechwarrior3 it runs great initially. Sometimes I can go for an hour and no problems, other times the video freezes and I drop back to the desktop (audio keeps going until I eject the CD) after 5 minutes. These lockups occur randomly - never the same place in the game or same types of things (e.g. when there is a ton of action going on). Mechwarrior4, on the other hand, reboots my machine as soon as it tries to change the resolution from the mission briefing screens to the game play screen. Thief: The dark project has a mix of both, sometimes working for hours, sometimes dropping to the desktop, sometimes rebooting the machine.

Here's what I've tried. All the different drivers that are out there. A registry hack from the MS knowledge base for the infinite loop thing. New motherboard/cpu (same behavior in this machine as in my old ECS D6VAA w/dual PIII 667's on XP-pro). Reformat the HD and new install of XP-pro. Running those games under compatability mode. Finally popped in a $50 Visiontek Geforce2 GTS-v and all the above games worked great.

Any ideas? AGP aperature size? AGP driving control?

Edit----------------------

Got it going (see below) - thanks for you input

 

[vedin]

First, I'd check your settings on everything. Paraknowya.com has a nice little FAQ with just about everything you could ever want to know in it. If that doesn't work, loose half the RAM. Kyros don't like over 256megs.

 

[Mingon]

<< loose half the RAM. Kyros don't like over 256megs >>



I never had any probs, I still dont understand why they should have any probs

 

[rogue1979]

Try raising the I/O voltage to 3.6v. Also what kind of power supply do you have? 1.3GHz Thunderbird needs alot of juice.

Edit: My brothers system (Epox 8KA3+ KT133a chipset/Radeon 64MB DDR) is having a similar problem. He fixed it by going from 256MB of Ram down to 128MB. He is not happy about it but it works fine now.

 

[vonplyr]

i had the same problem but i though it was the new clip of 256mb ram that i just put in. i took it out and everything worked great. went from 512 down back to 256. so maybe it wasnt the ram but the kyroii.

 

[aviris]

Thanks for your help everybody - vedin especially. I went to Paraknowya.com, found the setting list and thrashed around in my BIOS for a bit and it works great now. Just to make sure I stayed up most of the night "testing" it to make sure

To sum up - I still have all 512 of ram, my power supply is a 300W enermax. I changed the AGP aperature to 256 and enabled the Fast Writes and all is well.

 

[vedin]

::Jumps up and down::Woohoo!!! I finally helped somebody! ::His head suddenly gets so big that it shoves his monitor in, then through the wall:: Dangit....