Troubleshooting
Problem
A Windows server may crash and post a 0x000000F4 as a result of the loss of the storage devices or while running heavy virtual Ethernet traffic.
Resolving The Problem
The known causes for Stop Code 0x000000F4 in the iSCSI attached Windows servers include:
|
o | DASD failures in IBM System i system target system. |
| o | High sustained volume of virtual Ethernet traffic has starved the iSCSI traffic in the target iSCSI HBA being shared by the system drive. |
Actions
The recommended actions for the listed potential causes include the following:
| o | Verify if any DASD failures have occurred in System i system. Restart the server after any identified failures are corrected. |
| o | If a high sustained volume of virtual Ethernet traffic is required, it is recommended that the virtual Ethernet traffic is routed through another pair of iSCSI HBAs (Target and Initiator). |
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp
If the server crashed posting this Stop Code and there are no indications of the listed potential failing conditions, you should contact IBM Support. Collect and provide any Microsoft dumps that may have occurred as a result of the failure for further analysis.
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
413140177
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1014983