Parity Error Insanity

Sides

Reputable
Jul 22, 2014
9
0
4,510
Okay, so let me start by saying I've been working on this issue on and off for a month and a half now. At work, we've got five work stations (HP xw4000 workstation) that I'm reformatting. When I started I was given the error "Hardware malfunction, NMI Parity Check, Memory Parity Error, The System Hast Halted". Seemed like an easy fix at first. I tried replacing RAM to no avail. I even took RAM sticks from other IDENTICAL working machines and was given the same issue. Come to find out all five of these computers give me the same problem. I've ruled out the issue of memory. So I've tried reloading them with windows (I deleted the partition and created a new one). I'm about to try completely wiping the hard drives because I read something somewhere about the issue being with the chipset driver. Anyways, I can't even remember everything I've tried at this point. All major drivers are up to date, I've done graphics card memory stress tests. What else can I try? The most frustrating thing is that some of the computers will not even stay booted for more than 2 minutes and others can go a week without an issue. (If it helps point to an issue, I get this issue more if a computer has been powered off for a few hours or days) Any help is much appreciated. This is about to drive me crazy!
 

Sides

Reputable
Jul 22, 2014
9
0
4,510
Let me add that there's a good chance these computers were tinkered with at some point in time because they've been sitting back in our IT department for who knows how long. I've also done numerous RAM tests without so much as a hint of a RAM problem.
 

psoohoo

Honorable
Jul 30, 2014
211
0
10,760
Power supply issue?
Maybe at a certain load, the power supply would provide either cause an under or overvoltage which causes the RAM to corrupt the memory cell.

Machines using non-parity RAM will keep going until you hit the corrupt memory location and get a BSOD while parity memory will return a system halt as you have described.
 

Sides

Reputable
Jul 22, 2014
9
0
4,510
By turning off the computer for a while and then turning it back on I can practically make the computer blue screen on command. However, it will never blue screen while within BIOS no matter how long it sits there. I even tried disconnecting everything except for the motherboard, graphics card, and PSU. Could this point to anything in particular? Maybe an issue while reading from the hard drive?