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: fffff680083a8520, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ba8700, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0e0e0
fffff680083a8520
FAULTING_IP:
nt!MiTrimWorkingSet+c0
fffff800`02ba8700 498b0a mov rcx,qword ptr [r10]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: CCC.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880066f4480 -- (.trap 0xfffff880066f4480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000083a8520 rbx=0000000000000000 rcx=0000098000000000
rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ba8700 rsp=fffff880066f4610 rbp=0000000000000002
r8=00000000000002b8 r9=fffffa800228f1e0 r10=fffff680083a8520
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiTrimWorkingSet+0xc0:
fffff800`02ba8700 498b0a mov rcx,qword ptr [r10] ds:0f00:fffff680`083a8520=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b558f2 to fffff80002ad6740
STACK_TEXT:
fffff880`066f4318 fffff800`02b558f2 : 00000000`00000050 fffff680`083a8520 00000000`00000000 fffff880`066f4480 : nt!KeBugCheckEx
fffff880`066f4320 fffff800`02ad482e : 00000000`00000000 00000000`00000001 fffff8a0`07ae2600 fffff800`02adbc00 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`066f4480 fffff800`02ba8700 : fffff8a0`07ae26a4 fffff8a0`07ae26c0 fffffa80`03967f7c fffff880`00000001 : nt!KiPageFault+0x16e
fffff880`066f4610 fffff800`02ba8968 : 00000000`00000019 fffff880`00000d5f 00000000`00000169 00000000`00000006 : nt!MiTrimWorkingSet+0xc0
fffff880`066f46c0 fffff800`02d1e797 : ffffffff`ffffffff fffffa80`07c3fec8 fffffa80`03c78060 00000000`00000032 : nt!MiReduceWs+0x48
fffff880`066f46f0 fffff800`02f280ed : 00000000`00000001 fffff880`066f4ca0 00000000`00000000 00000000`1fbed901 : nt!MmAdjustWorkingSetSizeEx+0x397
fffff880`066f4780 fffff800`02e2fbcb : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`1fbed9c0 : nt!PspSetQuotaLimits+0x32d
fffff880`066f48d0 fffff800`02ad5993 : fffffa80`03c78060 fffff880`066f4ca0 00000000`1dd1fd90 00000000`1dd1fd90 : nt! ?? ::NNGAKEGL::`string'+0x49b60
fffff880`066f4c20 00000000`777fff1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1fbed988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777fff1a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiTrimWorkingSet+c0
fffff800`02ba8700 498b0a mov rcx,qword ptr [r10]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiTrimWorkingSet+c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiTrimWorkingSet+c0
BUCKET_ID: X64_0x50_nt!MiTrimWorkingSet+c0
So basically, some software tried to read a bad pointer. I'm not sure which driver actually caused it, but it looks like CCC.exe was the process that owned the address space when the bug check occurred so I would make sure you have the latest 64-bit ATI drivers and the newest version of DirectX.
Memory corruption can also cause this sort of thing, so if you haven't ran memtest86+ already, then I would definitely do that. You might also open up a system monitor and make sure your RAM is getting a high enough voltage (usually 1.8V i think), even when your system is under load.