A friend of mine asked me to build a pc for him. It has these specs: MSI P35 mobo 2 GB G.E.I.L. DDR2-800 Intel E4400 Asus Geforce 7200 Procase CRS2051-12BP 500W ATX2 PSU Samsung 160 GB SATA drive LG Dvd-RW Everything works fine, but when I press the on button, the system turns on for a few seconds. Then it turns off, and after 2 seconds it turns itself on and then works without any problems. Does anyone know what the problem is?
I take it you've checked the processor and heatsink are seated correctly (thermal paste applied, etc)? It too, could be something not configured correctly in the BIOS - for example, is Spread Spectrum 'disabled' ? I'm told it should always be disabled for better stability and performance. Other than that, I hope others can offer more constructive suggestions. Good luck!
Yes it is correctly seated. The CPU temperature stays below 20 degrees Celcius. The bios of this mobo doesn't have this feature. Thanks It's not annoying, but I want to know if this is caused by me or if it's a normal thing with the mobo.
This exact same thing happened to me. It's most likely the power cord not making contact with the power socket.
I would check all your connections from the Button to the mother board, And check the power supply.. Is all these things NEW? Also check the USB wires from the case to the Motherboard, Look for any pinch wires...This happen to me awhile back..It was a pinched wire..
The power cable is correctly connected. Yes everything is new. The power supply doesn't have this problem when used in a different pc. I checked every cable, and they are correctly connected. I've noticed that it always happens at the same time, and after the 'initial' reboot it works nice without any problems at all.
I would start pulling everything unneeded to run at startup, You say that it starts up and does this at the same place every time? Now this could be a hard drive problem or OS problem.. How far does it load before it will do this?
I have the exact same problem, Sorry to create new thread....long days... I have unplugged all non-essentials, and the system does exactly the same. It even does it in another P35 chipset based motherboard (Gigabyte P35-DS3R), so this common reoccurence must be realted to the chipset? I have tested the system in an older motherboard based (Asrock 4core dual vsta) and the problem does not occur. I even put my cpu in my friend's 965 asus p5w mobo, and the problem did not occur. I have ruled out the CPU, PSU, cooling, and Motherboard (excluding chipset), RAM. ( i used an old ddr 2 512mb module for testing) Maybe this is just a test power up phase? Try leaving your computer powered on for a minute, turn it off by the power button by holding it down for a few seconds. Leave the psu switched on, plugged into the wall, and leave for about a minute. Try powering on again, and i can bet it doesnt happen again. However, if you unplug the power cable from the wall socket, it will happen again..... It is a really bizzare thing, my computer is 100% stable in prime 95, orthos, and intel TAT for 4 hours, including a looped 3dmark 05 bench. I just cant get my head around this, it must be a BIOS, and /or an Intel p35 problem in the design, or simply a boot up power check once the comptuer has been disconnected from permanent power supply for longer than 5 minutes maybe. Tough nut to crack this, and i hope this helps in any way shape/form
I have just updated the BIOS to version 1.4 on the MSI P35 NEO 2. No change. I have checked all cables, remounted the motherboard and cpu heatsink to be safe, yet the same thing happens every time. I suppose i'll have to live with it lol. It doesnt affect performance or stability, must be a chipset thing with the e4xxx series of cpu's.
After much frustration, i found out that this an inherent behaviour for the P35chipset. Double Boot Issue Fixed - for IP35 and IP35-E - PC Perspective Forums It is known as a ''double boot'', and is a bug on the intel P35 chipset. Its nothing us system builders have done wrong, and there is no electrical fault. I suppose we will have to wait for a BIOS fix in the future.....
