IP35 Pro with error 8.7 only when using Q9550

[vwdude17]

I've got the 8.7 (check CPU voltage) error after moving to a C2Q Q9550. My C2D E6750 works perfect on this board (ABIT IP35 Pro with Beta BIOS 18), but this new C2Q Q9550 gives me the 8.7 error. I already replaced the PSU, even had the C2Q Q9550 changed out for a new one. Nothing. All power leads (24, 4x, 4x, and 8x) are plugged in using a 650W Corsair PSU. I've even tried running it with just 1 stick of RAM, no hard drives, and even no video card. Nothing! I am going crazy here! Please help! Cant figure this one out. Any clues?

[BUFF]

stepping?
& this is the beta from the EO stepping BIOS thread?

Pretty sure that it's not a PSU problem, it's not recognising the CPU.

[vwdude17]

Yes, BIOS Beta in use now is m629b_18.bin

Any specific switches I should be using when flashing this BIOS version? Anything I could verify to make sure E0 stepping is enabled?

Thanks for the help.

[jclafi]

In the CPU BOX there is a label with the Stepping Model information.

Good Luck

[vwdude17]

In the CPU BOX there is a label with the Stepping Model information.

Good Luck

I am aware of that. Just asking if there is anyhing I can do while flashing the BIOS maybe that would help me out.

[Lvcoyote]

I am aware of that. Just asking if there is anyhing I can do while flashing the BIOS maybe that would help me out.

The short answer is no...... time for a new Motherboard from a company that is still in business. Using different BIOS switches when flashing has no effect on CPU compatibility.

[vwdude17]

Ok... last attempt...
With my E6750 in place I flashed beta BIOS 18 again, did a "hard reset" by removing cmos battery, flipping the CMOS switch, and moving the CMOS jumper for 30 minutes with no power plugged into the PSU. After 30 minutes, put it all back, booted into BIOS, loaded optimized defaults, rebooted ok, then shut down and installed the Q9550.... got error 8.7 again. @#!#$*&!!!!

Now off to figure out how to RMA this board. Any clues there?

Lvcoyote... I think you are right. If I can't RMA this one or it's too painful, I am already looking at one of the Gigabyte P45 boards to get me out of this mess.

[vwdude17]

Looks like no more RMA's... Moving on to another board... What a shame.

Want to buy this IP35 from me? make me an offer...

[chuck4456]

Ok... last attempt...
With my E6750 in place I flashed beta BIOS 18 again, did a "hard reset" by removing cmos battery, flipping the CMOS switch, and moving the CMOS jumper for 30 minutes with no power plugged into the PSU. After 30 minutes, put it all back, booted into BIOS, loaded optimized defaults, rebooted ok, then shut down and installed the Q9550.... got error 8.7 again. @#!#$*&!!!!

Now off to figure out how to RMA this board. Any clues there?

Lvcoyote... I think you are right. If I can't RMA this one or it's too painful, I am already looking at one of the Gigabyte P45 boards to get me out of this mess.

I see that you were running an E6750.
How old is your board?
Does the BIOS chip have a silver label or is it a chip with no label with the numbers stamped upon the surface.
Taking some notes.
Report back.

[chuck4456]

The short answer is no...... time for a new Motherboard from a company that is still in business. Using different BIOS switches when flashing has no effect on CPU compatibility.

He seems to making a very good point, all things considered.

[Terbinator]

Just buy a new motherboard from a company thats still going.

[Bricketh]

Wish I had seen this thread before ordering my q9550, as I have the same board, same E0 stepping CPU, and same issue. I tried everything except for a new PSU, but that works well with my old E6600 in it, and it should have enough power (700W) for this rig. I am going to test the chip in my friend's Asus p35 board (p5q, I think it is) tomorrow. If it works, I guess I need a new board...

[imkdd]

I had the same problem when I upgraded from an E6600 to the Q9550. I tried all the things suggested by others here, but found once, completely by accident, that if I let it restart itself a few times, it eventually got past the error and started.

Once in, I was able to set the voltage properly, but virtually every time I booted up, it would give me the two-tone 87 error for a few moments, then continue booting normally. I learned to live with it.

Just a few days ago, my Soundblaster card died and I had to replace it. Ever since then, no errors on startup!

The difference? The old card was PCI and the new one is PCI-E x1. I no longer have any straight PCI cards. Can't say for sure, but I'm guessing the PCI card affected the MB voltage enough to cause the error.

Try pulling any PCI (not PCI-E) cards and see what happens.

Good Luck!

imkdd

[Bricketh]

Thanks imkdd. I do not have any PCI cards, just my PCI-E video card. I did try adding addtional power via the molex connector by the PCI-E slots, but no dice. Also removed all but one stick of RAM, but again, to no avail. The processor works in my friend's Asus P35 mobo, so I ordered a new board for myself (Asus P5Q SE Plus, which is the P45 chipset). I was going to order the same board he had, but couldn't find it anywhere but refurbs on eBay, and I have struggled enough at this point to mess with that...

Edit: Almost forgot to mention... I did let it run for a while with that post code, and it would simply recycle itself after a few seconds each time at best. At one point, I let it just sit for about 5 minutes while I stared blankly at it, trying to understand why it wouldn't work. I probably rebooted the thing more in that one night of trying to make the new CPU work than I have in the almost 3 years since I built the PC!

[Bricketh]

Wanted to provide a quick update. I swapped out my board, and all is well. The old board will go to my brother for his rebuild effort. Thanks all!