View Full Version : Neo2 + 3000 won't post
vapourit
01-31-2005, 06:44 AM
I went from 9x 265 fsb = ~2.4 GHz to trying for a higher HTT at 8x 300 fsb (5:4 ram) and now my PC won't boot at all. It just turned on and sits there, no signal going to the monitor. I pulled the battery for a few minutes and I've tried shorting pins 2-3 on jbat1.
The diagnostic lights show 2 red's and 2 oranges which meant no processor or processor damaged, but I brought my 3000+ to work and it tested fine.
Did a kill my neo2 platinum? Is there anything else I can try. I unplugged all DVD/HD.
HELP!
SuperDude
01-31-2005, 02:01 PM
Tried resetting the cmos?
justwOo
02-01-2005, 02:21 PM
Pulling the battery resets the cmos
Did you check your ram? Like try reseating it or using different stuff?
let us know how ya make out
Napoleonic
02-01-2005, 09:14 PM
my neo2 can't get stable so far when at 300+ HTT, maybe that's the limit
dnottis
02-01-2005, 10:26 PM
Reset cmos - otherwise looks like maybe you killed your board.
I tried 300 x 8 last night too - CMOS reset fixed it on non-boot.
Liquid3D
02-01-2005, 10:53 PM
I don't think you killed your mobo, but pulling the battery is not the method I'd use for resetting the Cmos, that's what the jumper is for. LOOK IN THE MANUAL and FOLLOW THE INSTRUCTIONS for clearing CMOS.
Sometimes it's better to think like a noob. Regardless of expereince I keep the manual near-by just to be sure. I can't tell you how many times I thought I checked everything and found I left the jumper in the "Clear" position or something silly like that. I'd also pull the memory re-set it. No neded to unplug the HDD or DVD that really has nothing to do with this.
Did you raise the DDRVoltage when pushing past the 300FSB area? Could you have corrupted your HDD? Is it SATA or ATA? Unplug the PC pull memory and place in second set of DIMM's, re-set CMOS jumper (don't fiddle with the battery replacing it incorrectly could cuase a problem) and then re-start. I bet my Karma acount you'll be running tonite.
zA.Gosu
02-02-2005, 01:30 AM
What slot was the HD in? Im betting SATA corruption, cause he prolly used 1 or 2, and :banana::banana::banana::banana:ed it up at high fsb
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.