2288H V5: Missing CPU VRD Temperature and High Fan Speed

Source symptom and events

A 2288H V5 runs its fans unusually fast while CPU VRD temperature cannot be read. The source current_event excerpt reports CPU1 VSA voltage, VRD temperature and core-voltage data acquisition failures, plus a CPU1 DDR VDDQ2 undervoltage event:

Original English CPU1 management-health read failures and DDR VDDQ2 undervoltage alarm

The listed VDDQ2 value is 0.880V, below the printed threshold 1.140V. The source narrative mentions power-loss information, but this crop does not itself prove the underlying supply fault or a specific failed component.

Inventory and other logs

Original English CPU1 XeonBronze3204 and memory inventory; CPU2 marked absent

The source says memory can still be identified. This inventory shows a present CPU1 and absent CPU2, so unavailable CPU2 sensors must not automatically be treated as an extra CPU failure.

Original English FDM5.7.0/decoderV1.3.6 header with no diagnostic entries in the displayed crop

No additional fault entry appears in the shown FDM excerpt. That limited crop is not a complete clean bill of hardware health.

Sensor values

Original English sensor table showing CPU1 VDDQ Temp28and CPU1 VRD Tempna
Original English inlet27andoutlet35sensor readings with other raw values preserved

CPU1 VDDQ temperature is 28 in the source, while CPU1 VRD temperature is na. Inlet/outlet readings are 27 and 35. Normal inlet/outlet readings do not restore a missing regulator sensor. Other raw CPU readings, including negative DTS/margin values, remain unchanged; this article does not interpret them as literal ambient temperatures.

Source explanation and recommendation

VRD refers to a voltage-regulator-down implementation/specification for motherboard processor voltage regulation. The source attributes the high-fan condition to a CPU VRD power-chip or access-path fault and recommends CPU replacement with a spare motherboard available. That is its case-specific service recommendation, not proof that the CPU is always the defective FRU. Correlate firmware, sensor-access, CPU/socket and board evidence using the vendor’s diagnostic procedure before replacing hardware.

Can't find an answer?

Upload a log for AI diagnosis, or ask the AI assistant directly in the console.