ProLiant Servers (ML,DL,SL)
Showing results for 
Search instead for 
Did you mean: 

DL380 BSOD due to CPU microcode revision mismatch??

Chris Velasquez

DL380 BSOD due to CPU microcode revision mismatch??

I have a customer that is experiencing BSOD on a DL380G3 running Windows 2003. They've logged a call with Microsoft and received the following;

The problem was caused by an overwrite of a 32 byte region of the page table. This happens to be the hardware cache granularity for the x86 processor. It looks like it could either have been caused by a faulty driver or a hardware error.

In any event case, it looks like you have a microcode revision mismatch on the two processors. I recommend that you get the latest BIOS flash installed on this machine.

0: kd> !cpuinfo
CP F/M/S Manufacturer MHz PRCB Signature MSR 8B Signature Features
TargetInfo::ReadMsr is not available in the current debug session
0 6,11,1 GenuineIntel 1396 0000001c00000000 00003fff
1 6,11,4 GenuineIntel 1396 0000000100000000 00003fff

The 1C and 10 aren't the same - that's bad, and will need to be fixed via a BIOS update.

Please see:
842465 Stop 7F, 0x00000008 (double-fault) error occurs because of a single-bit error.

Has anyone seen this and does a "System Bios" upgrade effect the CPU Microcode revision??

Chris Velasquez
Oleg Koroz
Honored Contributor

Re: DL380 BSOD due to CPU microcode revision mismatch??

.. ProLiant DL380 G3 ROM P29 (09/15/2004)
Updated to integrate the latest Intel processor support code into ....