Just got a 1700+ nothing but problems, please help!

[GoingUp]

So I have an old KG7 mobo with a gig of ram and I drop in a 1700+. I also migrated the system to a different case. I boot up, and it takes for goddamn ever to detect the IDE devices. Then I go into the bios and set optimal settings and change the processor to a 1700+. Then when I try to reboot, I can't do anything. Cant get back into the bios, the system just sits and waits after the memory counting. Its wierd because sometimes the machine will count say, 224948k ram or 678534k ram. Othertimes it will count the full gig, but after that it just hangs at detecting IDE devices. I have a 300 watt PSU and the case is running with its cover off. Everything in the case is blazing hot, I dont understand why. Ambient temp is 32c and processor is at about 40c. I have the latest bios available.

Any ideas why my system just stops and hangs like that?

 

[DAPUNISHER]

I would suspect the PSU but you were running the ultra power hungry 1.4ghz t-bird@1.65ghz so no way should the 1700+ draw as much juice. Perhaps the board has trouble because it's a t-bred B? It's the prime suspect since you had that t-bird and everything else running smooth before, unless the new case also meant a new PSU?

 

[maluckey]

I had a similar problem... twice. The first was my IDE devices either didn't detect, or took forever, then the system upon boot would sometimes crash. It turned out to be an IDE cable not being seated properly. The Second time, it was the HDD connector plug, not getting good contact to the HDD prongs, and intermittently losing contact. With this one, in addition to the above symtoms, it also had random reboots. That one was hard to find, because everything was checked, and was plugged in. It only worked right when it felt like it. I only found it by accident, when I wiggled it by mistake, and the drive cut off.

There are probably hundreds more possible causes, but at least these are easy to check.

 

[GoingUp]

Originally posted by: DAPUNISHER
I would suspect the PSU but you were running the ultra power hungry 1.4ghz t-bird@1.65ghz so no way should the 1700+ draw as much juice. Perhaps the board has trouble because it's a t-bred B? It's the prime suspect since you had that t-bird and everything else running smooth before, unless the new case also meant a new PSU?

its a tbred A chip...

I'll try a different IDE cable...

 

[GoingUp]

problem solved! I switched 2 memory modules around and that got rid of the memory errors, then on my HD I had a jumper on that activated (master with slave present) but I had no slave on that IDE chain. I removed the jumper to make it a single drive, and it is immediately detected!

 

[Murphq]

I am having a similiar problem on my rig? So did you completly remove the jumper, or did you set it to something else?

 

[Duvie]

Originally posted by: Murphq
I am having a similiar problem on my rig? So did you completly remove the jumper, or did you set it to something else?

It can depend on the brand of drive....Go to manufacturers webpage and look at the diagram or find the diagram that came with the drive.

 

[GoingUp]

Originally posted by: Duvie

Originally posted by: Murphq
I am having a similiar problem on my rig? So did you completly remove the jumper, or did you set it to something else?

It can depend on the brand of drive....Go to manufacturers webpage and look at the diagram or find the diagram that came with the drive.

I completely removed the jumper to configure the drive as a single drive... it depends on the drive

 

[DAPUNISHER]

Originally posted by: Gobadgrs
problem solved! I switched 2 memory modules around and that got rid of the memory errors, then on my HD I had a jumper on that activated (master with slave present) but I had no slave on that IDE chain. I removed the jumper to make it a single drive, and it is immediately detected!

It's always the small stuff ain't it? Good to hear it's purring along now :beer:

 

[GoingUp]

Originally posted by: DAPUNISHER

Originally posted by: Gobadgrs
problem solved! I switched 2 memory modules around and that got rid of the memory errors, then on my HD I had a jumper on that activated (master with slave present) but I had no slave on that IDE chain. I removed the jumper to make it a single drive, and it is immediately detected!

It's always the small stuff ain't it? Good to hear it's purring along now :beer:

Man, that small stuff always eats so much time too.... grrrr