The drivers and firmware were updated after the Blue Screen occurred on one machine and before the Blue Screen occurred on another machine. So, there is no correlation there. I did not see this error show up in the logs. However, I have found that going into the BIOS and disabling the No-Execute Memory Protection setting under the processor options makes the Blue Screen stop appearing.
I found the solution to this problem. According to HP, who was able to confirm this with Intel, there is the â No-Execute Memory Protectionâ option in the BIOS that was designed to work in conjunction with Windows Server 2008. If the option is enabled while running Server 2003, it may return a blue screen, â NMI: Parity Check/ Memory Parity Errorâ as soon as it reaches Windows after the boot. The HP rep said that we should disable the option on all of the new servers until we decide to upgrade to Server 2008 or later.