Machine Check Exception in Bootcamp Win 7

Discussion in 'Mac Pro' started by packsherpah, Mar 2, 2011.

  1. packsherpah macrumors newbie

    Joined:
    Jul 19, 2010
    #1
    I have a 2010 mac pro 12 core system which I run bootcamp and I have always gotten the following error in the error log every time I boot the system into Windows 7 X64:

    WHEA LOGGER EVENT ID 46: A fatal hardware error has occurred.

    Component: Memory
    Error Source: Machine Check Exception

    This error is always there, but my machine is actually stable as far as I can tell. I am just bothered by the constant existence of the error and don't like thinking it could be affecting applications from time to time.

    Now the thread I linked to below states that dual core xeon motherboards (EVGA SR-2) which is the PC equivalent to the 2010 Mac Pro motherboard (I think) - had the same problems for months, but then they released a new bios and the problem went away. Of course there is no BIOS in boot camp, so I think this error will not be solved until Apple fixes something in Bootcamp and releases a patch?. Not sure if this is a well known issue, but I suspect everyone with a dual CPU motherboard on any recent Mac Pro's gets this error or some form of it in Bootcamp running Windows 7.

    Take a look at this thread here, I think this is related to my problem:

    http://www.evga.com/forums/tm.aspx?m=536769&mpage=1


    I have this error in the event log on every boot up of win 7 x64 (aka in bootcamp). It is there every time. I know there is nothing wrong with the memory in my macpro, I have run every test imaginable on it. Any thoughts on how to make this go away?
     
  2. packsherpah thread starter macrumors newbie

    Joined:
    Jul 19, 2010
    #2
    bump, would love to get some help on this topic.
     
  3. Atrumangelus macrumors newbie

    Joined:
    Oct 18, 2012
    #3
    I just saw your post looking into a Mac I administer that is also running Win7 on bootcamp. After seeing your post, I looked at your other Macs running Win7/bootcamp and other of them have the same error on boot. This may be an issue with Bootcamp.
     

Share This Page