thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Bluescreeny
No to jedziemy Malina:
Na początek solidny memtest86 pamięci RAM.
Problem często sprawia sterownik karty sieciowej Atheros i od czasu do czasu karty sieciowej Ati. Aodinstaluj je np Driver Sweeper'em i zainstaluj aktualne.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101811-14071-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Tue Oct 18 15: 12: 25.871 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 20: 34.291
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+5d067 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Operacja uko czona pomy lnie.
FAULTING_IP:
+616c2faf03a8dcf0
00000000`00000000 ? ?
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002ffd718 -- (.exr 0xfffff88002ffd718)
ExceptionAddress: fffff8800505d067 (athrxusb+0x000000000005d067)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002ffd7c0 -- (.trap 0xfffff88002ffd7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000610 rbx=0000000000000000 rcx=0000000000000610
rdx=fffffa8005bd7044 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800505d067 rsp=fffff88002ffd950 rbp=0000000000000000
r8=000000000000061a r9=fffffa8005bd7044 r10=fffff88002fd5b80
r11=fffff88002ffdb18 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
athrxusb+0x5d067:
fffff880`0505d067 ? ?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a70c2e to fffff80002a78ed0
STACK_TEXT:
fffff880`02ffc7f8 fffff800`02a70c2e : fffffa80`068741b0 00000000`00000000 fffff880`02ffcf70 fffff800`02aa5e28 : nt!KeBugCheck
fffff880`02ffc800 fffff800`02a9ebed : fffff800`02c85c24 fffff800`02bbea3c fffff800`02a07000 fffff880`02ffd718 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc830 fffff800`02aa6250 : fffff800`02bc6b5c fffff880`02ffc8a8 fffff880`02ffd718 fffff800`02a07000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc860 fffff800`02ab31b5 : fffff880`02ffd718 fffff880`02ffcf70 fffff880`00000000 9cd79e78`de966538 : nt!RtlDispatchException+0x410
fffff880`02ffcf40 fffff800`02a78542 : fffff880`02ffd718 fffffa80`04553edb fffff880`02ffd7c0 fffff880`050851f5 : nt!KiDispatchException+0x135
fffff880`02ffd5e0 fffff800`02a76e4a : fffffa80`05db7000 fffff880`0487aa9c fffffa80`041894b0 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd7c0 fffff880`0505d067 : fffffa80`05155b98 fffffa80`05155a10 fffffa80`057eb000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd950 fffffa80`05155b98 : fffffa80`05155a10 fffffa80`057eb000 00000000`00000001 00000610`0000000f : athrxusb+0x5d067
fffff880`02ffd958 fffffa80`05155a10 : fffffa80`057eb000 00000000`00000001 00000610`0000000f fffffa80`05bd7044 : 0xfffffa80`05155b98
fffff880`02ffd960 fffffa80`057eb000 : 00000000`00000001 00000610`0000000f fffffa80`05bd7044 fffffa80`05ba9030 : 0xfffffa80`05155a10
fffff880`02ffd968 00000000`00000001 : 00000610`0000000f fffffa80`05bd7044 fffffa80`05ba9030 00000000`00000000 : 0xfffffa80`057eb000
fffff880`02ffd970 00000610`0000000f : fffffa80`05bd7044 fffffa80`05ba9030 00000000`00000000 00000000`00000000 : 0x1
fffff880`02ffd978 fffffa80`05bd7044 : fffffa80`05ba9030 00000000`00000000 00000000`00000000 fffffa80`04553d30 : 0x610`0000000f
fffff880`02ffd980 fffffa80`05ba9030 : 00000000`00000000 00000000`00000000 fffffa80`04553d30 00000000`00000000 : 0xfffffa80`05bd7044
fffff880`02ffd988 00000000`00000000 : 00000000`00000000 fffffa80`04553d30 00000000`00000000 fffff880`050569c8 : 0xfffffa80`05ba9030
STACK_COMMAND: kb
FOLLOWUP_IP:
athrxusb+5d067
fffff880`0505d067 ? ?
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: athrxusb+5d067
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrxusb
IMAGE_NAME: athrxusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 458bca1d
FAILURE_BUCKET_ID: X64_0x1E_0_athrxusb+5d067
BUCKET_ID: X64_0x1E_0_athrxusb+5d067
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101811-13650-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50
Debug session time: Tue Oct 18 14: 51: 15.729 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 02: 27.165
Loading Kernel Symbols
................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002a485fd, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiCopyDataPageToImagePage+14d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a485fd, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'disk' and 'Unknown_Module_00000000`00000000' overlap
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!MiCopyDataPageToImagePage+14d
fffff800`02a485fd 488b18 mov rbx,qword ptr [rax]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca80e0
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002a7fa3a to fffff880041347f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02a7fa3a : 00000000`002ce895 fffffa80`052689d8 fffff800`02bf8c40 00000000`00000001 : 0xfffff880`041347f2
fffff800`00b9cca0 fffff800`02a7a6cc : fffff800`02beae80 fffff800`00000000 00000000`00000000 fffff800`02b90c80 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!MiCopyDataPageToImagePage+14d
fffff800`02a485fd 488b18 mov rbx,qword ptr [rax]
SYMBOL_NAME: nt!MiCopyDataPageToImagePage+14d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!MiCopyDataPageToImagePage+14d
BUCKET_ID: X64_0x1E_c0000005_nt!MiCopyDataPageToImagePage+14d
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101811-12870-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a63000 PsLoadedModuleList = 0xfffff800`02ca0e50
Debug session time: Tue Oct 18 20: 09: 30.724 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 00: 07.534
Loading Kernel Symbols
...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004df08f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004df08f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031af6f0 fffff800`02d1da89 : fffffa80`04df08d0 fffffa80`03e81b60 00000000`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afc10 fffff800`02bff547 : fffffa80`04df08d0 fffff800`02c785f8 fffffa80`03e81b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afc40 fffff800`02b67b95 : fffff800`02cda360 fffffa80`04d7ee08 fffffa80`04d7ee00 fffffa80`03e81b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afc80 fffff800`02ae2161 : fffff880`01106e00 fffff800`02b67b70 fffffa80`03e81b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afcb0 fffff800`02d78166 : fffff800`00901734 fffffa80`03e81b60 00000000`00000080 fffffa80`03e6d040 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`02ab3486 : fffff880`02f64180 fffffa80`03e81b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`02ec2540 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101711-14539-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a5a000 PsLoadedModuleList = 0xfffff800`02c97e50
Debug session time: Mon Oct 17 16: 16: 41.211 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 46: 58.647
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004acf9e1, fffff880076f4a50, 0}
Probably caused by : atipmdag.sys ( atipmdag+2a19e1 )
Followup: MachineOwner
---------
2: 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: fffff88004acf9e1, Address of the instruction which caused the bugcheck
Arg3: fffff880076f4a50, 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:
atipmdag+2a19e1
fffff880`04acf9e1 ff5020 call qword ptr [rax+20h]
CONTEXT: fffff880076f4a50 -- (.cxr 0xfffff880076f4a50)
rax=3b660a9fa3077600 rbx=0000000000000000 rcx=fffffa8005d21a80
rdx=0000000000000020 rsi=fffff880076f54d8 rdi=fffffa8005d58000
rip=fffff88004acf9e1 rsp=fffff880076f5430 rbp=0000000000000000
r8=fffff880076f54a0 r9=0000000000000780 r10=fffffa8005d21a80
r11=0000000000000002 r12=0000000000000780 r13=0000000000000001
r14=fffff8a006dda0c0 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
atipmdag+0x2a19e1:
fffff880`04acf9e1 ff5020 call qword ptr [rax+20h] ds: 002b: 3b660a9f`a3077620=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004acf9e1
STACK_TEXT:
fffff880`076f5430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atipmdag+0x2a19e1
FOLLOWUP_IP:
atipmdag+2a19e1
fffff880`04acf9e1 ff5020 call qword ptr [rax+20h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atipmdag+2a19e1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atipmdag
IMAGE_NAME: atipmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b8ddbbc
STACK_COMMAND: .cxr 0xfffff880076f4a50 ; kb
FAILURE_BUCKET_ID: X64_0x3B_atipmdag+2a19e1
BUCKET_ID: X64_0x3B_atipmdag+2a19e1
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101711-13868-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Mon Oct 17 08: 29: 07.166 2011 (UTC + 2: 00)
System Uptime: 0 days 1: 07: 15.602
Loading Kernel Symbols
.................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff80002ab022b, fffff88003316908, fffff88003316160}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ab022b, The address that the exception occurred at
Arg3: fffff88003316908, Exception Record Address
Arg4: fffff88003316160, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!ExpScanGeneralLookasideList+a0
fffff800`02ab022b 418b40d8 mov eax,dword ptr [r8-28h]
EXCEPTION_RECORD: fffff88003316908 -- (.exr 0xfffff88003316908)
Cannot read Exception record @ fffff88003316908
CONTEXT: fffff88003316160 -- (.cxr 0xfffff88003316160)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ac9a3a to fffff880041b37f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02ac9a3a : 00000000`002ce895 fffffa80`052ab698 fffff800`02c42c40 00000000`00000001 : 0xfffff880`041b37f2
fffff800`00b9cca0 fffff800`02ac46cc : fffff800`02c34e80 fffff800`00000000 00000000`00000000 fffff800`02bdac80 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+a0
fffff800`02ab022b 418b40d8 mov eax,dword ptr [r8-28h]
SYMBOL_NAME: nt!ExpScanGeneralLookasideList+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88003316160 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!ExpScanGeneralLookasideList+a0
BUCKET_ID: X64_0x7E_nt!ExpScanGeneralLookasideList+a0
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101711-13228-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Mon Oct 17 22: 31: 36.404 2011 (UTC + 2: 00)
System Uptime: 0 days 1: 59: 22.840
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002d571c8, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+48 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d571c8, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!MiRelocateImageAgain+48
fffff800`02d571c8 f0480fba2e00 lock bts qword ptr [rsi],0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca90e0
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ab2a17 to fffff80002a72f00
STACK_TEXT:
fffff880`069c7838 fffff800`02ab2a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02d571c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`069c7840 fffff800`02a72542 : fffff880`069c8018 ffffffff`ffffffff fffff880`069c80c0 5db2423a`35fe9683 : nt! ? : FNODOBFM: `string'+0x460da
fffff880`069c7ee0 fffff800`02a70e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`069c80c0 fffff800`02d571c8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00207000 : nt!KiGeneralProtectionFault+0x10a
fffff880`069c8250 fffff800`02d6b0ae : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x48
fffff880`069c82a0 fffff800`02d60893 : fffff880`069c8500 00000000`00000000 fffff880`069c85a8 fffff880`069c84f8 : nt!MmCreateSection+0x302
fffff880`069c84b0 fffff800`02ece205 : fffff8a0`08170498 00000000`00000000 00000000`00000001 00000002`00000000 : nt!NtCreateSection+0x162
fffff880`069c8530 fffff800`02ece5b7 : 00000000`00000010 fffff8a0`00287720 fffff880`069c86c0 00000000`0000002c : nt!PfSnGetSectionObject+0x2d5
fffff880`069c8620 fffff800`02ece9e7 : fffff880`069c8740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x247
fffff880`069c8710 fffff800`02ecee0f : 00000000`fdc535c0 fffffa80`05e082c0 fffff8a0`09846000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187
fffff880`069c8980 fffff800`02cc72bf : 00000000`00000000 00000000`49af697d fffffa80`06189150 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`069c8a50 fffff800`02d3e13c : fffffa80`061ca840 fffffa80`06189150 00000000`14050800 00000000`7efde000 : nt! ? : NNGAKEGL: `string'+0x51390
fffff880`069c8a80 fffff800`02a515b5 : fffff800`02bebe80 00000000`00000000 fffff800`02d3e040 fffffa80`061ca840 : nt!PspUserThreadStartup+0xfc
fffff880`069c8ae0 fffff800`02a51537 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`069c8c20 00000000`77603260 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0016f968 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77603260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiRelocateImageAgain+48
fffff800`02d571c8 f0480fba2e00 lock bts qword ptr [rsi],0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!MiRelocateImageAgain+48
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!MiRelocateImageAgain+48
BUCKET_ID: X64_0x1E_c0000005_nt!MiRelocateImageAgain+48
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101711-13104-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a63000 PsLoadedModuleList = 0xfffff800`02ca0e50
Debug session time: Mon Oct 17 19: 51: 58.639 2011 (UTC + 2: 00)
System Uptime: 0 days 2: 36: 26.465
Loading Kernel Symbols
................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff80002b5d9e0, fffff880031a80e8, fffff880031a7940}
Probably caused by : ntkrnlmp.exe ( nt!WmipDoFindRegEntryByDevice+10 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002b5d9e0, The address that the exception occurred at
Arg3: fffff880031a80e8, Exception Record Address
Arg4: fffff880031a7940, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!WmipDoFindRegEntryByDevice+10
fffff800`02b5d9e0 48394810 cmp qword ptr [rax+10h],rcx
EXCEPTION_RECORD: fffff880031a80e8 -- (.exr 0xfffff880031a80e8)
Cannot read Exception record @ fffff880031a80e8
CONTEXT: fffff880031a7940 -- (.cxr 0xfffff880031a7940)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ae2a3a to fffff8800415c7f2
STACK_TEXT:
fffff800`04078c98 fffff800`02ae2a3a : 00000000`002ce881 fffffa80`0530b818 fffff800`02c5bc40 00000000`00000001 : 0xfffff880`0415c7f2
fffff800`04078ca0 fffff800`02add6cc : fffff800`02c4de80 fffff800`00000000 00000000`00000000 fffff880`04002db0 : nt!PoIdle+0x53a
fffff800`04078d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
FOLLOWUP_IP:
nt!WmipDoFindRegEntryByDevice+10
fffff800`02b5d9e0 48394810 cmp qword ptr [rax+10h],rcx
SYMBOL_NAME: nt!WmipDoFindRegEntryByDevice+10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff880031a7940 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!WmipDoFindRegEntryByDevice+10
BUCKET_ID: X64_0x7E_nt!WmipDoFindRegEntryByDevice+10
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101511-13962-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a5a000 PsLoadedModuleList = 0xfffff800`02c97e50
Debug session time: Sat Oct 15 15: 30: 37.966 2011 (UTC + 2: 00)
System Uptime: 0 days 5: 54: 54.777
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8005e52000, fffffa8005e52930, 4930000}
Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+e276 )
Followup: MachineOwner
---------
2: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8005e52000, The pool entry we were looking for within the page.
Arg3: fffffa8005e52930, The next pool entry.
Arg4: 0000000004930000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d020e0
fffffa8005e52000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002bfd6d3 to fffff80002acbf00
STACK_TEXT:
fffff880`031b6208 fffff800`02bfd6d3 : 00000000`00000019 00000000`00000020 fffffa80`05e52000 fffffa80`05e52930 : nt!KeBugCheckEx
fffff880`031b6210 fffff880`01459695 : 00000000`00000000 00000000`00000006 fffffa80`72614841 00000000`00000000 : nt!ExFreePool+0xda4
fffff880`031b62c0 fffff880`0420e276 : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000006 : ndis!NdisFreeMemory+0x15
fffff880`031b62f0 00000000`00000006 : 00000000`00000000 00000000`00000000 00000000`00000006 fffffa80`05e26a80 : athrxusb+0xe276
fffff880`031b62f8 00000000`00000000 : 00000000`00000000 00000000`00000006 fffffa80`05e26a80 00000000`000000ec : 0x6
STACK_COMMAND: kb
FOLLOWUP_IP:
athrxusb+e276
fffff880`0420e276 ? ?
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: athrxusb+e276
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrxusb
IMAGE_NAME: athrxusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 458bca1d
FAILURE_BUCKET_ID: X64_0x19_20_athrxusb+e276
BUCKET_ID: X64_0x19_20_athrxusb+e276
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101511-13556-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Sat Oct 15 18: 53: 23.147 2011 (UTC + 2: 00)
System Uptime: 0 days 3: 21: 05.973
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004fcc2a3, fffff8800235f668, fffff8800235eec0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL: EndPreparation+7b )
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: fffff88004fcc2a3, The address that the exception occurred at
Arg3: fffff8800235f668, Exception Record Address
Arg4: fffff8800235eec0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL: EndPreparation+7b
fffff880`04fcc2a3 488b01 mov rax,qword ptr [rcx]
EXCEPTION_RECORD: fffff8800235f668 -- (.exr 0xfffff8800235f668)
ExceptionAddress: fffff88004fcc2a3 (dxgmms1!VIDMM_GLOBAL: EndPreparation+0x000000000000007b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800235eec0 -- (.cxr 0xfffff8800235eec0)
rax=fffffa8005c19940 rbx=fffffa8005ce9000 rcx=8f65b4c8b66fac04
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004fcc2a3 rsp=fffff8800235f8a0 rbp=fffffa800673d300
r8=0000000000000000 r9=fffffa8005ce9c40 r10=fffffa8005ce9c40
r11=0000000000000024 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 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
dxgmms1!VIDMM_GLOBAL: EndPreparation+0x7b:
fffff880`04fcc2a3 488b01 mov rax,qword ptr [rcx] ds: 002b: 8f65b4c8`b66fac04=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbb0e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL: EndPreparation+7b
fffff880`04fcc2a3 488b01 mov rax,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004fc479d to fffff88004fcc2a3
STACK_TEXT:
fffff880`0235f8a0 fffff880`04fc479d : 00000000`00000000 fffffa80`06740000 00000000`00000024 00000000`00000000 : dxgmms1!VIDMM_GLOBAL: EndPreparation+0x7b
fffff880`0235f910 fffff880`04fde65d : 00000000`00000000 fffff8a0`01dc4650 fffffa80`00000000 fffffa80`0673d300 : dxgmms1!VIDMM_GLOBAL: PrepareDmaBuffer+0xd09
fffff880`0235fae0 fffff880`04fde398 : fffff880`02f68f40 fffff880`04fddd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0235fcd0 fffff880`04fdde96 : 00000000`00000000 fffffa80`0673d010 00000000`00000080 fffffa80`05c76010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0235fd00 fffff800`02d28166 : 00000000`025439d7 fffffa80`05cc7b60 fffffa80`03e6e040 fffffa80`05cc7b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0235fd40 fffff800`02a63486 : fffff880`02f64180 fffffa80`05cc7b60 fffff880`02f6efc0 fffff880`0122a534 : nt!PspSystemThreadStartup+0x5a
fffff880`0235fd80 00000000`00000000 : fffff880`02360000 fffff880`0235a000 fffff880`0235f690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL: EndPreparation+7b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff8800235eec0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL: EndPreparation+7b
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL: EndPreparation+7b
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101311-15225-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Thu Oct 13 17: 20: 56.212 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 04: 55.038
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff88000c0b263, 0, ffffffffffffffff}
Probably caused by : CI.dll ( CI!CiValidateImageData+2f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c0b263, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
CI!CiValidateImageData+2f
fffff880`00c0b263 8b4958 mov ecx,dword ptr [rcx+58h]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb0e0
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: ipla.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002b04a17 to fffff80002ac4f00
STACK_TEXT:
fffff880`07264c98 fffff800`02b04a17 : 00000000`0000001e ffffffff`c0000005 fffff880`00c0b263 00000000`00000000 : nt!KeBugCheckEx
fffff880`07264ca0 fffff800`02ac4542 : fffff880`07265478 f15e156b`ee5da180 fffff880`07265520 00000000`00000000 : nt! ? : FNODOBFM: `string'+0x460da
fffff880`07265340 fffff800`02ac2e4a : 00000008`01ee0101 00000000`00000000 00000000`00121800 fffff8a0`00060001 : nt!KiExceptionDispatch+0xc2
fffff880`07265520 fffff880`00c0b263 : 00000000`00000000 00000000`00000003 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`072656b0 fffff800`02d5fce5 : fffffa80`05d1a940 fffffa80`05d1a940 f15e156b`ee5da180 fffffa80`01de9d10 : CI!CiValidateImageData+0x2f
fffff880`07265890 fffff800`02d5fbb9 : fffffa80`00000000 fffffa80`00005724 fffff880`00000000 fffffa80`00000000 : nt!SeValidateImageData+0x21
fffff880`072658c0 fffff800`02ab65b7 : fffffa80`01de9d10 fffffa80`0407fdc0 00000000`00000000 ffffffff`ffffffff : nt!MiValidateImagePfn+0xb5
fffff880`07265910 fffff800`02ab6d8b : fffffa80`0407fd00 fffff880`07265a80 fffffa80`03fcaec8 fffffa80`04021060 : nt!MiWaitForInPageComplete+0x9a7
fffff880`072659f0 fffff800`02ae009b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`07265ac0 fffff800`02ac2fee : 00000000`00000008 00000000`002db070 00000000`00000001 00000000`00000004 : nt!MmAccessFault+0x14bb
fffff880`07265c20 00000000`756a2050 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`002dafa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x756a2050
STACK_COMMAND: kb
FOLLOWUP_IP:
CI!CiValidateImageData+2f
fffff880`00c0b263 8b4958 mov ecx,dword ptr [rcx+58h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: CI!CiValidateImageData+2f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: CI
IMAGE_NAME: CI.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5be01d
FAILURE_BUCKET_ID: X64_0x1E_c0000005_CI!CiValidateImageData+2f
BUCKET_ID: X64_0x1E_c0000005_CI!CiValidateImageData+2f
Followup: MachineOwner
---------
Kod:
[code]
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp4\Minidump\101011-15381-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50
Debug session time: Mon Oct 10 18: 43: 13.039 2011 (UTC + 2: 00)
System Uptime: 0 days 3: 58: 44.476
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004ba5e86, fffff8800235d108, fffff8800235c960}
Probably caused by : atipmdag.sys ( atipmdag+2b6e86 )
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: fffff88004ba5e86, The address that the exception occurred at
Arg3: fffff8800235d108, Exception Record Address
Arg4: fffff8800235c960, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
atipmdag+2b6e86
fffff880`04ba5e86 8902 mov dword ptr [rdx],eax
EXCEPTION_RECORD: fffff8800235d108 -- (.exr 0xfffff8800235d108)
ExceptionAddress: fffff88004ba5e86 (atipmdag+0x00000000002b6e86)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 00000000125ee000
Attempt to write to address 00000000125ee000
CONTEXT: fffff8800235c960 -- (.cxr 0xfffff8800235c960)
rax=0000000000000003 rbx=fffffa8005d6c000 rcx=fffffa8005d91bc0
rdx=00000000125ee000 rsi=fffff8800235d610 rdi=0000000000001000
rip=fffff88004ba5e86 rsp=fffff8800235d348 rbp=0000000000000014
r8=0000000000001000 r9=fffff88004ce77a0 r10=fffff8800235d220
r11=fffff88005106000 r12=00000000ffffffff r13=fffffa8005e2ca40
r14=0000000000000000 r15=00000000c0000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
atipmdag+0x2b6e86:
fffff880`04ba5e86 8902 mov dword ptr [rdx],eax ds: 002b: 00000000`125ee000=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 00000000125ee000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cac0e0
00000000125ee000
FOLLOWUP_IP:
atipmdag+2b6e86
fffff880`04ba5e86 8902 mov dword ptr [rdx],eax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004b7fb9d to fffff88004ba5e86
STACK_TEXT:
fffff880`0235d348 fffff880`04b7fb9d : 00000000`00000001 fffff880`0e180600 00000000`00000002 fffff800`02a84494 : atipmdag+0x2b6e86
fffff880`0235d350 00000000`00000001 : fffff880`0e180600 00000000`00000002 fffff800`02a84494 fffffa80`03eac620 : atipmdag+0x290b9d
fffff880`0235d358 fffff880`0e180600 : 00000000`00000002 fffff800`02a84494 fffffa80`03eac620 fffff880`0491532a : 0x1
fffff880`0235d360 00000000`00000002 : fffff800`02a84494 fffffa80`03eac620 fffff880`0491532a 00000000`125ee000 : 0xfffff880`0e180600
fffff880`0235d368 fffff800`02a84494 : fffffa80`03eac620 fffff880`0491532a 00000000`125ee000 00000000`125ee000 : 0x2
fffff880`0235d370 fffff800`00000000 : fffff880`0e172000 00000000`00000016 fffffa80`05e74000 fffff880`045db879 : nt!KiIpiProcessRequests+0x194
fffff880`0235d450 fffff880`0e172000 : 00000000`00000016 fffffa80`05e74000 fffff880`045db879 fffffa80`05d6e100 : 0xfffff800`00000000
fffff880`0235d458 00000000`00000016 : fffffa80`05e74000 fffff880`045db879 fffffa80`05d6e100 fffffa80`05e74000 : 0xfffff880`0e172000
fffff880`0235d460 fffffa80`05e74000 : fffff880`045db879 fffffa80`05d6e100 fffffa80`05e74000 00000000`8000004f : 0x16
fffff880`0235d468 fffff880`045db879 : fffffa80`05d6e100 fffffa80`05e74000 00000000`8000004f fffff880`0e174c00 : 0xfffffa80`05e74000
fffff880`0235d470 fffff880`045dba1e : 00000000`00000000 80000001`8000007e 00000000`00000000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL: UpdateFence+0x15
fffff880`0235d4a0 fffff880`0235d610 : 00000000`00000000 fffff880`044c79ac fffffa80`04f6e060 fffff8a0`09b5d010 : dxgmms1!VIDMM_GLOBAL: xWaitForAllEngines+0x56
fffff880`0235d5a0 00000000`00000000 : fffff880`044c79ac fffffa80`04f6e060 fffff8a0`09b5d010 00000000`00000000 : 0xfffff880`0235d610
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atipmdag+2b6e86
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atipmdag
IMAGE_NAME: atipmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b8ddbbc
STACK_COMMAND: .cxr 0xfffff8800235c960 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atipmdag+2b6e86
BUCKET_ID: X64_0x7E_atipmdag+2b6e86
Followup: MachineOwner
---------
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
Post: #1
