New
#21
Sorry to see another crash.
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usually caused by Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
This dump blames memory corruption and code corruption.
I find this out of date driver on your system and it may be contributing to your system instability: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_092610-20108-01.zip\092610-20108-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50 Debug session time: Sun Sep 26 11:05:22.177 2010 (GMT-4) System Uptime: 0 days 0:02:28.286 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff87fd0d77c1c, 0, fffff80002f63e87, 5} Could not read faulting driver name Probably caused by : memory_corruption Followup: memory_corruption --------- 6: kd> !analyze -v ******************************************************************************* * * * 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: fffff87fd0d77c1c, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002f63e87, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec10e0 fffff87fd0d77c1c FAULTING_IP: nt!CmpParseKey+11c7 fffff800`02f63e87 0b8d0c4948c7 or ecx,dword ptr [rbp-38B7B6F4h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: mscorsvw.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880098f2c80 -- (.trap 0xfffff880098f2c80) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8a000058000 rbx=0000000000000000 rcx=00000000b2d05e15 rdx=00000000000000f1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002f63e87 rsp=fffff880098f2e10 rbp=fffff880098f3310 r8=0000000024c898f1 r9=0000000000000087 r10=0000000000000006 r11=fffff8a00370fc00 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po cy nt!CmpParseKey+0x11c7: fffff800`02f63e87 0b8d0c4948c7 or ecx,dword ptr [rbp-38B7B6F4h] ss:0018:fffff87f`d0d77c1c=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002d088c1 to fffff80002c89740 STACK_TEXT: fffff880`098f2b18 fffff800`02d088c1 : 00000000`00000050 fffff87f`d0d77c1c 00000000`00000000 fffff880`098f2c80 : nt!KeBugCheckEx fffff880`098f2b20 fffff800`02c8782e : 00000000`00000000 fffff8a0`015d690c 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`098f2c80 fffff800`02f63e87 : fffff8a0`015d690c fffff880`098f3310 fffff8a0`00024010 fffff8a0`00022948 : nt!KiPageFault+0x16e fffff880`098f2e10 fffff800`02f82e84 : fffff800`02f62cc0 00000000`00000000 fffffa80`073aa010 fffff800`02f67b01 : nt!CmpParseKey+0x11c7 fffff880`098f30e0 fffff800`02f87e4d : fffffa80`073aa010 fffff880`098f3240 fffff8a0`00000040 fffffa80`05526510 : nt!ObpLookupObjectName+0x585 fffff880`098f31e0 fffff800`02f66dcc : fffff8a0`0377d000 00000000`00000000 fffff8a0`0373b701 00000000`000cd800 : nt!ObOpenObjectByName+0x1cd fffff880`098f3290 fffff800`02f68f0f : 00000000`000cce78 00000000`00020019 00000000`000cce98 00000000`00000000 : nt!CmOpenKey+0x28a fffff880`098f33e0 fffff800`02c88993 : fffffa80`07b32060 fffff880`098f34a0 00000000`fffdb000 fffff880`00000004 : nt!NtOpenKeyEx+0xf fffff880`098f3420 00000000`77020caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000cce38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77020caa STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80002f63e87 - nt!CmpParseKey+11c7 [ 4b:0b ] 1 error : !nt (fffff80002f63e87) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ANOD Network Security Filter driver, Alpha filter driver, Alpha Networks, Inc. Alpha is a spinoff from D Link. See if you can update this driver through D Link. I assume you have a DLink adapter?