BSOD during WMC viewing?

Sorry you are having problems. I will take a look.

One of the dumps is a Driver Verifier enabled dump with an error code of 1A. This dump point to memory corruption and does not give us a specific driver.

The other dump shows and error code of D1; but this dump is corrupted. It does not give us the cause. Error code D1 is usually caused by a device driver.

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\090510-30593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83240000 PsLoadedModuleList = 0x83388810
Debug session time: Sun Sep  5 21:47:38.380 2010 (GMT-4)
System Uptime: 0 days 7:03:54.740
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
........................
2: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, c002c0e8, 7a8af867, a9a13138}

Probably caused by : memory_corruption ( nt!MiGetPageProtection+1a6 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041201, The subtype of the bugcheck.
Arg2: c002c0e8
Arg3: 7a8af867
Arg4: a9a13138

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 832ede7a to 832ec5c0

STACK_TEXT:  
a706bc10 832ede7a a706bc98 8afb5620 8acae7e0 nt!MiGetPageProtection+0x1a6
a706bc3c 832e5968 0581d000 a9a13138 8acae7e0 nt!MiQueryAddressState+0x353
a706bc78 834b9605 0581d000 a9a13138 8eac6620 nt!MiQueryAddressSpan+0x7e
a706bd14 8328344a ffffffff 057f6000 00000000 nt!NtQueryVirtualMemory+0x572
a706bd14 76f964f4 ffffffff 057f6000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0017ecb0 00000000 00000000 00000000 00000000 0x76f964f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetPageProtection+1a6
832ec5c0 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetPageProtection+1a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_41201_VRF_nt!MiGetPageProtection+1a6

BUCKET_ID:  0x1a_41201_VRF_nt!MiGetPageProtection+1a6

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

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 00000000 

CURRENT_IRQL:  0

FAULTING_IP: 
+6475952f01f2dcf8
00000000 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from 00000000 to 8329282b

FAILED_INSTRUCTION_ADDRESS: 
+6475952f01f2dcf8
00000000 ??              ???

STACK_TEXT:  
88353bdc 00000000 badb0d00 88338a3c 00000001 0x8329282b


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

I suspect this is a driver problem. You have the following out of date drivers on your system. Win 7 does not like obsolete drivers; they can and do cause conflicts, memory corruption and crashes. Turn Driver Verifier off before updating your drivers.

Afc.sys Wed Feb 23 01:58:55 2005 - Arcsoft(R) ASPI Shell (CD/DVD program) http://www.arcsoft.com/public/download.asp. Upgrade this software or uninstall it. It is not designed for Win 7.

nvsmu.sys Mon Jun 29 03:36:34 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers. Update this driver.

SSPORT.sys Tue Nov 21 23:41:42 2006 - Samsung printer driver Downloads SAMSUNG. This driver is very obsolete. Update it or or upgrade your printer.

lvusbsta.sys - I don't have a date for this driver but it was indicated in one of the dumps. It is a USB Statistic Driver belongs to the software Logitech USB Monitor Filter or Logitech QuickCam or Logitech ImageStudio by Logitech Inc (www.logitech.com). See if you can update this driver. The date you are looking for is July 13, 2009 or later. I saw other evidence that your Logitech hardware/software was involved in the crash.

Turn Driver Verifier off. Update the drivers above, especially those in red font. Post back if you need any help. Reboot and run your system. Upload any new BSOD's. Getting rid of those obsolete drivers may eliminate your problems. If not, we will go to the next step and test your RAM.

apparently your fixed somehow caused my audio drivers to get corrupted or something. I will post in hardware section.

Reinstall your audio (soundcard) drivers.