Oto kodu z moich bluescreenów:
1.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070111-19687-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0280e000 PsLoadedModuleList = 0xfffff800`02a4be50
Debug session time: Fri Jul 1 21:12:28.229 2011 (GMT+2)
System Uptime: 0 days 0:04:18.634
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880043141de, fffff88001fb69b8, fffff88001fb6210}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
2: 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: fffff880043141de, The address that the exception occurred at
Arg3: fffff88001fb69b8, Exception Record Address
Arg4: fffff88001fb6210, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
dxgmms1!VidSchiScheduleCommandToRun+f2
fffff880`043141de 837f050f cmp dword ptr [rdi+5],0Fh
EXCEPTION_RECORD: fffff88001fb69b8 -- (.exr 0xfffff88001fb69b8)
ExceptionAddress: fffff880043141de (dxgmms1!VidSchiScheduleCommandToRun+0x00000000000000f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000005
Attempt to read from address 0000000000000005
CONTEXT: fffff88001fb6210 -- (.cxr 0xfffff88001fb6210)
rax=fffff88001fb6c10 rbx=fffffa8004ed0010 rcx=fffffa8004ed07a0
rdx=fffffa8004ed0010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043141de rsp=fffff88001fb6bf0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa8004ed07e0
r11=0000000000000000 r12=00000000055da950 r13=fffff88004340dc0
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010297
dxgmms1!VidSchiScheduleCommandToRun+0xf2:
fffff880`043141de 837f050f cmp dword ptr [rdi+5],0Fh ds:002b:00000000`00000005=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000005
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab60e0
0000000000000005
FOLLOWUP_IP:
dxgmms1!VidSchiScheduleCommandToRun+f2
fffff880`043141de 837f050f cmp dword ptr [rdi+5],0Fh
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: CODE_CORRUPTION
LAST_CONTROL_TRANSFER: from fffff88004340e7a to fffff880043141de
STACK_TEXT:
fffff880`01fb6bf0 fffff880`04340e7a : 00000000`00000000 fffffa80`055da950 00000000`00000080 fffffa80`04ed0010 : dxgmms1!VidSchiScheduleCommandToRun+0xf2
fffff880`01fb6d00 fffff800`02b23166 : 00000000`0fb3ae1f fffffa80`05539b60 fffffa80`039f0040 fffffa80`05539b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`01fb6d40 fffff800`0285e486 : fffff880`02dd4180 fffffa80`05539b60 fffff880`02ddefc0 fffff880`0104b534 : nt!PspSystemThreadStartup+0x5a
fffff880`01fb6d80 00000000`00000000 : fffff880`01fb7000 fffff880`01fb1000 fffff880`01fb6690 00000000`00000000 : nt!KxStartSystemThread+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
fffff880043141df - dxgmms1!VidSchiScheduleCommandToRun+f3
[ ff:7f ]
1 error : !dxgmms1 (fffff880043141df)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: .cxr 0xfffff88001fb6210 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
2: 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: fffff880043141de, The address that the exception occurred at
Arg3: fffff88001fb69b8, Exception Record Address
Arg4: fffff88001fb6210, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
dxgmms1!VidSchiScheduleCommandToRun+f2
fffff880`043141de 837f050f cmp dword ptr [rdi+5],0Fh
EXCEPTION_RECORD: fffff88001fb69b8 -- (.exr 0xfffff88001fb69b8)
ExceptionAddress: fffff880043141de (dxgmms1!VidSchiScheduleCommandToRun+0x00000000000000f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000005
Attempt to read from address 0000000000000005
CONTEXT: fffff88001fb6210 -- (.cxr 0xfffff88001fb6210)
rax=fffff88001fb6c10 rbx=fffffa8004ed0010 rcx=fffffa8004ed07a0
rdx=fffffa8004ed0010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043141de rsp=fffff88001fb6bf0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffffa8004ed07e0
r11=0000000000000000 r12=00000000055da950 r13=fffff88004340dc0
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010297
dxgmms1!VidSchiScheduleCommandToRun+0xf2:
fffff880`043141de 837f050f cmp dword ptr [rdi+5],0Fh ds:002b:00000000`00000005=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000005
READ_ADDRESS: 0000000000000005
FOLLOWUP_IP:
dxgmms1!VidSchiScheduleCommandToRun+f2
fffff880`043141de 837f050f cmp dword ptr [rdi+5],0Fh
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: CODE_CORRUPTION
LAST_CONTROL_TRANSFER: from fffff88004340e7a to fffff880043141de
STACK_TEXT:
fffff880`01fb6bf0 fffff880`04340e7a : 00000000`00000000 fffffa80`055da950 00000000`00000080 fffffa80`04ed0010 : dxgmms1!VidSchiScheduleCommandToRun+0xf2
fffff880`01fb6d00 fffff800`02b23166 : 00000000`0fb3ae1f fffffa80`05539b60 fffffa80`039f0040 fffffa80`05539b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`01fb6d40 fffff800`0285e486 : fffff880`02dd4180 fffffa80`05539b60 fffff880`02ddefc0 fffff880`0104b534 : nt!PspSystemThreadStartup+0x5a
fffff880`01fb6d80 00000000`00000000 : fffff880`01fb7000 fffff880`01fb1000 fffff880`01fb6690 00000000`00000000 : nt!KxStartSystemThread+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
fffff880043141df - dxgmms1!VidSchiScheduleCommandToRun+f3
[ ff:7f ]
1 error : !dxgmms1 (fffff880043141df)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: .cxr 0xfffff88001fb6210 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------2.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070111-20576-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Fri Jul 1 21:45:19.537 2011 (GMT+2)
System Uptime: 0 days 0:23:49.941
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002a894e0, fffff8800891db60, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a894e0, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800891db60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!IoGetRelatedDeviceObject+0
fffff800`02a894e0 488b4110 mov rax,qword ptr [rcx+10h]
CONTEXT: fffff8800891db60 -- (.cxr 0xfffff8800891db60)
rax=fffff8800891e7e8 rbx=0000000000000000 rcx=ffff7a8006656830
rdx=ffff7a8006656831 rsi=fffff88002fd4180 rdi=ffff7a8006656830
rip=fffff80002a894e0 rsp=fffff8800891e548 rbp=fffffa80041fa4a0
r8=0000000000000002 r9=fffff88002fd4100 r10=0000000000000000
r11=0000000000000000 r12=fffff8800891e580 r13=ffff7a8006656830
r14=fffffa800695e500 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!IoGetRelatedDeviceObject:
fffff800`02a894e0 488b4110 mov rax,qword ptr [rcx+10h] ds:002b:ffff7a80`06656840=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: windbg.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002a894e0
STACK_TEXT:
fffff880`0891d298 fffff800`02a79469 : 00000000`0000003b 00000000`c0000005 fffff800`02a894e0 fffff880`0891db60 : nt!KeBugCheckEx
fffff880`0891d2a0 fffff800`02a78dbc : fffff880`0891e308 fffff880`0891db60 00000000`00000000 fffff800`02aa8450 : nt!KiBugCheckDispatch+0x69
fffff880`0891d3e0 fffff800`02a9fbed : fffff800`02c9acb8 00000000`00000000 fffff800`02a08000 fffff880`0891e308 : nt!KiSystemServiceHandler+0x7c
fffff880`0891d420 fffff800`02aa7250 : fffff800`02bc81e8 fffff880`0891d498 fffff880`0891e308 fffff800`02a08000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0891d450 fffff800`02ab41b5 : fffff880`0891e308 fffff880`0891db60 fffff880`00000000 ffff7a80`06656830 : nt!RtlDispatchException+0x410
fffff880`0891db30 fffff800`02a79542 : fffff880`0891e308 00000000`00000000 fffff880`0891e3b0 fffff880`02fd4180 : nt!KiDispatchException+0x135
fffff880`0891e1d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceHandler+7c
fffff800`02a78dbc b801000000 mov eax,1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceHandler+7c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c
BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c
Followup: MachineOwner
---------3.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070111-21200-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Fri Jul 1 21:49:36.173 2011 (GMT+2)
System Uptime: 0 days 0:03:37.953
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960000e65a9, fffff880077e8ef0, 0}
Probably caused by : win32k.sys ( win32k!xxxInternalDoPaint+19 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000e65a9, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880077e8ef0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
win32k!xxxInternalDoPaint+19
fffff960`000e65a9 48397b10 cmp qword ptr [rbx+10h],rdi
CONTEXT: fffff880077e8ef0 -- (.cxr 0xfffff880077e8ef0)
rax=0000000000000000 rbx=0000200000000000 rcx=0000200000000000
rdx=fffff900c0669250 rsi=fffff900c0669250 rdi=fffff900c0669250
rip=fffff960000e65a9 rsp=fffff880077e98d0 rbp=0000000000000000
r8=fffff900c01d6010 r9=00000000ffffffff r10=0000000000002407
r11=fffff900c06778d0 r12=fffff880077e9b68 r13=fffff880077e9b68
r14=00000000000025ff r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
win32k!xxxInternalDoPaint+0x19:
fffff960`000e65a9 48397b10 cmp qword ptr [rbx+10h],rdi ds:002b:00002000`00000010=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960000e65a9
STACK_TEXT:
fffff880`077e98d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxInternalDoPaint+0x19
FOLLOWUP_IP:
win32k!xxxInternalDoPaint+19
fffff960`000e65a9 48397b10 cmp qword ptr [rbx+10h],rdi
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!xxxInternalDoPaint+19
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0
STACK_COMMAND: .cxr 0xfffff880077e8ef0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!xxxInternalDoPaint+19
BUCKET_ID: X64_0x3B_win32k!xxxInternalDoPaint+19
Followup: MachineOwner
---------
4.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070111-22495-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02860000 PsLoadedModuleList = 0xfffff800`02a9de50
Debug session time: Fri Jul 1 21:07:15.595 2011 (GMT+2)
System Uptime: 0 days 0:13:43.000
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800028a02a2, fffff880072f5020, 0}
Probably caused by : memory_corruption ( nt!MiQueryAddressState+142 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800028a02a2, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880072f5020, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!MiQueryAddressState+142
fffff800`028a02a2 48833800 cmp qword ptr [rax],0
CONTEXT: fffff880072f5020 -- (.cxr 0xfffff880072f5020)
rax=7ffffa8004f0d860 rbx=0000000000000000 rcx=0108000000000000
rdx=fffff880072f5ac8 rsi=fffffa8003db7250 rdi=0000000000002000
rip=fffff800028a02a2 rsp=fffff880072f5a00 rbp=0000000000000000
r8=00000000005d5000 r9=fffffa8003db8b30 r10=0000000000000000
r11=fffff70001080000 r12=fffff6fb7da00000 r13=fffff68000002ea0
r14=fffff880072f5ac0 r15=00000000005d4000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!MiQueryAddressState+0x142:
fffff800`028a02a2 48833800 cmp qword ptr [rax],0 ds:002b:7ffffa80`04f0d860=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: SearchProtocol
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800028a00aa to fffff800028a02a2
STACK_TEXT:
fffff880`072f5a00 fffff800`028a00aa : fffffa80`03db7250 fffffa80`03db8b30 fffffa80`03db8b30 00000000`005d4000 : nt!MiQueryAddressState+0x142
fffff880`072f5a50 fffff800`02bb6798 : fffff880`00000002 00000000`005d5000 fffffa80`03db7250 fffff880`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`072f5ac0 fffff800`028d1153 : 00000000`00000900 fffffa80`064e9750 fffff880`072f5bf8 00000000`0465e558 : nt!NtQueryVirtualMemory+0x386
fffff880`072f5bb0 00000000`772f00ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0465e538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f00ea
FOLLOWUP_IP:
nt!MiQueryAddressState+142
fffff800`028a02a2 48833800 cmp qword ptr [rax],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiQueryAddressState+142
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff880072f5020 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiQueryAddressState+142
BUCKET_ID: X64_0x3B_nt!MiQueryAddressState+142
Followup: MachineOwner
---------
5.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070111-23088-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02811000 PsLoadedModuleList = 0xfffff800`02a4ee50
Debug session time: Fri Jul 1 20:52:08.848 2011 (GMT+2)
System Uptime: 0 days 0:49:23.253
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002889a13, fffff880039bf648, fffff880039beea0}
Probably caused by : ndis.sys ( ndis!ndisReferenceNextUnprocessedOpenEx+83 )
Followup: MachineOwner
---------
2: 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: fffff80002889a13, The address that the exception occurred at
Arg3: fffff880039bf648, Exception Record Address
Arg4: fffff880039beea0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!KeAcquireSpinLockAtDpcLevel+43
fffff800`02889a13 f0480fba2900 lock bts qword ptr [rcx],0
EXCEPTION_RECORD: fffff880039bf648 -- (.exr 0xfffff880039bf648)
ExceptionAddress: fffff80002889a13 (nt!KeAcquireSpinLockAtDpcLevel+0x0000000000000043)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880039beea0 -- (.cxr 0xfffff880039beea0)
rax=0000000000000000 rbx=fffff88002d63180 rcx=7ffffa80053e70f8
rdx=0000000000000001 rsi=0000000000000000 rdi=7ffffa80053e70f8
rip=fffff80002889a13 rsp=fffff880039bf880 rbp=fffffa8005814588
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000005814588 r13=0000000000000000
r14=fffff88001526110 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
nt!KeAcquireSpinLockAtDpcLevel+0x43:
fffff800`02889a13 f0480fba2900 lock bts qword ptr [rcx],0 ds:002b:7ffffa80`053e70f8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab90e0
ffffffffffffffff
FOLLOWUP_IP:
ndis!ndisReferenceNextUnprocessedOpenEx+83
fffff880`014d1c83 4584e4 test r12b,r12b
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880014d1c83 to fffff80002889a13
STACK_TEXT:
fffff880`039bf880 fffff880`014d1c83 : 7ffffa80`053e7010 fffffa80`05814588 00000000`00000000 00000000`000000a8 : nt!KeAcquireSpinLockAtDpcLevel+0x43
fffff880`039bf8d0 fffff880`01564799 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`01526101 : ndis!ndisReferenceNextUnprocessedOpenEx+0x83
fffff880`039bf920 fffff880`01548792 : fffffa80`00000000 00000000`00000000 fffffa80`051a7100 00000000`00000008 : ndis!ndisPnPNotifyAllTransports+0x119
fffff880`039bfa90 fffff880`01514b68 : fffffa80`053e14c0 fffff880`039bfc48 fffffa80`051a71a0 00000000`00000001 : ndis!NdisFNetPnPEvent+0xd2
fffff880`039bfad0 fffff880`0157d7d8 : 00000000`00000000 fffffa80`048b63f8 fffffa80`048b62e0 fffffa80`051a71a0 : ndis!ndisDevicePnPEventNotifyFiltersAndAllTransports+0x128
fffff880`039bfbd0 fffff880`0151595c : fffffa80`048b63f8 fffff880`00000004 fffffa80`03a2a4d0 fffff800`0296748e : ndis!ndisQueryPower+0x2b8
fffff880`039bfc40 fffff800`0299ce55 : 00000000`00000001 00000000`00000000 fffffa80`051a7050 fffffa80`048b6388 : ndis!ndisPowerDispatch+0x19c
fffff880`039bfc90 fffff800`02b26166 : ffffffff`fa0a1f00 fffffa80`05aa6060 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`039bfd40 fffff800`02861486 : fffff880`02d63180 fffffa80`05aa6060 fffff880`02d6dfc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`039bfd80 00000000`00000000 : fffff880`039c0000 fffff880`039ba000 fffff880`039bf9e0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ndis!ndisReferenceNextUnprocessedOpenEx+83
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ndis
IMAGE_NAME: ndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184
STACK_COMMAND: .cxr 0xfffff880039beea0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_ndis!ndisReferenceNextUnprocessedOpenEx+83
BUCKET_ID: X64_0x7E_ndis!ndisReferenceNextUnprocessedOpenEx+83
Followup: MachineOwner
---------6.
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070111-23961-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
Debug session time: Fri Jul 1 21:20:20.143 2011 (GMT+2)
System Uptime: 0 days 0:06:36.922
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffffa8004e51230, 7ffffa8004e51230, fffffa8004e51230}
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
Followup: Pool_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa8004e51230, the pool entry being checked.
Arg3: 7ffffa8004e51230, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8004e51230, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 2
IRP_ADDRESS: ffffffffffffff88
DEVICE_OBJECT: fffffa80049d9ff8
LAST_CONTROL_TRANSFER: from fffff80002c05130 to fffff80002ad3f00
STACK_TEXT:
fffff880`07be43d8 fffff800`02c05130 : 00000000`00000019 00000000`00000003 fffffa80`04e51230 7ffffa80`04e51230 : nt!KeBugCheckEx
fffff880`07be43e0 fffff800`02c074c1 : fffff880`07be4478 fffffa80`049d9c00 00000000`00000000 fffff8a0`01cd87a0 : nt!ExFreePool+0x780
fffff880`07be4470 fffff800`02af34ec : 00000000`00000001 fffff880`00c39af5 00000000`20707249 00000000`00000001 : nt!ExFreePoolWithTag+0x411
fffff880`07be4520 fffff800`02ad68cd : 00000000`00000000 fffff8a0`01cd87a0 00000000`00000001 fffffa80`0678e850 : nt!IopCompleteRequest+0x54c
fffff880`07be45f0 fffff880`0124eda1 : fffffa80`04715180 00000000`00000001 fffff880`07be48c0 00000000`00000000 : nt!IopfCompleteRequest+0x75d
fffff880`07be46d0 fffff880`01251413 : fffffa80`04715180 fffffa80`049d9c10 fffff880`07be4800 fffff880`07be4800 : Ntfs!NtfsCommonWrite+0x2bfa
fffff880`07be4890 fffff880`00c3823f : fffffa80`049d9fb0 fffffa80`049d9c10 fffffa80`03c64010 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`07be4950 fffff880`00c366df : fffffa80`04576de0 00000000`00000001 fffffa80`04576d00 fffffa80`049d9c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07be49e0 fffff800`02de7929 : 00000000`00000001 fffffa80`06790f20 00000000`00000001 fffffa80`049d9c10 : fltmgr!FltpDispatch+0xcf
fffff880`07be4a40 fffff800`02de86c3 : fffffa80`049d9ff8 00000000`00000000 fffffa80`06790f20 fffffa80`06790f94 : nt!IopSynchronousServiceTail+0xf9
fffff880`07be4ab0 fffff800`02ad3153 : 00000000`00000601 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7e2
fffff880`07be4bb0 00000000`74102dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`023cf028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74102dd9
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+780
fffff800`02c05130 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+780
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+780
BUCKET_ID: X64_0x19_3_nt!ExFreePool+780
Followup: Pool_corruption
---------No i jak?
Myślicie dać sobie spokój i odesłać im to g**** co przysłali czy powalczyć? W sumie to jak na to patrzę to nie wiem czy sie śmiać czy płakać...
