chazdraves
Golden Member
Here's what I'm running:
AMD 1.0 GHz Duron Processor
Abit KT7A Motherboard
ATI Radeon 8500LE
384MB SDRAM (1 128 Stick 1 256 Stick)
A 250-Watt Power Supply
10 GB Hard Drive
DVD-ROM
Ensoniq Sound Card
Here's the problem:
Whenever I start my computer it tells me that the processor "is unworkable or has been changed" I can enter the BIOS and try to fix this or I can simply press F1 and continue booting. If I do go into the BIOS, however, it will no longer boot the next time I start my computer. I recently made the mistake of entering the BIOS to change something, and now it has ceased to boot. The computer turns on, the fans start, the hard drive goes, the A:\ drive lights up, the DVD-ROM lights up, the hard drive goes very briefly again and it completely stops. I get nothing on my monitor, I don't get any of the normal "beeps", nothing. It does what I said and then it just stops and idles. I was told that it may actually be a bad power supply and not the CPU. Any ideas? Thanks in advance, it hasn't been working for 2 weeks now!
- Chaz
AMD 1.0 GHz Duron Processor
Abit KT7A Motherboard
ATI Radeon 8500LE
384MB SDRAM (1 128 Stick 1 256 Stick)
A 250-Watt Power Supply
10 GB Hard Drive
DVD-ROM
Ensoniq Sound Card
Here's the problem:
Whenever I start my computer it tells me that the processor "is unworkable or has been changed" I can enter the BIOS and try to fix this or I can simply press F1 and continue booting. If I do go into the BIOS, however, it will no longer boot the next time I start my computer. I recently made the mistake of entering the BIOS to change something, and now it has ceased to boot. The computer turns on, the fans start, the hard drive goes, the A:\ drive lights up, the DVD-ROM lights up, the hard drive goes very briefly again and it completely stops. I get nothing on my monitor, I don't get any of the normal "beeps", nothing. It does what I said and then it just stops and idles. I was told that it may actually be a bad power supply and not the CPU. Any ideas? Thanks in advance, it hasn't been working for 2 weeks now!
- Chaz