New motherboard keeps crashing & weird things, CPU bad? (Solved, kind of. Moved on)

[mxnerd]

"Any problems shown in Device Manager? " No.

I did not check those 2 forums and I don't think it will help. I just can't spend so much time on a board that give me so much trouble in a week.

Anyway, I already requested RMA from Newegg. Will return the board tomorrow.

 

[mxnerd]

Replaced the board with ECS Z97-PK, works well, not much drama, the microcode update did not make system non bootable.

Except: The first second creating Windows XP Mode machine in Windows 7 Virtual PC immediately BSOD the system, every single time. Had to use VirtualBox.

Well, I really got tired of the whole process. No wonder PC IS DYING.

 

[Auric]

Gremlins.

 

[mxnerd]

I would say probably the CPU is bad?

Got this WHEA-Logger error Event ID 19 in Event Viewer after running for a day.

=========================
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID : 0 or 2


Changed yet another set of RAM, formatted the SSD, reinstall Windows 7, 6 hours later, these errors pop up again, about once every hour.

I did not OC at all since 1st day. Never, ever encountered anything like this.

Should I be worried? Any thoughts? Really can't take this any longer.

 

[mxnerd]

Ran Prime95 again for 9 hours and no issue.

Intel Processor Diagnostic Tools also found nothing wrong.

Just don't know why the hell getting these events?

 

[mxnerd]

Turns out WHEA-Logger warning could be a combination of OS, processor and software (VMware)

Googled and found quite a few postings regarding this particular warning. Some have to adjust CPU voltage to make the warning go away, mine is VMware related like a few people.

In my case, I was running Windows 7, running a 32bit Endian Firewall VM inside VMware (everytime I started this VM this warning was logged, but not any other VM) and with a 4th Gen processor Pentium G3258.

I'll accept it and move on.

Hope Windows 10 & new VMware can fix this.