Windows 7 BSOD Of Death

[Topper1]

Hi,
I tried all the usual fixes and still get this increasingly frequent BSOD.

Asus P5QPL-AM
Pentium Dual-Core E6500 @2.93GHz
Windows 7 Ultimate (64bit) Service Pack 1
NVIDIA GeForce 9500GT.

Ran Avira Antivirus Rescue System disc
Uninstalled Avira Antivirus
Ran MemTest
Ran CHKDSK
Tried to update drivers manually via Windows but y'know...

Hope someone can shed some light.
Thank you!

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck D1, {28, 2, 0, fffff8800161a360}


Unable to load image \SystemRoot\system32\DRIVERS\L1E62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+79e9 )

Please update your bios:
BiosVersion = 0405
BiosReleaseDate = 01/29/2010

Link Removed

Please update your Ethernet driver
L1E62x64.sys Mon Mar 29 03:08:44 2010:

Link Removed

Please uninstall Deamon tools:
sptd.sys Sun Oct 11 21:55:14 2009

This is a known cause of bsod's in win 7.

 

[Topper1]

Thanks for your time!
I will do that...I already tried to update that Atheros driver (it's caused problems before...) but couldn't find one newer - infact I couldn't even find one as up-to-date as the one I have installed (1.0.0.49) but I'll try and uninstall/reinstall it anyway ....and get back to you later.
THANKS again.

 

[kemical]

Your very welcome. I checked the driver on the link I gave for the Atheros and I'm sure it was slightly later than yours (only by a month) unless I misread which is entirely possible lol..
If the bsod's continue can you post the new dmp file, ta..

 

[Topper1]

Your very welcome. I checked the driver on the link I gave for the Atheros and I'm sure it was slightly later than yours (only by a month) unless I misread which is entirely possible lol..
If the bsod's continue can you post the new dmp file, ta..

Hi again,
so i uninstalled Daemon and installed the Atheros driver and before I updated my BIOS I had another BSOD, I don't know if that tells you anything. The BIOS are updated now so I'll wait and see...and get back to you regardless...
PS: (Probably a dumb question as it's the wrong kind of error but out of curiosity...) These IRQs not a cause for concern???

 

[Topper1]

Hi, had another crash about 10 hours after the last one. Here's the dump. Thanks again...

 

[usasma]

Just my 2¢:

Don't worry about the IRQ's (and they're different things from the IRQL's listed in BSOD's)

I can't see how many updates your have (no systeminfo.txt report in the uploaded reports), please check Windows Updates and get ALL available updates

Your external drive is at approx 10% free space. Please try to remain at 15% free space on ALL hard drives for adequate performance from Windows.

This device is disabled:

D-Link WDA-2320 Desktop Adapter PCI\VEN_168C&DEV_0013&SUBSYS_3A1B1186&REV_01\4&B244743&0&08F0 This device is disabled.

As you are having networking issues - please uninstall the software for this device and then physically remove the device from your system. If needed, feel free to re-install it after we've finished troubleshooting.

Please turn off Driver Verifier. It's done it's job (identifying the networking Driver that kemical pointed out), so it's no longer needed (and it slows your system down and it's also designed to cause BSOD's). To turn it off, please open up verifier.exe and select "Delete existing settings", then click on the "Finish" button. Reboot for the changes to take affect.

sptd.sys (from Daemon Tools) is still present in the latest dump files. Please follow these instructions to ensure that 1) Daemon Tools is removed and 2) that the troublesome sptd.sys driver is removed from your system (it doesn't usually uninstall when you uninstall Daemon Tools):
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I strongly suspect that this hold true for Win8 systems also.

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

If all the stuff in this post (including the driver updates below) doesn't fix the BSOD's. Please post back with the latest memory dumps and we'll work from there (but I suspect stopping Driver Verifier and the sptd.sys removal will fix it).

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

pcouffin.sys Tue Dec 5 09:39:30 2006 (457584A2)
low level access layer for CD devices (A part of many different CD/DVD burning programs)
Link Removed

RimUsb_AMD64.sys Mon May 14 12:06:16 2007 (464888F8)
Blackberry Device Driver
Link Removed

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed

intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
Intel IDE storage driver
Link Removed

sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
Link Removed

Disregard these - they are dynamic drivers from Daemon Tools:

aq47hy4r.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

aqd7un0c.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

ar5oy97s.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

af73ld1o.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

absw92xt.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

ai2ya3hp.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

azdh5hba.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

azvclq3f.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

ao3idu9l.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

aqghf759.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

a1t3zemf.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

amhe65i1.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

aqpy7rpt.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

a21hrqse.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

azthz05e.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

ahv2zqme.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

aixgr416.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

ax87je83.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)

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

Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Sun Jan 27 00:53:36.049 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012613-30825-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 5:42:14.578[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+7a0c )[/B]
BugCheck [B]D1, {fffff9801658ae80, 2, 0, fffff8800559ea0c}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff9801658ae80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800559ea0c, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_L1E62x64+7a0c[/B]
  BIOS Version                  0414   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 18:22:50.880 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012613-31465-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:36:00.394[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+7a0c )[/B]
BugCheck [B]D1, {fffff98009f52e60, 2, 0, fffff88008878a0c}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff98009f52e60, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88008878a0c, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]firefox.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_L1E62x64+7a0c[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 14:13:56.208 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012613-31090-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:27:33.722[/B]
*** WARNING: Unable to verify timestamp for L1E60x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E60x64.sys
Probably caused by :[B]L1E60x64.sys ( L1E60x64+7598 )[/B]
BugCheck [B]D1, {fffff98014fc0e80, 2, 0, fffff88004a4d598}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff98014fc0e80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004a4d598, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]uTorrent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_L1E60x64+7598[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 02:23:42.798 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012513-39140-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:08:36.312[/B]
*** WARNING: Unable to verify timestamp for L1E60x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E60x64.sys
Probably caused by :[B]L1E60x64.sys ( L1E60x64+7598 )[/B]
BugCheck [B]D1, {fffff98026a2ee80, 2, 0, fffff88004071598}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff98026a2ee80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004071598, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]uTorrent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_L1E60x64+7598[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 02:06:52.859 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012513-28891-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:22:03.373[/B]
*** WARNING: Unable to verify timestamp for L1E60x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E60x64.sys
Probably caused by :[B]L1E60x64.sys ( L1E60x64+7598 )[/B]
BugCheck [B]D1, {fffff9802bdeae80, 2, 0, fffff880043e8598}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff9802bdeae80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880043e8598, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]uTorrent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_L1E60x64+7598[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 01:31:38.912 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012513-32042-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:44:14.426[/B]
*** WARNING: Unable to verify timestamp for L1E60x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E60x64.sys
Probably caused by :[B]L1E60x64.sys ( L1E60x64+7598 )[/B]
BugCheck [B]D1, {fffff98034f48e80, 2, 0, fffff88003c71598}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff98034f48e80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003c71598, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
PROCESS_NAME: [B]uTorrent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_L1E60x64+7598[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 16:52:17.418 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012413-27861-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:49:14.948[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff88004a078dc, fffff88009637150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004a078dc, Address of the instruction which caused the bugcheck
Arg3: fffff88009637150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 13:01:52.970 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012413-26660-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 2:04:46.484[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff88004a078dc, fffff88008e85150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004a078dc, Address of the instruction which caused the bugcheck
Arg3: fffff88008e85150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 07:15:26.362 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012413-26176-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:28:57.876[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff88004a078dc, fffff88008b0c150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004a078dc, Address of the instruction which caused the bugcheck
Arg3: fffff88008b0c150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 03:45:18.298 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012413-27066-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:33:56.687[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880055ed8dc, fffff88008b10150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880055ed8dc, Address of the instruction which caused the bugcheck
Arg3: fffff88008b10150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 03:10:12.744 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012413-29296-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:22:48.258[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880055f48dc, fffff880071cf150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880055f48dc, Address of the instruction which caused the bugcheck
Arg3: fffff880071cf150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 02:46:15.260 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-29172-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:19:45.774[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880041b48dc, fffff88008d6f150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880041b48dc, Address of the instruction which caused the bugcheck
Arg3: fffff88008d6f150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 23:42:51.535 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-26254-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:22:17.049[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880055e68dc, fffff88008653150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880055e68dc, Address of the instruction which caused the bugcheck
Arg3: fffff88008653150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 22:45:21.689 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-26067-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:55:15.203[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880040718dc, fffff8800283e150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880040718dc, Address of the instruction which caused the bugcheck
Arg3: fffff8800283e150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 20:36:56.290 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-29187-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]1 days 7:50:36.804[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880055c08dc, fffff88002837150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880055c08dc, Address of the instruction which caused the bugcheck
Arg3: fffff88002837150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 22 00:46:36.925 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012113-28376-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:13:01.439[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]D1, {100000010325, 2, 0, fffff88003c718dc}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000100000010325, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003c718dc, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 22 00:32:48.479 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012113-28189-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:10:15.008[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880041728dc, fffff8800868b150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880041728dc, Address of the instruction which caused the bugcheck
Arg3: fffff8800868b150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 20 22:02:44.564 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012013-26598-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:10:27.078[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff880055f18dc, fffff88009560150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880055f18dc, Address of the instruction which caused the bugcheck
Arg3: fffff88009560150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 20 15:56:38.755 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012013-27034-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:13:10.269[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]3B, {c0000005, fffff8800557f8dc, fffff880098af150, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800557f8dc, Address of the instruction which caused the bugcheck
Arg3: fffff880098af150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 18 13:30:36.787 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011813-26176-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 19:49:42.176[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]D1, {a8f229, 2, 0, fffff88002fc38dc}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000a8f229, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88002fc38dc, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]emule.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_L1E62x64+78dc[/B]
  BIOS Version                  0405   
  BIOS Release Date             01/29/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Sun Jan 27 00:53:36.049 2013 (UTC - 5:00)**************************
[B]pcouffin.sys                Tue Dec  5 09:39:30 2006 (457584A2)[/B]
[B]AsUpIO.sys                  Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[B]intelide.sys                Mon Jul 13 19:19:48 2009 (4A5BC114)[/B]
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
[B]sptd.sys                    Sun Oct 11 16:55:14 2009 (4AD24632)[/B]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
L1E62x64.sys                Sun Mar 28 22:08:44 2010 (4BB00BAC)
stdriver64.sys              Sun Dec 12 22:30:59 2010 (4D059373)
nvBridge.kmd                Fri Jan  7 20:57:22 2011 (4D27C482)
avkmgr.sys                  Wed Sep 19 04:31:52 2012 (505982F8)
avipbb.sys                  Thu Nov 22 05:13:46 2012 (50ADFADA)
avgntflt.sys                Mon Nov 26 11:20:26 2012 (50B396CA)
nvlddmkm.sys                Sat Dec 29 01:47:52 2012 (50DE9218)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 14:13:56.208 2013 (UTC - 5:00)**************************
[B]aqpy7rpt.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
L1E60x64.sys                Sun Mar 28 22:06:46 2010 (4BB00B36)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 02:23:42.798 2013 (UTC - 5:00)**************************
[B]aq47hy4r.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 02:06:52.859 2013 (UTC - 5:00)**************************
[B]aqd7un0c.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 26 01:31:38.912 2013 (UTC - 5:00)**************************
[B]ar5oy97s.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
avkmgr.sys                  Thu Sep 15 09:36:11 2011 (4E71FF4B)
avgntflt.sys                Tue Apr 24 02:14:35 2012 (4F9644CB)
avipbb.sys                  Thu Apr 26 06:12:40 2012 (4F991F98)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 16:52:17.418 2013 (UTC - 5:00)**************************
[B]af73ld1o.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 13:01:52.970 2013 (UTC - 5:00)**************************
[B]absw92xt.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 07:15:26.362 2013 (UTC - 5:00)**************************
[B]ai2ya3hp.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 03:45:18.298 2013 (UTC - 5:00)**************************
[B]azdh5hba.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 03:10:12.744 2013 (UTC - 5:00)**************************
[B]azvclq3f.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan 24 02:46:15.260 2013 (UTC - 5:00)**************************
[B]ao3idu9l.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 23:42:51.535 2013 (UTC - 5:00)**************************
[B]aqghf759.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 22:45:21.689 2013 (UTC - 5:00)**************************
[B]a1t3zemf.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan 23 20:36:56.290 2013 (UTC - 5:00)**************************
[B]amhe65i1.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 22 00:46:36.925 2013 (UTC - 5:00)**************************
[B]RimUsb_AMD64.sys            Mon May 14 12:06:16 2007 (464888F8)[/B]
[B]a21hrqse.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 22 00:32:48.479 2013 (UTC - 5:00)**************************
[B]azthz05e.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 20 22:02:44.564 2013 (UTC - 5:00)**************************
[B]ahv2zqme.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 20 15:56:38.755 2013 (UTC - 5:00)**************************
[B]aixgr416.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jan 18 13:30:36.787 2013 (UTC - 5:00)**************************
[B]ax87je83.SYS                Tue Jul 14 17:12:55 2009 (4A5CF4D7)[/B]
[/FONT]

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
Link Removed
Link Removed
aqpy7rpt.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
aq47hy4r.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.
aqd7un0c.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
ar5oy97s.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
Link Removed
Link Removed
af73ld1o.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.
absw92xt.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.
ai2ya3hp.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.
azdh5hba.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.
azvclq3f.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.
ao3idu9l.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.
aqghf759.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.
a1t3zemf.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.
amhe65i1.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
a21hrqse.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.
azthz05e.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.
ahv2zqme.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.
aixgr416.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.
ax87je83.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.

 

[usasma]

Duplicate post deleted.

 

[kemical]

Much thanks John your input is extremely welcome as well as your expertise.

 

[usasma]

Writing fm my phone...

P5 series mobos sometimes have issues w/Auto setting in BIOS for memory
I suggest getting memory settings fm RAM mfr and using them in the BIOS
In other words - DO NOT use the Auto setting!

Good luck!

 

[Topper1]

Thank You Usasma, I've followed the steps you said and I'm currently trying to update those remaining drivers. I'll keep you and Kemical posted regarding any future BSODs (or lack thereof...)
THANKS again!

 

[Topper1]

Writing fm my phone...

P5 series mobos sometimes have issues w/Auto setting in BIOS for memory
I suggest getting memory settings fm RAM mfr and using them in the BIOS
In other words - DO NOT use the Auto setting!

Good luck!

Hi again,
I'm not sure how to go about this...I have two different modules from different manufacturers, does that matter?

 

[usasma]

Yes it does matter that they are un-matched sticks..

Option 1 - don't mess with it right now and see if the BSOD's stop anyway. If not, then you can mess with it.
Option 2 - post over in the Hardware forums ( Link Removed ) for more expert advice on how to do this.

 

[kemical]

Hi,

Topper do you know how to access your bios? Usually it's accessed by pressing either delete or F2 on the keyboard as soon as you see the first boot screen. You might miss it first time around so keep trying if you do.
Once in the bios you go check through each section by using the enter key for access and the escape key to exit. Once you find the RAM settings change the timings from auto to manual. You can then go down the list making sure the timings are correct.
I checked your timings for both the PNY and Hynix sticks and they are both at 6,6,6, 18. It might well be the case that the settings are already set up as intended but just check anyway.

 

[Topper1]

Three days later and no BSODs. I think I'm out-of-the-woods, I would like to thank those two gentlemen (or women) Kemical and Usasma who helped me out. THANKS!

 

[Topper1]

It's back... could it be something to do with a bad USB/phone/SD card connection?
Here's the dump...

 

[koolkat77]

Please remove Avira Antivirus with its removal tool:

• Link Removed

Replace with MS security essentials and Malwarebytes (free):

• Microsoft Security Essentials - Microsoft Windows
• Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer

Make a full scan with both separately after installation.

Perform a system file check as explained in this link:

• Link Removed

Run Disk Check on your hard drive:

• Link Removed

Let us know the results.

 

[usasma]

sptd.sys (from Daemon Tools) is still installed. Please remove it using this removal tool:

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Memory dumps all blame the network driver:
L1E62x64.sys Sun Mar 28 22:08:44 2010 (4BB00BAC)
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20)
Link Removed
Please update it. If unable to update it, please post back to let us know

Yes, a bad USB/phone/SD card connection could also cause these problems. If uncertain, please run Driver Verifier according to these instructions: Link Removed

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed

intelide.sys Mon Jul 13 19:19:48 2009 (4A5BC114)
Intel IDE storage driver
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Mon Feb 11 19:44:24.585 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021113-29952-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:21:17.114[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+79e9 )[/B]
BugCheck [B]D1, {28, 2, 0, fffff88001641360}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001641360, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  emule.exe
FAILURE_BUCKET_ID: [B]X64_0xD1_L1E62x64+79e9[/B]
  BIOS Version                  0414   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Feb 11 00:35:35.451 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021013-25755-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 2:15:08.980[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+78dc )[/B]
BugCheck [B]D1, {171e2, 2, 0, fffff880055e88dc}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000000171e2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880055e88dc, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  emule.exe
FAILURE_BUCKET_ID: [B]X64_0xD1_L1E62x64+78dc[/B]
  BIOS Version                  0414   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Feb 10 22:19:32.169 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021013-26083-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 11:50:29.155[/B]
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by :[B]L1E62x64.sys ( L1E62x64+79e9 )[/B]
BugCheck [B]D1, {28, 2, 0, fffff880016d3360}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016d3360, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  emule.exe
FAILURE_BUCKET_ID: [B]X64_0xD1_L1E62x64+79e9[/B]
  BIOS Version                  0414   
  BIOS Release Date             06/11/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Mon Feb 11 19:44:24.585 2013 (UTC - 5:00)**************************
[B]AsUpIO.sys                  Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[B]intelide.sys                Mon Jul 13 19:19:48 2009 (4A5BC114)[/B]
[B]ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)[/B]
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
L1E62x64.sys                Sun Mar 28 22:08:44 2010 (4BB00BAC)
stdriver64.sys              Sun Dec 12 22:30:59 2010 (4D059373)
nvBridge.kmd                Fri Jan  7 20:57:22 2011 (4D27C482)
RTKVHD64.sys                Tue Jun 28 07:09:04 2011 (4E09B650)
RimSerial_AMD64.sys         Wed Jul  6 19:20:01 2011 (4E14EDA1)
[B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B]
mbam.sys                    Mon Aug 20 12:49:41 2012 (50326AA5)
avkmgr.sys                  Wed Sep 19 04:31:52 2012 (505982F8)
avipbb.sys                  Thu Nov 22 05:13:46 2012 (50ADFADA)
avgntflt.sys                Mon Nov 26 11:20:26 2012 (50B396CA)
nvlddmkm.sys                Sat Dec 29 01:47:52 2012 (50DE9218)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Feb 11 00:35:35.451 2013 (UTC - 5:00)**************************
RimSerial_AMD64.sys         Tue Jan  9 11:50:11 2007 (45A3C7C3)
[/font]

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
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Topper1]

Okay, first THANKS for your time (again.)
I keep trying to reinstall the Atheros driver (L1E62x64.sys) but it keeps telling me that I'm current have the latest driver installed...
I can't find the other two drivers you listed (Link Removed) & (Link Removed)
I ran the verifier and had a crash just now, I'm running the diagnostic tool now and will post.

Link Removed: Hi, Thanks for your time too.... I uninstalled Avira, ran the Removal Tool, installed MS Security Essentials and scanned, ran the System File Checker and there were issues but I can't open the report. I will enclose the report with the newest W7F Diagnostic report/dump.
I'll run CHKDSK tomorrow but I did that a couple of weeks ago and there were no errors...

THANKS AGAIN
Okay so I have exceeded some upload limit and can't upload the dump.

 

[usasma]

Try un-installing the old Atheros driver before installing the freshly downloaded one. It may be that the one on your system is corrupted and the new one may fix that corruption.

Don't worry about the other 2 drivers at this point (AsUpIO.sys and intelide.sys) - we'll work on them later if needed.

Upload the reports/memory dumps to a free file-hosting service on the web and post a link to it here.