Windows 7 Blue Screen almost daily now, especially while using WMC

Based on this minidump files..yes..it is device drivers issue, however, we don't know what drivers caused BSODs yet...
Please run system file check first to make sure window system files are running properly
SFC /SCANNOW Command - System File Checker

Then, please run driver verifier to know what drivers are bads:
Using Driver Verifier to identify issues with Drivers

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.654\062710-37409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e4be50
Debug session time: Mon Jun 28 12:48:04.536 2010 (UTC + 7:00)
System Uptime: 0 days 10:51:05.284
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff88006cc6790, 80000000acab4963, fffff88006cc6250, 2}

Probably caused by : win32k.sys ( win32k!ESTROBJ::vCharPos_H1+81 )

Followup: MachineOwner
---------

Regard
Tuan

Homunculistic said:

I ran a system file check and it came back all okay, so I started verifier and everytime it booted, it would BSOD before Windows would even finish booting. I attached the 3 minidumps that generated before I killed verifier. Please let me know if I can do anything else to help narrow it down.

By the way, I'm going on vacation for the next week so I may not get a chance to work on fixing this issue until then.

Thanks again for all the help!

Peter

Ok Peter,
we have a pretty straight reasons for BSODs now.
2 things were blamed from the minidump files. First of all was your Razer Lachesis Mouse driver, and second was your Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20)
Please download and install fresh copy of them (remove all trace of old drivers from device manager before installing new update).
Here is the bugcheck:

Code:

BugCheck C4, {f6, 818181810000015c, fffffa80079729c0, fffff880041c85cd}

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

Followup: MachineOwner
---------
BugCheck A, {fffff8a000001998, 2, 1, fffff80002f7980a}

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+f138 )

Followup: MachineOwner
---------

Hope you have safe&sounds trip
~Tuan

I couldn't see much from the minidump this time, they dont blame any specific drivers. However, there is an exception code in the minidump that suggest this might be memory corruption. I would download third party called memtest86, burn it to CD and let it run for at least 6,7 passes

Code:

BugCheck A, {e, 2, 1, fffff80002cf031b}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, 102c7d853, 8, 102c7d853}

Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )

Followup: MachineOwner
---------

Also, I doubt this can be service in startup issue, please also run clean boot to know what cause BSODs
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

~Tuan

Please turn off driver verifier for now and see if BSODs has gone, I also want to give u a quote:

- The purpose of testing all 3rd party drivers is to see if they are the problem. Most BSOD's are caused by issues with 3rd party drivers - so that's why we test them.
- If there are no BSOD's within 36 hours (my estimate), then it's most likely that you either have a Windows problem or a hardware problem. To rule out Windows drivers - run Driver Verifier on all Windows (aka Microsoft) drivers. If still no errors, then try a clean install without any extra programs (but all updates).
- If you're testing 3rd party drivers and you get a Driver Verifier BSOD that mentions Windows drivers - then (again) it's most likely a hardware issue or a Windows issue.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

What third party Antivirus software are you using?
Hardware was blamed in the dmp with cdd.dll, which is a canonical display driver, but probably it's not the cause
0x50 bugchecks can be extremely difficult to solve as hardware issues generally come into play. Do you overclock anything?
Update your directx if possible:
http://www.microsoft.com/downloads/d...displaylang=en

Then run this free video stress test:
FurMark

Code:

BugCheck 50, {ffffffffffffff8b, 0, fffff8801491c987, 0}

Unable to load image \SystemRoot\System32\cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll

Could not read faulting driver name
Probably caused by : hardware ( dxgkrnl!DxgkCddSetPointerPosition+1f )

Followup: MachineOwner
---------

This might be a hard case if it is hardware related and I might need other experts in this forum to help you out

However, I've given you something to try, please follow it. You've said run memtestx86 for at least 6,7 passes right, I need u to use memtestx86 in case u use different one.

Regard,

Tuan