GA-965P-DS3 (rev3.3) caught in endless reboot loop (before boot, totally black)

stoejer

Junior Member
May 6, 2007
2
0
0
Hi

I have recently purchased the following hardware for a new rig:

- a Gigabyte GA-965P-DS3 motherboard (rev 3.3 with F10 BIOS)
- a Core 2 Duo E6300 processor and
- 2 x 1 GB Transcend JetRam DDR-667 (JM388Q643A-6)

I bought the DS3 because of its fine reviews and the Transcend JetRam, because according to this articel, they should overclock mighty fine http://www.anandtech.com/printarticle.aspx?i=2862 .

For the first week, I ran the system at clock speeds with absolutely no problems. I then decided to clock the RAM at DDR2-800 speeds instead of the factory 667.

Whenever I upped the RAM voltage by 0.1v or 0.2v the result would be a black screen, no POST. I tried this again without changing the speeds but only upping the voltage from 1.8v to 1.9v or 2.0v. The results were the same; black screen.

It was always possible to get back into the BIOS by resetting the BIOS by jumping the CLR_CMOS pins on the motherboard.

Since changing the RAM voltage resulted in a black screen I decided to overclock it from 667 to 800 without touching the voltage at all.

This is where it got really bad. The system rebooted and it actually POSTed. However, it stalled right after POSTing, before booting the OS. I then reset the system and something flashed on screen, where the only thing I could read was something BIOS and a lot of progress dots. Scouring the net afterwards it seems it might have looked for a BIOS on my harddrive or something but I am not sure.

When I power the system on it will go into an endless reboot cycle. The case fan spins up and stops after a few seconds; 2 seconds I think. Nothing is shown on screen, it's completely black. Then it turns the power off and does the same thing over and over again.

This seems to be referred to as "the cold boot issue" but I have tried just about anything I have read to no avail.

I have tried unplugging the system, removing the power cord, taking the CMOS battery and memory modules out, leaving the system like that for 10 minutes and then only inserting one memory module before trying to boot the system again. Still the same result; endless reboots with nothing shown on screen. CLR_CMOS does nothing.

My question now is, what can I do? Will I have to RMA this board? Is it toast? Is there any chance that borrowing and trying another memory module will make the system boot? Remember that it ran perfectly fine for over a week with these memory modules at DDR2-667 settings.
 

Kromis

Diamond Member
Mar 2, 2006
5,214
1
81
Will resetting the CMOS do anything? Lol, I don't know. Just pulling suggestions out of my arse.
 

stoejer

Junior Member
May 6, 2007
2
0
0
Resetting the CMOS does not help, no. From my original post, "CLR_CMOS does nothing" was supposed to mean that clearing/resetting the CMOS had no effect on the problem.

In the meantime I have tried a Kingston memory module with no improvements. :( That module was on the list of supported memory modules, so I am currently at a loss.
 

imported_Arc

Junior Member
May 2, 2007
9
0
0
I had the exact same 'endless reboot loop' as you do. GA-965P-DS3 with E6600 and 2GB Corsair XMS2-6400 Ram.

I am currently waiting on a replacement mobo from newegg. I *really* hope I don't encounter this problem again.