07-30-2008 04:46 AM
I'm currently having problems with the DC7800 desktop PC's. The problem is that randomly it blue screens with a memory parity error. We've deployed 50 of them, but only 4-5 come up with this error. I've updated the Bios and applied the new chipset drivers, replaced memory and changed slots. The PC have been build in Altiris with Windows XP Pro.
Any help will be appricated.
07-30-2008 07:37 AM
The most obvious thing would be memory. This is a rather rare BSOD error these days.
Are you using quality memory of the recommended specifications? If you have more than one memory module in the computers take all but one module out and see if the error still happens.
Since you have replaced the memory and moved it around it would seem that the next suspect would be the motherboard.
Hope this helps.
07-30-2008 07:41 AM
07-30-2008 07:47 AM
07-31-2008 01:30 AM
I think your on to some thing here Eric. I've just replaced a PC that was blue screening. I'm going to do some test of my own.
I will attempt to replace the CPU with a know good CPU and see if it blue screens.
will keep you updated.
Once again thanks,
07-31-2008 05:55 AM
Another possible cause of this error is a PCI device asserting SERR#. Do you have any PCI expansion cards in your dc7800s? This could also come from one of the embedded devices. To test this theory, you can try disabling PCI SERR# generation in F10 Setup, Advanced, PCI Devices.
Most of the times I have seen this error, it has been with an add-in card that was having serious problems or incorrectly using the SERR# signal.
I am an HP Employee.
07-31-2008 06:00 AM
and if you are gettting the reboot on error then:
Navigate to the Control Panel in Windows XP by left-clicking on Start, followed by Settings and then choosing Control Panel.
In the Control Panel window, open System.
Note: In Microsoft Windows XP, depending on how your operating system is setup, you may not see the System icon. To correct this, click on the link on the left-hand side of the Control Panel window that says Switch to Classic View.
In the System Properties window, click on the Advanced tab.
Locate the Startup and Recovery area and click on the Settings button.
In the Startup and Recovery window, locate and uncheck the check box next to Automatically restart.
Click OK in the Startup and Recovery window.
Click OK in the System Properties window.
From now on, when a problem causes a BSOD or another major error that halts the system, the PC will not automatically reboot. Rebooting manually will be necessary.
say thanks with HP POINTS
09-09-2008 01:27 AM
Thanks in advance
09-09-2008 02:36 AM
after ripping my hair out on this issue, I have found that the PCI Video Card was the problem for most of the blue screening. Once I change from NVS280 PCI to the NVS290 PCI Express. I haven't had the problem. we have approx 120 of these PC's, the blue screens where happeing on Dual screens and single screens. In order for the single screens to stop blue screening I updated the Bios and Chipset.
This has become a very expensive problem. I've trying to talk to our vendor to reply the problem to HP. Will keep you updated.
09-09-2008 03:06 AM
Looks like 280 is our culprit, and is conflicting with the 7800 mobo and BIOS. Finally starting to isolate the issue.
Thanks very much Jason for that reply, very very helpful.
09-09-2008 05:44 AM
I am an HP Employee.
09-09-2008 05:50 AM
09-16-2008 06:21 PM
I had the same issue on a DC7800 running a PCI Firewire card. RAM, and MB had all been replaced, and still the same error.
Changing the PCI SERR# to Disabled, and the problem is gone.
09-16-2008 07:18 PM
09-18-2008 07:35 AM
I have disabled the PCI SERR# generation in BIOS setup, and will wait to see if I have another issue.
Thanks to everyone else for posting. This problem has been frustrating.
09-18-2008 07:48 AM
It does certainly seem to have prevented any further OS halts at this stage, though. So it seems to be a resolution, albeit a frustrating one!
While I'm on the subject, can anyone inform me just what the function of SERR# enable actually does? All I can estimate is it is some form of error reporting? Can anyone expand on that? I'm still hesitant about rolling this fix out without knowing just what this configuration is. Are there any adverse affects I should know about if I leave this disabled?
Thanks in advance folks!
09-18-2008 10:22 AM
On the PCI bus, SERR#, or System Error, "is for reporting address parity errors, data parity errors on the Special Cycle command, or any other system error where the result will be catastrophic." (PCI 2.3 spec.) In other words, a serious error condition occurred and SERR# is a "party-line" signal that any card can use to signal that something bad happened. On these HP systems, by default, SERR# causes an NMI or non-maskable interrupt. This is an interrupt to the CPU that cannot be put off or ignored (masked). Depending on what OS is loaded, different NMI handlers behave differently. In the case of Windows OSes, the blue "memory parity error" message is displayed.
By disabling SERR# in F10 Setup, the SERR# from the PCI card does not cause an NMI. The consequences? For PCI video cards, I would not be concerned. You might get temporary video glitches, etc., but I wouldn't suspect anything else. If you are using a PCI storage controllers (SATA cards, RAID cards, etc.), that may not be a good idea as data corruption to or from your drives is more serious.
For the sake of PCI video cards, I think it is safe to disable this signal.
I hope this is helpful.
I am an HP Employee.
10-15-2008 07:56 PM
11-03-2008 12:45 PM
"NMI: Parity Check / Memory Parity Error System Has Halted"
After a little googling I came across this post, we're using a similar setup as some other users, two video cards, supporting four monitors. I'm disabling the SERR# as mentioned by others in the BIOS and will post again in a few weeks if the problem is resolved or not.
11-04-2008 12:15 AM
Since disabling the SERR# option in the BIOS we have had no further issues with the machine blue screening.
Looks like the Mystery is Solved
11-04-2008 07:45 AM
If I change the PCI SERR# option to disable mode, we have no NMI error but the system reboot for any reason - twice during 24 hours - very hard to reproduce the problem
More sensitive with Vista - I install XP pro and the problem is still opened
diagnostices are OK, ...
10-17-2009 03:10 AM
So good to be able to have company when a problem is driving you crazy. HP nust be aware of these problems, and instead of being proactive, we have to loose sleep and face the customer "by ourselves." I have gone name brand to avoid these types of problems and have a company stand behind me, especially since I am way out here in Trinidad and largely on my own. I have gotten all sorts of spontaneous reboots with this computer, failed RAID drives, and been unable to install e-Sata cards etc.. I am wondering if I would not have more QC just going back to building using "quality" components on my own? Thanks to all you guys for the "PCI Serr#" disable. I will see how it goes, but since I am so reliant on this computer for my business, I simply do not feel comfortable and my shopping for a "better" computer starts now! If HP pays any attention, we understand that problems arise, so please make your customers feel that you are there to back your product.
10-21-2009 12:34 PM