| | #1 (permalink) | |
| Ok guys, this doesn't happen often, but I have one that I have never seen before. Abit AT7-e KT333 mobo. XP2100+ T-Brd B Corsair XMS3000 CL2 512mb, one module ATI Radeon 8500 64mb. SB Audigy X-Gamer 3COM 10/100 NIC 60GB Maxtor ATA133 7200RPM drive. Sony CDROM HP 9300i CDRW Antec 480watt TrueBlue PSU SLK800 with Smartfan2 Ok, most know of my OC successes with this new chip. yesterday I got home from work and wanted to play some more. First, let me say that I am still on a BIOS that doesn't officially support my chip, I will fix that today. Now I was running with a multi of 13 and 175mhz HClock at 1.75Vcore. All I did was boot to BIOS and drop the Multi one level, now this setting reads "12.5/13" and the previous one was "13 and up", (Yes, these are strange). After accepting and saving the BIOS change, the system began it's reboot and failed to POST. I could get back into the BIOS, but each time it would fail to POST. I have managed to get booted into windows and get running by going back to my 1800+ and loading the "Fail Safe Defaults", then modifying them appropriately. But, my attempts to go back to the XP2100+ have failed repeatedly. I have cleared CMOS by Jumper, and even completely powered off and removed the CMOS battery letting it sit for over an hour. I will get home tonight and swap back to the XP1800+, then flash the BIOS and see what happens. The only other possibility I can think of is to use the XP1800+ to get to the BIOS again, load Fail safe, boot, shut down, swap CPU's, and see what comes up. I believe that I have somewhat corrupted the BIOS in some weird way, I am not certain that I have damaged the CPU as I do not think the change should have hurt it, but I can't tell for sure yet. But, if any of you guys have actually seen this and know of something that I should try, please lay it on me. | ||
| | | |
| | #4 (permalink) | |
| i know i was at a friends house and he was messing around with the multipliers and whatnot, his system is oc'ed, he rebooted and couldnt get the system to post after one certain configuration.....but all he did was clear the cmos and wait 15 mins and it let him recogfigure back to the highest setting he knew worked It kinda souns like maybe you fried it......i could be totally wrong, but the things we do are usually never a hit and miss deal, pretty precise art, it has to be......there should be no reason why you cant just throw in the same chip, and go with the same settings.....unless that same chip is altered physically now....as in its fried? hehe i dunno if that made sense....i just woke up and wrote this =P | ||
| | | |
| | #7 (permalink) | |
| Remember how pissed I was after I tried to hit that 200FSB? That is what happened to me. It took be hours just to get the CMOS clear, then I had to underclock the chip to get it into windows. Once I was at that point I reflashed the bios. I reset everything to my original OC that was working so nice before, no post. I had to clear the CMOS again. This time I underclocked and booted into Windows. Drank 3 beers. Brought the timing up and rebooted. Drank 3 beers. Brought the FSB up to 166. Drank 3 beers. Brought the timing up a little more. Drank 3 beers. Brought the FSB back to 170. Drank 6 beers in celebration. I don't know why I had to incrementally bring it back like that when originally I just pretty much went for it. But it came back and has been working fine ever since. I may know what your problem was...did you have beer? | ||
| | | |
| | #8 (permalink) | ||||||||||||||||||||
Hey i figured i'd just let you know that my first comp, an AMD K6-2 w/ 3dNow!, is running as well as it did when i first built it.. soo AMD isn't as problem prone as you think | |||||||||||||||||||||
| | | ||||||||||||||||||||
| | #9 (permalink) | |
| Well, thanx for the compassion guys. No BA, no beer yet, could be an issue I thing the CMOS just doesn't want to play, like it's pissed at me that I would even think about running it slower after it gave me a 500mhz OC. Spiteful Biotch ! I'll figure it out, and a BIOS flash should clear it up after I get it back on the 1800+ first. Thanx again. Oh, BTW, I know why many of you, like BA, come here instead of many of the other websites like [H] and Overclocker's.com. I was browsing their forums looking for someone who had a similar problem, I found plenty of guys with problems, and NO ONE giving them help, unbelievable, NOBODY goes without some kind of help here, but over on those sites, 0 replys, I was amazed. | ||
| | | |
| | #12 (permalink) | ||||||||||||||||||||
Ba Is RIGHT ON THE MONEY here. Not sure why it happens. Sometimes when you rock your bios just a tad hard it gets shakey. Things dont go as planned. And even cmos clears wont help. I usually have to flash the bios and then incrementally keep trying to get back to the OC i had before. seems to work if your cautious. All signs point to Cmos chip and not CPU in your case. I can tell you from experience a few times over. AMD's dont fry lightly. you get em extra crispy or raw. get the point. There is no medium rare. Let us know how it goes and if you have any questions LC you know how to call. I got a 2400 throughbread and the at7 400 board here. Similar stuff . ![]() | |||||||||||||||||||||
| | | ||||||||||||||||||||
| | #20 (permalink) | |
| Icpiper pretty nice going i wich i could get that far but maybe later i got my self a new board GA-7vax with KT 400 , but i don't think i'll go very far cuz i got a 1700+ pal.(****) works well but high temp always around 50c & 55-56 Gaming already Ovclk to 1.540 by the FBS 140=280 MHZ. BTW: i'm not shure but i think you got the highest overclock on a AMD cpu , 1800+ is a 1.533 right & now you got 2.279 , WOW! more then 700 mhz Ovclk. & more then the 2800+ that is @2.25GHZ. I would give you a award for that if i had one to give. | ||
| | | |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Piper is going to rant again. | lcpiper | Anything Goes | 26 | 29-April-05 11:17 PM |