BSoD on brand new MacBook Pro


  1. Posts : 1
    Windows 7 Professional x64
       #1

    BSoD on brand new MacBook Pro


    Hi

    I'm running Windows 7 Professional x64 through bootcamp on my new MacBook Pro. The laptop and the installation are about 3 weeks old. The system's crashed three times now, all after several hours of moderate usage (watching DVDs, gaming) and it's annoying me as my old laptop ran Windows 7 for over a year without a single BSoD. Attached is the compressed output from the program recommended in the instructons on how to post (sorry - I couldn'tfind any Performance Monitor reports).

    Any help would be very greatfully appreciated!
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    Your chipset drivers appear to have issues. Have you installed the latest version from the Intel website?
    Code:
    Intel(R) 5 Series/3400 Series Chipset Family USB Universal Host Controller - 3B36    PCI\VEN_8086&DEV_3B36&SUBSYS_72708086&REV_06\3&11583659&0&E8    This device cannot start.
    Your BootCamp IR Remote driver is old (2008), I'd suggest updating the Apple BootCamp software also (I don't know much about this myself)

    The STOP errors don't seem to specify anything in particular. If updating the chipset drivers doesn't help, then I'd suggest running Driver Verifier according to these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Nov 13 19:04:01.709 2010 (UTC - 5:00)
    System Uptime: 0 days 4:36:53.254
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000007F
    Arguments 00000000`00000008 00000000`80050033 00000000`000006f8 fffff800`02e3eec8
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Nov 10 13:33:28.051 2010 (UTC - 5:00)
    System Uptime: 0 days 18:28:35.601
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000007F
    Arguments 00000000`00000008 00000000`80050033 00000000`000006f8 fffff800`02e97ec0
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Nov  9 19:01:33.041 2010 (UTC - 5:00)
    System Uptime: 0 days 9:40:11.196
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000007F
    Arguments 00000000`00000008 00000000`80050033 00000000`000006f8 fffff800`02e4aec8
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 23:08.
Find Us