Windows 7 ntoskrnl.exe BSOD Please Help!

werdna63

New Member
Joined
Aug 7, 2012
Messages
8
Hello, I have been having computer crashes resulting in a BSOD for a few months now. It's really annoying, and I would like some of the more seasoned Windows 7 users to take a look at my .dmp files. The crashes always happen when I'm doing something graphically intensive, such as gaming or streaming video, and I usually crash 1-2 times a day, if that helps.
 


Attachments

Solution
I ran the last 10 memory dumps
There were 5 different BSOD error codes
and they blamed 3 different causes

Still looks like hardware as I stated above (although AMD Overdrive is still the most likely suspect).
Have you run the hardware diagnostics that I asked for? If so, what were the results?

AMD Overdrive is still installed. If you've followed all of the previous suggestions and it's still there, then try this:
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):
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*.*...
Please zip up the contents of C:/Windows/Minidump and upload it with your next post.

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 Link Removed - Invalid URL (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

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.

Please uninstall the AppleCharger program. Recently we've seen several BSOD's due to this program.

Update your ebdrv Broadcom NetXtreme II Kernel 12/31/2008 10:29:28 AM
This appears to be a wireless driver - possibly USB.
Win7 doesn't like wireless USB devices - especially with Vista era drivers
Please uninstall it's software and remove the device from your system.
To access the internet, please use either a PCI/PCIe wireless card that plugs into your motherboard - or a very long ethernet cable.

Please uninstall this driver:
GVTDrv64 GVTDrv64 Kernel 9/5/2006 2:10:02 AM
This belongs to the Gigabyte EasyTune6 program (aka ET6). Also, if you have the Easy Saver program installed, please uninstall it also - as it's known to cause problems also.

Your wired networking drivers also date from 2008 - and I believe that they're a part of your chipset drivers, so they'll have to be updated also.
 


Last edited:
Hello, and thanks for helping. I uninstalled the ET6 Drivers and program, and the AOD Driver, and uninstalled the Applecharger program. I had previously reinstalled my AMD drivers, when the issue arose, so I decided to see if just uninstalling ET6, AOD driver, and Applecharger would work. But alas, I had another BSOD about 20 minutes ago. I will reinstall the AMD drivers again, just to be sure, and I've taken out the USB Wireless card.
 


Attachments

We'll also need you to zip up and upload the contents of the C:\Windows\Minidump directory.
 


There was no memory dump from the last couple of days in the upload - the latest one was from 07 August. Check in C:\Windows for a file named MEMORY.dmp. If it is dated around the time of the last crash, please zip it up and upload it to a free file hosting service (it'll be a large file) and post a link here so that we can download it.

I ran 12 memory dumps - generated from 01 Aug 2012 to 07 Aug 2012 (7 days)
There were 6 different BSOD error codes cited
and 6 different causes blamed

This is most likely a hardware problem. They (hardware problems) are 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 (3rd party hardware/drivers)
- low-level driver problems (like the Gigabyte tools, or the AMD OverDrive)
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed - Invalid URL or Link Removed - Invalid URL ).

The steps that I posted earlier are the most likely solution - but we need further memory dumps to see what remains in the crashes.
Also, since hardware is a likely possibility here, please start running these free hardware diagnostics: Link Removed - Invalid URL

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: Link Removed
- Info on how to troubleshoot BSOD's (DRAFT): Link Removed
- How I do it: Link Removed

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:
[FONT=lucida console]
AODDriver2.sys         Tue Mar  6 04:55:00 2012 (4F55DEF4)
AppleCharger.sys       Mon Jan 10 04:57:29 2011 (4D2AD809)
AtihdW76.sys           Thu Feb 23 07:30:12 2012 (4F463154)
GEARAspiWDM.sys        Mon May 18 08:17:04 2009 (4A1151C0)
GVTDrv64.sys           Tue Sep  5 03:10:02 2006 (44FD22CA)
MpFilter.sys           Fri Mar  9 06:05:26 2012 (4F59E3F6)
NetgearUDSMBus.sys     Thu Jun 16 02:45:37 2011 (4DF9A691)
NetgearUDSTcpBus.sys   Thu Jun 16 02:38:59 2011 (4DF9A503)
RTKVHD64.sys           Tue Jul 19 08:52:18 2011 (4E257E02)
Sftfslh.sys            Fri Sep 30 12:43:06 2011 (4E85F19A)
Sftplaylh.sys          Fri Sep 30 12:43:05 2011 (4E85F199)
Sftredirlh.sys         Fri Sep 30 12:43:14 2011 (4E85F1A2)
Sftvollh.sys           Fri Sep 30 12:42:46 2011 (4E85F186)
VBoxDrv.sys            Tue May 22 08:25:38 2012 (4FBB85C2)
VBoxNetAdp.sys         Tue May 22 08:25:39 2012 (4FBB85C3)
VBoxNetFlt.sys         Tue May 22 08:25:37 2012 (4FBB85C1)
VBoxUSBMon.sys         Tue May 22 08:25:39 2012 (4FBB85C3)
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)
gdrv.sys               Thu Mar 12 23:22:29 2009 (49B9D175)
mcupdate.dll           Mon Jul 13 21:29:09 2009 (4A5BDF65)
netr28ux.sys           Thu Jan  5 07:44:48 2012 (4F059B40)
nvmf6264.sys           Thu Mar  4 20:04:39 2010 (4B9058A7)
nvstor.sys             Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys           Fri Apr  9 05:22:41 2010 (4BBEF1E1)
[/FONT]

Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL

BSOD BUGCHECK SUMMARY

Code:
[FONT=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080712-14071-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Aug  7 18:02:07.398 2012 (UTC - 4:00)
System Uptime: 0 days 3:05:56.553
BugCheck 3B, {c000001d, fffff96000077aea, fffff880074cff70, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  java.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff960`00077aea fffff880`074cff70 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080612-16738-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Aug  6 12:04:15.193 2012 (UTC - 4:00)
System Uptime: 0 days 1:24:58.348
BugCheck A, {fffff8000743dff0, 2, 1, fffff800032d3cdf}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xA
PROCESS_NAME:  java.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 0000000A
Arguments fffff800`0743dff0 00000000`00000002 00000000`00000001 fffff800`032d3cdf
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080612-14648-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Aug  6 10:38:14.171 2012 (UTC - 4:00)
System Uptime: 0 days 13:55:44.567
BugCheck 50, {fffff880fffff878, 0, fffff800035773fc, 5}
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+2c6 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObpWaitForMultipleObjects+2c6
Bugcheck code 00000050
Arguments fffff880`fffff878 00000000`00000000 fffff800`035773fc 00000000`00000005
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080512-19032-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Aug  5 20:41:27.277 2012 (UTC - 4:00)
System Uptime: 0 days 6:11:44.674
BugCheck 1E, {ffffffffc0000005, fffff800033b6dd3, 0, ff6c}
Probably caused by : afd.sys ( afd! ?? ::NNGAKEGL::`string'+2aa8 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  dndclient.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_afd!_??_::NNGAKEGL::_string_+2aa8
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`033b6dd3 00000000`00000000 00000000`0000ff6c
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080512-19531-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Aug  5 14:29:03.424 2012 (UTC - 4:00)
System Uptime: 0 days 22:07:29.072
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080412-27612-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Aug  4 14:20:04.119 2012 (UTC - 4:00)
System Uptime: 0 days 0:50:03.274
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  csrss.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080412-22526-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Aug  4 12:56:40.907 2012 (UTC - 4:00)
System Uptime: 0 days 22:27:18.396
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080212-66035-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Aug  2 19:43:31.965 2012 (UTC - 4:00)
System Uptime: 0 days 7:32:40.370
BugCheck D1, {fffff78400000008, 2, 0, fffff880018dae7d}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Rainmeter.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 000000d1
Arguments fffff784`00000008 00000000`00000002 00000000`00000000 fffff880`018dae7d
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080212-29000-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Aug  2 12:10:05.766 2012 (UTC - 4:00)
System Uptime: 0 days 13:44:05.921
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080112-23384-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  1 22:24:56.308 2012 (UTC - 4:00)
System Uptime: 0 days 5:27:58.368
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : amdppm.sys ( amdppm!ReadGenAddr+18 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_amdppm!ReadGenAddr+18
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080112-22807-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  1 16:56:20.036 2012 (UTC - 4:00)
System Uptime: 0 days 5:36:45.096
BugCheck E4, {1, fffff800034c9660, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+104aa )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xE4
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xE4_nt!_??_::FNODOBFM::_string_+104aa
Bugcheck code 000000e4
Arguments 00000000`00000001 fffff800`034c9660 00000000`00000001 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080112-31153-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  1 11:18:33.064 2012 (UTC - 4:00)
System Uptime: 0 days 11:12:06.219
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FB
BiosReleaseDate = 08/26/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]
 


Last edited:
This has the most recent ones inside, including one from 5 minutes ago. I reinstalled the AMD drivers using the method you suggested, and I'm on the internet via Ethernet cable plugged into a range extender which is extending the range of my router. Any other tips? Your help is MUCH appreciated.Link Removed
 


I ran the last 10 memory dumps
There were 5 different BSOD error codes
and they blamed 3 different causes

Still looks like hardware as I stated above (although AMD Overdrive is still the most likely suspect).
Have you run the hardware diagnostics that I asked for? If so, what were the results?

AMD Overdrive is still installed. If you've followed all of the previous suggestions and it's still there, then try this:
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):
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. That will state the location of all OverDrive drivers.
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
- un-install all ATI video stuff using Control Panel...Programs...Un-install 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: Link Removed
DO NOT install the full Catalyst Control Center package!!!

Your iBall Advanced Mouse driver dates from 2009, please update it (more info on it here: Link Removed )

Analysis:
The following is for information purposes only.
Code:
[FONT=lucida console]**************************Sat Aug 18 15:27:06.519 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081812-17799-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 20:08:48.674[/B]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 3D, {fffff88005363fd0, 0, 0, fffff800032bcb75}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+5bb75 )[/B]
BugCheck Info: [B]INTERRUPT_EXCEPTION_NOT_HANDLED (3d)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 17 19:17:41.651 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081712-15756-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 11:49:30.944[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 1E, {ffffffffc000001d, fffff800032e9626, 2, fffffa8006d41b00}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+87626 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 15 21:18:56.267 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081512-13712-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 6:38:01.722[/B]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 1E, {0, 0, 0, 0}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+7f190 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 13 11:10:33.300 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081312-17066-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 12:46:35.455[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck A, {fffff80004b9cc50, 2, 0, fffff800032e9900}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+89900 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 12 21:27:44.202 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081212-18189-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]1 days 2:11:28.561[/B]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 1E, {0, 0, 0, 0}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+7f190 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 11 13:35:10.905 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081112-15288-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 19:32:55.238[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 1E, {ffffffffc000001d, fffffa800bb46440, 2, 0}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+7f1c0 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug  8 11:08:28.406 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080812-17175-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 1:44:45.561[/B]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 1E, {0, 0, 0, 0}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+7f190 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug  7 18:02:07.398 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080712-14071-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 3:05:56.553[/B]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 3B, {c000001d, fffff96000077aea, fffff880074cff70, 0}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]win32k.sys ( win32k+27aea )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug  6 12:04:15.193 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080612-16738-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 1:24:58.348[/B]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck A, {fffff8000743dff0, 2, 1, fffff800032d3cdf}[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+9af1b )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug  6 10:38:14.171 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080612-14648-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
System Uptime:[B]0 days 13:55:44.567[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 50, {fffff880fffff878, 0, fffff800035773fc, 5}[/B]
Probably caused by :[B]ntoskrnl.exe ( nt+3713fc )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
  BIOS Version                  FB
  BIOS Release Date             08/26/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  M68MT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]


3rd Party Drivers:
The following is for information purposes only. Any drivers in red should be updated.
Code:
[FONT=lucida console]**************************Sat Aug 18 15:27:06.519 2012 (UTC - 4:00)**************************
t_mouse.sys            Thu Apr 16 09:45:37 2009 (49E73681)
GEARAspiWDM.sys        Mon May 18 08:17:04 2009 (4A1151C0)
amdiox64.sys           Thu Feb 18 10:17:53 2010 (4B7D5A21)
nvmf6264.sys           Thu Mar  4 20:04:39 2010 (4B9058A7)
amdxata.sys            Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvstor.sys             Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys           Fri Apr  9 05:22:41 2010 (4BBEF1E1)
Sftvollh.sys           Fri Sep 30 12:42:46 2011 (4E85F186)
Sftplaylh.sys          Fri Sep 30 12:43:05 2011 (4E85F199)
Sftfslh.sys            Fri Sep 30 12:43:06 2011 (4E85F19A)
Sftredirlh.sys         Fri Sep 30 12:43:14 2011 (4E85F1A2)
AtihdW76.sys           Thu Feb 23 07:30:12 2012 (4F463154)
AODDriver2.sys         Tue Mar  6 04:55:00 2012 (4F55DEF4)
MpFilter.sys           Fri Mar  9 06:05:26 2012 (4F59E3F6)
atikmpag.sys           Fri Jul 27 21:14:47 2012 (50133D07)
atikmdag.sys           Fri Jul 27 21:48:09 2012 (501344D9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 17 19:17:41.651 2012 (UTC - 4:00)**************************
usbaapl64.sys          Tue Jan 10 19:56:04 2012 (4F0CDE24)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 15 21:18:56.267 2012 (UTC - 4:00)**************************
atikmpag.sys           Mon Jun 11 12:26:14 2012 (4FD61C26)
atikmdag.sys           Mon Jun 11 12:59:31 2012 (4FD623F3)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 13 11:10:33.300 2012 (UTC - 4:00)**************************
netr28ux.sys           Thu Jan  5 07:44:48 2012 (4F059B40)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 11 13:35:10.905 2012 (UTC - 4:00)**************************
AppleCharger.sys       Mon Jan 10 04:57:29 2011 (4D2AD809)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug  8 11:08:28.406 2012 (UTC - 4:00)**************************
NetgearUDSTcpBus.sys   Thu Jun 16 02:38:59 2011 (4DF9A503)
NetgearUDSMBus.sys     Thu Jun 16 02:45:37 2011 (4DF9A691)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug  7 18:02:07.398 2012 (UTC - 4:00)**************************
RTKVHD64.sys           Tue Jul 19 08:52:18 2011 (4E257E02)
[/FONT]
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
NetgearUDSTcpBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
NetgearUDSMBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed

 


Last edited:
Solution
Back
Top