AMD Athlon Prolems

[ndm]

Hi,

I dropped an Athlon 1600XP CPU into an ECS K7VTA3 Rev 1.0 board. Powered it up, the system started to boot but did a total system shutdown before getting to the memory count. The System refused to start at all after that.

I took the CPU out and put the Athlon 900 back in. (The XP was an upgrade to the regular Athlon). Everything worked fine until I got to the windows 2k login. The screen got some funny graphics and after that all subsequent attempts to boot failed. (Normally, windows 2k generated a stop message, the exact message changed as hardware was taken out of the box).

I had a FIC AZ11 board spare. I dropped the Athlon 900 into this board. It booted ok, but as soon as windows started, I had the same stop maessages I had with the ECS board.

Having tried the memory, cards and hdd's in another system, I concluded that the XP CPU has stuffed the ECS board, and that in turn had stuffed the Athlon 900 cpu as well.

What I can't understand is why the Athlon 900 only started to misbehave when it got anywhere near windows. You could run the thing on both the FIC and ECS boards for hours in DOS mode with no problems.

Any thoughts?

 

[mikemtc1]

I'm having trouble with my home computer. I have just upgraded it, I am using an ECS
K7S5A , an AMD 1700xp + and two 256 meg DDR ram, windows 98 ver1. I have been using it for about two weeks and although it works it seems to be getting worse. When installing anything using installshield it seems to hang and when checking it
MSGSRV32 has usually stopped responding. I also have to use endtask when shutting down as it hangs again. I have disabled power management, but this dosen't seem to have made any difference. Doe's anybody think windows XP would sort it out.

Any ideas

thanks in advance mikemtc1

 

[dakota81]

Are the motherboards setup to accept XP processors - meaning do they have the latest BIOS revision? Other than that, have you tried re-installing the operating system? Sometimes Windows gets to a point where you can do absolutely nothing to get it booted up. A friend's computer had Win2000 crash on startup every time he tried to hook up his new dvd-rom. Re-installed 2000 and the computer works like a charm.

 

[mikemtc1]

The MOBO is OK with Athlon XP chips. I have tried re-installing win98, but it didn't make any difference. I will check the MOBO web site for a new Bios. The ram may be a problem as the model is not tested in the MOBO manual.

Thanks mikemtc1

P.s the msgsrv32 is supposed to be a win 95 problem ?.

 

[Guest_imported]

I also am having an amd problem on my k7s5a mobo. I get errors everytime i boot up. One error in particular. " Windows protection error. You must restart your computer. System halted!" The only way to get the thing to boot windows is to do a step by step confirmation for windows startup. After wich everything is fine and dandy...until the next reboot. It only started doing this after i upgraded the mobo and cpu. so i figured, ok time to reinstall windows. So I did. And everything was great until I had pretty much all my drivers installed. This is growing rather anoying. From all the tech-knowledgable people I've mentioned this too they all seem to think its either the onboard usb or bad hard drives. Wich all makes no sense to me because all my usb devices are behaving like they should and the hard drives are fine. Any ideas would be greatly apreciated, I'm tempted to return this thing

amd athlon t-bird 1.3 gig 266fsb
ecs kts5a
2 x 128 meg dimms pc133 (micron I believe)
sound blaster live x-gamer 5.1
riva tnt 16 meg pci
usb optical ms mouse
logitech clicksmart 310 digital/web cam
logitech Itouch chordless key
Maxtor 20.4 gig udma/100 s.m.a.r.t. enabled
teac 4x4x24 cd/rw

 

[CitrixEngineer]

There are several questions here, so I'll try to be as generic as possible with answers that may apply to one scenario more than others;

It is highly unlikely that a CPU will damage a motherboard, unless correct cooling precautions were not taken. AMD chips are notorious for the amount of heat they generate, and should never be run without a correctly fitted heatsink and fan.

When changing processors, it is also advisable to completely re-install Windows - especially Windows NT variants, such as Windows 2000.

Make sure that you use the latest drivers for hardware components from the manufacturers website - or you may want to try

http://www.driverguide.com.

Hardware drivers can be the most argumentative of neighbours, and sometimes may require removal, via Device Manager, and re-installation to persuade them to co-habit peacefully.

For problems that seem to develop over time, tracking down and deleting temporary files from the hard disk, optimising the swap file and defragmenting the hard disk will help.

Hopefully there is something in here that will help all of the above scenarios. If not, I'm happy to help further.

CE