GA 965P - DS4

Associate
Joined
1 Aug 2004
Posts
1,306
Location
South Cheshire
I've just upgraded to a GA 965P - DS4 board and Conroe 6400. I've also got 480W PSU and 1GB of Ram. I'm experiencing weird boot up issues whereby the PC turns itself on and off multiple times before actually booting up successfully.

I've changed the PSU, graphics card and Ram to no avail. Does anyone have any suggestions from here?

Are there well known issues with this configuation?


Thanks for all suggestions

Chris
 
I think the same is happening to me - DS4 + E6400 + 2GB Geil Ultra PC6400 + Enermax 535W. There is one difference though - my setup would keep doing this pre-boot loop without eventually booting up succesfully. Nothing helped - I removed the battery, cleared CMOS, I also tested the board with all components incl PSU from my other setup (completely identical, but working flawlessly for a couple of months). Always the same - turn on, all fans spin up for about 15sec, then it shut itself down, turns on, fans spin...again and again. Any idea anybody?
 
Sounds like an RMA, nothing like that here on a DS4, i know when you change your memory settings, and put that intel thing on in the BIOS, when you save the settings it shuts down completely then boots back up, thats normal, but not booting all the time is deffo not normal, mine boots perfectly fine. :confused:
 
Last edited:
its a common prob with a lot of ds4's, the first one i had did it so i got a replacement. The one i have now is fine though and only doesi t when i run 475fsb x8 and damn annoying it is to! will boot n run fine at those settings until i switch of the pc, then when i switch on its power on, power off etc! doh!
 
I have this problem too. I've RMA'd the motherboard twice and twice it's been returned with no fault found. What should I do?
 
So your DS4 woudln't post/boot up and you can't use it, but it's not faulty? What are you supposed to do with it then? Have you been told which components it has been tested with, so you know what the safe working configuration is?
 
Yep that's right.

I've narrowed it down in the end.

I built it out of the case and installed:
mobo + ram + cpu + graphics card + heatsink fan (but not actually on the cpu, just connected)
This will boot, but is obviously useless as the cpu temp quickly rises.

Then I rest the heatsink on the CPU and the boot fails.

Take it off and it works.

It seems that any pressure on top of the cpu makes it fail to boot for some reason. I returned the CPU, mobo and heatsink. They say they tested it together and got no error. Yet I have seen the same behaviour before and after I've RMA'd it.

Not sure what to do now. It's costing a fortune in RMA and postage costs. Might just bite the bullet and buy a second mobo as that's the likely cause I feel. :(
 
This (not PhilipM's which is just silly) is a common problem with DS4s and is due to the default RAM voltage being too low for your RAM. When your system does boot, go into the BIOS and up the RAM voltage from 1.8 to 2.1. Also make sure you're on the latest BIOS as this was supposed to be fixed after F4 (I think).

Jonathan
 
Then I rest the heatsink on the CPU and the boot fails.

Take it off and it works.

That sounds like you don't have the CPU sat exactly right on its pins... Unlike previous chips where there were pins that either fitted or didn't, the conroes will start up, but not boot, when they are fitted very slightly out of line..
 
I've tried reseating the processor at least 12 times. Is there a trick to it? I would have thought I'd have got it right by now, after all, there are cut outs and an arrow so that it *should* only line up correctly!

*edit* turned out to be a faulty PSU!
 
Last edited:
mine does this when I've got the ram at the correct voltages.
just don't turn it off?
also, why arn't you running Folding@home on it?
 
Does that to me but its usually only after a crash of some sort where i've needed to reset the computer so I'm gonna presume its some kind of inbuilt protection thats somewhat buggered. If it starts that just turn off power at the mains for a few seconds, always solves it here.. If its still doing after that I'd guess theres a hardware fault or compatibility issue..
 
Back
Top Bottom