A Flurry of BSODs

[Don77]

Hello all,

My system acted up a few days ago about being on for about 48 hours and running stable after my gf finished her marathon Autocad session. There was a Windows update -- KB982110 -- so I updated. A BSOD came up warning about a "driver mismanaging PTEs". I restarted about 5 times and BSODs came up a few minutes after logging in each time. It was late and I called it a night. Next morning I powered and left it on for the day until another BSOD came up.

Hopefully I followed the posting instructions correctly.

Thanks for any help guys!

Don

 

[Don77]

minidump

minidump.zip

 

[usasma]

There's not much info in these memory dumps. They mostly blame Windows components - which isn't usually the problem. So, let's try....

Please uninstall your MacDrive (MDPMGRNT.SYS) and test for further BSOD's. It's the only 3rd party driver mentioned in the stack text of the 2 BSOD's.

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:

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: [url=http://www.carrona.org/dvrref.html]Driver Reference[/url] ).
Please pay particular attention to any dated 2008 or earlier:

adfs.SYS     Mon Nov 03 11:48:14 2008 - Adobe File System Driver - http://www.carrona.org/dvrref.html#adfs.SYS
DgiVecp.sys  Thu Oct 30 23:38:29 2008 - IEEE-1284 parallel class driver for ECP, Byte, and Nibble modes - Device Guys or Samsung - http://www.carrona.org/dvrref.html#DgiVecp.sys
PxHlpa64.sys Wed Mar 12 21:58:17 2008 - Sonic CD/DVD driver (used by many different CD/DVD programs) - http://www.carrona.org/dvrref.html#PxHlpa64.sys
SSPORT.sys   Thu Aug 11 19:07:32 2005 - Samsung printer driver - http://www.carrona.org/dvrref.html#SSPORT.sys

If you're still receiving BSOD's after all of this, then please run 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:

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

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 01:07:45.348 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:30.002
BugCheck 1000007E, {ffffffffc000001d, fffff80002cc4157, fffff88002fe7988, fffff88002fe71f0}
Probably caused by : ntkrnlmp.exe ( nt!KeRemoveQueueEx+1b7 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 00:43:25.095 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:52.609
BugCheck D1, {fffff8800332a000, a, 1, fffff88000de5645}
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ataport.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for PCIIDEX.SYS - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ACPI.sys - 
*** WARNING: Unable to verify timestamp for MDPMGRNT.SYS
*** ERROR: Module load completed but symbols could not be loaded for MDPMGRNT.SYS
Probably caused by : atapi.sys ( atapi+2645 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[Don77]

Thanks usasma! Looks like it was the MacDrive that was culprit.