There is some Refernece to Registry Problems but it may also be a Hardware issue
Please Test your Memory and Run a Sfc /scannow
SFC /SCANNOW Command - System File Checker
After that Run a full scan with your Anti-Virus
Also please check for any Errors in Device Manger and Reinstall any Drivers if necessary
See the Attachment for more information
YOU WILL NEED TO BE AN ADMINISTRATOR AND IT WILL WORK FOR WINDOWS 7 AS WELL AS VISTA
For Reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Josh\Desktop\021011-14929-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Thu Feb 10 22:00:28.511 2011 (UTC + 0:00)
System Uptime: 0 days 0:00:46.493
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 50, {fffffffffffffff3, 0, fffff80002d5f43d, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffffff3, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d5f43d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffffffffffff3
FAULTING_IP:
nt!CmpKcbCacheLookup+1dd
fffff800`02d5f43d 418b45f4 mov eax,dword ptr [r13-0Ch]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: AAWWSC.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88006ba97b0 -- (.trap 0xfffff88006ba97b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000003ff rbx=0000000000000000 rcx=0000000000000aaa
rdx=000000000ef62637 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d5f43d rsp=fffff88006ba9940 rbp=fffff8a000b16010
r8=0000000000000004 r9=0000000000000000 r10=0000000000000000
r11=fffff88006ba9af0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!CmpKcbCacheLookup+0x1dd:
fffff800`02d5f43d 418b45f4 mov eax,dword ptr [r13-0Ch] ds:99c0:ffffffff`fffffff4=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b05f14 to fffff80002a85740
STACK_TEXT:
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpKcbCacheLookup+1dd
fffff800`02d5f43d 418b45f4 mov eax,dword ptr [r13-0Ch]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!CmpKcbCacheLookup+1dd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x50_nt!CmpKcbCacheLookup+1dd
BUCKET_ID: X64_0x50_nt!CmpKcbCacheLookup+1dd
Followup: MachineOwner
---------
Hope This Helps,
Josh