AMD Nightmare

habuman

Junior Member
Sep 28, 2000
1
0
0
I have a AMD 800 T-Bird, Asus K7V Mobo, Asus GeForce2 Pure and
updated Bios/Drivers. Everytime I try to run Final Reality or
sound test (Turtle Beach Aureal 2 Quadzilla) the system locks
up. Help me exercise the demon from my system!
 

KarsinTheHutt

Golden Member
Jun 28, 2000
1,687
0
0
If you are running Windows 9x or Millenium Edition, back up critical data, format your hard drive, and install Windows 2000. You should experience far fewer problems! :D
 

LXi

Diamond Member
Apr 18, 2000
7,987
0
0
habuman: The KX133 chipset is known to have problems with Tbirds, actually they were never meant to be used with Tbirds.
 

sandorski

No Lifer
Oct 10, 1999
70,440
5,984
126
Disregard 2 previous posts :p

For your soundcard, make sure to use Aureals reference drivers. Also, make sure the soundcard is in PCI slot 3. I think your problem is the souncard not being setup correctly.
 

AMDfreak

Senior member
Aug 12, 2000
909
0
71
Something else to check might be possible IRQ conflicts. Try to get the sound card on one by itself if you can. Sometimes just moving it to another slot helps.
 

Ausm

Lifer
Oct 9, 1999
25,213
14
81
or better yet Ditch the sound card and pick up a SB live Value....


Ausm
 

hungrypete

Diamond Member
Aug 4, 2000
3,001
0
0
definately swap the sound card before you do anything "wacky". My A7V fought my MX300 tooth and nail.
 

Arount

Member
Nov 30, 1999
93
0
0
Holler "PULL" and shoot it from the sky!!!!!!!


Frog

INTEL RULZ!!!!!!!!!!!!
 

XMan

Lifer
Oct 9, 1999
12,513
49
91
Sandorski is the guy you want to listen to, Habuman.

Aureal sound cards do some weird things in Athlon systems if you're not running the right drivers. The very latest ones should fix your difficulty.
 

rmblam

Golden Member
Aug 24, 2000
1,237
0
0
What does AMD have to do with your problem? Your lockups are due to:

A) You
B) Your software
c) An IRQ conflict
d) A memory issue
e) A driver issue
f) Wrong BIOS settings
g) Do I need to go on?
h) Not your processor unless it really is a slot a thunderbird on a KT7 which IS incompatible with the via kx133 chipset... Still not AMD..

Maybe someone should borrow you their Pentium 1.13 ghz chip and board with Rambus on it. I hear they are GREAT!!!! lol....
 

NicColt

Diamond Member
Jul 23, 2000
4,362
0
71
LOL sandorski you made my day :)

anyway disregard all post's except my and sandorski's.

my experience with this is that sound cards for some reason are picky with this setup, just make sure that the sound card is in slot 2 or 3 and has it's own IRQ. just run msinfo to see if your card is sharing and with what, if you need an irq just disable a com port. Hope this helps.
 

Spookydude

Junior Member
Sep 30, 2000
1
0
0
With the Vortex2 chipset on your soundcard, use the 2041 Aureal drivers and card in slot 3.
Then, go into to your BIOS and change everything you don't understand.
Reboot, cross your fingers, and chant "Intel rules, Intel rules" as it boots.
Then when it locks up, hit the worn out reset button and try something else.

Hope this helps.;)
 

ColdTech

Senior member
Sep 22, 2000
225
0
0
Also From Experience what version of Dx are you using... Those sound tests will use it, so that could be related... If It is dx7.0a than format & go back to 7.o..... From experience it causes some mean sh!t to happen & are systems have alot in common... Also Is it an actual k7v or a7v... if it is a k7v & a tbird Just simple expect problems untill you get it in a MB that supports it correctly... When The Manufacture says its incompatible you know there is bound to be sompthing wrong...
 

dszd0g

Golden Member
Jun 14, 2000
1,226
0
0
I am with the disregard all advice other than:
sandorski
rmblam
NicColt

I think it is probably a 90% chance that the issue is with the soundcard; either the drivers or a hardware conflict.

I would like to add that the tools that come with Microsoft Windows (esp WindowsKey-Break->Device Manager) are not very good about detecting hardware conflicts. I have worked on more than a few systems that I had to force slot(s) to specific IRQ(s) in order to get them to work. The last one was a P3 500 on a BX mobo, so you Intel folks stop bashing AMD, these exact same problems happen with Intel.