BSOD playing games or during downloads

SuperXHornet · Jul 18, 2012

When I start playing a game about 5 minutes into the game my screen flicker for a split second and then crashes into a BSoD. One of the BSoD's was something about mcupdate.dll and figured it had to do with mcafee so i uninstalled that. I wasn't able to get the other different kinds of BSoD's but maybe with the file I attached somebody can tell what is wrong. Also, when my comp crashes and I try to reboot it, it will freeze on startup,but if I wait 30 mins it will startup fine.

SuperXHornet · Jul 18, 2012

Forgot to put my system specs. Here they are...
OS: Windows 7 Home Premium x64
CPU:AMD Athlon(tm) II X2 270 Processor
Memory:8GB Kit (4GBx2) DDR3
HDD: HITACHI HDS721050CLA362 (500GB)
Graphics: AMD Radeon HD 6450
Motherboard: ASUS M4A78LT-MLE
Security: Norton 360

usasma · Jul 20, 2012

Late for work!

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 (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

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.

Otherwise try hardware diagnostics (in particular - MemTest86+ and Prime95): Hardware Diagnostics

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071112-26598-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 11 18:41:13.097 2012 (UTC - 4:00)
System Uptime: 0 days 1:10:40.377
BugCheck FE, {5, fffffa8008dd51a0, 10024396, fffffa80093c4258}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`08dd51a0 00000000`10024396 fffffa80`093c4258
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071612-28126-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 16 21:56:34.976 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:09.256
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : volsnap.sys ( volsnap!VspWriteContextCompletionRoutine+1f )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
FAILURE_BUCKET_ID:  X64_0x1E_volsnap!VspWriteContextCompletionRoutine+1f
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071812-25662-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 18 01:41:17.272 2012 (UTC - 4:00)
System Uptime: 0 days 0:26:07.552
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck FE, {5, fffffa80089301a0, 10024396, fffffa8008f2bc48}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  wevtutil.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_ANALYSIS_INCONCLUSIVE
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`089301a0 00000000`10024396 fffffa80`08f2bc48
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

[/font][/code]

*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

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

Code:

[font=lucida console]
AE2500w764.sys          Mon Mar 28 20:22:08 2011 (4D912630)
AODDriver2.sys          Wed Jun 15 04:38:35 2011 (4DF86F8B)
ASACPI.sys              Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys                Mon Aug 03 03:03:16 2009 (4A768BB4)
AsUpIO.sys              Sun Jul 05 22:21:38 2009 (4A515FB2)
AtihdW76.sys            Tue Jun 07 06:34:39 2011 (4DEDFEBF)
BHDrvx64.sys            Wed May 16 22:16:36 2012 (4FB45F84)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
EraserUtilRebootDrv.sys Tue May 15 20:36:03 2012 (4FB2F673)
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
IDSvia64.sys            Thu May 24 20:08:33 2012 (4FBECD81)
Ironx64.SYS             Fri Nov 12 18:06:50 2010 (4CDDC88A)
L1C62x64.sys            Wed Apr 01 01:09:17 2009 (49D2F6FD)
MpFilter.sys            Fri Mar 09 06:05:26 2012 (4F59E3F6)
SRTSP64.SYS             Tue Mar 29 22:46:12 2011 (4D929974)
SRTSPX64.SYS            Tue Mar 29 22:46:18 2011 (4D92997A)
SYMDS64.SYS             Tue Dec 07 19:16:58 2010 (4CFECE7A)
SYMEFA64.SYS            Sun Mar 13 23:20:58 2011 (4D7D899A)
SYMEVENT64x86.SYS       Thu Mar 24 19:02:36 2011 (4D8BCD8C)
SYMNETS.SYS             Tue Apr 19 18:33:31 2011 (4DAE0DBB)
WSDPrint.sys            Mon Jul 13 20:39:20 2009 (4A5BD3B8)
amdiox64.sys            Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys            Thu Sep 08 13:26:08 2011 (4E68FAB0)
atikmpag.sys            Thu Sep 08 12:52:41 2011 (4E68F2D9)
ccSetx64.sys            Mon Aug 08 17:47:34 2011 (4E405976)
cpuz135_x64.sys         Wed Sep 21 04:23:41 2011 (4E799F0D)
eeCtrl64.sys            Tue May 15 20:36:03 2012 (4FB2F673)
nvstor.sys              Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys            Fri Apr 09 05:22:41 2010 (4BBEF1E1)
viahduaa.sys            Sat May 15 06:22:39 2010 (4BEE75EF)
[/font]

Code:

[font=lucida console]

[/font]

SuperXHornet · Jul 22, 2012

It worked for a little while when I was playing Arma 2 ,but today while playing I got another crash. Well more than just one,but all during Arma 2

usasma · Jul 22, 2012

If AODDriver2.sys is still present and the software/device isn't present and the driver isn't needed - then please do this (thanks to jcgriff2):

Code:
Bring up elevated Admin cmd prompt -
START | type cmd.exe | RIGHT-click on cmd.exe | "Run as Administrator" | type/ paste the following -

Code:

where /r c:\ /f /t AODDrive*.* > 0 & start notepad 0

It may take a few minutes.

A Notepad will open wth the results. This will tell you the location of all the OverDrive drivers on your system.

Please post the results in your next post.

Then:
- create a System Restore point.
- create a System Repair disc and ensure that it works. To do this, go to Start...All Programs...Maintenance...Create a System Repair Disc
- uninstall all ATI video stuff using Control Panel...Programs...Uninstall a program (this may make the next 3 steps unnecessary - if so, just continue on).

- check in services.msc to see if there is an AOD service. If there is, set it to "Disabled" for the startup type.
- then disable any startups that name AODDriver2.sys using Autoruns (free from here: Autoruns for Windows )
- rename AODDriver2.sys to AODDriver2.BAD (it's probably in C:\Windows\System32\drivers)
----------01 June 2012 - Owner found AOD in C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64

- reboot and see if that fixes the problem(s). Check in C:\Windows\System32\drivers (or the other folder) to be sure that it stays renamed.
- install fresh video drivers using the procedure here: ATI video cards - DRIVER ONLY installation procedure
DO NOT install the full Catalyst Control Center package!!!

Please try this to help rule out Norton:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Remove all USB devices. If using a USB keyboard/mouse - switch to a PS2 keyboard/mouse. If you don't have ports for the PS2, then use another USB keyboard/mouse and plug it into different ports (if you're using the front ports on your system - move to the ports on the rear of the system).

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

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

Code:

[font=lucida console]
AE2500w764.sys    Mon Mar 28 20:22:08 2011 (4D912630)
AODDriver2.sys    Wed Jun 15 04:38:35 2011 (4DF86F8B)
ASACPI.sys        Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys          Mon Aug 03 03:03:16 2009 (4A768BB4)
AsUpIO.sys        Sun Jul 05 22:21:38 2009 (4A515FB2)
AtihdW76.sys      Tue Jun 07 06:34:39 2011 (4DEDFEBF)
GEARAspiWDM.sys   Mon May 18 08:17:04 2009 (4A1151C0)
IDSVia64.sys      Tue Nov 22 15:23:23 2011 (4ECC04BB)
IDSvia64.sys      Thu May 24 20:08:33 2012 (4FBECD81)
Ironx64.SYS       Fri Nov 12 18:06:50 2010 (4CDDC88A)
Ironx64.SYS       Mon Nov 14 21:00:53 2011 (4EC1C7D5)
L1C62x64.sys      Wed Apr 01 01:09:17 2009 (49D2F6FD)
SRTSPX64.SYS      Tue Mar 29 22:46:18 2011 (4D92997A)
SRTSPX64.SYS      Tue Nov 22 18:52:20 2011 (4ECC35B4)
SYMDS64.SYS       Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMDS64.SYS       Tue Dec 07 19:16:58 2010 (4CFECE7A)
SYMEFA64.SYS      Sun Mar 13 23:20:58 2011 (4D7D899A)
SYMEFA64.SYS      Tue Nov 22 19:49:28 2011 (4ECC4318)
SYMEVENT64x86.SYS Thu Mar 24 19:02:36 2011 (4D8BCD8C)
SYMEVENT64x86.SYS Tue Nov 22 13:30:48 2011 (4ECBEA58)
SYMNETS.SYS       Sat Nov 12 16:11:53 2011 (4EBEE119)
SYMNETS.SYS       Tue Apr 19 18:33:31 2011 (4DAE0DBB)
WSDPrint.sys      Mon Jul 13 20:39:20 2009 (4A5BD3B8)
amdiox64.sys      Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys      Thu Sep 08 13:26:08 2011 (4E68FAB0)
atikmpag.sys      Thu Sep 08 12:52:41 2011 (4E68F2D9)
ccSetx64.sys      Fri Nov 04 18:05:25 2011 (4EB461A5)
ccSetx64.sys      Mon Aug 08 17:47:34 2011 (4E405976)
cpuz135_x64.sys   Wed Sep 21 04:23:41 2011 (4E799F0D)
eeCtrl64.sys      Fri Oct 21 21:18:28 2011 (4EA219E4)
eeCtrl64.sys      Tue May 15 20:36:03 2012 (4FB2F673)
nvstor.sys        Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys      Fri Apr 09 05:22:41 2010 (4BBEF1E1)
viahduaa.sys      Sat May 15 06:22:39 2010 (4BEE75EF)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071812-27955-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 18 23:38:15.058 2012 (UTC - 4:00)
System Uptime: 0 days 0:44:31.338
BugCheck FE, {5, fffffa80084061a0, 10024396, fffffa8008f6cc48}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  TeamViewer_Ser
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`084061a0 00000000`10024396 fffffa80`08f6cc48
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072212-22027-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 22 08:19:39.024 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:36.304
BugCheck FE, {5, fffffa80085e01a0, 10024396, fffffa8008cceb58}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`085e01a0 00000000`10024396 fffffa80`08cceb58
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072212-24476-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 22 08:11:38.538 2012 (UTC - 4:00)
System Uptime: 0 days 0:36:01.818
BugCheck FE, {5, fffffa800876f1a0, 10024396, fffffa8008d3fb58}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  arma2oa.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`0876f1a0 00000000`10024396 fffffa80`08d3fb58
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

SuperXHornet · Jul 22, 2012

Ok did all the steps. I'll see what happened here is what I got form the cmd prompt step
55424 6/24/2011 10:31:02 AM "c:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\aoddriver2.sys"

SuperXHornet · Jul 23, 2012

Didn't work. Here's the dump

usasma · Jul 23, 2012

The AODDriver was in the first memory dump, but not in the next 2 - so it's likely that it's been removed and isn't causing problems any longer.

You have a wireless USB network adapter - and most of the memory dumps involve some sort of action with the usb drivers on your system. In the past we noted that Win7 didn't like wireless USB devices - but assumed it was because of the older, Vista-era drivers. Your wireless USB drivers date from 2011 - so that isn't the case here.

But regardless of what's happened in the past, I have to wonder if the USB issues in the memory dumps are a result of the wireless USB device. Please test it to see. In order to test it you'll have to:
- uninstall the software/drivers for the wireless USB device
- physically remove the wireless USB device from your system.

Use either a very long wire to temporarily connect to the internet, or obtain a PCI/PCIe wireless card that plugs into your motherboard. These devices are much more powerful, reliable, and robust than the wireless USB devices, so you'll have fewer problems with it.

Also, your wired networking driver (L1C62x64.sys) dates from 2009. Please update it from the PC/mobo manufacturer's website.

Norton continues to be present in the dump files. Please follow these instructions. Once we're finished troubleshooting feel free to reinstall it:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

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

Code:

[font=lucida console]
AE2500w764.sys    Mon Mar 28 20:22:08 2011 (4D912630)
AODDriver2.sys    Wed Jun 15 04:38:35 2011 (4DF86F8B)
ASACPI.sys        Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys          Mon Aug 03 03:03:16 2009 (4A768BB4)
AsUpIO.sys        Sun Jul 05 22:21:38 2009 (4A515FB2)
AtihdW76.sys      Tue Jun 07 06:34:39 2011 (4DEDFEBF)
IDSVia64.sys      Tue Nov 22 15:23:23 2011 (4ECC04BB)
Ironx64.SYS       Mon Nov 14 21:00:53 2011 (4EC1C7D5)
L1C62x64.sys      Wed Apr 01 01:09:17 2009 (49D2F6FD)
MpFilter.sys      Fri Mar 09 06:05:26 2012 (4F59E3F6)
SRTSPX64.SYS      Tue Nov 22 18:52:20 2011 (4ECC35B4)
SYMDS64.SYS       Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMEFA64.SYS      Tue Nov 22 19:49:28 2011 (4ECC4318)
SYMEVENT64x86.SYS Tue Nov 22 13:30:48 2011 (4ECBEA58)
SYMNETS.SYS       Sat Nov 12 16:11:53 2011 (4EBEE119)
WSDPrint.sys      Mon Jul 13 20:39:20 2009 (4A5BD3B8)
amdiox64.sys      Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys      Mon Jun 11 12:59:31 2012 (4FD623F3)
atikmdag.sys      Thu Sep 08 13:26:08 2011 (4E68FAB0)
atikmpag.sys      Mon Jun 11 12:26:14 2012 (4FD61C26)
atikmpag.sys      Thu Sep 08 12:52:41 2011 (4E68F2D9)
ccSetx64.sys      Fri Nov 04 18:05:25 2011 (4EB461A5)
ccSetx64.sys      Mon Aug 08 17:47:34 2011 (4E405976)
cpuz135_x64.sys   Wed Sep 21 04:23:41 2011 (4E799F0D)
nvstor.sys        Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys      Fri Apr 09 05:22:41 2010 (4BBEF1E1)
viahduaa.sys      Sat May 15 06:22:39 2010 (4BEE75EF)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072212-20124-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 22 14:39:46.057 2012 (UTC - 4:00)
System Uptime: 0 days 6:15:18.337
BugCheck FE, {5, fffffa80086b21a0, 10024396, fffffa8008cea258}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  ArmA2OA.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`086b21a0 00000000`10024396 fffffa80`08cea258
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072212-20950-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 22 23:43:12.778 2012 (UTC - 4:00)
System Uptime: 0 days 0:30:11.058
BugCheck FE, {5, fffffa8006afe1a0, 10024396, fffffa80088d5c48}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_nt!PoIdle+52a
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`06afe1a0 00000000`10024396 fffffa80`088d5c48
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072212-26504-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 22 23:07:11.449 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:33.729
BugCheck FE, {5, fffffa80081701a0, 10024396, fffffa80087f8258}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`081701a0 00000000`10024396 fffffa80`087f8258
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

SuperXHornet · Jul 25, 2012

The network adapter I use is the only way I could get interenet access to this computer and I don't have the cash right now to purchase a new network card and an ethernet cable is just out of the question because it's too far a distance to cover by a cable.

Also, I'm having trouble finding an updated driver for L1C62x64.sys on any website that seems reliable so I wasn't able to do that.

As for the Norton files, I did follow those steps in the previous post and if you say there are still norton files, then that removal tool didn't work for me because I did it all so I just went searching around the computer and just deleted the files myself and hope that got rid of them for good.

I did however, remember using a gamepad controller recently that I just borrowed from a cousin to use which did install some usb drivers which may be causing the bsod's. So just to be safe, I unistalled the usb driver and hopefully when I test this comp again, I'll have no problems.

SuperXHornet · Jul 30, 2012

Alright, I moved my computer to a place where I could hook it up through an ethernet cable yet I still have the bsod's so i don't think that caused it. Also, I'm having trouble with updating that driver so if you could just tell me how to do it I would much appreciate it.

usasma · Jul 30, 2012

Which driver? I suggested several.
If it's the wireless USB, just go to the website of the manufacturer and see if there's a more recent one available.

SuperXHornet · Aug 1, 2012

I'm stuck at this point , but here's some bsod's but are system service exception bsods so hopefully you can tell me something else

usasma · Aug 1, 2012

If this is your motherboard then you can download the LAN driver from here: ASUS - Motherboards- ASUS M4A78LT-M LE

As for the wireless USB device - what is the exact make and model?
If replacing these drivers doesn't fix it, then you're going to have to try something that removes the wireless USB device from the equation.

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

Code:

[font=lucida console]
AE2500w764.sys Mon Mar 28 20:22:08 2011 (4D912630)
ASACPI.sys     Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys       Mon Aug 03 03:03:16 2009 (4A768BB4)
AsUpIO.sys     Sun Jul 05 22:21:38 2009 (4A515FB2)
L1C62x64.sys   Wed Apr 01 01:09:17 2009 (49D2F6FD)
MpFilter.sys   Fri Mar 09 06:05:26 2012 (4F59E3F6)
amdxata.sys    Fri Mar 19 12:18:18 2010 (4BA3A3CA)
atikmdag.sys   Mon Jun 11 12:59:31 2012 (4FD623F3)
atikmpag.sys   Mon Jun 11 12:26:14 2012 (4FD61C26)
ccSetx64.sys   Mon Aug 08 17:47:34 2011 (4E405976)
nvstor.sys     Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys   Fri Apr 09 05:22:41 2010 (4BBEF1E1)
viahduaa.sys   Sat May 15 06:22:39 2010 (4BEE75EF)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072512-17316-01.dmp]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072512-17971-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 25 11:35:37.854 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:18.134
BugCheck FE, {5, fffffa80080371a0, 10024396, fffffa80085acc48}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  winlogon.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`080371a0 00000000`10024396 fffffa80`085acc48
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072512-26317-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 25 12:02:33.861 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:21.141
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck FE, {5, fffffa80080501a0, 10024396, fffffa8008590c48}
Probably caused by : ntkrnlmp.exe ( nt!RtlCopyMemoryNonTemporal+92 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFE
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_nt!RtlCopyMemoryNonTemporal+92
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`080501a0 00000000`10024396 fffffa80`08590c48
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\073012-15849-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 29 09:19:34.343 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:15.623
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

SuperXHornet · Aug 1, 2012

I think I rather just remove it from the equation. How do I do it?

usasma · Aug 2, 2012

You uninstall the software for it and then physically remove it from the system.
If the BSOD's stop, then you've proven that it's at fault.

SuperXHornet · Aug 4, 2012

Alright well I did what you said and got more bsod's. I also got a message saying the display adapter recovered from a crash or something similar. Maybe you can tell me from the attachment i have attached

SuperXHornet · Aug 4, 2012

Wasnt sure if the attachment went through or not but here it is again just in case

usasma · Aug 5, 2012

Looks like we've got some hard drive issues (2 of the last 3 memory dumps are STOP 0x24 and blame NTFS.sys)
Please:

Please do this:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Then run these free, bootable diagnostics: Initial Hardware Diagnostics
Start with the hard drive test first.

Just FYI - those display adapter recovery errors are BSOD'ish events (STOP 0x117). I'd suggest looking into the hard drive stuff before we go any further. If we remedy the hard drive stuff and you still have errors - then we'll start looking at the video.

SuperXHornet · Aug 6, 2012

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
165632 file records processed. File verification completed.
215 large file records processed. 0 bad file records processed. 0 EA records processed. 61 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
210406 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
165632 file SDs/SIDs processed. Cleaning up 1004 unused index entries from index $SII of file 0x9.
Cleaning up 1004 unused index entries from index $SDH of file 0x9.
Cleaning up 1004 unused security descriptors.
Security descriptor verification completed.
22388 data files processed. CHKDSK is verifying Usn Journal...
34486632 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Windows replaced bad clusters in file 43
of name \Windows\Logs\SYSTEM~1\RESTOR~4.ETL.
Windows replaced bad clusters in file 45
of name \Windows\Logs\SYSTEM~1\RESTOR~1.ETL.
165616 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
82637713 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

488282111 KB total disk space.
157378940 KB in 122903 files.
70676 KB in 22389 indexes.
0 KB in bad sectors.
281639 KB in use by the system.
65536 KB occupied by the log file.
330550856 KB available on disk.

4096 bytes in each allocation unit.
122070527 total allocation units on disk.
82637714 allocation units available on disk.

Internal Info:
00 87 02 00 98 37 02 00 8b 2a 04 00 00 00 00 00 .....7...*......
78 01 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 x...=...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Also when starting up on after the harddrive test it crashed as soon as i got in. This time just a system_service_exception

usasma · Aug 7, 2012

CHKDSK shows some errors
It also replaced some stuff in 2 files - as they're in the LogFiles directory I don't think that it's a problem.

Did the hard drive test pass?
If it didn't pass (or it didn't get run) - then try the Seagate Seatools test.
If that doesn't run, then try either the Seagate or WesternDigital tests inside of Windows (different downloads than in my links). You may want to run a scan with the free HDTune program also.

Once we're sure that the hard drive passes the diagnostic tests, then move on to trying SFC.EXE /SCANNOW from and elevated (Run as administrator) Command Prompt.

Finally, after the next BSOD, please run the CHKDSK /R /F procedure again to see if there are any more corruptions/problems.

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

L1C62x64.sys Wed Apr 1 01:09:17 2009 (49D2F6FD)
Atheros NIC driver
Driver Reference Table - L1C62x64.sys

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys

mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)

http://www.carrona.org/drivers/driver.php?id=mcupdate_AuthenticAMD.dll

ASACPI.sys Wed Jul 15 23:31:29 2009 (4A5E9F11)
Asus ATK0110 ACPI Utility [RED](a known BSOD maker in Win7)[/RED]. Also a part of the Asus PCProbe and AISuite Utilities
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys

AsIO.sys Mon Aug 3 03:03:16 2009 (4A768BB4)
Asus PCProbe Utility
http://www.carrona.org/drivers/driver.php?id=AsIO.sys

amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AMD storage controller driver - usually from the Windows 7 DVD
http://www.carrona.org/drivers/driver.php?id=amdxata.sys

nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
nVidia Storage Drivers
http://www.carrona.org/drivers/driver.php?id=nvstor.sys

nvstor64.sys Fri Apr 9 05:22:41 2010 (4BBEF1E1)
nVidia Storage Driver (nForce chipset driver)
http://www.carrona.org/drivers/driver.php?id=nvstor64.sys

viahduaa.sys Sat May 15 06:22:39 2010 (4BEE75EF)
VIA High Definition Audio Function Driver
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys

ccSetx64.sys Mon Aug 8 17:47:34 2011 (4E405976)
Symantec/ Norton Common Client Settings Driver
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys

cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
CPU-Z CPU monitor
http://www.carrona.org/drivers/driver.php?id=cpuz135_x64.sys

MpFilter.sys Fri Mar 9 06:05:26 2012 (4F59E3F6)
Microsoft Windows AntiMalware protection system
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys

atikmpag.sys Mon Jun 11 12:26:14 2012 (4FD61C26)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys

atikmdag.sys Mon Jun 11 12:59:31 2012 (4FD623F3)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
[url = http://www.carrona.org/drivers/driver.php?id=atikmdag.sys]http://www.carrona.org/drivers/driver.php?id=atikmdag.sys[/url]

BSOD BUGCHECK SUMMARY

Code:

[FONT=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080412-16333-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Aug  4 14:16:25.985 2012 (UTC - 4:00)
System Uptime: 0 days 0:24:32.265
BugCheck 24, {1904fb, fffff88007812078, fffff880078118d0, fffff88001234e4e}
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+de )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+de
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`07812078 fffff880`078118d0 fffff880`01234e4e
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080412-24601-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Aug  4 02:23:15.416 2012 (UTC - 4:00)
System Uptime: 0 days 12:26:58.696
BugCheck 24, {1904fb, fffff880076afaa8, fffff880076af300, fffff880012283c7}
*** 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!NtfsLookupAllocation+e7 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsLookupAllocation+e7
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`076afaa8 fffff880`076af300 fffff880`012283c7
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080312-17659-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Aug  3 13:05:02.455 2012 (UTC - 4:00)
System Uptime: 0 days 0:24:26.735
BugCheck 3B, {c0000005, fffff800030e7f6c, fffff88006c70940, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  rundll32.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030e7f6c fffff880`06c70940 00000000`00000000
BiosVersion = 0801   
BiosReleaseDate = 01/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

BSOD playing games or during downloads

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer