New board, new issues...

[Yellowhello]

Alright, so I got a new DFI Blood Iron P35-T2RL to replace the ASUS P5N32-E SLI Plus that I sold. I have literally had this motherboard for less than an hour and I'm already having problems.

I put together my computer using the stock cooler to install drivers and get to know the BIOS. After I installed the drivers, I decided to see how high FSB I could get on this board, because there were rumors that this board overclocked like crazy with dual core CPU's.

I brought the multiplier down to 6x, because I didn't what to overclock the CPU, just the FSB. I saved and it restarted like usual. I got back into the BIOS and proceeded to raise the FSB to 300, up from the stock 200. Saved, restarted, and it didn't POST. Hung at the BIOS start up screen. I cleared CMOS and tried again. Multiplier back at 6x, I tried a 1MHz overclock, up to 201. Saved, restarted, and no POST! WTF! This board was supposed to kick ass with dual cores!

I cleared CMOS a few times and tried again. No go. I turned the computer off, and turned it back on again. Now the computer won't even get to the BIOS screen, at stock settings. The computer is on, but the monitor remains in standby, and it's been doing this for every time after.

Please help! Should I RMA it? Was this a bad board choice? What should I do?

Thanks in advance,
Nate

[Capper]

turn it off, unplug the computer, and pull the CMOS battery for 10-15 minutes.
After that, if it boots, I'd recommend checking to make sure you have the latest BIOS.

If none of that works, try disconnecting peripherals, I've seen boards have boot issues caused by what was connected to it.

[Yellowhello]

Originally Posted by Capper

turn it off, unplug the computer, and pull the CMOS battery for 10-15 minutes.
After that, if it boots, I'd recommend checking to make sure you have the latest BIOS.

If none of that works, try disconnecting peripherals, I've seen boards have boot issues caused by what was connected to it.

I took out the CMOS for 10min. and put it back in, then cleared the CMOS again, and I was able to get into Windows. I'll try to update to the latest BIOS and see if that fixes the overclocking problem.

Thanks Capper!

[RA1D]

Rich to the rescue!

[Capper]

No problem buddy......thats a fairly common issue with DFI boards....they have incredible BIOS options, but they can be a bit finnicky.

[screwballl]

remember with overclocking, do it in small steps, not one big jump from 200 to 300.. I would say in your case go by 10s from 200 up to make sure it is stable and see what level it stops, may have to up the multiplier to 7 to get an odd fsb but may get better results...
just some ideas

[gvblake22]

Originally Posted by screwballl

remember with overclocking, do it in small steps, not one big jump from 200 to 300.. I would say in your case go by 10s from 200 up to make sure it is stable and see what level it stops, may have to up the multiplier to 7 to get an odd fsb but may get better results...
just some ideas

That is probably the biggest thing to remember here. Overclocking is not a "get rich quick" scheme, you have to take your time and be patient. Like screwballl mentioned, 10 MHz or so at a time is usually what I do.

[Yellowhello]

Originally Posted by gvblake22

That is probably the biggest thing to remember here. Overclocking is not a "get rich quick" scheme, you have to take your time and be patient. Like screwballl mentioned, 10 MHz or so at a time is usually what I do.

I understand this. But the reason I took such a big jump that one time was because the Blood Iron has a good reputation for overclocking dual cores and I was pretty confident that it could run 300FSB.

[gvblake22]

Originally Posted by yellowhello

I understand this. But the reason I took such a big jump that one time was because the Blood Iron has a good reputation for overclocking dual cores and I was pretty confident that it could run 300FSB.

Doesn't matter, new hardware is new hardware, is new hardware... I'm sure you know this too, but I'm going to say it anyway: just because someone with the same motherboard and processor got a certain overclock DOES NOT mean you will too

[Yellowhello]

Originally Posted by gvblake22

Doesn't matter, new hardware is new hardware, is new hardware... I'm sure you know this too, but I'm going to say it anyway: just because someone with the same motherboard and processor got a certain overclock DOES NOT mean you will too

Your right, I understand that too, and I'll keep it in mind.