Hi guys,
Been having BSOD issues with Windows Media Center recently. Happens when I try to play a blu-ray with ArcSoft TrueTheaters media center plugin (from within media center), randomly while playing videos, or playing a video then attempting to alt tab out.
System info is as follows:
Windows 7 x64 Retail (only OS to have been installed on this system)
Processor: AMD Phenom 9950
Motherboard: Asus M3N78-VM
Graphics: HIS Radeon 5770
Windows installation less than a month old.
I have also run a few memory diagnostics (Memtest86+ and the windows one) and everything seems fine there.
Hope someone can help, its driving me mad
Hi zzdri and welcome
these crashes were caused by acclp.sys a component of your Arcsoft. Its driver is a year and half old and needs to be updated.
Also in one crash memory was pointed at as the likely cause.
I would re-install the Arcsoft with an updated driver. Run a system wide virus scan
test your memory.
to test your memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Analysis
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows7_Vista_jcgriff2\073110-21325-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Sat Jul 31 12:31:00.597 2010 (GMT-4)
System Uptime: 0 days 0:02:41.642
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 28, fffffa8004751b30, fffff88003f24c2e}
Unable to load image \SystemRoot\SysWOW64\drivers\archlp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for archlp.sys
*** ERROR: Module load completed but symbols could not be loaded for archlp.sys
Probably caused by : archlp.sys ( archlp+cc2e )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000028, Handle value being referenced.
Arg3: fffffa8004751b30, Address of the current process.
Arg4: fffff88003f24c2e, Address inside the driver that is performing the incorrect reference.
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: Media_01.aui
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000314a3dc to fffff80002cc0f00
STACK_TEXT:
fffff880`093a2d58 fffff800`0314a3dc : 00000000`000000c4 00000000`000000f6 00000000`00000028 fffffa80`04751b30 : nt!KeBugCheckEx
fffff880`093a2d60 fffff800`0315fae4 : 00000000`00000028 fffffa80`04751b30 00000000`00000004 fffff800`02cbf0fd : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`093a2da0 fffff800`02f1b720 : 00000000`00000000 fffff880`093a2fa0 fffff880`093a3100 fffff880`093a3428 : nt!VfCheckUserHandle+0x1b4
fffff880`093a2e80 fffff800`02fa1928 : fffff880`093a2f00 0002ffff`00000000 fffffa80`0420e4b0 fffffa80`04742b00 : nt! ?? ::NNGAKEGL::`string'+0x2105e
fffff880`093a2f50 fffff800`02cc0153 : 00000000`00000028 00000000`00000000 fffff880`093a3428 ffffffff`00000018 : nt!NtQueryInformationFile+0x1e4
fffff880`093a3090 fffff800`02cbc6f0 : fffff800`0314f2c2 00000000`463b0012 ffffffff`d6d9b63d 00000000`7ba67585 : nt!KiSystemServiceCopyEnd+0x13
fffff880`093a3298 fffff800`0314f2c2 : 00000000`463b0012 ffffffff`d6d9b63d 00000000`7ba67585 00000000`00000a57 : nt!KiServiceLinkage
fffff880`093a32a0 fffff880`03f24c2e : 00000000`00000000 00000000`00000002 00000000`00000001 00000000`00000000 : nt!VfZwQueryInformationFile+0x62
fffff880`093a32e0 00000000`00000000 : 00000000`00000002 00000000`00000001 00000000`00000000 00000000`00000005 : archlp+0xcc2e
STACK_COMMAND: kb
FOLLOWUP_IP:
archlp+cc2e
fffff880`03f24c2e 6890ef842f push 2F84EF90h
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: archlp+cc2e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: archlp
IMAGE_NAME: archlp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 498c2f81
FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_archlp+cc2e
BUCKET_ID: X64_0xc4_f6_VRF_archlp+cc2e
Followup: MachineOwner
---------
Old drivers
Code:
archlp.sys archlp.sys+cc2e fffff880`03f18000 fffff880`03f43000 0x0002b000 0x498c2f81 2/6/2009 08:39:29
spldr.sys fffff880`0149b000 fffff880`014a3000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
spsys.sys fffff880`06f7b000 fffff880`06fec000 0x00071000 0x4a085e7a 5/11/2009 13:20:58
ASACPI.sys fffff880`03fb1000 fffff880`03fb9000 0x00008000 0x4a0b72fd 5/13/2009 21:25:17
amdxata.sys fffff880`00fc3000 fffff880`00fce000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
nvsmu.sys fffff880`03fc5000 fffff880`03fd0000 0x0000b000 0x4a486f05 6/29/2009 03:36:37
viahduaa.sys fffff880`05657000 fffff880`057eb000 0x00194000 0x4a56b055 7/9/2009 23:07:01
Quote