P8p67 no post AFTER changing boot Priorety?!?! Worked fine for months

[ade42]

Gday

I built my system a few months ago, all was good, everything worked fine!
Well today i was in bios changing the boot sequence as I never really set that up and was lazy and it was always not booting without me p[ressing F8 on each boot. Ok so I changed that and saved/boot and nothing, No Post beep, now on this board you have to wait some 10-40 seconds to hear the post beep, But now no beep and no signal out of GFX what so ever.

Ok so what have I done to fix this?

Moved the Ram into each slot and tried every configuratuon.

Taken all cards out (including GFX) and tried Ram 'swapping' on a completly empty system

Disconnected all drives/media while doing the above

Tried 3 alt power supplies.

Took out the CPU and put it back in (why not)

disconnected Keyboard/mouse and all usb devices.

Turned the system on while pressing the 'MEMOK' swicth.

Tried the various MB switches in all positions


Ok so in my thinking ive not left anything out...

So what the hell could it be?


What I have if this helps (prob not)

Corsair Vengeance CMZ16GX3M4A1600C9 16G (4x4GB) DDR3
Asus GTX 570 PCI-E 2.0 1280MB DDR5 2x Dual-Link DVI 1x mini HDMI Fan
Intel Core i7 2600K Processor LGA1155 3.4GHz CPU
Asus P8P67V3 P67 4DDR3 D12PH 2400OC RAID GLAN PCIE16 2FW SA3 ATX STEP3
Antec ATX TruePower 750W

Thats all you really need to know, as its not the HDD or anything else


If the MB is dead, what alt motherboard would people suggest for my newly ophend 'gear'?
May as well get a new one as it might take some months to get it looked at/replaced, as I am using this system to try to find a job, I can;t really have it down for a couple of months.....


Regards
Ade

 

[scout_03]

if you have to press f8 at each boot means windows need repair put back cd drive in first boot and repair windows,then set the c:hdd at first after you made repair to boot from it

 

[ade42]

Eh?

No it dosent!

F8 is how you can quickly change boot priorety Pre/post bios, say you are booting from a USB device you press F8 while booting and then you can select the drive you wish to boot from that one time only.

I only have to press F8 as the boot device in bios is set for a optical drive and for some reason would not boot from the SSD, so I did the F8 thing each boot, diddn't bother me much..

You see if you go back and read my prob, I have nothing, no post, nothing, putting a windows disc for a repair is usuless, as I cannot boot.


I do klnow a thing or two about systems, being a IT man for the last 25+ years! Just this particular MB and its issue is very very strange

 

[scout_03]

well you will have to wait for someone that use ssd for more help

 

[jsc]

Work systematically through our standard checklist and troubleshooting thread:
http://www.tomshardware.com/forum/261145-31-read-posting-boot-problems
I mean work through, not just read over it. We spent a lot of time on this. It should find most of the problems.

If not, continue.
The following is an expansion of my troubleshooting tips in the breadboarding link in the "Cannot boot" thread.

I have tested the following beep patterns on Gigabyte, eVGA, and ECS motherboards. Other BIOS' may be different, but they all use a single short beep for a successful POST.

Breadboard - that will help isolate any kind of case problem you might have.
http://www.tomshardware.com/forum/262730-31-breadboarding
If the system POST's here, you have a case shorting problem.

Breadboard with just motherboard, CPU & HSF, case speaker, and PSU.

Make sure you plug the CPU power cable in. The system will not boot without it.

I always breadboard a new build. It takes only a few minutes, and you know you are putting good parts in the case once you are finished.

You can turn on the PC by momentarily shorting the two pins that the case power switch goes to. You should hear a series of long, single beeps indicating memory problems. Silence indicates a problem with (in most likely order) the PSU, motherboard, or CPU. Remember, at this time, you do not have a graphics card installed so the load on your PSU will be reduced.

If no beeps:

Check for line power at the PSU input. Extension cords, power strips, and power cords do fail.

If you have power and no beeps, suspect components in likely order are PSU, motherboard, and CPU.

Running fans and drives and motherboard LED's do not necessarily indicate a good PSU. In the absence of a single short beep, they also do not indicate that the system is booting.

At this point, you can sort of check the PSU. Try to borrow a known good PSU of around 550 - 600 watts. That will power just about any system with a single GPU. If you cannot do that, use a DMM to measure the voltages. Measure between the colored wires and either chassis ground or the black wires. Yellow wires should be 12 volts. Red wires: +5 volts, orange wires: +3.3 volts, blue wire : -12 volts, violet wire: 5 volts always on. Tolerances are +/- 5% except for the -12 volts which is +/- 10%.

The green wire will alway have 5 volts on it. When you press the power switch, the voltage should drop to 0 volts.

The gray wire is really important. It should go from 0 to +5 volts when you turn the PSU on with the case switch. CPU needs this signal to boot.

You can turn on the PSU by completely disconnecting the PSU and using a paperclip or jumper wire to short the green wire to one of the neighboring black wires.
http://www.youtube.com/watch?v=5FWXgQSokF4&feature=youtube_gdata

A way that might be easier is to use the main power plug. Working from the back of the plug where the wires come out, use a bare paperclip to short between the green wire and one of the neighboring black wires. That will do the same thing with an installed PSU. It is also an easy way to bypass a questionable case power switch.

This checks the PSU under no load conditions, so it is not completely reliable. But if it can not pass this, it is dead. Then repeat the checks with the PSU plugged into the computer to put a load on the PSU.

If the system beeps:
If it looks like the PSU is good, install a memory stick. Boot. Beep pattern should change to one long and several short beeps indicating a missing graphics card. If you get this with motherboard graphics, your motherboard is bad.

Silence, long single beeps, or series of short beeps indicate a problem with the memory. If you get short beeps verify that the memory is in the appropriate motherboard slots.

Insert the video card and connect any necessary PCIe power connectors. Boot. At this point, the system should POST successfully (a single short beep). Notice that you do not need keyboard, mouse, monitor, or drives to successfully POST.
At this point, if the system doesn't work, it's either the video card or an inadequate PSU. Or rarely - the motherboard's PCIe interface.

Now start connecting the rest of the devices starting with the monitor, then keyboard and mouse, then the rest of the devices, testing after each step. It's possible that you can pass the POST with a defective video card. The POST routines can only check the video interface. It cannot check the internal parts of the video card. In this case, you will POST successfully (single short beep). But your monitor will display a "missing signal" message.

In that case, the first thing you do is to test the monitor and data cable with another system to make sure it works. If the monitor works, the video card is bad. If you have motherboard graphics, again, the motherboard is bad.

 

[ade42]

Yep gone over all those steps multipe times, and just did a set of em 'breadboard'. Still no joy, one new thing I didd't not before is that I think that this Mb has some Beeps if a GFX is not installed (it has no interghrated one) well, there are no beeps if the GFX card is in or out, Yet if there are No ram sticks in it beeps its merry head off.

This MB also has a habit of 'double boot' which means that you turn on the system then the fans all come up to speed and then the system shuts off (no signal onscren this whole time) then powers up again by it self and THEN goes into post etc. Well that 'double boot' thing stopped when the MB stopped booting.