-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Business PCs, Workstations and Point of Sale Systems
- HP Z420 Memory Training Error (code 3016)

Create an account on the HP Community to personalize your profile and ask a question
10-29-2020 02:14 PM
Hi,
I know there are other threads (now closed and quite old) concerning this but I have a question and wonder if anyone can help me.
I get this error message when powering up the system. From reading other threads on the topic and trying to narrow it down I suspect it's something to do with a bent pin on the CPU socket. However, I myself don't feel too comfortable correcting it and intend to get it serviced by a technician in the city where I live. The problem is that I won't be able to do that very soon.
However, I get the error message and can boot into Windows 10 fine using F1 and have absolutely no problems - everything seems to be working fine and stable. I stress tested my E5 - 1650 V2 Xeon which is overclocked to 4.3Ghz, have played some RAM intensive games, worked on some taxing music projects, all with no problems so far.
My question is: How serious is this error message? I know of course it's difficult to predict with certainty but will the computer be okay (more or less) for a few months until I can get it sorted?
Any advice / info would be greatly appreciated.
Thanks!
10-29-2020 04:16 PM
this error is not usually caused by the cpu/pins
as the previous posts state, it's usually caused by a poorly seated ram module or failing ram module or a bad ram socket
remove all ram, and clean edges with 98% isopropyl alcohol insert the first bank of ram (two dimms) boot and check for error, if none insert next two modules in same sockets. continue till all ram checked
now add next two ram modules (total 4) reboot and if good, next two modules
this method will determine if cause is bad ram or bad socket