Intermittent BSOD, no common activity.

Hello yall,

Having an issue with intermittent BSOD with no common activity. Decided to turn blue during idle, surfing the web and playing games. I am not over clocking but i do have the RAM set to what OCZ recommended, DRAM frequency to 1333Mhz, CPU/NB voltage to 1.2v, DRAM Voltage 1.65v, DRAM timings to 9-9-9-20. Currents set up is as follows.

OS: Win 7 64bit SP1
Mobo: Asus M4A79T deluxe
CPU: AMD Phenom II 965 @ 3.4 Ghz
Bios: 3505
RAM: OCZ Reaper 4x4Gb OCZ3RPR1333C9LV8G8
GPU: 2X MSI/ATI Radeon 5770 HD in crossfire
PSU: Kingwin Lazer 750W

I ran Memtest+ on all four sticks, then ran them all induvidualy with no errors. I compressed and attached all files as per your instructions.

Thanks for your time!

Do you still need assistance with this topic?

Yes please.

You have a NETGEAR WG111v3 Wireless-G USB Adapter
Windows 7 doesn't like these devices, especially if they use Vista era drivers - they'll spit out BSOD's rapidly in that case!
Here's my rant on these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

You have a problem with a Virtual USB Bus Enumerator. I'm uncertain as to what program it belongs to, but you should look into removing it (you'll find it in Device Manager - but you may have to enable hidden devices in order to see it).

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.

Update your Asus motherboard utilities (all of them) - some date from as early as 2007. You can find them at the Asus website for your motherboard. If there are no more recent versions available, post back for advice on which to get rid of and which to keep.

You have a Data Filter Driver and a Hardlock Device Driver by Aladdin Knowledge Systems that date from 2006. Please uninstall that program from your 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. While waiting for a reply, please run Driver Verifier according to these instructions: Driver Verifier Settings

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:

AODDriver2.sys              Tue Mar  6 04:55:00 2012 (4F55DEF4)
ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
AsIO.sys                    Mon Dec 17 04:11:49 2007 (47663D55)
AtiPcie.sys                 Tue May  5 11:00:22 2009 (4A005486)
AtihdW76.sys                Thu Feb 23 07:30:12 2012 (4F463154)
EIO64.sys                   Tue Jul 21 22:34:42 2009 (4A667AC2)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
RTKVHD64.sys                Thu May 31 05:21:30 2012 (4FC7381A)
Rt64win7.sys                Fri Jan 21 02:34:00 2011 (4D3936E8)
Sentinel64.sys              Mon Jun  2 02:14:55 2008 (48438FDF)
aksdf.sys                   Wed Dec 13 12:09:32 2006 (458033CC)
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)
atikmpag.sys                Mon Jun 11 12:26:14 2012 (4FD61C26)
avgidsdrivera.sys           Fri Dec 23 07:05:21 2011 (4EF46E81)
avgidsfiltera.sys           Fri Dec 23 07:05:40 2011 (4EF46E94)
avgidsha.sys                Wed Apr 18 22:19:15 2012 (4F8F7623)
avgldx64.sys                Tue Feb 21 22:57:53 2012 (4F4467C1)
avgmfx64.sys                Fri Dec 23 07:08:12 2011 (4EF46F2C)
avgrkx64.sys                Mon Jan 30 22:11:41 2012 (4F275BED)
avgtdia.sys                 Sun Mar 18 23:53:32 2012 (4F66ADBC)
cpuz134_x64.sys             Fri Jul  9 07:16:58 2010 (4C37052A)
dc3d.sys                    Wed May 18 04:07:24 2011 (4DD37E3C)
hardlock.sys                Thu Nov 30 12:12:07 2006 (456F10E7)
lvuvc64.sys                 Wed Jan 18 01:41:08 2012 (4F166984)
point64.sys                 Fri Apr  8 18:58:14 2011 (4D9F9306)
speedfan.sys                Sat Dec 18 06:03:51 2010 (4D0C9517)

Driver Reference Table - AODDriver2.sys
Driver Reference Table - ASACPI.sys
Driver Reference Table - AsIO.sys
Driver Reference Table - AtiPcie.sys
Driver Reference Table - AtihdW76.sys
Driver Reference Table - EIO64.sys
Driver Reference Table - PxHlpa64.sys
Driver Reference Table - RTKVHD64.sys
Driver Reference Table - Rt64win7.sys
Driver Reference Table - Sentinel64.sys
Driver Reference Table - aksdf.sys
Driver Reference Table - amdiox64.sys
Driver Reference Table - amdxata.sys
Driver Reference Table - atikmdag.sys
Driver Reference Table - atikmpag.sys
Driver Reference Table - avgidsdrivera.sys
Driver Reference Table - avgidsfiltera.sys
Driver Reference Table - avgidsha.sys
Driver Reference Table - avgldx64.sys
Driver Reference Table - avgmfx64.sys
Driver Reference Table - avgrkx64.sys
Driver Reference Table - avgtdia.sys
Driver Reference Table - cpuz134_x64.sys
Driver Reference Table - dc3d.sys
Driver Reference Table - hardlock.sys
Driver Reference Table - lvuvc64.sys
Driver Reference Table - point64.sys
Driver Reference Table - speedfan.sys

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080112-82384-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  1 20:06:07.517 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:53.000
BugCheck D1, {3e, 2, 1, fffff88002438002}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cdrom!DeviceEvtIoInCallerContext+1ad
Bugcheck code 000000d1
Arguments 00000000`0000003e 00000000`00000002 00000000`00000001 fffff880`02438002
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080112-63757-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  1 19:43:52.622 2012 (UTC - 4:00)
System Uptime: 0 days 0:54:03.731
BugCheck 50, {fffff8800af5a64c, 8, fffff8800af5a64c, 0}
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : spsys.sys ( spsys+2c50c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_spsys+2c50c
Bugcheck code 00000050
Arguments fffff880`0af5a64c 00000000`00000008 fffff880`0af5a64c 00000000`00000000
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\073112-82852-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jul 31 18:53:05.518 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:00.000
BugCheck D1, {fffff88002497f6a, 2, 8, fffff88002497f6a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_cdrom!DeviceEvtIoInCallerContext+1ad
Bugcheck code 000000d1
Arguments fffff880`02497f6a 00000000`00000002 00000000`00000008 fffff880`02497f6a
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\073112-83320-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jul 31 18:44:40.517 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:28.000
BugCheck D1, {fffff880025a9f6a, 2, 8, fffff880025a9f6a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_cdrom!DeviceEvtIoInCallerContext+1ad
Bugcheck code 000000d1
Arguments fffff880`025a9f6a 00000000`00000002 00000000`00000008 fffff880`025a9f6a
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\073012-86611-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 30 19:36:43.519 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:44.002
BugCheck D1, {fffff88002497f6a, 2, 8, fffff88002497f6a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_cdrom!DeviceEvtIoInCallerContext+1ad
Bugcheck code 000000d1
Arguments fffff880`02497f6a 00000000`00000002 00000000`00000008 fffff880`02497f6a
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072912-93007-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 29 20:54:57.517 2012 (UTC - 4:00)
System Uptime: 0 days 0:16:47.000
BugCheck D1, {3e, 2, 1, fffff88002438002}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cdrom!DeviceEvtIoInCallerContext+1ad
Bugcheck code 000000d1
Arguments 00000000`0000003e 00000000`00000002 00000000`00000001 fffff880`02438002
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072612-53149-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul 26 22:36:30.502 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:32.000
BugCheck D1, {3e, 2, 1, fffff88002438002}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cdrom!DeviceEvtIoInCallerContext+1ad
Bugcheck code 000000d1
Arguments 00000000`0000003e 00000000`00000002 00000000`00000001 fffff880`02438002
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072612-74084-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul 26 22:26:05.112 2012 (UTC - 4:00)
System Uptime: 0 days 0:53:13.595
BugCheck D1, {5, 2, 1, fffff880048dd574}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmdag.sys ( atikmdag+c6574 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_atikmdag+c6574
Bugcheck code 000000d1
Arguments 00000000`00000005 00000000`00000002 00000000`00000001 fffff880`048dd574
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072112-95067-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 21 23:11:42.566 2012 (UTC - 4:00)
System Uptime: 0 days 1:01:18.690
BugCheck D1, {7010, 2, 1, fffffa800a3c7d6a}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+1acc40 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0xD1_atikmdag+1acc40
Bugcheck code 000000d1
Arguments 00000000`00007010 00000000`00000002 00000000`00000001 fffffa80`0a3c7d6a
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071512-90230-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 15 04:02:19.168 2012 (UTC - 4:00)
System Uptime: 0 days 1:18:32.667
BugCheck 116, {fffffa8013220170, fffff88002d69250, 0, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+9250 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`13220170 fffff880`02d69250 00000000`00000000 00000000`00000002
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Thank you sir, I will do as you said and report back. Thanks again.

I forgot one program - Rainbow Tech/SafeNet USB Security Device
This uses the sentinel64.sys driver that dates from 2008.
This is likely the device with the problem that I mentioned in the 2nd paragraph above (the USB Bus Enumerator) - and since it dates from 2008 it's likely that it's not compatible with Win7. Please uninstall it and remove the device from your system.

Here is what i have come up with. Over the past couple days i have followed your instructions trying one thing at a time and waiting to see if any difference was made.

First stared off with uninstalling the Netgear stuff as i run my internet connection wired now its no big deal. Also uninstalled the problematic USB Enumerator, hardlock, Sentinal and aksdf drivers. Still BSOD.

I changed all my Mobo factory settings to default, I then got rid of catalyst control center and updated just the drivers as per your instructions. Still reciving BSOD.

Today i went back and verified AODDriver2 was in fact uninstalled and it wasn't, i uninstalled it.

I went through the Driver Verifier Settings instructions to find that the ASACPI driver was causing BSOD on the 3 start ups i let the machine go through. Went through the ASUS Utilities and updated the Cool and Quiet and ATK0110 Driver for Win7, and what do you know, it contained the ASACPI driver. So went through the device manager and tried to manually update the ASACPI driver under the Non-Plug and Play drop down and it said the latest version has already been installed, but then told me some settings have changed and has to reboot. hummm, alrighty then.

On the topic of ASUS Utilities There is only 3 other updates for my Mobo from 2009 which include, IM software patch for ExpressGate, ASUS PC Probe II and Ai Charger 1.00.06 for WinXP/Vista/Win7 32bit and 64bit Charge your iPhone / iPod / iPad through USB port quickly. I don't own and iproducts so don't really need the last but do you think these other two utilities need to be utilized?

I went ahead and zipped up another SF Diag Tool folder for your inspection to make sure there was nothing i missed.

Thank you again for providing amazing support!!!

EDIT: I guess i never stated that i have not experenced any BSOD after the last update of the ASACPI driver. However that was only less than an hour ago. I will report back if anything happens.

Please ensure that Driver Verifier is turned off - the last 4 memory dumps were Verifier Enabled - and all blamed ASACPI.sys

You may want to update the PCProbe program also - but I'd hold off until you see if the ASACPI.sys problem is fixed (PCProbe also contains a version of ASACPI.sys).

Recently we've seen a lot of problems with USB charger utility programs - so in general I suggest removing them unless you have a need for them (and if you do have a need, I suggest removing it for testing - then putting it back on if it's still needed).

I'm generally in favor of installing patches if you have the base program installed. I haven't even looked at the Asus ExpressGate program in years so I don't even know what it does.

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:

ASACPI.sys     Wed May 13 21:25:17 2009 (4A0B72FD)
AsIO.sys       Mon Dec 17 04:11:49 2007 (47663D55)
AtiPcie.sys    Tue May  5 11:00:22 2009 (4A005486)
AtihdW76.sys   Tue Dec  6 04:14:25 2011 (4EDDDCF1)
EIO64.sys      Tue Jul 21 22:34:42 2009 (4A667AC2)
MpFilter.sys   Fri Mar  9 06:05:26 2012 (4F59E3F6)
PxHlpa64.sys   Tue Oct 20 14:08:42 2009 (4ADDFCAA)
RTKVHD64.sys   Tue Jun 19 04:50:56 2012 (4FE03D70)
Rt64win7.sys   Fri Jun 10 02:33:15 2011 (4DF1BAAB)
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)
dc3d.sys       Sun May 27 10:20:12 2012 (4FC2381C)
point64.sys    Fri Apr  8 18:58:14 2011 (4D9F9306)
speedfan.sys   Sat Dec 18 06:03:51 2010 (4D0C9517)

http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=AtiPcie.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=EIO64.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=dc3d.sys
http://www.carrona.org/drivers/driver.php?id=point64.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081312-56550-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Aug 13 20:36:10.471 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:48.595
BugCheck C4, {f6, 1ac, fffffa80100d5b30, fffff88004195257}
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xc4_f6
PROCESS_NAME:  QButton.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_ASACPI+1257
Bugcheck code 000000c4
Arguments 00000000`000000f6 00000000`000001ac fffffa80`100d5b30 fffff880`04195257
BiosVersion = 3503   
BiosReleaseDate = 05/06/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Ok, I updated express gate, have not updated PCProbe, did not install the charging utility, and now im seeing BSOD from the PCIIDEX and HIDCLASS along with a ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY. Would a fresh windows install be an easier option?

2006 version of hardlock is back, please ensure that it's uninstalled from your system.

If that's the case, then I'd suggest a clean install of Windows.
If no problems appear - then it was either a 3rd party driver problem or a Windows problem
If the problems keep on happening, then it's a hardware problem.

Here's how I suggest you do a clean install:

Back-up, 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. Back-up 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 anti--virus in order to locate and remove any mal-ware.
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:
KillDisk ( Freeware Download Active@ KillDisk ).
DBAN ( DBAN Download | Darik's Boot And Nuke )
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

8. Visit Windows Update and get any other available updates

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

10. Test to see if the problem remains.
If the problems persist, then the problem is most likely with your hardware.
If the problems are gone, then proceed with installing the latest version of your favorite programs, testing after each one for errors.

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!!!