Hallo Forum Gemeinde,
Ich bekomme ab und an einen Blue Screen beim Kopieren oder verschieben von Dateien auf dem Raid Laufwerk.
System:
alle Client Rechner (8 PC´s) sind Windows 7 64 Bit Systeme
Kommen wir zu den Blue Screens und der Auswertung aus Bluescreenview.(Screen im Anhang)
Mini012011-01.dmp 20.01.2011 10:40:02 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff980`381c9058 00000000`00000000 fffffa60`011b641b 00000000`00000000 Ntfs.sys Ntfs.sys+17e10x64
im Moment rennt prime95 und den RAM zu testen. Auswertung reiche ich nach.
hier noch eine minidump ausgewertet.
FAULTING_MODULE: fffff80001c59000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b62d378
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff980381c9058
FAULTING_IP:
lf40fs64+d41b
fffffa60`011b641b ?? ???
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001d148b0 to fffff80001cb34d0
STACK_TEXT:
fffffa60`0b20a258 fffff800`01d148b0 : 00000000`00000050 fffff980`381c9058 00000000`00000000 fffffa60`0b20a340 : nt+0x5a4d0
fffffa60`0b20a260 00000000`00000050 : fffff980`381c9058 00000000`00000000 fffffa60`0b20a340 00000000`00000000 : nt+0xbb8b0
fffffa60`0b20a268 fffff980`381c9058 : 00000000`00000000 fffffa60`0b20a340 00000000`00000000 fffffa60`01221e10 : 0x50
fffffa60`0b20a270 00000000`00000000 : fffffa60`0b20a340 00000000`00000000 fffffa60`01221e10 00000000`00000000 : 0xfffff980`381c9058
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
lf40fs64+d41b
fffffa60`011b641b ?? ???
SYMBOL_NAME: lf40fs64+d41b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lf40fs64
IMAGE_NAME: lf40fs64.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
____________________________________________
2.
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: fffff80001e808c1, The address that the exception occurred at
Arg3: fffffa6001de7ab8, Exception Record Address
Arg4: fffffa6001de7490, Context Record Address
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
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:
+0
fffff800`01e808c1 ffd3 call rbx
EXCEPTION_RECORD: fffffa6001de7ab8 -- (.exr 0xfffffa6001de7ab8)
ExceptionAddress: fffff80001e808c1
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffa6001de7490 -- (.cxr 0xfffffa6001de7490)
rax=0000000000000001 rbx=52e0fffffa600120 rcx=39e0fffffa800d41
rdx=0000267400000000 rsi=fffffa800ca61bb0 rdi=39e0fffffa800d41
rip=fffff80001e808c1 rsp=fffffa6001de7cf0 rbp=fffff80001fb08f8
r8=fffffa6001de7d50 r9=fffff80001f92680 r10=0000000000000008
r11=0000000000000000 r12=fffffa800d4152e0 r13=0000000000000001
r14=0000000000000000 r15=fffffa6001b9ccc0
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
fffff800`01e808c1 ffd3 call rbx {52e0ffff`fa600120}
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffffa600120f6c0 to fffff80001e808c1
STACK_TEXT:
fffffa60`01de7cf0 fffffa60`0120f6c0 : fffff800`01fb0801 fffffa80`0ca61b00 00000000`00000000 fffffa60`01de7d50 : 0xfffff800`01e808c1
fffffa60`01de7cf8 fffff800`01fb0801 : fffffa80`0ca61b00 00000000`00000000 fffffa60`01de7d50 00000000`00000001 : 0xfffffa60`0120f6c0
fffffa60`01de7d00 fffffa80`0ca61b00 : 00000000`00000000 fffffa60`01de7d50 00000000`00000001 fffffa80`0ca34370 : 0xfffff800`01fb0801
fffffa60`01de7d08 00000000`00000000 : fffffa60`01de7d50 00000000`00000001 fffffa80`0ca34370 00000000`00000000 : 0xfffffa80`0ca61b00
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
0: kd> .exr 0xfffffa6001de7ab8
ExceptionAddress: fffff80001e808c1
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
0: kd> .cxr 0xfffffa6001de7490
rax=0000000000000001 rbx=52e0fffffa600120 rcx=39e0fffffa800d41
rdx=0000267400000000 rsi=fffffa800ca61bb0 rdi=39e0fffffa800d41
rip=fffff80001e808c1 rsp=fffffa6001de7cf0 rbp=fffff80001fb08f8
r8=fffffa6001de7d50 r9=fffff80001f92680 r10=0000000000000008
r11=0000000000000000 r12=fffffa800d4152e0 r13=0000000000000001
r14=0000000000000000 r15=fffffa6001b9ccc0
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
fffff800`01e808c1 ffd3 call rbx {52e0ffff`fa600120}
0: kd> lmvm Unknown_Module
start end module name
Vielen Dank für eure Hilfe
Ich bekomme ab und an einen Blue Screen beim Kopieren oder verschieben von Dateien auf dem Raid Laufwerk.
System:
SBS 2008 (64 BIT)
RAM: 16 GB
HDD: 10 TB RAID 5 (Adaptec RAID 3805)
alle Client Rechner (8 PC´s) sind Windows 7 64 Bit Systeme
Kommen wir zu den Blue Screens und der Auswertung aus Bluescreenview.(Screen im Anhang)
Mini012011-01.dmp 20.01.2011 10:40:02 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff980`381c9058 00000000`00000000 fffffa60`011b641b 00000000`00000000 Ntfs.sys Ntfs.sys+17e10x64
im Moment rennt prime95 und den RAM zu testen. Auswertung reiche ich nach.
hier noch eine minidump ausgewertet.
FAULTING_MODULE: fffff80001c59000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b62d378
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff980381c9058
FAULTING_IP:
lf40fs64+d41b
fffffa60`011b641b ?? ???
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001d148b0 to fffff80001cb34d0
STACK_TEXT:
fffffa60`0b20a258 fffff800`01d148b0 : 00000000`00000050 fffff980`381c9058 00000000`00000000 fffffa60`0b20a340 : nt+0x5a4d0
fffffa60`0b20a260 00000000`00000050 : fffff980`381c9058 00000000`00000000 fffffa60`0b20a340 00000000`00000000 : nt+0xbb8b0
fffffa60`0b20a268 fffff980`381c9058 : 00000000`00000000 fffffa60`0b20a340 00000000`00000000 fffffa60`01221e10 : 0x50
fffffa60`0b20a270 00000000`00000000 : fffffa60`0b20a340 00000000`00000000 fffffa60`01221e10 00000000`00000000 : 0xfffff980`381c9058
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
lf40fs64+d41b
fffffa60`011b641b ?? ???
SYMBOL_NAME: lf40fs64+d41b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lf40fs64
IMAGE_NAME: lf40fs64.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
____________________________________________
2.
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: fffff80001e808c1, The address that the exception occurred at
Arg3: fffffa6001de7ab8, Exception Record Address
Arg4: fffffa6001de7490, Context Record Address
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
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:
+0
fffff800`01e808c1 ffd3 call rbx
EXCEPTION_RECORD: fffffa6001de7ab8 -- (.exr 0xfffffa6001de7ab8)
ExceptionAddress: fffff80001e808c1
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffa6001de7490 -- (.cxr 0xfffffa6001de7490)
rax=0000000000000001 rbx=52e0fffffa600120 rcx=39e0fffffa800d41
rdx=0000267400000000 rsi=fffffa800ca61bb0 rdi=39e0fffffa800d41
rip=fffff80001e808c1 rsp=fffffa6001de7cf0 rbp=fffff80001fb08f8
r8=fffffa6001de7d50 r9=fffff80001f92680 r10=0000000000000008
r11=0000000000000000 r12=fffffa800d4152e0 r13=0000000000000001
r14=0000000000000000 r15=fffffa6001b9ccc0
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
fffff800`01e808c1 ffd3 call rbx {52e0ffff`fa600120}
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffffa600120f6c0 to fffff80001e808c1
STACK_TEXT:
fffffa60`01de7cf0 fffffa60`0120f6c0 : fffff800`01fb0801 fffffa80`0ca61b00 00000000`00000000 fffffa60`01de7d50 : 0xfffff800`01e808c1
fffffa60`01de7cf8 fffff800`01fb0801 : fffffa80`0ca61b00 00000000`00000000 fffffa60`01de7d50 00000000`00000001 : 0xfffffa60`0120f6c0
fffffa60`01de7d00 fffffa80`0ca61b00 : 00000000`00000000 fffffa60`01de7d50 00000000`00000001 fffffa80`0ca34370 : 0xfffff800`01fb0801
fffffa60`01de7d08 00000000`00000000 : fffffa60`01de7d50 00000000`00000001 fffffa80`0ca34370 00000000`00000000 : 0xfffffa80`0ca61b00
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
0: kd> .exr 0xfffffa6001de7ab8
ExceptionAddress: fffff80001e808c1
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
0: kd> .cxr 0xfffffa6001de7490
rax=0000000000000001 rbx=52e0fffffa600120 rcx=39e0fffffa800d41
rdx=0000267400000000 rsi=fffffa800ca61bb0 rdi=39e0fffffa800d41
rip=fffff80001e808c1 rsp=fffffa6001de7cf0 rbp=fffff80001fb08f8
r8=fffffa6001de7d50 r9=fffff80001f92680 r10=0000000000000008
r11=0000000000000000 r12=fffffa800d4152e0 r13=0000000000000001
r14=0000000000000000 r15=fffffa6001b9ccc0
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
fffff800`01e808c1 ffd3 call rbx {52e0ffff`fa600120}
0: kd> lmvm Unknown_Module
start end module name
Vielen Dank für eure Hilfe
Attachments
Last edited by a moderator: