Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

rolltide4life

macrumors member
Original poster
Hey Mac Pro users, do you receive whea logger error on your bootcamped mac (windows 7, 8.1, or 10)
I always have that particular WHEA Logger Event ID 46 error in my windows's event viewer. it affects any version of windows i use - 7, 8.1, and 10. I have 2012 mac pro 5,1. I have attached the screenshot to this post and see if you guys have the same error message as i do via windows event viewer.

Thanks,
 

Attachments

  • eventid46error.PNG
    eventid46error.PNG
    16.5 KB · Views: 429
Hey Mac Pro users, do you receive whea logger error on your bootcamped mac (windows 7, 8.1, or 10)
I always have that particular WHEA Logger Event ID 46 error in my windows's event viewer. it affects any version of windows i use - 7, 8.1, and 10. I have 2012 mac pro 5,1. I have attached the screenshot to this post and see if you guys have the same error message as i do via windows event viewer.

Thanks,
Have you run a good memory tester - or even the one in the Windows F8 boot menu?
 
Have you run a good memory tester - or even the one in the Windows F8 boot menu?

I havent tried that but i ran stress test program called prime95 with blend setting (CPU, cache, Ram, etc) and it failed within 1-2 hours of testing. It stopped with error message - rounding was 0.5 less than 0.4 hardware failure detected consult stress.txt
 
I havent tried that but i ran stress test program called prime95 with blend setting (CPU, cache, Ram, etc) and it failed within 1-2 hours of testing. It stopped with error message - rounding was 0.5 less than 0.4 hardware failure detected consult stress.txt
That (and your error log entry) is consistent with a hardware problem with RAM or CPU.

Go to http://www.memtest.org/ and download a thumb drive or CD bootable version of a very good memory tester.

Your error log entry of "machine check - memory" says "uncorrectable by ECC memory error". This is usually an indication of bad RAM, but can also be triggered by a driver trying to read or write non-existant memory.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.