Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Windows 7 running on Macbook Pro

11 Sep 2010   #1

Windows 7 Professional 64-bit MacbookPro
 
 
BSOD Windows 7 running on Macbook Pro

I am having regular BSODs on my Macbook Pro (purchased early 2010) running Windows 7.

Basic System details:
Intel Core 2 Duo P8700
4GB RAM (2 DIMMS)
Windows 7 Enterprise 64-bit
NVIDIA GeForce 9400M
Running bootcamp 3.1

I ran Windows_NT6_BSOD_v3.03_jcgriff2_.exe to generate all the files it does; I have zipped it and added as an attachment to this thread.

I wasn't able to generate the performance monitor report, as I couldn't figure out how to do that.

Any help is appreciated.

Aditya


My System SpecsSystem Spec
.

12 Sep 2010   #2
Microsoft MVP

 
 

Your Windows 7 installation only has about 14 updates - most Windows 7 installations are at 45 updates. Please visit Windows Update and get all the updates that are available.

These devices are listed as disabled:
Quote:
Generic Bluetooth Adapter USB\VID_05AC&PID_8213\60FB42817B95 This device is disabled.

LSI 1394 OHCI Compliant Host Controller PCI\VEN_11C1&DEV_5901&SUBSYS_590011C1&REV_07\4&13DEB8CE&0&00B0 This device is disabled.
It's possible that the drivers are still loading, please check to see if that's the case. If so, please Uninstall the device rather than disabling it.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
Quote:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:
Code:
IRFilter.sys Wed Jul 02 15:53:12 2008 - IR Remote Driver - Boot Camp - http://www.carrona.org/dvrref.html#IRFilter.sys
nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) - http://www.carrona.org/dvrref.html#nvm62x64.sys
nvsmu.sys    Tue Jul 22 13:21:00 2008 - nVidia nForce System Management Controller (nVidia nForce chipset driver) - http://www.carrona.org/dvrref.html#nvsmu.sys
If none of the above helps, then please run Driver Verifier according to these directions:
Quote:
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/Windows 7 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, Windows 7):
        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: Fri Sep 10 17:41:57.066 2010 (UTC - 4:00)
System Uptime: 0 days 2:28:16.027
BugCheck A, {1000000, 2, 0, fffff80002ed130b}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 15:13:06.198 2010 (UTC - 4:00)
System Uptime: 1 days 6:10:08.837
BugCheck 50, {fffff300092e6650, 1, fffff80002eda940, 7}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e0b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  CcmExec.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
 
 
My System SpecsSystem Spec
Reply

 BSOD Windows 7 running on Macbook Pro




Thread Tools



Similar help and support threads for2: BSOD Windows 7 running on Macbook Pro
Thread Forum
BSOD last night. MacBook Pro running Bootcamp BSOD Help and Support
Solved Bluetooth pains in Windows 7 running on MacBook Pro 9,1 via BootCamp Drivers
BSOD - Windows 7 on Macbook Pro BSOD Help and Support
Windows 7 on MacBook Pro = BSOD BSOD Help and Support
Macbook Pro running Win 7 x64 w/ bootcamp Hardware & Devices
Losing IP address on MacBook Pro running bootcamp Network & Sharing
virtual pc 2007 running xp on macbook pro Drivers

Our Sites

Site Links

About Us

Find 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 03:50 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33