While it is always
possible that an 'unsupported' CPU will fail to start up, in practice, the majority of the cases I've actually
see have involved 'hexacores', both from AMD and Intel. I'm kind of 'leaning away' from that as the source of your problem, as:
18h is the step where the BIOS 'queries' the processor ID string, and initializes its caches/cache management...
1Dh initializes the PMI for the CPU...
26h
looks like it's the initialization for the on-board LPCIO (
low
pin
count
input/
output) chip (in your case, an iTC 8720 - no 'newcomer'!) - the guy that 'does' the fan sensing/fan control, the floppy interface, the temp sensors, PS2 kbd/rodent...
27h is intializing the BIOS' keyboard buffer - where it 'puts' keystokes as they arrive, via its interrupt service routine...
I don'y
really know what's going on here (I've said it before {in fact, just yesterday
![[:isamuelson:8] [:isamuelson:8]]()
!}, and I'm sure I'll say it again - I'd
kill for source code to a modern BIOS!), but my overall 'feeling' is that these are not processor related indications...
What I'd start with is a 'strip-down'; most people pretty much just 'shovel in'
all their parts at once, so finding a single problem becomes
exceedingly complex... You always want to start with this:
![]()
...and
only 'the basics' installed - the vidcard, one DIMM, the power plugs - once you
know that's working, then, into the case - boot up again to see that was OK, then add parts,
one at a time to be able to detect
individual problems...
Mind you, there are two ways to do this: you can do it either
in or
out of the case. The advantages and drawbacks:
in the case is easier and faster,
but will not find case-related problems, like shorts from extra, mispositioned standoffs, or ground plane problems;
out of the case takes longer, and you may run into 'reach' problems - power supply cables and front panel power switch headers may not be long enough; for the power supply, it's usually just a matter of removing four screws to temorarily relocate it; for the power switch, you can just do this (
very carefully):
![]()
You only need to short the pins momentarily - that's all the power switch does...
Out of the case also affords you an easy opportunity to 'flip' the board to check your heatsink/fan attachment setup, to be sure all the pins are fully seated, locked, and not cracked... If you do the out of the case, you need to lay the board on a non-conductive surface: the box the MOBO came in is ideal, someone recently suggested a phone book which is excellent; but - the foam pad it came with, and the bag it was in
are not - being 'antistat', they are somewhat conductive, and may induce problems...
Another item worth mention at this point is case speakers: if you haven't got one - get one!
http://www.cwc-group.com/casp.html
A lot of people operate under the misaprehension that the 'diagnostic beeps' should come through the speakers attached to their sound-card/chip - not so! Your three hundred dollar Altec-Lansings won't do you any good here - you have to have a case speaker attached to the front panel header, and, often by this point, it's the
only diagnostic info you'll have to go on...
The standard 'strip-down':
Power down at PSU switch
remove
everything except
CPU and heatsink/fan (check carefully that the fan retaining pins are fully inserted, completely locked, and not cracked)
one stick of RAM, in slot designated for 'single slot' use
video card and monitor connector (if more than one PCIe slot, again, in slot closest to CPU)
all power plugs - 20+4 or 24, 2x2 or 2x4 ATX power, graphics card power
case speaker and power switch connectors
keyboard (don't need a mouse at this point)
place jumper on RST_CMOS pins
remove jumper from RST_CMOS pins
power up at PSU switch
power up by depressing case power switch (or shorting the 'power' pins...)
If you get video, enter BIOS with <DEL> (may need a <TAB> to get to POST screen, if 'splash' screen is enabled)
Select and execute "Load Optimized Defaults" - save and exit, reboot
power down
reinsert other components, one at a time, testing each time after addition...