VOGONS


First post, by Choppo51

User metadata
Rank Newbie
Rank
Newbie

I'm busy getting to the bottom of an issue I have with my PC not booting up.

I purchased an AMD K6-III/333 CPU 2 months back and just started building my pc to the spec I had back in the day this weekend.
Prior to this weekend, I had tested the motherboard last year September (Gigabyte GA-5AA Rev 2.2) with an AMD-K6/233 CPU I had spare just to confirm the motherboard was working correctly as I purchased it off eBay.

It all worked correctly, was able to POST and boot into DOS.

Today I built the entire PC as the last bits I needed had arrived. I set the motherboard jumpers correctly for the AMD K6-III/333 CPU and triple checked all jumpers and connectors before powering on.
I powered on the PC and it ran for 3 seconds before powering off. It would not power on after that. If I pulled the power cord, waited for 5 seconds and plugged it back in, the PC would power on for 3 seconds then turn off again.

I thought the CPU was maybe DOA as this was the first time I was able to test it since buying it off eBay. I then went to put in the same AMD-K6/233 CPU I previously successfully tested the board with and it does the same thing now...
Powers on for 3 seconds then powers off.

When it the PC powers on, there is no display as it turns off after 3 seconds. There are no POST beeps or noises. I can confirm the motherboard was on the F6 BIOS revision which was the last official BIOS revision ( besides the beta release I believe??) I have tried swapping DIMM modules with known working ones, have swapped out video cards as well, including trying both AGP and PCI video cards.

So yeah, is it possible the AMD K6-III/333 CPU was faulty and has fried my motherboard?

Thanks in advance.

Reply 2 of 16, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

That time feels like if the ATX power switch is stuck shorted.. It would power on then force a power off after a few secs.. I'd try a different PSU or momentarilly shorting the power header with a jumper and releasing it quickly.

Also, does the same happen without any CPU installed?

Turbo XT 12MHz, 8-bit VGA, Dual 360K drives
Intel 386 DX-33, Speedstar 24X, SB 1.5, 1x CD
Intel 486 DX2-66, CL5428 VLB, SBPro 2, 2x CD
Intel Pentium 90, Matrox Millenium 2, SB16, 4x CD
HP Z400, Xeon 3.46GHz, YMF-744, Voodoo3, RTX2080Ti

Reply 4 of 16, by Choppo51

User metadata
Rank Newbie
Rank
Newbie
wbahnassi wrote on 2026-02-28, 14:58:

That time feels like if the ATX power switch is stuck shorted.. It would power on then force a power off after a few secs.. I'd try a different PSU or momentarilly shorting the power header with a jumper and releasing it quickly.

Also, does the same happen without any CPU installed?

Hiya, I tried 3 different PSU's. All confirmed working units.

Same symptoms without the CPU installed.

Cheers,

Reply 5 of 16, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

Does it turn on the moment the ATX PSU's hard switch is turned on? Is there continuity between the two pins of the power header on the front panel connectors block?

Turbo XT 12MHz, 8-bit VGA, Dual 360K drives
Intel 386 DX-33, Speedstar 24X, SB 1.5, 1x CD
Intel 486 DX2-66, CL5428 VLB, SBPro 2, 2x CD
Intel Pentium 90, Matrox Millenium 2, SB16, 4x CD
HP Z400, Xeon 3.46GHz, YMF-744, Voodoo3, RTX2080Ti

Reply 6 of 16, by Choppo51

User metadata
Rank Newbie
Rank
Newbie
wbahnassi wrote on 2026-03-01, 05:26:

Does it turn on the moment the ATX PSU's hard switch is turned on? Is there continuity between the two pins of the power header on the front panel connectors block?

No, I have to push the power button on the case to power the system on. No continuity between the two pins of the power switch header on the motherboard.

Cheers,

Reply 7 of 16, by CharlieFoxtrot

User metadata
Rank Oldbie
Rank
Oldbie

In general I find it unlikely that a CPU can cause MB failure, especially when it is a correct CPU for the platform. Your case just sounds a coincidence.

Your problem sounds like a power delivery issue, like perhaps a regulator is failed. It also just may be that the new CPU has higher power consumpition and it pushed the already failing component over the edge.

Reply 9 of 16, by Beerfloat

User metadata
Rank Newbie
Rank
Newbie
CharlieFoxtrot wrote on 2026-03-01, 06:44:

In general I find it unlikely that a CPU can cause MB failure, especially when it is a correct CPU for the platform. Your case just sounds a coincidence.

Your problem sounds like a power delivery issue, like perhaps a regulator is failed. It also just may be that the new CPU has higher power consumpition and it pushed the already failing component over the edge.

This.

It would be good to test the CPU on another board but you gotta work with what you have.
Even if the K6-III/333 isn't faulty it is still one of the more power hungry socket 7 CPUs.
I'd be checking the power delivery on the board, particularly the 5 big caps next to the CPU socket. They're from the era of limited lifetime caps.

Reply 10 of 16, by MikeSG

User metadata
Rank Oldbie
Rank
Oldbie

Take the motherboard out, check for shorts on the bottom, check all metal standoffs are in the right place...

Reply 11 of 16, by rasz_pl

User metadata
Rank l33t
Rank
l33t

1 Congrats on a CPU that officially doesnt exist according to AMD 😀 its the year 2000 Fry's Electronics Black Friday special. Afaik available only there and then for cool $29.
2 diagram for GIGABYTE GA-5AA rev3.2 Re: 430VX or 580VPX schematics and post describing 2.2 vs 3.2 differences Gigabyte GA-5AA revision 1.1, 2.2 and 3.2 differences

on Ver2.2 CPU Vcore is generated by non stnchronous DC/DC converter. U11 controller + q8 mosfer + D10 diode + L10 coil.
You can check if everything is working by measuring voltage on L10 coil and on pin2 of U11.
Personally I would start by recapping this board. Dont fret too much about special brands, any cheapest lowesr caps with more or less similar parameters will do. Even the crappiest caps wont see hard load here and will deliver thousands of hours of continued use, more than you and your children would ever use this board 😀
TC23 _non_ lowesr 330uF 6.3V, pretty much any random cap
TC24 TC39 TC40 C114 and 5 ones along CPU socket all lowesr 1000-1500uF 6.3V

but shutting down after 3 seconds I suspect might be due to shorting to something inside the case, maybe one of the motherboard metal studs didnt line up with hole? try with mobo out of the case

https://github.com/raszpl/sigrok-disk FM/MFM/RLL decoder
https://github.com/raszpl/FIC-486-GAC-2-Cache-Module (AT&T Globalyst)
https://github.com/raszpl/386RC-16 ram board
https://github.com/raszpl/440BX Reference Design adapted to Kicad

Reply 12 of 16, by Choppo51

User metadata
Rank Newbie
Rank
Newbie

Hi all,

A follow up with this issue, I managed to find another super socket 7 motherboard which was confirmed to work. Tested with the CPU and it worked. I guess it was just by coincidence the motherboard died from the time I tested it. 🙁
I can confirm I tested the board outside of the case when it refused to boot the first time. There are no extra stand offs or anything touching that could have shorted the motherboard. I suspect it's just component failure on the board.

Reply 13 of 16, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie

Good news, the next step is try to repair the motherboard since it's one of the best ss7 one and deserve to be saved!

Reply 14 of 16, by Choppo51

User metadata
Rank Newbie
Rank
Newbie
Nemo1985 wrote on 2026-03-14, 10:24:

Good news, the next step is try to repair the motherboard since it's one of the best ss7 one and deserve to be saved!

Absolutely! Would really like to get it up and running as it's the same as what I had back in the day. 😀

Reply 15 of 16, by the3dfxdude

User metadata
Rank Oldbie
Rank
Oldbie
rasz_pl wrote on 2026-03-01, 12:06:

1 Congrats on a CPU that officially doesnt exist according to AMD 😀 its the year 2000 Fry's Electronics Black Friday special. Afaik available only there and then for cool $29.

I certainly did not buy my K6-3 333 MHz on black friday 2000. I know what I bought on that day 😀 They had these chips available through summer, if not most of the year. If they had this in their black friday 2000 sale(?), then it was the last few left. I'm pretty sure I remember someone there tell me they were trying to get rid of them on my earlier visits. Unsure why it didn't attract more attention, but I guess in 2000, Athlon was out, and getting price cuts. If anything, it would have been the Athlon on sale black friday 2000 because I know some speeds were sub $200 by that November, so if they went on sale, that would have brought people in. The K6-3 333 MHz was priced lower than the K6-2 on 100 MHz FSB, due to the low speed. This is why I bought them. It would have been otherwise a well performing socket 7 chip, priced quite low. Still beaten though, by the highest clocked K6-2 and the other K6-3 in the store, if you wanted to spend more money.

Beerfloat wrote:

Even if the K6-III/333 isn't faulty it is still one of the more power hungry socket 7 CPUs.

CharlieFoxtrot wrote:

Your problem sounds like a power delivery issue, like perhaps a regulator is failed. It also just may be that the new CPU has higher power consumpition and it pushed the already failing component over the edge.

Being the slowest clock speed in the FSB 100MHz (95MHz actually) class of chips, it would have been the one with the least power draw and heat production. I know my chip runs quite cool. The K6-2 was the hotter chip, since it was clocked higher than this one. This kind of makes me wonder, that this production batch was intended as OEM for laptops, but the buyer bailed on it, just like the K6-2+ 570 MHz, and so became a Frys store special. This chip would been the coolest 100MHz class chip until the K6-2/3+ die shrink.

It could be a bad chip, but as other people are saying, I would think that based on the behavior, I would look at the motherboard and power supply for clean power delivery. That is usually the situation for things like this.

Reply 16 of 16, by zami555

User metadata
Rank Newbie
Rank
Newbie
Choppo51 wrote on 2026-03-14, 06:51:

I suspect it's just component failure on the board.

You already got a very good advice on where to start to check to identify the failure. I would just like to add, that since that Gigabyte has already BGA chipset it's also possible that due to the handling of the board during tests/assembling some ball could lose contact from chip to PCB. You can try to press with your finger on top of the chipsets to try to force chip to get better contact to PCB (if only any of the balls is a culprit). If it boots then it will require reballing for chipset.