bootcamp win7 BSOD assistance, please...

Discussion in 'Windows, Linux & Others on the Mac' started by challengestage, Jan 18, 2010.

  1. challengestage macrumors newbie

    Joined:
    Jan 18, 2010
    #1
    hey all, long time reader, first time poster. before i begin, let me first say that i know that win7 is not officially supported by bootcamp, i'm just checking to see if someone else out there has encountered my problem and been able to resolve it.

    i recently purchased a copy of 64 bit windows 7 ultimate and set it up on a bootcamp 3.0 install on my late '07 15" mbp running snow leopard. after a few minor headaches surrounding my install, i have been running both snow leopard and win7 without any major problems for about two and half weeks.

    overall the experience has been pretty good. i have both a bluetooth mighty mouse which works perfectly between both os's as well as an older bluetooth keyboard which is a little more finicky: sometimes i have to power cycle the keyboard in order to activate it's bluetooth connection.

    unfortunately, i regularly (meaning at least once every 2 hours of activity, sometimes more often) receive a BSOD, showing a STOP with the following codes:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 10d
    BCP1: 0000000000000005
    BCP2: 0000000000000000
    BCP3: 0000000000001401
    BCP4: FFFFFA8002B44A70
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1
    i'm wondering if anybody out there has had this problem and been able to resolve...

    thanks for reading!
     
  2. Matthew Yohe macrumors 68020

    Joined:
    Oct 12, 2006
  3. Paul B macrumors 6502

    Joined:
    Sep 13, 2007
    #3
    It's not supported but it works. There are thousands of users, including me, who have successfully installed Windows 7 on their Intel Macs.

    If your copy of Windows is illegitimate, the issue might be in the build itself.

    Try reinstalling.
     
  4. Matthew Yohe macrumors 68020

    Joined:
    Oct 12, 2006
    #4
    True, but it's such a waste of time troubleshooting these types of problems when legit drivers from Apple are right around the corner.
     

Share This Page