Event Id | 1003 |
Source | IPMIDRV |
Description | The IPMI device driver attempted to communicate with the IPMI BMC device during device creation. However the communication failed due to a timeout. Either the configured timeouts are too small and the IPMI BMC device responses take longer than the timeouts, or the BMC has a technical fault. You can increase the timeouts associated with the IPMI device driver or seek assistance from the BMC device manufacturer. |
Event Information | According to Microsoft : Cause : This event is logged when the IPMI device driver attempted to communicate with the IPMI BMC device during device creation. Resolution : Set IPMI parameters Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data. Modify the value of entries in the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\HardwareManagement\IPMI Verify and correct the value of these five entries: BusyWaitTimeoutPeriod, BusyWaitPeriod, IpmbWaitTimeoutPeriod, CommandWaitTimeoutPeriod , and SlaveAddressDetectionMethod . Contact your hardware vendor and ask them to recommend appropriate values. To edit these registry values:
To test that the IPMI driver is functioning correctly, check that it loaded successfully and check that the RequestResponseEx method of the Microsoft_IPMI WMI class returns a CompletionCode of 0 (Command completed normally.) To check that the driver loaded successfully:
|
Reference Links | Event ID 1003 from Source IPMIDRV |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.