Going to try a re-start i have alot (33) major updates, that might fix it.
Um, Suspect you are using who crashed us, or similar. Windb says Memory corruption.
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Again... Would suggest running a memory test.
Ken J
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.
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\Windows_NT_jcgriff2\100610-10342-02.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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02c9be50
Debug session time: Wed Oct 6 21:36:11.500 2010 (GMT-4)
System Uptime: 0 days 0:00:41.811
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88008136420, 1, fffff80002d8fac3, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: 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: fffff88008136420, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d8fac3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d060e0
fffff88008136420
FAULTING_IP:
nt!RtlpWow64CtxFromAmd64+c3
fffff800`02d8fac3 418980b0100000 mov dword ptr [r8+10B0h],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: SlingAgentServ
CURRENT_IRQL: 0
TRAP_FRAME: fffff88008134c50 -- (.trap 0xfffff88008134c50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000010002
rdx=000000000000002b rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d8fac3 rsp=fffff88008134de0 rbp=fffff88008134e70
r8=fffff88008135370 r9=0000000000000000 r10=0000000000000000
r11=fffff88008134e10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlpWow64CtxFromAmd64+0xc3:
fffff800`02d8fac3 418980b0100000 mov dword ptr [r8+10B0h],eax ds:5b60:fffff880`08136420=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4ef14 to fffff80002ace740
STACK_TEXT:
fffff880`08134ae8 fffff800`02b4ef14 : 00000000`00000050 fffff880`08136420 00000000`00000001 fffff880`08134c50 : nt!KeBugCheckEx
fffff880`08134af0 fffff800`02acc82e : 00000000`00000001 fffff880`08135370 00000000`00100000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`08134c50 fffff800`02d8fac3 : 00000000`00000000 00000000`00000000 fffff880`08135b88 fffff880`08135b80 : nt!KiPageFault+0x16e
fffff880`08134de0 fffff800`02d8fc9d : fffff880`08135370 fffff880`08134e70 fffff880`081356b4 00000000`0255f201 : nt!RtlpWow64CtxFromAmd64+0xc3
fffff880`08134e10 fffff800`02d8fff7 : fffff880`08134e70 fffff880`08135660 00000000`0001002f 00000000`0255f240 : nt!RtlpWow64GetContextOnAmd64+0x4d
fffff880`08134e40 fffff800`02d96fce : 00000000`00000000 00000000`00000000 00000000`000002cc 00000000`00000000 : nt!PspWow64GetContextThreadOnAmd64+0x1d7
fffff880`081359e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryInformationThread+0xbdd
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80002d8fac7 - nt!RtlpWow64CtxFromAmd64+c7
[ 00:10 ]
1 error : !nt (fffff80002d8fac7)
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
---------
Quote