BSOD during games (Diablo III, Left 4 Dead 2), multiple error codes

[evrise]

This is a PC that was custom-built by a friend last September. Since early May I've been getting BSODs more and more frequently while playing games like Diablo III and Left 4 Dead 2. Since it's been happening during games, I suspect it could be my GPU, but I haven't had to troubleshoot much before so I'm not sure.

I have tried to update my graphics driver (AMD CCC 12.4 from 12.3), but when I did so my PC refused to recognize the new drivers at all (tried Driver Sweeper and restarting, no luck). I ended up restoring back to a system restore point before I tried to update in order to get the PC usable again, as I need it for work as well.

I have WhoCrashed installed and have been checking the crash dumps, but they vary each time and googling hasn't helped me much.


Here are some specs:
OS: Windows 7 Ultimate x64
CPU: AMD Phenom II X4 970
Mobo: GIGABYTE GA-970A-UD3
Memory: G.SKILL Ripjaws X Series 8GB (2 x 4GB)
GPU: XFX HD-687A-ZHFC Radeon HD 6870
HDD: SAMSUNG Spinpoint F3 HD103SJ 1TB
PSU: OCZ ModXStream Pro 700W

Thanks in advance for your help. Hopefully I've not left anything important out.

 

[usasma]

33 memory dumps from 12 April 2012 to the present

perfmon /report shows these errors:

Error

Symptom:

A service (Windows Update) is reported as having an unexpected error codeCause:One or more services has failed. The service did not stop gracefully, suggesting the service may have crashed or one of its components stopped in an unsupported way.Details:Service exited with code not equal to 0 or 1077Resolution:Restart the serviceRelated:Performance Diagnosis

Symptom:

Device is not present, not working properly, or does not have all of its drivers installed.Cause:A device has a configuration problem that prevents it from working properly.Details:The device, AODDriver4.1, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_AODDRIVER4.1\0000.Resolution:1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.Related:Explanation of Error Codes Generated by Device Manager
Manage Devices in Windows

Have you done anything with Windows Update that would cause it to crash? Have you visited Windows Update and did it succeed?

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download and install a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC). This is a separate issue and isn't required for the AMD OverDrive removal.

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Only 62 updates since SP1 - most systems have 75 or more. Please visit Windows Update again and get all available updates. If you have problems with this, post back for additional advice.

Waiting on the memory dump files to finish running.....
I suspect the AODDriver2.sys as the primary issue here, so please start working on that.
If the memory dumps don't finish in the next 15 minutes I'll have to leave and won't be back until this afternoon (6 - 8 hours)

 

[usasma]

33 memory dumps from 12 April 2012 to the present
13 different BSOD error codes
8 different causes blamed

This is most likely a hardware error. It is usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (such as missing Windows Updates)
- low-level driver problems (such as AODDriver2.sys)
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

You updated to SP1 on 17 or 18 April 2012 - so the dumps before then may not have significant info. I include them for completeness.

These older drivers need to be updated or removed from your system. Links are included to help you figure out where to update them from:

mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F)
MagicISO SCSI Host Controller driver
http://www.carrona.org/drivers/driver.php?id=mcdbus.sys

netr28x.sys Wed Feb 25 22:02:09 2009 (49A60631)
Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)
http://www.carrona.org/drivers/driver.php?id=netr28x.sys

LHidFilt.Sys Wed Jun 17 12:49:39 2009 (4A391EA3)
LMouFilt.Sys Wed Jun 17 12:49:43 2009 (4A391EA7)
Logitech SetPoint Drivers
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys

If all of these things don't stop the BSOD's, please start with the free hardware diagnostics here: Hardware Diagnostics

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

[FONT=lucida console]
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys    Fri Mar 09 06:05:26 2012 (4F59E3F6)
HWiNFO64A.SYS   Tue Feb 07 08:08:34 2012 (4F312252)
EtronXHCI.sys   Fri Jan 06 03:59:41 2012 (4F06B7FD)
atikmpag.sys    Thu Mar 08 22:58:02 2012 (4F597FCA)
EtronHub3.sys   Fri Jan 06 03:59:47 2012 (4F06B803)
AtihdW76.sys    Tue Dec 06 04:14:25 2011 (4EDDDCF1)
mcdbus.sys      Tue Feb 24 05:34:07 2009 (49A3CD1F)
atikmdag.sys    Thu Mar 08 23:04:49 2012 (4F598161)
Rt64win7.sys    Thu Feb 16 00:39:50 2012 (4F3C96A6)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
netr28x.sys     Wed Feb 25 22:02:09 2009 (49A60631)
LHidFilt.Sys    Wed Jun 17 12:49:39 2009 (4A391EA3)
LMouFilt.Sys    Wed Jun 17 12:49:43 2009 (4A391EA7)
RTKVHD64.sys    Tue Mar 27 05:01:50 2012 (4F7181FE)
AODDriver2.sys  Mon Dec 19 02:30:03 2011 (4EEEE7FB)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
netr28x.sys     Mon Nov 14 10:52:43 2011 (4EC1394B)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
atikmpag.sys    Mon Dec 05 21:12:14 2011 (4EDD79FE)
atikmdag.sys    Mon Dec 05 21:52:23 2011 (4EDD8367)
AtihdW76.sys    Tue Oct 18 03:09:49 2011 (4E9D263D)
MpNWMon.sys     Wed Apr 06 16:07:23 2011 (4D9CC7FB)
AODDriver2.sys  Wed Jun 15 04:38:35 2011 (4DF86F8B)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
netr28x.sys     Fri Jun 19 03:56:06 2009 (4A3B4496)
[/FONT]

http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=EtronXHCI.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=EtronHub3.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=mcdbus.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amdiox64.sys
http://www.carrona.org/drivers/driver.php?id=netr28x.sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=cpuz135_x64.sys
http://www.carrona.org/drivers/driver.php?id=netr28x.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=MpNWMon.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=netr28x.sys

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052912-15537-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 19:02:26.359 2012 (UTC - 4:00)
System Uptime: 0 days 1:20:58.857
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!PoIdle+52a
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052912-13993-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 17:41:01.820 2012 (UTC - 4:00)
System Uptime: 0 days 3:30:38.318
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
Bugcheck code 0000007E
Arguments ffffffff`c0000005 fffff880`041a4eea fffff880`03cd73f8 fffff880`03cd6c50
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052912-16551-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 14:09:46.601 2012 (UTC - 4:00)
System Uptime: 0 days 2:33:09.100
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04020d45 fffff880`06ebb6a8 fffff880`06ebaf00
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052912-16614-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 11:36:00.534 2012 (UTC - 4:00)
System Uptime: 0 days 2:18:27.033
Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownStructures+22e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Ragexe.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsTeardownStructures+22e
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0ad73e38 fffff880`0ad73690 fffff880`0128d79e
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052912-11918-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 02:33:38.522 2012 (UTC - 4:00)
System Uptime: 0 days 1:42:45.646
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+356c3 )
BUGCHECK_STR:  0x1a_3452
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356c3
Bugcheck code 0000001A
Arguments 00000000`00003452 00000000`007f3000 fffff700`010971b0 dbb00001`9305bc66
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-13681-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 20:17:35.642 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:48.750
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+ef )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+ef
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`0309caff
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-21699-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 17:48:41.735 2012 (UTC - 4:00)
System Uptime: 0 days 1:33:58.859
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+31 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+31
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`045bfca9 fffff880`021c65d8 fffff880`021c5e30
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-13135-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 16:14:16.393 2012 (UTC - 4:00)
System Uptime: 0 days 0:52:40.891
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x19_20_nt!PoIdle+52a
Bugcheck code 00000019
Arguments 00000000`00000020 fffffa80`06be3800 fffffa80`06be43e0 00000000`04be3800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-12230-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_65740001`00000004
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_65740001`00000004
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 03:45:49.652 2012 (UTC - 4:00)
System Uptime: 0 days 2:18:16.150
*** WARNING: Unable to verify timestamp for Unknown_Module_65740001`00000004
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_65740001`00000004
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`00000000 fffffa80`093d6130
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-21138-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 01:27:09.012 2012 (UTC - 4:00)
System Uptime: 0 days 9:35:14.511
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`0af6df50 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052712-13618-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 27 15:51:19.520 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:19.018
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateFcb+211 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCreateFcb+211
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`08e67808 fffff880`08e67060 fffff800`030c138b
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-12682-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00010001`000b000b
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00010001`000b000b
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 03:59:53.593 2012 (UTC - 4:00)
System Uptime: 0 days 0:43:01.091
*** WARNING: Unable to verify timestamp for Unknown_Module_00010001`000b000b
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00010001`000b000b
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-12277-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 03:16:25.603 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:54.101
BugCheck D3, {fffff960002ffa0c, 2, 0, fffff8000310f269}
Probably caused by : ntkrnlmp.exe ( nt!RtlLookupFunctionEntry+1ce )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD3
FAILURE_BUCKET_ID:  X64_0xD3_nt!RtlLookupFunctionEntry+1ce
Bugcheck code 000000D3
Arguments fffff960`002ffa0c 00000000`00000002 00000000`00000000 fffff800`0310f269
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052512-11653-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 25 21:04:15.943 2012 (UTC - 4:00)
System Uptime: 0 days 2:13:53.442
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xc2_7_nt!PoIdle+52a
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`84b00000 fffffa80`06ce37f0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052512-11996-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 25 18:49:52.945 2012 (UTC - 4:00)
System Uptime: 0 days 15:21:56.054
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+16 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
FAILURE_BUCKET_ID:  X64_0x50_nt!KeSetEvent+16
Bugcheck code 00000050
Arguments ffffffff`ffff7fff 00000000`00000000 fffff800`030d7766 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052512-12589-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_a5b7ab2b`6b527bd3
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_a5b7ab2b`6b527bd3
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 25 03:27:31.732 2012 (UTC - 4:00)
System Uptime: 0 days 0:45:51.840
*** WARNING: Unable to verify timestamp for Unknown_Module_a5b7ab2b`6b527bd3
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_a5b7ab2b`6b527bd3
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`0699c520 fffffa80`0699c520 fffff8a0`09749338
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052412-12558-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 24 00:12:25.330 2012 (UTC - 4:00)
System Uptime: 0 days 22:38:46.439
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`030d6f7c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052312-12589-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 23 01:33:11.637 2012 (UTC - 4:00)
System Uptime: 0 days 1:22:46.135
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!PoIdle+52a
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`03bbed45 00000000`00000000 00000003`000000ab
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052112-13166-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 21 23:28:28.231 2012 (UTC - 4:00)
System Uptime: 1 days 21:58:54.729
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000002
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000002
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!PoIdle+52a
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`00132b88 ab700001`caea7867 fffffa80`08c347b0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052012-13977-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 20 01:28:41.989 2012 (UTC - 4:00)
System Uptime: 1 days 2:40:18.323
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  MOM.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+13b
Bugcheck code 0000000A
Arguments fffff880`02f602e0 00000000`00000002 00000000`00000000 fffff800`030e12eb
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051812-14710-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 18 22:47:44.703 2012 (UTC - 4:00)
System Uptime: 0 days 0:44:32.201
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275 )
BUGCHECK_STR:  0xc2_7_File
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  left4dead2.exe
FAILURE_BUCKET_ID:  X64_0xc2_7_File_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`0000109b 00000000`00000001 fffffa80`07767050
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051812-16879-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 18 16:56:08.606 2012 (UTC - 4:00)
System Uptime: 1 days 3:01:07.556
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : msrpc.sys ( msrpc!NdrSafeAllocate+85 )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xC5_2_msrpc!NdrSafeAllocate+85
Bugcheck code 000000C5
Arguments fffff8a0`1618f508 00000000`00000002 00000000`00000001 fffff800`031c3617
BiosVersion = F4
BiosReleaseDate = 10/13/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051712-17862-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_2e776f64`6e697728
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_2e776f64`6e697728
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 17 13:54:30.733 2012 (UTC - 4:00)
System Uptime: 0 days 17:41:14.141
*** WARNING: Unable to verify timestamp for Unknown_Module_2e776f64`6e697728
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_2e776f64`6e697728
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`033af8f1 fffff880`09f26ed0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042312-18844-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_006e006f`00700073
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_006e006f`00700073
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Apr 23 12:11:31.764 2012 (UTC - 4:00)
System Uptime: 1 days 16:26:23.661
*** WARNING: Unable to verify timestamp for Unknown_Module_006e006f`00700073
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_006e006f`00700073
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`033a82d8 fffff880`033a7b30 fffff880`012e31b2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042012-14757-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Apr 20 23:29:04.397 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:49.958
BugCheck D1, {144, 2, 1, fffff8800572ed79}
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : netr28x.sys ( netr28x+104d79 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_netr28x+104d79
Bugcheck code 000000D1
Arguments 00000000`00000144 00000000`00000002 00000000`00000001 fffff880`0572ed79
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042012-19078-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Apr 20 10:53:32.140 2012 (UTC - 4:00)
System Uptime: 0 days 11:17:59.701
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteInternalAttributeStream+b3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteInternalAttributeStream+b3
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0ae8e588 fffff880`0ae8dde0 fffff880`012ff14b
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041812-20654-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Apr 18 22:34:19.721 2012 (UTC - 4:00)
System Uptime: 0 days 2:56:26.908
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!PoIdle+52a
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`0002eb78 d4000000`52bd5867 fffffa80`0a0fc590
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041812-17284-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Apr 18 14:36:05.717 2012 (UTC - 4:00)
System Uptime: 0 days 1:01:30.278
Probably caused by : memory_corruption ( nt!MiBuildPageFileCluster+13d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MiBuildPageFileCluster+13d
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02d5a41d fffff880`033080e8 fffff880`03307940
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041712-15662-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Apr 17 02:37:33.445 2012 (UTC - 4:00)
System Uptime: 0 days 10:14:06.100
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`001d5fd5 00000000`00000003 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041512-19172-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Apr 15 04:32:18.285 2012 (UTC - 4:00)
System Uptime: 0 days 3:13:58.939
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13b42 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13b42
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`0009b870 cb500000`95ba0867 fffffa80`0c87b380
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041412-22183-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Apr 14 10:33:54.108 2012 (UTC - 4:00)
System Uptime: 0 days 11:12:12.388
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+338c6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338c6
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`0597baf0 00000000`0000ffff 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041212-18720-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Apr 12 21:53:25.469 2012 (UTC - 4:00)
System Uptime: 0 days 4:49:06.139
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )
BUGCHECK_STR:  0xc2_7_Mdl 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0xc2_7_Mdl__dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`00001097 00000000`00000000 fffffa80`0cffd780
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041212-13525-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Apr 12 10:02:45.859 2012 (UTC - 4:00)
System Uptime: 0 days 0:28:39.139
BugCheck F4, {3, fffffa800bc0c060, fffffa800bc0c340, fffff80002ddc240}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0bc0c060 fffffa80`0bc0c340 fffff800`02ddc240
BiosVersion = F3
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[evrise]

Thank you for the prompt response! I'll try to address everything you've mentioned. I can tell you right now that I am not overclocking, but I'm not sure about the Windows Update issues. I've been letting it update whenever it asks to, but have not gone there on my own in a while; I cannot recall it crashing or mentioning anything.

Okay, I just checked Windows Update, something is definitely wrong because it says "Check for updates for your computer" but when I attempt to do so, it brings me this error message: "Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer." After a restart, I'm still getting the same thing. I went into Services to try restarting Windows Update, but it brings this error: "Windows could not start the Windows Update service on Local Computer" with Error 193: 0xc1.

So that's definitely not looking good. I will start working on the AMD drivers and the rest and post back with that info soon.

 

[usasma]

To start the Windows Update service, do this:
Go to Start and type in "services.msc" (without the quotes) and press Enter
Scroll down the list until you get to Windows Update.
Right click on it and select "Properties"
Make sure that "Startup type" is set to Automatic (delayed start)
Then click on the "Start" button to start the service. If it doesn't start, post back with the exact error message.

 

[evrise]

Still no luck, I received the same error code as before when I tried to start the service. It is indeed already set to Automatic (delayed start).
Error 193: 0xc1.

 

[evrise]

Okay, so I have made some progress on your steps, but it's not positive so far... I will attach some images for clarity.

I uninstalled the AMD drivers, then reinstalled as you mentioned. First issue (amd-install-options.jpg): under Custom installation, there was no option to avoid installing AMD Overdrive. Second issue: when installing the display driver, I received two error messages (amd-driver-error1.jpg and amd-driver-error2.jpg). No idea what those mean. Now, even though the install says it has completed, my PC basically has no graphics driver installed (driver-problems.jpg) and the AODDriver4.01 error persists.

I have performed scans with both MSE and Malwarebytes with no issues reported.

Update: I was away for a bit, but after uninstalling the AODDriver as instructed it has stayed uninstalled, so that's fine for now. The main graphics driver is still inoperable, however; I am stuck in default resolution right now. Have tried reinstalling twice now, still no luck there. This is now the same issue I encountered when I tried to update my graphics earlier (mentioned in my first post). That time, a system restore fixed the graphics driver, but not the BSOD issues.

 

[usasma]

Try the free malware scans here: Free Online AntiMalware Resources
Your video drivers shouldn't give this error - and the Windows Update errors shouldn't happen this way. The most likely cause is a malware infection.

 

[evrise]

Thanks again for your help on this.

I've now updated the drivers you listed, and it's still BSODing (latest one was about an hour ago). I've tried a few of the malware scanners you linked, specifically HouseCall, Bitdefender, and Kaspersky. None have found anything, so I'm really at a loss now. Do you think it's advisable for me to just reinstall my OS and see if that helps any? I have it on a separate partition, so it wouldn't set me back much.

 

[usasma]

Here's a suggestion on how to do the reinstall of Windows "clean". This'll let you troubleshoot while installing Windows.

Backup, Wipe, and "Clean Install" of Windows

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7 and Vista.

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.
NOTE: Disconnect any additional hard drives (internal and external) that you may have installed. This may break any multi-boot setups that you have, so be prepared to conduct recovery operations on them once you're done. Don't forget that, if this is due to an infection, the additional hard drives may be infected also.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).

3. Use one of these free utilities to wipe the hard drive clean:
DBAN ( DBAN Download | Darik's Boot And Nuke )
KillDisk ( Freeware Download Active@ KillDisk ).
This will also delete any recovery partitions on the system - so the installation/recovery DVD's are essential!!!

4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

5. Visit Windows Update and get all updates

6. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

7. Visit Windows Update and get the Service Packs for your system. (usually under Important Updates).
Read these notes for installing Windows 7 SP1: Learn how to install Windows 7 Service Pack 1 (SP1) and Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)
Search Google/Bing for installing other OS's Service Packs.

8. Visit Windows Update and get any other available updates

9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009/2010 is OK. Updates are available at the Asus support website.

CAVEAT: If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys). Update this driver immediately!!!

 

[evrise]

This reply is quite late, but unfortunately I was super busy today. Anyway, I've gone ahead and followed your instructions to a T. So far it's been stable, but I'll have to report back after I have a chance to play some games tomorrow. Just wanted to post an update. Thanks again for your help thus far.

 

[evrise]

Okay, here's another update.
At first it seemed like the reinstall did the trick, but after testing out a few games, the BSODs returned, happening the same way as before. Just to check a hunch, I borrowed a friend's graphics card (same make and line, just a 6770 instead) and tested that in my PC for a while. Everything ran perfectly, including the games that were previously BSODing all the time. I've given him the card back by now, and I know a couple of hours of testing isn't really conclusive (that was all he could spare), but it does seem somewhat telling.

 

[usasma]

You can purchase a new card from a retailer that will take returns. Then test it for a week or two to see if it's a permanent fix.