So I've been struggling with this issue all last night, and I've pretty much run up against the wall of my technical knowledge. I figured I'd post here, to see what everyone's thoughts were.
The Setup:
I just purchased a new KT7A motherboard as well as a 1GHz Athlon processor (obvious, given the topic title). They were both retail, so I didn't think I'd have too many issues with them. Little did I know.
The Problem:
So I installed the processor and heat sink with no troubles (by no troubles, I mean that it all went onto the board with no issues). So I put the board into the case, popped in my RAM (also newly bought: 256MB of PC133 RAM), plugged in all my cards, installed all my hard drives etc. Flipped the switch - and nothing. I got a POST code of 40 (4 long beeps, no short beeps) and my computer turned itself off. I checked out various websites for POST codes, and all I could get out of it was that 40 was "reserved."
The (Attempted) Solutions:
First, I tried resetting the CMOS. Interestingly, this stopped the beeping, and my computer turned on ok. However, my video card was quite obviously not working (given the lack of anything being displayed on my monitor), and I wasn't getting any sort of POST codes indicating as much.
I then unplugged all my cards except the video card. Again with the 4 beeps and shutdown. A CMOS reset, once again, stopped the beeping but still didn't produce any sort of image on my monitor.
I then looked through the manual that came with the mobo and saw that the memory had to be in the right slots (ah ha! you're thinking, thats the culprit!). No dice - the memory was installed correctly. I even whipped out some old PC100 RAM to fill all the DIMMs, just to be sure. At this point, the beeping was beginning to drive me slightly loopy (still 4 long beeps, and shut down).
So I figure maybe its the video card? So I try an old PCI video card. Still beeping.
The Question:
At this point, I've totally run out of ideas on what could be wrong. The two things I can think of are: bad memory (which I don't think is the case), or a bad processor (which I hope to all that is holy isn't the issue). So, my question to you out there in the net world is: Any ideas?
All help is much appreciated!
The Setup:
I just purchased a new KT7A motherboard as well as a 1GHz Athlon processor (obvious, given the topic title). They were both retail, so I didn't think I'd have too many issues with them. Little did I know.
The Problem:
So I installed the processor and heat sink with no troubles (by no troubles, I mean that it all went onto the board with no issues). So I put the board into the case, popped in my RAM (also newly bought: 256MB of PC133 RAM), plugged in all my cards, installed all my hard drives etc. Flipped the switch - and nothing. I got a POST code of 40 (4 long beeps, no short beeps) and my computer turned itself off. I checked out various websites for POST codes, and all I could get out of it was that 40 was "reserved."
The (Attempted) Solutions:
First, I tried resetting the CMOS. Interestingly, this stopped the beeping, and my computer turned on ok. However, my video card was quite obviously not working (given the lack of anything being displayed on my monitor), and I wasn't getting any sort of POST codes indicating as much.
I then unplugged all my cards except the video card. Again with the 4 beeps and shutdown. A CMOS reset, once again, stopped the beeping but still didn't produce any sort of image on my monitor.
I then looked through the manual that came with the mobo and saw that the memory had to be in the right slots (ah ha! you're thinking, thats the culprit!). No dice - the memory was installed correctly. I even whipped out some old PC100 RAM to fill all the DIMMs, just to be sure. At this point, the beeping was beginning to drive me slightly loopy (still 4 long beeps, and shut down).
So I figure maybe its the video card? So I try an old PCI video card. Still beeping.
The Question:
At this point, I've totally run out of ideas on what could be wrong. The two things I can think of are: bad memory (which I don't think is the case), or a bad processor (which I hope to all that is holy isn't the issue). So, my question to you out there in the net world is: Any ideas?
All help is much appreciated!
Facebook
Twitter