System Ständig Stopp-Fehler: 0xfffff800

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c9e670
Debug session time: Sat Jun 16 00:37:23.505 2012 (UTC + 2:00)
System Uptime: 0 days 0:05:44.003
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880099597d8, fffff88009959030, fffff880012cdc73}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880099597d8
Arg3: fffff88009959030
Arg4: fffff880012cdc73

Debugging Details:
------------------


EXCEPTION_RECORD: fffff880099597d8 -- (.exr 0xfffff880099597d8)
ExceptionAddress: fffff880012cdc73 (Ntfs!NtfsFcbTableCompare+0x0000000000000003)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88009959030 -- (.cxr 0xfffff88009959030)
rax=000100000003ef69 rbx=dffff8a009ff8c20 rcx=fffffa8004c7e640
rdx=fffff88009959b10 rsi=fffff88009959b10 rdi=fffffa8004c7e640
rip=fffff880012cdc73 rsp=fffff88009959a18 rbp=fffff88009959ae0
r8=dffff8a009ff8c40 r9=0000ffffffffffff r10=fffff88001277180
r11=fffff88009959b58 r12=fffff88009959bb4 r13=0000000000000000
r14=fffffa8004c7e180 r15=fffffa8004c7e180
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
Ntfs!NtfsFcbTableCompare+0x3:
fffff880`012cdc73 498b08 mov rcx,qword ptr [r8] ds:002b:dffff8a0`09ff8c40=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: coreServiceShe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d08100
GetUlongFromAddress: unable to read from fffff80002d081c0
ffffffffffffffff

FOLLOWUP_IP:
Ntfs!NtfsFcbTableCompare+3
fffff880`012cdc73 498b08 mov rcx,qword ptr [r8]

FAULTING_IP:
Ntfs!NtfsFcbTableCompare+3
fffff880`012cdc73 498b08 mov rcx,qword ptr [r8]

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from fffff80002b0249d to fffff880012cdc73

STACK_TEXT:
fffff880`09959a18 fffff800`02b0249d : 00000000`00000000 fffffa80`040dcbb0 fffff880`09959a44 fffff880`09959b68 : Ntfs!NtfsFcbTableCompare+0x3
fffff880`09959a20 fffff800`02b02515 : fffff880`09959b90 fffffa80`0407a010 fffffa80`040dcb01 fffff880`09959b10 : nt!FindNodeOrParent+0x3d
fffff880`09959a50 fffff880`012cc1a9 : 00010000`0003ef69 fffff980`158e0938 00000000`00000000 fffffa80`04c7e180 : nt!RtlLookupElementGenericTableFullAvl+0x15
fffff880`09959a80 fffff880`0129dd8b : fffffa80`040dcbb0 fffffa80`04c7e180 fffffa80`040dcbb0 00010000`0003ef69 : Ntfs!NtfsCreateFcb+0x79
fffff880`09959b60 fffff880`012c2179 : fffff880`096704a0 fffffa80`0407a010 fffffa80`040dcbb0 00000000`00000000 : Ntfs!NtfsOpenFile+0x1cb
fffff880`09959d50 fffff880`0122aa3d : fffffa80`040dcbb0 fffffa80`0407a010 fffff880`096704a0 fffffa80`05e82b00 : Ntfs!NtfsCommonCreate+0xc49
fffff880`09959f30 fffff800`02ad0cb7 : fffff880`09670410 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`09959f60 fffff800`02ad0c78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`096702e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Ntfs!NtfsFcbTableCompare+3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b

STACK_COMMAND: .cxr 0xfffff88009959030 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsFcbTableCompare+3

BUCKET_ID: X64_0x24_Ntfs!NtfsFcbTableCompare+3

Followup: MachineOwner
---------

0: kd> .exr 0xfffff880099597d8
ExceptionAddress: fffff880012cdc73 (Ntfs!NtfsFcbTableCompare+0x0000000000000003)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
0: kd> lmvm Ntfs
start end module name
fffff880`0121c000 fffff880`013bf000 Ntfs (pdb symbols) c:\symbols\ntfs.pdb\D51347AE03CB4523A2844EA865BA0BE92\ntfs.pdb
Loaded symbol image file: Ntfs.sys
Mapped memory image file: c:\symbols\Ntfs.sys\4D79997B1a3000\Ntfs.sys
Image path: \SystemRoot\System32\Drivers\Ntfs.sys
Image name: Ntfs.sys
Timestamp: Fri Mar 11 04:39:39 2011 (4D79997B)
CheckSum: 0019968A
ImageSize: 001A3000
File version: 6.1.7601.17577
Product version: 6.1.7601.17577
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 6.1.7601.17577
FileVersion: 6.1.7601.17577 (win7sp1_gdr.110310-1504)
FileDescription: NT File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> .exr 0xfffff880099597d8
ExceptionAddress: fffff880012cdc73 (Ntfs!NtfsFcbTableCompare+0x0000000000000003)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\061712-19359-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02ca2670
Debug session time: Sun Jun 17 20:45:43.406 2012 (UTC + 2:00)
System Uptime: 0 days 6:18:39.889
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88006bab152, fffff880085f89e8, fffff880085f8240}

Probably caused by : atikmdag.sys ( atikmdag+37f152 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006bab152, The address that the exception occurred at
Arg3: fffff880085f89e8, Exception Record Address
Arg4: fffff880085f8240, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
atikmdag+37f152
fffff880`06bab152 000f add byte ptr [rdi],cl

EXCEPTION_RECORD: fffff880085f89e8 -- (.exr 0xfffff880085f89e8)
ExceptionAddress: fffff88006bab152 (atikmdag+0x000000000037f152)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT: fffff880085f8240 -- (.cxr 0xfffff880085f8240)
rax=d755af7cb1f8b66f rbx=0000000000000000 rcx=0000000000000018
rdx=0000000000000000 rsi=cccccccccccccccd rdi=0000000000000000
rip=fffff88006bab152 rsp=fffff880085f8c28 rbp=0000000000000000
r8=fffff88006bab153 r9=fffff880085f8c70 r10=00002d58dec9b7b0
r11=0000000000000122 r12=0000000000000400 r13=0000000000002700
r14=0000000000000020 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
atikmdag+0x37f152:
fffff880`06bab152 000f add byte ptr [rdi],cl ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c100
GetUlongFromAddress: unable to read from fffff80002d0c1c0
0000000000000000 Nonpaged pool

FOLLOWUP_IP:
atikmdag+37f152
fffff880`06bab152 000f add byte ptr [rdi],cl

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88006a7beae to fffff88006bab152

STACK_TEXT:
fffff880`085f8c28 fffff880`06a7beae : 00000000`00000004 00000000`00000000 cccccccc`cccccc00 00000000`00000000 : atikmdag+0x37f152
fffff880`085f8c30 00000000`00000004 : 00000000`00000000 cccccccc`cccccc00 00000000`00000000 fffff880`009e6180 : atikmdag+0x24feae
fffff880`085f8c38 00000000`00000000 : cccccccc`cccccc00 00000000`00000000 fffff880`009e6180 00000000`00000824 : 0x4


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+37f152

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a8a1a8b

STACK_COMMAND: .cxr 0xfffff880085f8240 ; kb

FAILURE_BUCKET_ID: X64_0x7E_atikmdag+37f152

BUCKET_ID: X64_0x7E_atikmdag+37f152

Followup: MachineOwner