View Full Version : BEEEBOOOBEEEBOOO - uh oh. a7v with 1.1ghz :(
I have an A7V that was faithfully going at 950 with an 800 tbird at 1.85 with the L1's closed. However, I recently put a 1.1 in, and tried to close the bridges with a pencil, as I had with the other proc. Upon trying both 1.2 and 1.3, I recieved errors upon boot, so I jumpered the proc back down to 1.1 with default voltage. Last night I got a different pencil to try ONE MORE TIME before I closed the case, and tried for 1.2. Bad things then began to happen. After a few agonizing seconds with no bios beep (the latest bios btw), I was rewarded with a beeebooobeeebooo alarm coming from the board. After a rapid shutdown, I checked the now very warm proc and noticed a... slight burning smell. I am using thermal paste with a good hs/fan that has served me for almost a year. A couple more tries after jumpering back down to 1.1 now have the same results. :(
I had used this comp for gaming for 3 days before trying this last maneuver. The FSB is default 100, and all other components are top-notch. GeForce-3, pc133 256M, 7200rpm Maxtor, SbLive...yada yada yada.
I guess my real question is, does anyone have experience with this error, and is it safe to try another proc in the motherboard... or have I turned it into a CPU Killer? Getting another proc is no biggie, I may just put the 800 back in as it was doing fine in the first place. Going over the install, the only possible user error I can think of would be a possible crosslink of the bridges. Any ideas?
i'd put in the other chip.
i can't see the mobo being a killer now, and it probably was due to a stray pencil mark... but i'd look at the chip to see for sure.
is there any brown residue on it near the core?
Well, I dont really see much of a brown residue... I can see the blue stuff from the original coating on the core, and I still have some thermal paste on it as well. It does seem to have a "sweating" look to it that branches out from the core to the surrounding chips, a darker look that may have been there before... I dont remember... but this look is duplicated on another 1.1 that I have, and the original 800 as well, so not sure about that. After the first alarm go-round, I promptly erased the pencil marks, and made sure the whole thing was clean before retrying. Could that first time with a possible crosslink have killed it? It WAS pretty hot when I pulled it out. I am going to take it to work today and put it in a machine that I have no concern for and see what happens. Maybe I should hope it doesnt work so I can still use the board, you think. 8p
If the darn thing DOES work in another machine, do u guys think maybe the bios could be the issue, or have I done deeper damage? I have tried the CLRTC a couple times just to see if that would fix it, which it would not.
Any ideas or thoughts are welcome. 8)
well, i have'nt had the experience to say...
as far as whether cross-linking will damage.
i don't think it being hot was a good sign at all tho.
pull the btty from the mobo for like 3mins.
then try the 800
i bet the mobo is fine, and will be fine.
carefull with thermal paste as not to get it all over, only on the core itself.
In general it is not a good sign when you get a burning smell, only things frying make a burning smell. Something is probably toast just have to figure if it is the mobo or cpu. Is it possable the HSF wasn't held down good enough to compress the 4 feet on the cpu? Sometimes the clips tend to weaken with repeated use and need to be rebent.
Have you tried reseating everything cards, memory, cpu, and even the power cord going to the mobo?
Well,
My relief is mixed, but it IS relief I guess. The 1.1 did NOT work at all in the other machine, and the 800 posted like a champ the first time. I re-penciled it (Vewwy Carefuwlly), and then clocked it back to 950, where it is all warm and fuzzy gaming away for me. :)
A note---- I DID have the same alarm initially before I repenciled the chip, which was disconcerting and I can only think the cause is that the chip was not fully or properly unlocked and was reporting an incorrect cpu speed. This was reflected when I repenciled and posted into a bios safe-mode screen. That stated, make SURE that your pencil marks are dense enough to provide conduction, and not crosslinked.
Cyall, and thanks for the input.
TibeR (Jun 08, 2001 06:32 p.m.):
Well,
My relief is mixed, but it IS relief I guess. The 1.1 did NOT work at all in the other machine, and the 800 posted like a champ the first time. I re-penciled it (Vewwy Carefuwlly), and then clocked it back to 950, where it is all warm and fuzzy gaming away for me. :)
A note---- I DID have the same alarm initially before I repenciled the chip, which was disconcerting and I can only think the cause is that the chip was not fully or properly unlocked and was reporting an incorrect cpu speed. This was reflected when I repenciled and posted into a bios safe-mode screen. That stated, make SURE that your pencil marks are dense enough to provide conduction, and not crosslinked.
Cyall, and thanks for the input.
I bet the hsw didnt have contact with the core. Since i dont think crosslinking the l1 bridges will damage the cpu since i did on my old duron with purpose just to check. Only thing that happened was that it was still locked. Runned it for weeks like that and now 6months after it still lives:)
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.