Did you get a fake Xeon from Amazon?
Did you get a fake Xeon from Amazon?
I purchased the Xeon E5 2650 v4 from Amazon (sold and shipped). The only model number listed on Google matches the 2011-v3 socket type, which fits my server board setup. The problem is that the CPU I received has the correct markings, but it isn’t actually a 2011-v3 as shown in the attached photo. There’s a label on the bottom of the box reading "LGA2011V4." What’s going on and what does LGA2011V4 mean? Thanks.
It's a Supermicro X10. The motherboard is confirmed—previously I had a 2011-v3 processor installed, and the socket clearly shows a large "2011-3" mark on it. @nick This detail really puzzled me. The unit I got isn't a 2011-3. Edited May 23, 2019 by Pallas Cat added a reply
A Google about Supermicro X10 resulted in the product page for the Xeon_X10_E5, which indicates the socket is 2011. However, all images display dual sockets, making it unclear if they are the same board. Edit: After further searching, a single socket variant was identified.
I believe it's from 2011-3, though your board appears to be from 2011. It's possible the labeling got mixed up. Edit: I notice a 2011-3 stamped on the sockets bracket. Edit 2: It seems the bracket might have been combined with the actual socket.
The 2011-v3 socket used to fit a 2011-v3 processor for more than a year can't accommodate a newer CPU that wasn't originally designed for it. A clearer image of the 2011-3 stamping on the socket helped clarify this point. Edit: reference showing an actual E5 2650 v4 appeared. Added a picture by Pallas Cat on May 23, 2019.
They already shared this before, it's okay. You can reach out to Amazon and request a refund or return, providing photos. Their customer service is excellent. The 2011V4 model doesn’t exist—scammers are clearly confused.
The processor seems to have physical incompatibility with the 2011-v3 BIOS problems, though those are fixed via IPMI even without RAM or CPU installed. This isn't a BIOS-related issue at all. It makes me curious—could there have been an error during manufacturing or something more complex happening?