• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

P5N-E SLI Boot issue

Beatbox

n00b
Joined
Jun 12, 2007
Messages
29
So I built my new rig tonight, and well it wont boot.

When I first booted it the CPU fan was making some wierd noise then after 3 secs or so the PC would shut down (without beeps or anything).

I took the fan off and put it back on, but now when I boot it, the fans try to start spinning for not even a second then it shuts down... :confused:

Config:

P5N-E SLI Mobo
Intel E4300 CPU
BFG 8800 GTS GPU
Antec TruePower Trio 650W PSU
Seagate Barracuda 320GB HDD
Samsung DVD-RW
 
might be a bad board. my cousin's board did that the split second thingy. it was both his power supply and the board. cuz every other compenent tested out find on my hardware.
keep fiddling. my p5n-3 is still out on the floor. try the black mem slots so ppl suggested.
 
I believe that their used to be an issue with this board that the BIOS wouldn't allow Core2s to boot. Some people had to use an old 775 Celeron or something to get it to boot and then update the BIOS.

Pretty sure that this isn't the issue here but what is your BIOS revision, should say on the box somewhere!

On a side note mine still doesn't boot occasionally, about 1 in 50 boots so I just ignore it.

EDIT

Here is the supported CPU list for your board.

http://support.asus.com/cpusupport/cpusupport.aspx?model=P5N-E%20SLI&SLanguage=en-us

The E4300 is not on that list, may be a typo somewhere?
 
It appeared to be a problem with the 4 pins connector of my PSU that plugs into the board.

Now the PC boots, but shuts down after a couple second (generally at the screen when it shows "Core 2 Duo @ 1,86 GHZ ...".

I am able to enter bios, but it shuts down almost immediately, or soon after...

EDIT: Checked the RAM, doesn't seem to be it. I checked with a single 1g of RAM (with both) and both times it saw the 1024MB of RAM... It sees the SATA drive correctly, too...
 
Try only using 1 stick of ram in one of the yellow slots. Be sure to set the ram timing to the manufactures recommends this board is very pick about it's ram.

If that doesn't work when your computer shuts down feel around the motherboard for really hot spots if you find one then your computer is shorting out the back is probably touching some metal from the case or something.

When I first build mine I have a bad sata hard drive you might want to test yours in another computer.

If all else fails take the entire thing apart then put it back together....had that fix one of my computer builds before.
 
mine was also being a pain when first installed was doing something similar and then i found it was shorting out against the case i took it out of case and it booted fine when just on a anti static bag i just insulated a couple of points on the board near the cpu on the rear of the board and no more problem some of the capacitors seems to stick a long way out from the back of my board
 
These boards are very picky. I built a system for my friend replacing his burnt out P5AD2 Premium. We used all the same components just on the new board, but his Crucial Ballistix didn't work with it. He had two 512MB DDR2-533 chips and a 1GB DDR2-667 chip. No matter what combo, we tried, the 512's just couldn't be used, even by themselves.
 
I had mine running with a cheapo 512 stick of Wintec Ampo ram until my Firestix arrived. Never gave me any problems for the fews days that I had it running like that.
 
Another thing to try would be to run the ram at 533 or 667mhz and make sure to manually set the timing of the ram. My board would detect the trc wrong and set it to some really high value, once it was set to the spd value shown in cpuz then all was stable.
 
Back
Top