jestem na forum nowy
od jakiegoś czasu ciągle męczą mnie bluescreeny. zastanawiam się, jaki może być problem.
a więc zaczynamy:
Procesor: Intel Core 2 Duo E4600 @ 2,4GHz
Płyta główna: Gigabyte GA-P35-DS3L rev 2.0
Grafika: NVIDIA GeForce 9600 GSO 512
Ram: standardowo mam 2x2GB Corsair XMS2-6400 800Mhz, ale teraz wstawione jakis noname 1GB, żeby sprawdzić czy błędy powoduje pamięć - jednak BSOD mam nadal.
Dysk: Seagate 1TB
System: Vista Bussiness 64bity
HD Tune:
Kod: Zaznacz cały
HD Tune: ST31000528AS Health
ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 116 99 6 103802959 Ok
(03) Spin Up Time 96 95 0 0 Ok
(04) Start/Stop Count 100 100 20 245 Ok
(05) Reallocated Sector Count 100 100 36 0 Ok
(07) Seek Error Rate 75 60 30 39550605 Ok
(09) Power On Hours Count 99 99 0 1038 Ok
(0A) Spin Retry Count 100 100 97 0 Ok
(0C) Power Cycle Count 100 100 20 108 Ok
(B7) (unknown attribute) 100 100 0 0 Ok
(B8) (unknown attribute) 100 100 99 0 Ok
(BB) (unknown attribute) 98 98 0 2 Ok
(BC) (unknown attribute) 100 99 0 65539 Ok
(BD) (unknown attribute) 100 100 0 0 Ok
(BE) Airflow Temperature 63 53 45 622395429 Ok
(C2) Temperature 37 47 0 37 Ok
(C3) Hardware ECC Recovered 49 31 0 103802959 Ok
(C5) Current Pending Sector 100 100 0 0 Ok
(C6) Offline Uncorrectable 100 100 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok
(F0) Head Flying Hours 100 253 0 1301 Ok
(F1) (unknown attribute) 100 253 0 -616957524 Ok
(F2) (unknown attribute) 100 253 0 -898343873 Ok
Power On Time : 1038
Health Status : Ok
dump nr 1 z dzisiaj
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061111-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`0220b000 PsLoadedModuleList = 0xfffff800`023cfdd0
Debug session time: Sat Jun 11 13:57:25.869 2011 (UTC + 2:00)
System Uptime: 0 days 0:06:27.740
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa800b000000, 0, fffff8000226f570, 2}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+c0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800b000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000226f570, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002432080
fffffa800b000000
FAULTING_IP:
nt!ExAcquireResourceSharedLite+c0
fffff800`0226f570 498b03 mov rax,qword ptr [r11]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: SearchIndexer.e
CURRENT_IRQL: 0
TRAP_FRAME: fffffa600b9bcda0 -- (.trap 0xfffffa600b9bcda0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=4cc88b4d90909090 rbx=0000000000000000 rcx=fffffa8ff72549d0
rdx=fffffa800475b4e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000226f570 rsp=fffffa600b9bcf30 rbp=0000000000000001
r8=fffffa80071549e0 r9=0000000000000000 r10=000000000000000b
r11=fffffa800b000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na po cy
nt!ExAcquireResourceSharedLite+0xc0:
fffff800`0226f570 498b03 mov rax,qword ptr [r11] ds:fffffa80`0b000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800022c5a8a to fffff80002265490
STACK_TEXT:
fffffa60`0b9bccb8 fffff800`022c5a8a : 00000000`00000050 fffffa80`0b000000 00000000`00000000 fffffa60`0b9bcda0 : nt!KeBugCheckEx
fffffa60`0b9bccc0 fffff800`02264019 : 00000000`00000000 fffffa60`005eca50 00000000`00000000 fffffa80`0475b4b0 : nt! ?? ::FNODOBFM::`string'+0x2c465
fffffa60`0b9bcda0 fffff800`0226f570 : ffffffff`ffb3b4c0 fffffa80`04177ca0 fffffa80`0618f700 fffffa80`04177ca0 : nt!KiPageFault+0x119
fffffa60`0b9bcf30 fffffa60`010ce940 : fffffa80`04177ca0 fffffa80`04177ca0 fffffa80`048b1780 fffffa60`0b9bd088 : nt!ExAcquireResourceSharedLite+0xc0
fffffa60`0b9bcf80 fffffa60`010cfd0f : fffff880`006d8c80 fffffa60`0b9bd328 fffffa80`00000400 00000000`00000001 : Ntfs!NtfsWriteLog+0x350
fffffa60`0b9bd1c0 fffffa60`010e37d1 : fffffa80`04177ca0 00000000`0404f000 fffff880`006d8c80 00000000`6d343308 : Ntfs!NtfsWriteFileSizes+0x34f
fffffa60`0b9bd320 fffffa60`010e33b7 : fffffa80`04177ca0 fffffa80`0475b180 fffffa80`04177ca0 00000000`00000050 : Ntfs!NtOfsSetLength+0xb1
fffffa60`0b9bd420 fffffa60`010e4454 : fffffa80`04177ca0 fffffa80`04c80001 00000000`6d3432b8 00000000`00000000 : Ntfs!NtOfsPutData+0x57
fffffa60`0b9bd560 fffffa60`010e42ae : fffffa80`04177ca0 00000000`00000001 fffffa80`04177d20 00000000`00000001 : Ntfs!NtfsWriteFcbUsnRecordToJournal+0xa4
fffffa60`0b9bd620 fffffa60`010c0378 : fffffa80`00000000 fffffa80`0475b180 fffff880`0c5eab50 fffffa80`049131c0 : Ntfs!NtfsWriteUsnJournalChanges+0x15e
fffffa60`0b9bd6a0 fffffa60`010c94a3 : fffffa80`04177ca0 fffff880`0c5eac80 fffff880`0c5eab50 fffffa80`0475b180 : Ntfs!NtfsCommonClose+0x6f8
fffffa60`0b9bd770 fffffa60`00a0fe91 : fffffa80`03e33400 fffffa80`048b1780 fffffa80`00000000 00000000`00000000 : Ntfs!NtfsFsdClose+0x2a3
fffffa60`0b9bd870 fffffa60`00a0e0dd : fffffa80`05f7dde0 fffffa80`06bd68c0 fffffa80`045c4e00 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x211
fffffa60`0b9bd8e0 fffffa60`00a0fe91 : fffffa80`048b1b20 fffffa80`04c80010 00000000`00000002 fffff800`0233fde2 : fltmgr!FltpDispatch+0xcd
fffffa60`0b9bd940 fffffa60`00a0e0dd : fffffa80`06bda750 fffffa80`04754090 fffffa80`06bd6800 00000000`000007ff : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x211
fffffa60`0b9bd9b0 fffff800`024cfa7e : fffffa80`049131c0 fffffa80`04754090 00000000`00000000 00000000`20707249 : fltmgr!FltpDispatch+0xcd
fffffa60`0b9bda10 fffff800`02269ed3 : 00000000`00000000 fffffa80`049131c0 fffffa80`04913190 00000000`74636553 : nt!IopDeleteFile+0x17e
fffffa60`0b9bdaa0 fffff800`024cfd9e : fffff880`0cf87660 fffffa80`00000001 fffffa80`05f53c10 00000000`00000000 : nt!ObfDereferenceObject+0x103
fffffa60`0b9bdb30 fffff800`024d0054 : fffff880`0b9fec10 fffff880`0b9fec00 00000000`00000001 00000000`00001198 : nt!ObpCloseHandleTableEntry+0xce
fffffa60`0b9bdbd0 fffff800`02264f33 : fffffa80`04c67bb0 fffffa60`0b9bdca0 00000000`022c5270 00000000`00000e58 : nt!ObpCloseHandle+0x94
fffffa60`0b9bdc20 00000000`77b86c8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0c2fe878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b86c8a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExAcquireResourceSharedLite+c0
fffff800`0226f570 498b03 mov rax,qword ptr [r11]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ExAcquireResourceSharedLite+c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb7275f
FAILURE_BUCKET_ID: X64_0x50_nt!ExAcquireResourceSharedLite+c0
BUCKET_ID: X64_0x50_nt!ExAcquireResourceSharedLite+c0
Followup: MachineOwner
---------
dump nr 2 z dzisiaj:
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061111-02.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`0225e000 PsLoadedModuleList = 0xfffff800`02422dd0
Debug session time: Sat Jun 11 18:16:31.091 2011 (UTC + 2:00)
System Uptime: 0 days 2:00:41.332
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8000236dbe0, fffffa60019166e8, fffffa60019160c0}
Probably caused by : memory_corruption ( nt!MiLogPageAccess+e0 )
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: fffff8000236dbe0, The address that the exception occurred at
Arg3: fffffa60019166e8, Exception Record Address
Arg4: fffffa60019160c0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!MiLogPageAccess+e0
fffff800`0236dbe0 410fba653814 bt dword ptr [r13+38h],14h
EXCEPTION_RECORD: fffffa60019166e8 -- (.exr 0xfffffa60019166e8)
ExceptionAddress: fffff8000236dbe0 (nt!MiLogPageAccess+0x00000000000000e0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffa60019160c0 -- (.cxr 0xfffffa60019160c0)
rax=0200000000000000 rbx=fffff88000e6f018 rcx=f88000e6f0180000
rdx=fffff6fcc0017c08 rsi=fffffa80040d49c0 rdi=fffffa8001245000
rip=fffff8000236dbe0 rsp=fffffa6001916920 rbp=000000000000005a
r8=fffff80002423240 r9=0000000000000003 r10=0000000000000066
r11=fffff88009a2a000 r12=fffffa8001245ff8 r13=2c6c702e6b657a63
r14=0000000000000000 r15=fffff6fcc0017c08
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiLogPageAccess+0xe0:
fffff800`0236dbe0 410fba653814 bt dword ptr [r13+38h],14h ds:002b:2c6c702e`6b657a9b=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
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 fffff80002485080
ffffffffffffffff
FOLLOWUP_IP:
nt!MiLogPageAccess+e0
fffff800`0236dbe0 410fba653814 bt dword ptr [r13+38h],14h
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002355de3 to fffff8000236dbe0
STACK_TEXT:
fffffa60`01916920 fffff800`02355de3 : 00000000`1fcbd000 41100000`15dc6921 00000003`00000000 00000000`73576d4d : nt!MiLogPageAccess+0xe0
fffffa60`01916980 fffff800`02379a71 : fffff800`02423240 00000000`00000003 fffffa60`01916bb0 fffffa60`01916be0 : nt!MiAgeWorkingSet+0x2d3
fffffa60`01916b40 fffff800`022612f0 : fffffa80`00000159 00000000`00000002 fffff800`0240e3a8 00000000`00000000 : nt!MiProcessWorkingSets+0x231
fffffa60`01916bb0 fffff800`022cc0d0 : fffffa80`00c8db00 00000000`00000001 00000000`00000004 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x34af0
fffffa60`01916c10 fffff800`024c2f77 : fffffa80`00c8dbb0 00000000`00000080 00000000`00000000 00000000`00000001 : nt!KeBalanceSetManager+0x120
fffffa60`01916d50 fffff800`022f5636 : fffff800`023d1680 fffffa80`00c8dbb0 fffff800`023d6b80 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffffa60`01916d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiLogPageAccess+e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb7275f
STACK_COMMAND: .cxr 0xfffffa60019160c0 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_nt!MiLogPageAccess+e0
BUCKET_ID: X64_0x7E_nt!MiLogPageAccess+e0
Followup: MachineOwner
---------
pojawiaja się tez system_service_exception i bad pool header.
Na tych moich pamieciach Corsair wywala błędy, po zmianie na 1gb noname też się pojawiają.
Sigverif.exe pokazuje że, dsoftbus01.sys nie jest podpisany cyfrowo i zmieniony 26. marca 2011.
Druga sprawa, BSOD zaczely sie pojawiac mniej więcej po zaisntalowaniu sterowników do karty sieciowej WIFI (ten sagem dodawany do neostrady). Sterowniki ściągniete z sieci. Nie wiem nawet czy oficjalne.
Komputer był tez przedtem przewozony w aucie przez 300km więc, moze cos się ficzynie uszkodziło?
prosze o wszelkie rady i wskazówki.
Pozdrawiam
p.s. jesli potrzeba wiecej dumpow to mgoe wstawiac z wczoraj ( jest chyba z 6 )
-- 11 cze 2011, 19:24 --
wczoraj
1
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061011-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02057000 PsLoadedModuleList = 0xfffff800`0221cdb0
Debug session time: Fri Jun 10 00:28:33.674 2011 (UTC + 2:00)
System Uptime: 0 days 0:46:39.455
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800020bd4bc, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+292b7 )
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: fffff800020bd4bc, 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!IoGetRelatedDeviceObject+c
fffff800`020bd4bc 488b4008 mov rax,qword ptr [rax+8]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002280080
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: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002085ec7 to fffff800020ac410
STACK_TEXT:
fffffa60`0a8c69a8 fffff800`02085ec7 : 00000000`0000001e ffffffff`c0000005 fffff800`020bd4bc 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0a8c69b0 fffff800`020ac269 : fffffa60`0a8c70e8 00000000`00000000 fffffa60`0a8c7190 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x292b7
fffffa60`0a8c6fb0 fffff800`020aae4d : 00000000`00000000 fffff800`023276b0 fffffa80`04714bf0 fffffa80`04714bf0 : nt!KiExceptionDispatch+0xa9
fffffa60`0a8c7190 fffff800`020bd4bc : fffff800`02327431 fffffa60`0a8c7408 00000000`00000000 fffffa80`040c13d0 : nt!KiGeneralProtectionFault+0xcd
fffffa60`0a8c7328 fffff800`02327431 : fffffa60`0a8c7408 00000000`00000000 fffffa80`040c13d0 00000000`00000000 : nt!IoGetRelatedDeviceObject+0xc
fffffa60`0a8c7330 fffff800`020946db : fffffa80`072699f0 fffffa60`0a8c7908 00000000`00000001 00000000`00000000 : nt!FsRtlAcquireFileExclusiveCommon+0x41
fffffa60`0a8c75d0 fffff800`022fa1b6 : fffffa60`0a8c7601 00000000`00000000 fffffa80`072699f0 fffffa60`00000000 : nt!CcZeroEndOfLastPage+0x5b
fffffa60`0a8c7640 fffff800`02459f23 : 00000000`00000000 00000000`0000000d fffff880`1011ad98 fffffa80`00000000 : nt!NtCreateSection+0x1ad
fffffa60`0a8c76d0 fffff800`0245c1c6 : 00000000`00000000 fffff880`1011ad98 fffff880`1011a000 fffffa60`00000060 : nt!PfpFileBuildReadSupport+0x163
fffffa60`0a8c77c0 fffff800`02485bb9 : fffff880`00000000 00000000`000004c1 00000000`00000045 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x126
fffffa60`0a8c78c0 fffff800`02485e72 : 00000000`00000000 fffffa60`0a8c7ca0 fffffa60`0a8c7a08 fffff880`1011a001 : nt!PfpPrefetchRequestPerform+0x2f9
fffffa60`0a8c7960 fffff800`024860d6 : fffffa60`0a8c7a08 fffffa80`07796901 fffffa80`097bb8d0 00000000`00000000 : nt!PfpPrefetchRequest+0x171
fffffa60`0a8c79d0 fffff800`02498808 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`0417ed01 : nt!PfSetSuperfetchInformation+0x1a5
fffffa60`0a8c7ab0 fffff800`020abeb3 : fffffa80`03c9d060 00000000`00000000 00000000`00000001 00000000`00008788 : nt!NtSetSystemInformation+0x8fb
fffffa60`0a8c7c20 00000000`77c0667a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0417f4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c0667a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+292b7
fffff800`02085ec7 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+292b7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb71b96
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+292b7
BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+292b7
Followup: MachineOwner
---------
2
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061011-02.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02046000 PsLoadedModuleList = 0xfffff800`0220bdb0
Debug session time: Fri Jun 10 19:06:54.201 2011 (UTC + 2:00)
System Uptime: 0 days 1:49:38.233
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002095af6, fffffa600c0bd4c0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\n64i1639.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for n64i1639.sys
*** ERROR: Module load completed but symbols could not be loaded for n64i1639.sys
Probably caused by : n64i1639.sys ( n64i1639+22c70 )
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: fffff80002095af6, Address of the instruction which caused the bugcheck
Arg3: fffffa600c0bd4c0, 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!ExInterlockedRemoveHeadList+36
fffff800`02095af6 49894808 mov qword ptr [r8+8],rcx
CONTEXT: fffffa600c0bd4c0 -- (.cxr 0xfffffa600c0bd4c0)
rax=fffffa8005eeb980 rbx=fffffa8005f41e30 rcx=fffffa80053a7c88
rdx=fffffa80053a7c98 rsi=0000000000000042 rdi=fffffa800458e3b0
rip=fffff80002095af6 rsp=fffffa600c0bdd20 rbp=fffffa80053a7c00
r8=2751f0f4fa792418 r9=0000000001070009 r10=0000000000000002
r11=fffffa80063b7670 r12=fffffa80053a7c88 r13=0000000000000000
r14=0000000000000000 r15=fffffa600c0bdf40
iopl=0 nv up di pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010012
nt!ExInterlockedRemoveHeadList+0x36:
fffff800`02095af6 49894808 mov qword ptr [r8+8],rcx ds:002b:2751f0f4`fa792420=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: Skype.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffffa6002ca0c70 to fffff80002095af6
STACK_TEXT:
fffffa60`0c0bdd20 fffffa60`02ca0c70 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExInterlockedRemoveHeadList+0x36
fffffa60`0c0bdd30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : n64i1639+0x22c70
FOLLOWUP_IP:
n64i1639+22c70
fffffa60`02ca0c70 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: n64i1639+22c70
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: n64i1639
IMAGE_NAME: n64i1639.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4aa68a07
STACK_COMMAND: .cxr 0xfffffa600c0bd4c0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_n64i1639+22c70
BUCKET_ID: X64_0x3B_n64i1639+22c70
Followup: MachineOwner
---------
3
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061011-03.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02009000 PsLoadedModuleList = 0xfffff800`021cedb0
Debug session time: Fri Jun 10 20:47:53.282 2011 (UTC + 2:00)
System Uptime: 0 days 1:01:13.176
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904aa, fffffa60017f5388, fffffa60017f4d60, fffff800020655da}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireExclusiveScb+47 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904aa
Arg2: fffffa60017f5388
Arg3: fffffa60017f4d60
Arg4: fffff800020655da
Debugging Details:
------------------
EXCEPTION_RECORD: fffffa60017f5388 -- (.exr 0xfffffa60017f5388)
ExceptionAddress: fffff800020655da (nt!KeWaitForSingleObject+0x000000000000014a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: ffffffffffffffff
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffffa60017f4d60 -- (.cxr 0xfffffa60017f4d60)
rax=fffff80002234440 rbx=000000088dae9955 rcx=fffffa60005ec7f0
rdx=0000000000000000 rsi=fffffa80036afca8 rdi=fffffa80036afbb0
rip=fffff800020655da rsp=fffffa60017f55c0 rbp=fa04ab850d395f88
r8=fffffa80036afd38 r9=0000000000000000 r10=0000000000000000
r11=000000000000000c r12=0000000000000000 r13=fffffa60017f56c0
r14=fffffa60005ec180 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!KeWaitForSingleObject+0x14a:
fffff800`020655da 807d0002 cmp byte ptr [rbp],2 ss:0018:fa04ab85`0d395f88=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: c
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: ffffffffffffffff
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002232080
0000000000000000
FOLLOWUP_IP:
Ntfs!NtfsAcquireExclusiveScb+47
fffffa60`01020967 84c0 test al,al
FAULTING_IP:
nt!KeWaitForSingleObject+14a
fffff800`020655da 807d0002 cmp byte ptr [rbp],2
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff80002075d2a to fffff800020655da
STACK_TEXT:
fffffa60`017f55c0 fffff800`02075d2a : 00000000`000001e2 01cc2795`0000001b 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x14a
fffffa60`017f5650 fffffa60`01020967 : ffffffff`ffb3b4c0 00000000`00000000 00000000`00000000 fffff880`00fe6010 : nt!ExAcquireResourceExclusiveLite+0xca
fffffa60`017f56c0 fffffa60`010ce631 : fffffa80`072d6110 fffffa80`0592e760 fffff880`00fd89e0 fffffa80`058a5d00 : Ntfs!NtfsAcquireExclusiveScb+0x47
fffffa60`017f5700 fffffa60`010ced8b : fffffa80`058a5d00 fffffa80`0592e760 fffffa80`0592e760 fffffa80`04745180 : Ntfs!NtfsCommonFlushBuffers+0x591
fffffa60`017f57d0 fffffa60`00a04e17 : fffffa80`0592eb00 fffffa80`0592e760 fffffa80`058a5d00 fffffa60`017f57f8 : Ntfs!NtfsFsdFlushBuffers+0x10b
fffffa60`017f5840 fffffa60`00a040dd : fffffa80`04596880 fffffa80`06b07750 fffffa80`049d9000 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`017f58b0 fffffa60`00a04e17 : fffffa80`0592eb00 fffff800`0213c5fc fffffa80`05d87ca0 fffffa60`00a286fb : fltmgr!FltpDispatch+0xcd
fffffa60`017f5910 fffffa60`00a040dd : fffffa80`06d98a40 fffffa80`072d6110 fffffa80`06b07700 fffffa60`017f59d0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`017f5980 fffff800`022eaafc : 00000000`00000000 fffff800`02120de9 fffffa60`005f5d40 fffffa80`036afbb0 : fltmgr!FltpDispatch+0xcd
fffffa60`017f59e0 fffff800`022cf2c3 : fffffa80`0440a5b0 fffffa80`0440a5b0 fffffa80`072d6110 fffffa60`017f5b50 : nt!IopSynchronousServiceTail+0x13c
fffffa60`017f5a40 fffff800`0205deb3 : fffffa80`036afbb0 fffffa80`036afbb0 fffffa80`06b07750 fffffa80`072d6110 : nt!NtFlushBuffersFile+0x193
fffffa60`017f5ad0 fffff800`0205e3c0 : fffff800`022d2efb 00000000`00000000 fffffa60`005ec180 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffffa60`017f5c68 fffff800`022d2efb : 00000000`00000000 fffffa60`005ec180 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffffa60`017f5c70 fffff800`022d2609 : 00000000`00000001 fffffa80`049d76e8 fffffa80`049d76e0 fffffa80`036afbb0 : nt!CmpFileFlush+0x3f
fffffa60`017f5cc0 fffff800`0206b056 : fffff800`022d25e0 fffff800`0219b801 fffffa80`00000000 00000000`00000001 : nt!CmpLazyFlushWorker+0x29
fffffa60`017f5cf0 fffff800`02280403 : fffff800`02206220 9f67b233`e49d6043 fffffa80`036afbb0 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`017f5d50 fffff800`02098576 : fffffa60`005ec180 fffffa80`036afbb0 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`017f5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Ntfs!NtfsAcquireExclusiveScb+47
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1
STACK_COMMAND: .cxr 0xfffffa60017f4d60 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsAcquireExclusiveScb+47
BUCKET_ID: X64_0x24_Ntfs!NtfsAcquireExclusiveScb+47
Followup: MachineOwner
---------
4
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061011-04.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02017000 PsLoadedModuleList = 0xfffff800`021dcdb0
Debug session time: Fri Jun 10 21:20:54.409 2011 (UTC + 2:00)
System Uptime: 0 days 0:31:27.330
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3D, {0, 0, 0, fffffa6002d223ca}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_GetIoRequestFromObject+3e )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffffa6002d223ca
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x3D
PROCESS_NAME: plugin-containe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffffa6001722ae8 -- (.exr 0xfffffa6001722ae8)
ExceptionAddress: fffffa6002d223ca (USBPORT!USBPORT_Core_GetIoRequestFromObject+0x000000000000003e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffffa6001722b90 -- (.trap 0xfffffa6001722b90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=336364542f4e6554 rbx=0000000000000000 rcx=fffffa8004590398
rdx=fffffa8006deb602 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6002d223ca rsp=fffffa6001722d20 rbp=fffffa8006deb600
r8=000000004f444648 r9=5000e4807c000000 r10=5000e4807ccc0052
r11=00000000000007ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
USBPORT!USBPORT_Core_GetIoRequestFromObject+0x3e:
fffffa60`02d223ca 48396820 cmp qword ptr [rax+20h],rbp ds:33636454`2f4e6574=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000206c1ae to fffff8000206c410
STACK_TEXT:
fffffa60`01721b18 fffff800`0206c1ae : 00000000`0000003d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffffa60`01721b20 fffff800`0206cfe8 : fffffa80`00000002 fffff800`0253d5a0 00000006`45e40f43 fffffa60`0cf93000 : nt!KiBugCheckDispatch+0x6e
fffffa60`01721c60 fffff800`0207f6dd : 00000000`00000000 fffff800`02017000 fffffa60`0cf99000 fffff800`0221af20 : nt!KiInterruptHandler+0x28
fffffa60`01721c90 fffff800`02086d1f : fffffa60`00000001 00000000`00000001 fffff800`00000000 fffffa60`0cf98c20 : nt!RtlpExecuteHandlerForException+0xd
fffffa60`01721cc0 fffff800`02043df3 : fffffa60`01722ae8 fffffa60`017224c0 00000000`00000000 fffffa60`01722b90 : nt!RtlDispatchException+0x22f
fffffa60`017223b0 fffff800`0206c269 : fffffa60`01722ae8 fffffa80`045903a8 fffffa60`01722b90 fffffa80`04590398 : nt!KiDispatchException+0xc3
fffffa60`017229b0 fffff800`0206ae4d : fffffa80`06f85440 00000000`00000001 00000000`00000002 fffff800`02531cb6 : nt!KiExceptionDispatch+0xa9
fffffa60`01722b90 fffffa60`02d223ca : 00000000`00000000 00000000`00000000 fffffa80`0738bc40 fffffa80`0736f950 : nt!KiGeneralProtectionFault+0xcd
fffffa60`01722d20 fffffa60`02d1eb45 : fffffa80`060971a0 fffffa80`06097050 fffffa80`0736f950 fffffa80`06097050 : USBPORT!USBPORT_Core_GetIoRequestFromObject+0x3e
fffffa60`01722d50 fffffa60`02d1f420 : fffffa80`46616d64 fffffa80`06deb600 fffff800`32466d64 fffffa80`00000000 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x675
fffffa60`01722e30 fffffa60`02d1c872 : fffffa80`39585043 fffffa80`060971a0 fffffa80`06098088 fffffa80`060971a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514
fffffa60`01722ea0 fffffa60`02d0918b : fffffa80`31636f49 fffffa80`06098088 fffffa60`0cf98c02 fffffa80`060971a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a
fffffa60`01722ef0 fffff800`020759d7 : fffffa80`060980a0 fffffa60`34776478 fffffa60`0cf98ca0 fffffa60`005ef580 : USBPORT!USBPORT_Xdpc_Worker+0x26f
fffffa60`01722f40 fffff800`0206f8e5 : fffffa60`02d08f1c fffffa60`005ec180 fffffa60`0cf98ca0 fffffa80`03ac3900 : nt!KiRetireDpcList+0x117
fffffa60`01722fb0 fffff800`0206f6f7 : fffffa80`0000040e fffffa60`0cf98bf0 00000000`00000000 00000006`4ad1bba5 : nt!KyRetireDpcList+0x5
fffffa60`0cf98be0 fffff800`020b2db3 : 00000000`0d5a5700 fffff800`0206d5df 00000000`01010101 00000000`00000000 : nt!KiDispatchInterruptContinue
fffffa60`0cf98c10 fffff800`0206d5df : 00000000`01010101 00000000`00000000 00000000`00000000 fffffa80`04aded40 : nt!KiDpcInterruptBypass+0x13
fffffa60`0cf98c20 00000000`6e3d870a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x20f
00000000`1261e1a4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6e3d870a
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Core_GetIoRequestFromObject+3e
fffffa60`02d223ca 48396820 cmp qword ptr [rax+20h],rbp
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: USBPORT!USBPORT_Core_GetIoRequestFromObject+3e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 479199d8
FAILURE_BUCKET_ID: X64_0x3D_USBPORT!USBPORT_Core_GetIoRequestFromObject+3e
BUCKET_ID: X64_0x3D_USBPORT!USBPORT_Core_GetIoRequestFromObject+3e
Followup: MachineOwner
---------
5
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061011-05.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02013000 PsLoadedModuleList = 0xfffff800`021d8db0
Debug session time: Fri Jun 10 22:22:38.925 2011 (UTC + 2:00)
System Uptime: 0 days 1:01:02.941
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffffa60023f7880, fffffa600b9232d0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1ed880 )
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: fffffa60023f7880, Address of the instruction which caused the bugcheck
Arg3: fffffa600b9232d0, 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:
nvlddmkm+1ed880
fffffa60`023f7880 ?? ???
CONTEXT: fffffa600b9232d0 -- (.cxr 0xfffffa600b9232d0)
rax=0000000000000001 rbx=76b251547157537a rcx=fffffa80070ff950
rdx=000000001e000001 rsi=0000000000000002 rdi=fffffa8006201110
rip=fffffa60023f7880 rsp=fffffa600b923b30 rbp=0000000000000000
r8=fffffa600b923c20 r9=0000000010000000 r10=0000000000000000
r11=fffffa600b923bf8 r12=fffffa80073bf010 r13=0000000000000000
r14=0000000000000000 r15=0000000000000002
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nvlddmkm+0x1ed880:
fffffa60`023f7880 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 000000ff60020b48 to fffffa60023f7880
STACK_TEXT:
fffffa60`0b923b30 000000ff`60020b48 : fffffa60`022ace6a fffffa80`083f2678 fffffa80`073bf010 fffffa60`0b923c20 : nvlddmkm+0x1ed880
fffffa60`0b923b38 fffffa60`022ace6a : fffffa80`083f2678 fffffa80`073bf010 fffffa60`0b923c20 fffffa60`0264993c : 0xff`60020b48
fffffa60`0b923b40 fffffa80`083f2678 : fffffa80`073bf010 fffffa60`0b923c20 fffffa60`0264993c 000000ff`60020b00 : nvlddmkm+0xa2e6a
fffffa60`0b923b48 fffffa80`073bf010 : fffffa60`0b923c20 fffffa60`0264993c 000000ff`60020b00 fffffa60`022ace6a : 0xfffffa80`083f2678
fffffa60`0b923b50 fffffa60`0b923c20 : fffffa60`0264993c 000000ff`60020b00 fffffa60`022ace6a 00000000`00000001 : 0xfffffa80`073bf010
fffffa60`0b923b58 fffffa60`0264993c : 000000ff`60020b00 fffffa60`022ace6a 00000000`00000001 fffffa60`022ac88e : 0xfffffa60`0b923c20
fffffa60`0b923b60 000000ff`60020b00 : fffffa60`022ace6a 00000000`00000001 fffffa60`022ac88e fffffa60`0b923d50 : nvlddmkm+0x43f93c
fffffa60`0b923b68 fffffa60`022ace6a : 00000000`00000001 fffffa60`022ac88e fffffa60`0b923d50 fffffa80`061ed000 : 0xff`60020b00
fffffa60`0b923b70 00000000`00000001 : fffffa60`022ac88e fffffa60`0b923d50 fffffa80`061ed000 fffffa80`073bf010 : nvlddmkm+0xa2e6a
fffffa60`0b923b78 fffffa60`022ac88e : fffffa60`0b923d50 fffffa80`061ed000 fffffa80`073bf010 fffffa60`0234acdf : 0x1
fffffa60`0b923b80 fffffa60`0b923d50 : fffffa80`061ed000 fffffa80`073bf010 fffffa60`0234acdf 00000001`083f2678 : nvlddmkm+0xa288e
fffffa60`0b923b88 fffffa80`061ed000 : fffffa80`073bf010 fffffa60`0234acdf 00000001`083f2678 fffffa60`02386d7d : 0xfffffa60`0b923d50
fffffa60`0b923b90 fffffa80`073bf010 : fffffa60`0234acdf 00000001`083f2678 fffffa60`02386d7d 00000000`00000000 : 0xfffffa80`061ed000
fffffa60`0b923b98 fffffa60`0234acdf : 00000001`083f2678 fffffa60`02386d7d 00000000`00000000 00000000`00000400 : 0xfffffa80`073bf010
fffffa60`0b923ba0 00000001`083f2678 : fffffa60`02386d7d 00000000`00000000 00000000`00000400 fffffa80`073bf010 : nvlddmkm+0x140cdf
fffffa60`0b923ba8 fffffa60`02386d7d : 00000000`00000000 00000000`00000400 fffffa80`073bf010 00000000`00000000 : 0x1`083f2678
fffffa60`0b923bb0 00000000`00000000 : 00000000`00000400 fffffa80`073bf010 00000000`00000000 00000000`00000000 : nvlddmkm+0x17cd7d
FOLLOWUP_IP:
nvlddmkm+1ed880
fffffa60`023f7880 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+1ed880
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a2fc3d4
STACK_COMMAND: .cxr 0xfffffa600b9232d0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+1ed880
BUCKET_ID: X64_0x3B_nvlddmkm+1ed880
Followup: MachineOwner
---------
6
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061011-06.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02050000 PsLoadedModuleList = 0xfffff800`02215db0
Debug session time: Fri Jun 10 22:40:03.498 2011 (UTC + 2:00)
System Uptime: 0 days 0:04:43.187
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904aa, fffffa600c2e2e48, fffffa600c2e2820, fffff800022a080b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPrefetchFile+7a2 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904aa
Arg2: fffffa600c2e2e48
Arg3: fffffa600c2e2820
Arg4: fffff800022a080b
Debugging Details:
------------------
EXCEPTION_RECORD: fffffa600c2e2e48 -- (.exr 0xfffffa600c2e2e48)
ExceptionAddress: fffff800022a080b (nt!MiPfPrepareReadList+0x000000000000005b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffffa600c2e2820 -- (.cxr 0xfffffa600c2e2820)
rax=fffffa80072a09a0 rbx=0000000000000000 rcx=724370796c4a6b4a
rdx=0000000000000690 rsi=fffff8800e9f8c00 rdi=0000000000000000
rip=fffff800022a080b rsp=fffffa600c2e3080 rbp=fffffa80047e45d0
r8=0000000000000801 r9=000000006c526d4d r10=0000000000000001
r11=0000000000000002 r12=ffffffe00439e838 r13=fffffa8007f44aa0
r14=0000000000000000 r15=0000000000000001
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!MiPfPrepareReadList+0x5b:
fffff800`022a080b 4c8b39 mov r15,qword ptr [rcx] ds:002b:72437079`6c4a6b4a=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002279080
ffffffffffffffff
FOLLOWUP_IP:
Ntfs!NtfsPrefetchFile+7a2
fffffa60`011344b2 443be3 cmp r12d,ebx
FAULTING_IP:
nt!MiPfPrepareReadList+5b
fffff800`022a080b 4c8b39 mov r15,qword ptr [rcx]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff800022a04a9 to fffff800022a080b
STACK_TEXT:
fffffa60`0c2e3080 fffff800`022a04a9 : fffffa80`6c526d4d fffffa80`07f44aa0 00000000`00000001 fffffa80`0485d010 : nt!MiPfPrepareReadList+0x5b
fffffa60`0c2e3140 fffffa60`011344b2 : 00000000`00000000 00000000`00000000 fffffa80`0485d010 fffffa80`04870c90 : nt!MmPrefetchPages+0x6d
fffffa60`0c2e3190 fffffa60`0110a9d4 : fffffa80`04870c90 fffffa60`0c2e3400 00000000`00000025 fffff880`0e9f8c00 : Ntfs!NtfsPrefetchFile+0x7a2
fffffa60`0c2e32c0 fffffa60`010ef485 : fffffa80`04870c90 00000000`00000000 fffffa80`0485d010 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x1863a
fffffa60`0c2e3300 fffffa60`00a0fe17 : 00000000`00000000 fffffa80`0485d010 00000000`00000001 fffffa80`04870c90 : Ntfs!NtfsFsdFileSystemControl+0x145
fffffa60`0c2e33b0 fffffa60`00a2cc32 : fffffa80`045934c0 fffffa80`06b12750 fffffa80`05e62d00 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`0c2e3420 fffffa60`00a0fe17 : fffffa80`0485d3b0 fffff800`020a53c0 00000000`00000010 00000000`00000082 : fltmgr!FltpFsControl+0x102
fffffa60`0c2e3480 fffffa60`00a2cc32 : fffffa80`06b05780 00000000`00000000 fffffa80`06b12700 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`0c2e34f0 fffff800`02328a6a : fffffa80`0413d1b0 fffffa80`06b12750 fffffa80`0413d1b0 fffffa80`06063800 : fltmgr!FltpFsControl+0x102
fffffa60`0c2e3550 fffff800`023311e2 : 00000000`00100001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5da
fffffa60`0c2e36a0 fffff800`0244af75 : fffff880`0e5bf250 ffffffff`ffe91ca0 fffffa60`0c2e3828 00000000`00000000 : nt!NtFsControlFile+0x56
fffffa60`0c2e3710 fffff800`0244bcb5 : 00000000`00000004 00000000`00000660 fffff880`0ec80758 00000000`00000022 : nt!PfpPrefetchDirectoryStream+0x1e5
fffffa60`0c2e37c0 fffff800`0247eb8e : fffff880`00000004 00000000`00000000 00000000`00004021 00000000`00000000 : nt!PfpVolumePrefetchMetadata+0x3d5
fffffa60`0c2e38c0 fffff800`0247ee72 : 00000000`00000000 fffffa60`0c2e3ca0 fffffa60`0c2e3a08 fffff880`0ec80001 : nt!PfpPrefetchRequestPerform+0x2ce
fffffa60`0c2e3960 fffff800`0247f0d6 : fffffa60`0c2e3a08 00000000`00000001 fffffa80`061317d0 00000000`00000000 : nt!PfpPrefetchRequest+0x171
fffffa60`0c2e39d0 fffff800`02491808 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`0aa7f201 : nt!PfSetSuperfetchInformation+0x1a5
fffffa60`0c2e3ab0 fffff800`020a4eb3 : fffffa80`0847fbb0 00000000`00000000 00000000`00000000 fffffa80`088cfeb0 : nt!NtSetSystemInformation+0x8fb
fffffa60`0c2e3c20 00000000`77b7667a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0aa7f9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b7667a
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Ntfs!NtfsPrefetchFile+7a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1
STACK_COMMAND: .cxr 0xfffffa600c2e2820 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPrefetchFile+7a2
BUCKET_ID: X64_0x24_Ntfs!NtfsPrefetchFile+7a2
Followup: MachineOwner
---------
-- 11 cze 2011, 19:27 --
przedwczoraj
1
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini060911-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02062000 PsLoadedModuleList = 0xfffff800`02227db0
Debug session time: Thu Jun 9 21:17:58.649 2011 (UTC + 2:00)
System Uptime: 0 days 3:42:09.571
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904aa, fffffa600c592178, fffffa600c591b50, fffff800020be5da}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireExclusiveFcb+64 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904aa
Arg2: fffffa600c592178
Arg3: fffffa600c591b50
Arg4: fffff800020be5da
Debugging Details:
------------------
EXCEPTION_RECORD: fffffa600c592178 -- (.exr 0xfffffa600c592178)
ExceptionAddress: fffff800020be5da (nt!KeWaitForSingleObject+0x000000000000014a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: ffffffffffffffff
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffffa600c591b50 -- (.cxr 0xfffffa600c591b50)
rax=fffff8000228d440 rbx=0000001f0957739e rcx=fffffa60005ec7f0
rdx=0000000000000000 rsi=fffffa800439b158 rdi=fffffa800439b060
rip=fffff800020be5da rsp=fffffa600c5923b0 rbp=3bc75f449de3f3fd
r8=fffffa800439b1e8 r9=0000000000000000 r10=0000000000000000
r11=000000000000000c r12=0000000000000000 r13=fffffa600c5924b0
r14=fffffa60005ec180 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!KeWaitForSingleObject+0x14a:
fffff800`020be5da 807d0002 cmp byte ptr [rbp],2 ss:0018:3bc75f44`9de3f3fd=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: Upgrader.exe
CURRENT_IRQL: c
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: ffffffffffffffff
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000228b080
0000000000000000
FOLLOWUP_IP:
Ntfs!NtfsAcquireExclusiveFcb+64
fffffa60`01018834 84c0 test al,al
FAULTING_IP:
nt!KeWaitForSingleObject+14a
fffff800`020be5da 807d0002 cmp byte ptr [rbp],2
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff800020ced2a to fffff800020be5da
STACK_TEXT:
fffffa60`0c5923b0 fffff800`020ced2a : 00000000`000001d6 00000000`0000001b 00000000`00040000 fffff980`09c3a400 : nt!KeWaitForSingleObject+0x14a
fffffa60`0c592440 fffffa60`01018834 : ffffffff`ffb3b4c0 fffffa80`05edb180 fffffa80`04ab58a0 fffff880`013be010 : nt!ExAcquireResourceExclusiveLite+0xca
fffffa60`0c5924b0 fffffa60`01098da0 : fffff880`013c0010 fffffa60`0c592850 fffffa80`04ab58a0 fffff880`013c0010 : Ntfs!NtfsAcquireExclusiveFcb+0x64
fffffa60`0c592500 fffffa60`01008260 : fffffa80`04ab58a0 fffffa80`05edb180 fffffa80`073e8c01 00000000`00000000 : Ntfs!NtfsFlushVolume+0x170
fffffa60`0c592620 fffffa60`0101479a : fffffa80`04ab58a0 fffffa60`0c592601 fffffa80`05e9fa30 fffffa80`060e6b00 : Ntfs!NtfsVolumeDasdIo+0x150
fffffa60`0c5926b0 fffffa60`01014b68 : fffffa80`04ab58a0 fffffa80`08670940 fffffa60`0c592801 fffffa80`00000000 : Ntfs!NtfsCommonRead+0x19ab
fffffa60`0c592820 fffffa60`00a05e17 : fffffa80`08670ce0 fffffa80`08670940 fffffa80`05e97620 fffffa80`073e8b90 : Ntfs!NtfsFsdRead+0x1b8
fffffa60`0c5928d0 fffffa60`00a050dd : fffffa80`03abcac0 fffffa80`06b93750 fffffa80`05e97600 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`0c592940 fffffa60`00a05e17 : fffffa80`08670ce0 00000000`00000000 fffffa80`06b7a7c0 00000000`00000000 : fltmgr!FltpDispatch+0xcd
fffffa60`0c5929a0 fffffa60`00a050dd : fffffa80`06b7a7c0 fffffa80`07c8d4e0 fffffa80`06b93700 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`0c592a10 fffff800`02343afc : 00000000`00000001 fffffa80`036bc580 fffff880`10889a20 00000000`75183380 : fltmgr!FltpDispatch+0xcd
fffffa60`0c592a70 fffff800`023204cf : fffffa80`07c8d4e0 fffffa80`07c8d4e0 fffffa80`07c8d4e0 fffffa60`0c592ca0 : nt!IopSynchronousServiceTail+0x13c
fffffa60`0c592ad0 fffff800`020b6eb3 : fffff880`0c3244d0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x5fd
fffffa60`0c592bb0 00000000`75183917 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007ee18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75183917
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Ntfs!NtfsAcquireExclusiveFcb+64
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1
STACK_COMMAND: .cxr 0xfffffa600c591b50 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+64
BUCKET_ID: X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+64
Followup: MachineOwner
---------
2
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini060911-02.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02001000 PsLoadedModuleList = 0xfffff800`021c6db0
Debug session time: Thu Jun 9 22:59:47.420 2011 (UTC + 2:00)
System Uptime: 0 days 0:04:23.233
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800020e6702, fffffa600b328f60, 0}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+6f2 )
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: fffff800020e6702, Address of the instruction which caused the bugcheck
Arg3: fffffa600b328f60, 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!MiIdentifyPfn+6f2
fffff800`020e6702 498b5b40 mov rbx,qword ptr [r11+40h]
CONTEXT: fffffa600b328f60 -- (.cxr 0xfffffa600b328f60)
rax=0200000000000000 rbx=0000058000000000 rcx=0000000000000006
rdx=00000000003fac38 rsi=fffffa8004aee430 rdi=02000000000b077e
rip=fffff800020e6702 rsp=fffffa600b3297c0 rbp=fffffa600b329800
r8=0200000000000000 r9=0000000000000446 r10=fffffa800713daf8
r11=03949c50730a6ae6 r12=0000000000000000 r13=fffffffffffff000
r14=000fffffffffffff r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!MiIdentifyPfn+0x6f2:
fffff800`020e6702 498b5b40 mov rbx,qword ptr [r11+40h] ds:002b:03949c50`730a6b26=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002100ffe to fffff800020e6702
STACK_TEXT:
fffffa60`0b3297c0 fffff800`02100ffe : 00000000`0007f587 fffffa80`04aee430 fffffa80`0758dbb0 00000000`00000000 : nt!MiIdentifyPfn+0x6f2
fffffa60`0b329860 fffff800`023f0175 : fffffa80`04aee000 fffffa60`0b329ca0 fffffa60`0b329928 00000000`00000000 : nt!MmQueryPfnList+0x13e
fffffa60`0b3298a0 fffff800`023376ac : fffffa80`000000a8 00000000`00000000 fffffa80`04aee000 00000000`05c95f01 : nt!PfpPfnPrioRequest+0x115
fffffa60`0b3298f0 fffff800`022cbcba : 00000000`00000000 00000000`05c95ff0 00000000`033deb20 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x44f2a
fffffa60`0b329960 fffff800`02055eb3 : fffffa80`0758dbb0 00000000`05c95ff0 00000000`05383b40 00000000`00000000 : nt!NtQuerySystemInformation+0xd0a
fffffa60`0b329c20 00000000`7761536a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`033dea78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7761536a
FOLLOWUP_IP:
nt!MiIdentifyPfn+6f2
fffff800`020e6702 498b5b40 mov rbx,qword ptr [r11+40h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiIdentifyPfn+6f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb71b96
STACK_COMMAND: .cxr 0xfffffa600b328f60 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiIdentifyPfn+6f2
BUCKET_ID: X64_0x3B_nt!MiIdentifyPfn+6f2
Followup: MachineOwner
---------
3
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini060911-03.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02050000 PsLoadedModuleList = 0xfffff800`02215db0
Debug session time: Thu Jun 9 23:25:55.239 2011 (UTC + 2:00)
System Uptime: 0 days 0:03:20.082
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8000230b1aa, fffffa600abc1e70, 0}
Probably caused by : CLFS.SYS ( CLFS!CClfsManagedLogCollection::FindOrCreateManagedLog+5a )
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: fffff8000230b1aa, Address of the instruction which caused the bugcheck
Arg3: fffffa600abc1e70, 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!CompareUnicodeStrings+16
fffff800`0230b1aa 440fb711 movzx r10d,word ptr [rcx]
CONTEXT: fffffa600abc1e70 -- (.cxr 0xfffffa600abc1e70)
rax=0000000000000003 rbx=fffffa8007501a78 rcx=811af926a556c58b
rdx=fffffa600abc2760 rsi=fffffa8007501a78 rdi=fffffa8007501a90
rip=fffff8000230b1aa rsp=fffffa600abc26d8 rbp=fffffa80079e2018
r8=0000000000000000 r9=000000000000003f r10=0000000000000043
r11=0000000000000009 r12=0000000000000001 r13=fffffa600abc2760
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=00210246
nt!CompareUnicodeStrings+0x16:
fffff800`0230b1aa 440fb711 movzx r10d,word ptr [rcx] ds:002b:811af926`a556c58b=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000230b3a7 to fffff8000230b1aa
STACK_TEXT:
fffffa60`0abc26d8 fffff800`0230b3a7 : fffffa80`040220b0 fffffa80`07501a78 fffffa80`079e2018 fffffa80`07501a78 : nt!CompareUnicodeStrings+0x16
fffffa60`0abc2700 fffffa60`00668742 : fffffa60`0abc2828 fffffa60`0abc2ca0 fffffa80`045b04a0 fffffa60`0abc2828 : nt!RtlFindUnicodePrefix+0x63
fffffa60`0abc2740 fffffa60`006a7744 : fffffa60`0abc2828 fffffa60`0abc2ca0 fffffa80`040d2d08 fffffa60`0abc2ca0 : CLFS!CClfsManagedLogCollection::FindOrCreateManagedLog+0x5a
fffffa60`0abc2780 fffff800`022ae9e1 : 00000000`00000000 00000000`00000000 fffffa80`040d2c60 fffffa60`0abc2b90 : CLFS!ClfsMgmtpRegisterManagedClient+0x54
fffffa60`0abc27e0 fffff800`022ad9e1 : 00000000`00000000 00000000`00000000 fffffa80`040d2c60 00000000`00000000 : nt!TmpRegisterForLogManagement+0xa1
fffffa60`0abc28a0 fffff800`022aa27f : fffffa60`0abc2ca0 fffffa80`040d2c60 00000000`00000000 fffff880`0b6bd5b0 : nt!TmpCreateLogFile+0x155
fffffa60`0abc2a30 fffff800`022aa0e1 : fffffa80`040d2c60 00000000`00000000 fffffa60`0abc2bc8 fffffa60`0abc2b90 : nt!TmpCreateOrOpenLogTransactionManager+0x2e
fffffa60`0abc2a70 fffff800`022aa7a1 : 00000000`04ddf5d0 00000000`00000000 fffffa60`0abc2ca0 fffffa60`0abc2b90 : nt!TmInitializeTransactionManager+0x221
fffffa60`0abc2b10 fffff800`020a4eb3 : fffffa80`04133bb0 00000000`04ddf5a8 00000000`00000000 ffffffff`ffffffff : nt!NtCreateTransactionManager+0x1dc
fffffa60`0abc2bb0 00000000`772a5aca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04ddf588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772a5aca
FOLLOWUP_IP:
CLFS!CClfsManagedLogCollection::FindOrCreateManagedLog+5a
fffffa60`00668742 b9250200c0 mov ecx,0C0000225h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: CLFS!CClfsManagedLogCollection::FindOrCreateManagedLog+5a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: CLFS
IMAGE_NAME: CLFS.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 47919076
STACK_COMMAND: .cxr 0xfffffa600abc1e70 ; kb
FAILURE_BUCKET_ID: X64_0x3B_CLFS!CClfsManagedLogCollection::FindOrCreateManagedLog+5a
BUCKET_ID: X64_0x3B_CLFS!CClfsManagedLogCollection::FindOrCreateManagedLog+5a
Followup: MachineOwner
---------
błędów tyle, że każdy znajdzie coś dla siebie
-- 11 cze 2011, 19:48 --
WhoCrashed daje
Kod: Zaznacz cały
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 2011-06-11 16:16:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061111-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x10FBE0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000236DBE0, 0xFFFFFA60019166E8, 0xFFFFFA60019160C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 2011-06-11 16:16:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8000236DBE0, 0xFFFFFA60019166E8, 0xFFFFFA60019160C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 2011-06-11 11:57:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x50 (0xFFFFFA800B000000, 0x0, 0xFFFFF8000226F570, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 2011-06-10 20:40:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-06.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213B3)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFA600C2E2E48, 0xFFFFFA600C2E2820, 0xFFFFF800022A080B)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: System operacyjny Microsoft? Windows?
company: Microsoft Corporation
description: Sterownik systemu plików NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 2011-06-10 20:22:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-05.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1ED880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFFA60023F7880, 0xFFFFFA600B9232D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 186.18
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 186.18
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 186.18 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
On Fri 2011-06-10 19:20:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0x3D (0x0, 0x0, 0x0, 0xFFFFFA6002D223CA)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 2011-06-10 18:47:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-03.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213B3)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFA60017F5388, 0xFFFFFA60017F4D60, 0xFFFFF800020655DA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: System operacyjny Microsoft? Windows?
company: Microsoft Corporation
description: Sterownik systemu plików NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 2011-06-10 17:06:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002095AF6, 0xFFFFFA600C0BD4C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2011-06-09 22:28:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800020BD4BC, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2011-06-09 21:25:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060911-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000230B1AA, 0xFFFFFA600ABC1E70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2011-06-09 20:59:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060911-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800020E6702, 0xFFFFFA600B328F60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2011-06-09 19:17:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060911-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213B3)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFA600C592178, 0xFFFFFA600C591B50, 0xFFFFF800020BE5DA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: System operacyjny Microsoft? Windows?
company: Microsoft Corporation
description: Sterownik systemu plików NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 2011-05-31 15:47:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini053111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002081ECA, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 2011-05-30 18:21:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini053011-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213B3)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFA600DBB6328, 0xFFFFFA600DBB5D00, 0xFFFFFA6000A328F0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: System operacyjny Microsoft? Windows?
company: Microsoft Corporation
description: Sterownik systemu plików NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 2011-05-26 22:45:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini052711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55410)
Bugcheck code: 0xC2 (0x99, 0xFFFFFA80070BD950, 0x0, 0x0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
43 crash dumps have been found and analyzed. Only 15 are included in this report. 4 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nettdi64.sys (Panda TDI Filter, Panda Security, S.L.)
n64i1639.sys (netimflt, Panda Security, S.L.)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 186.18 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
