W7 BSOD 0x000001e

A consistent bugcheck indicates predictability, which bad hardware typically does not afford. In other words, I suspect a driver issue.

Please enable driver verifier: Driver Verifier - Enable and Disable

If Verifier doesn't flag anything, we'll start on hardware.

When you get more BSODs, please use these directions to post it: https://www.sevenforums.com/crashes-d...tructions.html


...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 16:30:03.807 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:08.384
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

That is Bit Defender. Please remove it with this tool: http://www.bitdefender.com/uninstall

Replace it with MSE: http://www.microsoft.com/security_essentials

Be sure Verifier is disabled.

I wonder if your Atheros network adapter drivers are the cause. See if you can find some updated drivers for it, on your computer manufacturer's site or another source.

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:54:30.288 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:37.864
BugCheck C4, {91, 2, fffff800031fac40, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:38:16.524 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:29.101
BugCheck 24, {1904fb, fffff88008ab96e8, fffff88008ab8f50, fffff880014c974c}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+111c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:28:44.584 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:04.160
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+464 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 22:21:36.860 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:08.047
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ndis.sys ( ndis!ndisMTimerObjectDpc+18 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 20:43:21.263 2010 (UTC - 4:00)
System Uptime: 0 days 4:16:24.465
BugCheck 3B, {c0000005, fffff80003083905, fffff88008f11940, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 16:25:53.073 2010 (UTC - 4:00)
System Uptime: 0 days 19:12:00.650
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Code:

athrx.sys    Fri Nov 06 15:56:02 2009 (4AF48D62)

Might want to install these network drivers: Realtek

Update your Logitech QuickCam drivers for the heck of it:

Code:

lvuvc64.sys  Wed Oct 07 04:28:44 2009

If the BSODs persist, start out by doing a RAM test: RAM - Test with Memtest86+

Enable driver verifier, wait for a few BSODs, and then follow these directions: https://www.sevenforums.com/crashes-d...tructions.html

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 17 15:56:55.614 2010 (UTC - 4:00)
System Uptime: 0 days 14:03:38.190
BugCheck 1E, {ffffffffc0000005, fffff88008a377e0, 0, 0}
Probably caused by : tcpip.sys ( tcpip!WfpAleFastUdpInspection+27e )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Hmm...driver verifier is not enabled in that dump. In fact, looking back, I notice that verifier wasn't enabled for any.

Please follow these directions: Driver Verifier - Enable and Disable

Reboot, then open a command prompt and enter the following:

Code:

verifier /query>%userprofile%\desktop\verifier.txt

Could you please attach the new verifier.txt file to your next post?