ES Xeon Discussion
- Thread starter britinpdx
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Hey guys, I have purchased two Xeon 6732P ES CPUs through a friend. I don’t know the QDF yet, but I was told the stepping is B0. Can anyone explain the stepping rule of Granite Rapids? I heard A stepping has problems related to frequency. B2 seems to be QS steppings and H0 seems to be stepping of the retail version? So I guess B0 is just fine?
cpuid a06d0 stepping = A0/A2 (not issues just low turbo clocks)
cpuid a06d1 stepping = B0/B2 QS / production XCC E2A
cpuid a06d1 stepping = H0 QS / production MCC E2B
Last edited:
Thank you everyone for answering my questions about fans pulsing and issues with installing Windows 11. It seems like everything that could go wrong, went wrong. This time my power supply failed. Luckily, it was before the RMA period expiration date. Anyways, I borrowed PSU from my other computer, and adjusted the fan speed. With higher RPM, the fan pulsing is much less frequent. The pulsing was every 5 seconds. Now, it is like every 3 minutes. So, that's better. Thank you for letting me know about TPM2.0 chip. I didn't know that there is such a chip. I ordered a GIGABYTE CTM010, but it is taking a long time.
In the end, I was enable to run Ubergarm Kimi-K2-0905 Smol IQ4 at 16 tokens/sec. That is a speed I never imagined possible, and I am very happy with the speed. Now the only issue is the RAM temperature. When I run LLMs for more than 2 minutes, the DIMM temperature reaches 89 degrees Celsius. I'm worried about frying my RAM. I want to place fans blowing air directly at my RAM, but there is no place to mount the fans. I wonder if I need to tape 40mm fans to my RAM.
Last edited:
it is the RCD and with DDR5 the voltage regulators were placed on the RDIMM (+12 -> 1.1V)
I installed Gigabyte CTM010 TPM 2.0 card on MS74-HB1, but Windows 11 Pro installation is interrupted again. I get "Recovery" screen during the installation, and the message is "It looks like Windows didn't load correctly". The options are "See advanced repair options" and "Restart my PC". Do I need change anything in BIOS after inserting CTM010?
Last edited:
UEFI only, secure boot. what w11 installation media do yo use ?
try with out PCIe GPU if any. try only one CPU in first socket and swap to sort out bad cores.
memory popuplated balanced ? memory bad ?
i had a cpu with one or more bad cores, linux memtest etc worked fine but W10 got BSOD, W11 was not born that time.
Previously I tried installing Windows 11 on Supermicro X13SWA-TF Motherboard + Intel W3-2423 (Retail) and ASUS PRO WS W790E Sage SE + Intel ES QYFS. I got the same "Recovery" message, but I don't think they count because I didn't have TPM chips installed on the motherboards. Now, I'm currently using Gigabyte MS73-HB1 with Intel QS Q3W5 (Platinum 8570). I'm only using one CPU. CPU1 slot is empty. I used USB flash drive as the installation media. It worked fine when I installed Windows on my AMD 9600X desktop computer yesterday. There is no RAM issue, because all eight DIMMs worked fine when I ran LLMs on Ubuntu.
I see the following messages from IPMI Event Log
system_management_software : unknown was asserted
smi_handler : oem_timestamped
system_management_software : The system stopped responding because of an exception while running the operating system.
smi_handler : Extended SEL data
I guess I need to try different settings in BIOS, but it feels I tried everything already.
I see the following messages from IPMI Event Log
system_management_software : unknown was asserted
smi_handler : oem_timestamped
system_management_software : The system stopped responding because of an exception while running the operating system.
smi_handler : Extended SEL data
I guess I need to try different settings in BIOS, but it feels I tried everything already.
This might be due to a conflict issue between the Nvidia GPU and the Aspeed GPU on your board
This issue on all server motherboards from all manufacturers if it with Aspeed GPU. When installing Windows 24H2(not include 23H2 and lower) or Windows Server 2025, a gray screen will appear during the Windows auto installation the Nvidia graphics card driver, and a BSOD (You can't see it) will be triggered, this causing Infinite restart.
Usually, I avoid this by using the following methods: Unplug the Nvidia GPU, installing the Windows in the VGA/IPMI KVM display, installing the Aspeed display driver after entering Windows, and then installing the Nvidia GPU and the driver.
This issue on all server motherboards from all manufacturers if it with Aspeed GPU. When installing Windows 24H2(not include 23H2 and lower) or Windows Server 2025, a gray screen will appear during the Windows auto installation the Nvidia graphics card driver, and a BSOD (You can't see it) will be triggered, this causing Infinite restart.
Usually, I avoid this by using the following methods: Unplug the Nvidia GPU, installing the Windows in the VGA/IPMI KVM display, installing the Aspeed display driver after entering Windows, and then installing the Nvidia GPU and the driver.
I tried again without Nvidia GPU using the Remote KVM from BMC. I get IPMI log "ID: 16684 OTHER Event sensor of type None logged a smi_handler : Extended SEL data Unknown Extended SEL Data" and the following Error from Windows "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation."
That event is nothing, I have it too. You need a complete reinstallation. If there are still problems, I have no other ideas.
Insider Preview Build 27938 also not work with the nvidia card,no driver also,randomly reboot and no screen.
I don't know about the 25H2 or else, but that 24H2 issue was there.
Maybe try what I said on it?
they run both Intel (CS)ME (W790) not Intel SPS(C741)
Intel ME creates a softwre TPM. but if you have some encrypted HDD etc and you motherboard dies you can't just replace the motherboard with a new one.
A simple way: In the early stage of oobe, use shift+F10 to open the CMD and open Device Manager in CMD, then disable Aspeed GPU.