Sun Blade X6270 - BSOD while trying to load MDT 2010 with 10 Gbe network drivers on Windows (2008 R2)

Asset ID:	1-72-1386892.1
Update Date:	2016-10-24
Keywords:

Solution Type Problem Resolution Sure

Solution 1386892.1 : Sun Blade X6270 - BSOD while trying to load MDT 2010 with 10 Gbe network drivers on Windows (2008 R2)

Applies to:

Sun Blade X6270 M2 Server Module - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

BSOD while trying to load MDT 2010 with 10 Gbe network drivers on Windows (2008 R2).
Customer needs to load MDT 2010.When the WinPE 3.0 image loads they get a BSOD error message

0x00000124

If they remove the 10 Gbe network drivers from the image they don't get a BSOD .

Occasionally the WinPE OS will boot correctly, maybe 1 in every 6 attempts.

Once the OS has been loaded we don't seem to have any issues.

PC check and VTS were run on the Blade and the issue was not noticed.

If you attemp to build the blade server via MDT 2010 and you received the Windows "0x00000124" Stop error message.
This occurs when the MDT (Microsoft Deployment Toolkit) attempts to load the 10g Ethernet drivers.

The HW information of NEM is as below

FRU Device Description : RFEM0 (LUN 0, ID 128)
Board Product : SUN DUAL 10GBE PCIE 2.0 FEM
Board Serial : 0201XR
Board Part Number : 375-3648-02
Board Extra : 50
Board Extra : x4871a-z/4871a-z

FRU Device Description : NEM0 (LUN 0, ID 241)
Board Product : SUN BLADE 6000 ETHERNET SWITCHED NEM 24P 10GE
Board Serial : 1005LCB-1039RW001M
Board Part Number : 541-3770-02
Board Extra : SAS 5.3.2.0

FRU Device Description : NEM1 (LUN 0, ID 242)
Board Product : SUN BLADE 6000 ETHERNET SWITCHED NEM 24P 10GE
Board Serial : 1005LCB-1039RW0020
Board Part Number : 541-3770-02
Board Extra : SAS 5.3.2.0

This affects WinPE 3.0/3.1 which currently uses Intel drivers (v16.6)

Cause

The NIC driver is incorrect and is causing the issue.
Since BSOD is not seen after the driver is removed, it looks like a NIC driver issue.

Solution

This issue is resolved by using the latest driver from the Intel

Intel has updated NIC driver to V16.7, which includes specific driver for WinPE.

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18725&ProdId=3189&lang=eng

Download package and unzip. Check in sub folder

PROXGB\Winx64\NDIS62\WinPE

and read the Readme file. The issue should not persist after using the above driver.

Attachments

This solution has no attachment