Gigabyte GA-P35-DS3L Thread

[Plasmah]

rcf22... Very good investigating thanks for the tip!

[NP2H]

Originally Posted by rcf22

Hey Guys,

I will probably create a new thread for this, but it pertains solely to this board, so I wanted to post this here first:

There is a known issue with the P35-DS3L that several boards will reboot upon OC settings being applied in the BIOS. Namely, unlocking the FSB option causes the system to reboot right after the POST screen with all FSB and memory settings returned to default (locked FSB, auto memory timings and multiplier).

I had been held prisoner at stock speeds by this problem for several months after being able to overclock my first week with this board up to 3.2GHz. I was very pleased until this occurred, and today I did some more research on the topic. Several "solutions" have been mentioned, and here are several I have seen:

1) Set Halt on Errors to None
2) Disable serial and parallel ports
3) Clear CMOS, etc.
4) Bad PSU
5) Bad voltage/memory timing settings

However, I had tried all this without any success. BUT, my problem was solved from an unexpected source! An external USB hard drive seemed to be the problem. I'm not sure the root cause of this, but upon unplugging this, the system boots up properly with any overclock settings I've tried! Thinking back to it, I had this HDD disconnected when building my system, and the problem could've very well began when I connected it. The drive is a Western Digital 250GB MyBook if you're curious.

So, any of you DS3L'ers out there stuck at stock speeds, yank out any USB legacy devices you have connected to see if that solves your booting issue! In my situation, I was 100% the hardware was fine because 1) I had overclocked through the BIOS before, and 2) I had overclocked successfully through software even with this boot issue. I still have several USB devices connected, so perhaps hard drives are the main culprit.

I'm currently at 3.0GHz and look forward to shooting for 3.6. Look forward to updating my OC settings on the front page Sgt. Spike

May want to check your BIOS setting for the USB Legacy Device feature as well.

[apvm]

Just to share my experience, after flashing from F6 to F7 bios, no overclocking no matter how small, it will reboot back to default. Clear cmos fixed it.

[rcf22]

To NP2H and apvm,

Yeah, it seems like there is a different "fix" for each person. I had tried disabling things (but not USB legacy entirely, I still use some USB 1.0 devices) before as well as clearing CMOS without any luck, whereas others have reported other solutions. I'm not sure why this happening, the board just seems finicky for some reason. It's good to document all these though so we can help future overclockers stuck at stock!

[Basheron]

Alrite. Got everything in, I lapped the southbridge waterblock and got a nice contact with extremely small amount of thermal paste. I took my CPU waterblock and rebuilt it all under water to prevent any air pockets. I found out that the CPU overclocks easily to 3.2 (CPU355x9=3.2, memory 355x3=1066), after that it takes a lot of Vcore. I've gotten it to 3.44 but it gets unstable.

So, the temps in Speedfan, Temp1 is 37C, Temp 2 is 31C, Temp 3 is -3C, and Core0-3 are all 23C and below. Is the order NB/SB/Case/Cores? I wonder why the third temp is negative?

[crackzattic]

has anyone used the F8a beta bios yet?

[Piro Fyre]

Originally Posted by crackzattic

has anyone used the F8a beta bios yet?

I'm currently using them right now and they seem stable. Wouldn't suggest updating to them yet unless you need 45nm support.

[madroxinide]

In speedfan, what is the difference betwen Temp1 and Temp2?

In everest Temp1 is known as "System Temp" is this the northbridge? Where is this sensor located?

[Silviastud]

Originally Posted by crackzattic

has anyone used the F8a beta bios yet?

Using it and it's working fine for my 3.6ghz 24/7 clock.

[smokinbonz]

Originally Posted by rcf22

Hey Guys,

I will probably create a new thread for this, but it pertains solely to this board, so I wanted to post this here first:

There is a known issue with the P35-DS3L that several boards will reboot upon OC settings being applied in the BIOS. Namely, unlocking the FSB option causes the system to reboot right after the POST screen with all FSB and memory settings returned to default (locked FSB, auto memory timings and multiplier).

I had been held prisoner at stock speeds by this problem for several months after being able to overclock my first week with this board up to 3.2GHz. I was very pleased until this occurred, and today I did some more research on the topic. Several "solutions" have been mentioned, and here are several I have seen:

1) Set Halt on Errors to None
2) Disable serial and parallel ports
3) Clear CMOS, etc.
4) Bad PSU
5) Bad voltage/memory timing settings

However, I had tried all this without any success. BUT, my problem was solved from an unexpected source! An external USB hard drive seemed to be the problem. I'm not sure the root cause of this, but upon unplugging this, the system boots up properly with any overclock settings I've tried! Thinking back to it, I had this HDD disconnected when building my system, and the problem could've very well began when I connected it. The drive is a Western Digital 250GB MyBook if you're curious.

So, any of you DS3L'ers out there stuck at stock speeds, yank out any USB legacy devices you have connected to see if that solves your booting issue! In my situation, I was 100% the hardware was fine because 1) I had overclocked through the BIOS before, and 2) I had overclocked successfully through software even with this boot issue. I still have several USB devices connected, so perhaps hard drives are the main culprit.

I'm currently at 3.0GHz and look forward to shooting for 3.6. Look forward to updating my OC settings on the front page Sgt. Spike

Kinda Interesting, Although i dont really know if its an issue. Something similiar had happened where i lost my oc settings

Almost at the same time i turned my pc on i also turned on a usb external drive and I lost my Oc settings. I was stable and i am still stable after i reinput my settings. so yeah something wired happened to me and i think it was related to the usb drive. I attribute it as a random thing (noisy swith maybe ) Like i turned it on at the exact wrong time. That was 1 week or to agao and it hasnt happened again and i havent tried to turn them on the same way and probably wont. Just my experience