IP35-Pro Intermittant Postcode Error 87

[akaqueequeg]

I had this rig for about 18 months now problem free until this morning when I rebooted after upgrading PCtools sypdoctor to version 7.

On rebooting the system hung with a blank screen at the stage where it displays the harddrives installed.

After powering down and restarting with the same fault once more my rig successfully booted to windows. I missed the post code on the first occasion as when took of the case panel to check the LED it booted sucessfully.

I used this opportunity to check some of the functinality and run Prime 95 with core temp to check the cpu was and memory were functioning correctly. I run prime for 1 hour with no problems, core temps were approximately 65C under full load.

All the fans in the case were woking and everything appeared to by seated correctly.

I rebooted again and entered the Bios were I change boot priority to floppy and put floopy seak on. I exited and run a microsoft mem diagnositic. No problems five cycles.

So far there appears to be no problem with the memory or CPU. On all occasions when I have powered down I get the correct 9.9 post which combined with a problem free overclock suggest that it is unlikely the powersupply.

After mem diagnostic, I reboot this time failing at the same point with a 75 error message which is a failure to dectect IDE device. So now the floppy seek was failing. I cleared the CMOS and rentered the Bios and loaded my normal settings.

The on the next two ocassions the fault occured I recorded the post message of 87 which according the the manual is

"NET PC. Build SYSID structure"

(although 8.7 is a CPU low voltage, I will need to double check the post code I will edit my post later with the result. But the powersupply connections are seated properly and there was no issues in prime which usally really obvious with powersupply issues, plus I also got the 75 error which would be explained by low Vcore)

Edit: Rebooted and had the same error three times, definiately 87 not 8.7.

Help on this is appreciated to identify the error, most of my PC should still be under warranty but I will need to know the cause first to now who to contact

Thank you.

[Lvcoyote]

Well, I disagree..... It's most definitely the PSU as far as I see it. What exact PSU is it??

[BUFF]

tried without your overclock?

[akaqueequeg]

Well, I disagree..... It's most definitely the PSU as far as I see it. What exact PSU is it??

Its a corsairs TX650 watt. Can you explain why you think it may be the PSU?

I had a previous PSU problem and the CPU was never stable under load because presumably the railings where fluctuating too much. Plus the error messages were erratic

tried without your overclock?

No, but I will do and report back.

Still I doubt this would explain it because it has been overclocked without this fault for 18 months. All the voltages are at there stock settings too so the parts shouldn't be under any stress from over-voltage. Also I originally validated the overclock on 12 hours of prime95 with 4 cores running and performed multiple loops of the crysis benchmarking tool and 3d mark with no problems.

Plus its stable in prime95 for at least 1 hour now.


Another thing I have noticed is that the boot up sequence does not seem to be displaying the same data each time. Some times it skips the memory display and it is now doesn't display the number of Cores the CPU is using just displays some details about the EMT64 instruction.

When I run CPU Z all the memory and CPU is detected correctly as is when I enter the Bios. Also I have experienced no problems once the computer reaches windows I can still run games and apps o.k.