Bsod when Quit a game.

The memory dump files blame a Windows component while running sc2.exe (Starcraft2). While it's not likely that Starcraft2 is the issue, it would be a good thing to ensure that you have all updates for that game.

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:

How To Find 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. Please pay particular attention to any dated 2007 or earlier:

Code:

adfs.SYS     Mon Nov 03 11:48:14 2008 - Adobe File System Filter driver - http://www.carrona.org/dvrref.html#adfs.SYS
ctac32k.sys  Wed Jul 02 04:38:22 2008 - Creative Audio driver - http://www.carrona.org/dvrref.html#ctac32k.sys
RTCore64.sys Wed May 25 02:39:12 2005 - RivaTuner/EVGA Precision driver - http://www.carrona.org/dvrref.html#RTCore64.sys
WmBEnum.sys  Thu Jan 24 18:01:30 2008 - Logitech WingMan Virtual Bus Enumerator Driver - http://www.carrona.org/dvrref.html#WmBEnum.sys
WmFilter.sys Thu Jan 24 18:01:27 2008 - Logitech WingMan Hid Filter                                                               - http://www.carrona.org/dvrref.html#WmFilter.sys
WmVirHid.sys Thu Jan 24 18:01:16 2008 - Logitech WingMan Virtual Hid Device Driver - http://www.carrona.org/dvrref.html#WmVirHid.sys
WmXlCore.sys Thu Jan 24 18:01:22 2008 - Logitech WingMan Translation Driver - http://www.carrona.org/dvrref.html#WmXlCore.sys

Because the memory dumps blame a Windows component, I'd suggest using Driver Verifier to attempt to force the system to give up the name of the faulting driver.
So, after the drivers are updated, please run Driver Verifier according to these directions:

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"
- 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.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 13 02:29:17.587 2010 (GMT-4)
System Uptime: 0 days 1:25:08.744
BugCheck 3B, {c0000005, fffff9600023c43e, fffff8800910be80, 0}
Probably caused by : win32k.sys ( win32k!MulDeleteDeviceOrRedirectionBitmap+1a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 17:22:37.747 2010 (GMT-4)
System Uptime: 0 days 3:35:12.903
BugCheck 3B, {c0000005, fffff9600030c43e, fffff88008c0ee80, 0}
Probably caused by : win32k.sys ( win32k!MulDeleteDeviceOrRedirectionBitmap+1a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SC2.exe