Did I kill it?

[ClockRock]

I hope that anyone has some advise:
I was trying to push my 700 Duron to 1 GHz and had it up to 103x9.5 = 979MHz. On an ABIT KT7. System ran stable at 34C (idle) / 42C (load). Suddenly error in kernel32.dll.
OK, I reboot (actually only try to).
From now on, the only thing I see on the screen after reboot is the BIOS version and Duron 979 Mhz detected (or so).
After that the system hangs, no RAM check, does not react to INS, DEL etc.
Looks like I fried the CPU, but how?
What's a good way to figure out if CPU or MOBO are dead?
Any hints (except for verbal abuse) are appreciated.

[ken257]

Since your system comes up you should be fine, nothing is dead. More then likely your settings are just not bootable. If you can get into the bios relax some of your settings a bit. If you can't enter bios there is a jumper to clear the cmos. This will restore the default settings so the system can boot again.

[SleepyKat]

I don't think you killed it either. I cratered my 1 GHz TB after 5 min at 1550. Win98 freaked. I let it cooled down and reset the CMOS to factory default and everything powered up and it locked at Win...the OS sw got scrambled, so I had to reload Win98 (sometime got shook loose) . At 1417 for the past few days.

[ClockRock]

OK, so I am getting a bit more optimistic after all your replies. Does anyone know how the system would come up (at all) if the CPU really was dead?

[SleepyKat]

if the cpu was dead, the MB will not do anything. It's like firing up a system without a processor..nothing happens.

[rugby]

SleepyKat (May 29, 2001 06:45 p.m.):
if the cpu was dead, the MB will not do anything. It's like firing up a system without a processor..nothing happens.

I hear that one. Just happened to me. I just got my 1.2 Tbird today and can't wait to see how high I can take it. Too bad I've got a kt7 board and not the kt7a.

[ClockRock]

OK, thanks for all your advise and hints.
The CPU still works. This is how I got it to work:
1.) Clear CMOS - no result
2.) Desperate attempt: Remove all cards except graphic card and see what happens - system boots :-)
3.) Put back all cards one-by-one to see which one is culprit --> System still working after ALL cards have been put in :-)

What happened - NO IDEA
But it works again :-)

[castle lager fan]

Hi Rugby,

Where are you from?

I'm South African now living in San Jose.

[Tomas]

Would71 (May 29, 2001 06:06 p.m.):
My three main mobos are a KT7A, a KT7, and an EPoX MVP3G5.. of those three boards, the KT7 is by far the crankiest board. It'll run fine for weeks, overclocked or no. (right now I have an original factory-unlocked Duron/650 on it, that runs fine at 800) On occasion, the board just decides it doesn't want to boot anymore. It quotes the CPU speed and multiplier, does a RAM test, and locks at the RAM test. Makes me think the bloody thing died. I try all sorts of things.. different RAM, clearing CMOS, yanking the battery overnight, etc. Nothing gets it to boot..

I had the same problem with my abit kt7. It wouldnt let me run my 133mhz ram on 133mhz. Couldnt even get it too post if i set it at anything higher than slow in the memory timing + low md load or something like that. If i got into windows i got like 300mb/s and something in sisoft sandra.

Also it was increadible unstable on every setting with my tbird 1.1.

Then i decided to buy the asus a7v133 and now im running on 133mhz even my old 64mb(100mhz) stick:)) At all high settings!!

The results are 590something/608 in sisoft!! So il say dump that ****TY abit board an go for an asus.

also now got 1.1@1.33 on default volt on this old tbird avha(200mhz) version. Only got 1.2 on the abit.
..except time. For some strange reason, if I let it sit for a couple days, it often works again like nothing ever happened. It's the ONLY board I know of that does this.. does it with any chip I use in it, any RAM, whatever. In fact, I bought the KT7A because I thought the KT7 was dead. Assembled the new system around the KT7A, decided a few days later to test the "dead" KT7, and what do you know, it worked.

I'll have to say, I'm not very impressed with Abit. Not many people may have experience with them, but my next board will probably be another EPoX. I loved both Super-7s I had from them. This MVP3G5 rocks for a S-7.. 2 meg L3 cache when used with my K6-3/400. I'm thinking about making a Tribes 2 server out of it. (what can I say, I love that cache memory) :D

I'm sorry, I know I didn't really help your question much.. but I'm just about as lost as you are on that issue.

[Tomas]

sorry this got all WRONG!!

I had the same problem with my abit kt7. It wouldnt let me run my 133mhz ram on 133mhz. Couldnt even get it too post if i set it at anything higher than slow in the memory timing + low md load or something like that. If i got into windows i got like 300mb/s and something in sisoft sandra.

Also it was increadible unstable on every setting with my tbird 1.1.

Then i decided to buy the asus a7v133 and now im running on 133mhz even my old 64mb(100mhz) stick:)) At all high settings!!

The results are 590something/608 in sisoft!! So il say dump that ****TY abit board an go for an asus.

also now got 1.1@1.33 on default volt on this old tbird avha(200mhz) version. Only got 1.2 on the abit.