Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have a Dell PowerEdge 2950 running Windows Server 2003 R2, Enterprise x64 with Service Pack 2 installed.

Recently, we've been experiencing multiple STOP errors occurring with that server. Fortunately it is in place as a fail over machine so it is not currently affecting our production environment. The error that shows up in the server log is this:

Event Type: Error
Event Source:   System Error
Event Category: (102)
Event ID:   1003
Description:
Error code 000000000000009c, parameter1 0000000000000004, 
parameter2 fffffadf90881240, parameter3 00000000f2000000, 
parameter4 0000000000060151.

So far the best I've been able to track down is that the 9C error is some sort of generic hardware problem. The other parameters have been no use in narrowing this one down.

There have been no hardware changes since the machine was brought into service last year. It has a twin box that is identical (the primary that this one acts as a fail over for) that is not experiencing the behavior. The last software change was on 4/16/2009 when several security updates were applied. The blue screens started happening on 5/9/2009.

Are there any diagnostics that may help with tis problem?

share|improve this question

3 Answers 3

up vote 2 down vote accepted

See Kazna3's answer at http://www.d-a-l.com/archive/index.php/t-49205.html He/she writes:

But first, the BSOD is pretty old. The 0x9C BUGCHECK is hardware related, well known. The rest of it concerns the processor, it's a processor fault or just the processor driver. :(

Have a look here for the explanation: 0x9C: MACHINE_CHECK_EXCEPTION (http://msdn2.microsoft.com/en-us/library/ms795775.aspx)

Microsoft used to advise this when we got it with the P4s:

Step 1) Update your BIOS (hardware patches called microcode updates ride here, if your processor or AMLI has an errata, it would be fixed here).

Step 2) Call hardware vendor immediately as this is a strict hardware error.

Step 3) Replace hardware, starting with CPU.

In other words, your hardware is likely borked. Possibly a brown-out, or high heat. Just because a component is solid-state doesn't mean it can't fail. Eg: RAM fails all the time - there's a reason it ships in static-resistant bags.

share|improve this answer
    
Thanks for the tip. After step 2, we where given the download to an ISO with an installer / verifier for all the latest drivers by the manufacturer (Dell). After updating all drivers the problem seems to have gone the way of the dodo. –  palehorse May 28 '09 at 12:10

Do you have physical access to the machine? Does the status LCD give an error code when this happens, or does it seem oblivious?

If you have OpenManage installed, you're a leg-up already. Check the OpenManage logs to see if it has logged any hardware errors. OpenManage alsoincludes a pretty full-featured diagnostic suite. Check out http://www.dell.com/downloads/global/power/ps1q06-20050259-Thathireddy.pdf for an explanation on using it. Dell's support usually has you run a couple CLI diagnostic tests, so it may be best to get in contact with them.

As a generic step (and to preclude Support asking you to do this), update your BIOS and Embedded Server Management BMC firmware.

Replace your CPU if you have a spare.

Also, it may sound strange but if you have a DRAC installed, remove it. I had a 2850 that was giving CPU error codes (E07F0), freezing randomly, and occasionally failing to boot. Swapping out the DRAC corrected it and it's been in problem free ever since.

If none of this works, it's time to give Dell a call. This is 100% below the OS layer.

share|improve this answer
    
We do have OpenManage. Apparently the diagnostic utilites are no longer available through Serer Administrator. We'll take a look at using them, thanks. –  palehorse May 11 '09 at 18:34

See Microsoft KB 939315 - storport driver can cause this.....did you see the error on reboot or shutdown or simply while running?

share|improve this answer
    
That error is inserted into the system log after the blue screen (BSOD) crash happens. –  palehorse Oct 1 '09 at 20:24

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.