|
|
|
|
Strumenti |
05-04-2009, 17:50 | #21 |
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26480
|
Bene, quel percorso di rete per i simboli funziona.
Sembra che il file atikmdag.sys dei Catalyst di ATI sia una delle cause del bsod. Esegui anche il comando !analyze -v, in modo da avere qualche dettaglio in più
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
05-04-2009, 18:43 | #22 |
Senior Member
Iscritto dal: Jun 2002
Città: Brasile
Messaggi: 1647
|
Hai qualche consiglio su come evitare il problema ?
Ho fatto anche un -v. Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini040509-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\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 Personal Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01e15000 PsLoadedModuleList = 0xfffff800`01fdadb0 Debug session time: Sun Apr 5 05:40:18.982 2009 (GMT+2) System Uptime: 0 days 16:15:34.546 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {b, fffff8800a96f1a0, 50c010c, fffff8800a96f1d0} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+25ae3 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 000000000000000b, type of pool violation the caller is guilty of. Arg2: fffff8800a96f1a0 Arg3: 00000000050c010c Arg4: fffff8800a96f1d0 Debugging Details: ------------------ BUGCHECK_STR: 0xc2_b CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: msnmsgr.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001f4a052 to fffff80001e6a350 STACK_TEXT: fffffa60`08b77b78 fffff800`01f4a052 : 00000000`000000c2 00000000`0000000b fffff880`0a96f1a0 00000000`050c010c : nt!KeBugCheckEx fffffa60`08b77b80 fffffa60`0262aae3 : 00000000`00000003 fffff880`0a96f1d0 fffffa80`06899000 00000000`30305852 : nt!ExFreePool+0x520 fffffa60`08b77c30 00000000`00000003 : fffff880`0a96f1d0 fffffa80`06899000 00000000`30305852 00000000`00000002 : atikmdag+0x25ae3 fffffa60`08b77c38 fffff880`0a96f1d0 : fffffa80`06899000 00000000`30305852 00000000`00000002 fffffa60`0260d626 : 0x3 fffffa60`08b77c40 fffffa80`06899000 : 00000000`30305852 00000000`00000002 fffffa60`0260d626 fffff880`0a96f1d0 : 0xfffff880`0a96f1d0 fffffa60`08b77c48 00000000`30305852 : 00000000`00000002 fffffa60`0260d626 fffff880`0a96f1d0 fffff880`0a96f1d0 : 0xfffffa80`06899000 fffffa60`08b77c50 00000000`00000002 : fffffa60`0260d626 fffff880`0a96f1d0 fffff880`0a96f1d0 fffffa80`06899000 : 0x30305852 fffffa60`08b77c58 fffffa60`0260d626 : fffff880`0a96f1d0 fffff880`0a96f1d0 fffffa80`06899000 fffff880`07f2bc10 : 0x2 fffffa60`08b77c60 fffff880`0a96f1d0 : fffff880`0a96f1d0 fffffa80`06899000 fffff880`07f2bc10 00000002`00000048 : atikmdag+0x8626 fffffa60`08b77c68 fffff880`0a96f1d0 : fffffa80`06899000 fffff880`07f2bc10 00000002`00000048 00000000`00000000 : 0xfffff880`0a96f1d0 fffffa60`08b77c70 fffffa80`06899000 : fffff880`07f2bc10 00000002`00000048 00000000`00000000 00000000`00000000 : 0xfffff880`0a96f1d0 fffffa60`08b77c78 fffff880`07f2bc10 : 00000002`00000048 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`06899000 fffffa60`08b77c80 00000002`00000048 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`07f2bc10 fffffa60`08b77c88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0a96f1d0 : 0x2`00000048 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+25ae3 fffffa60`0262aae3 ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: atikmdag+25ae3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49892551 FAILURE_BUCKET_ID: X64_0xc2_b_atikmdag+25ae3 BUCKET_ID: X64_0xc2_b_atikmdag+25ae3 Followup: MachineOwner ---------
__________________
"il 99% dei problemi di un pc stanno tra la sedia e la tastiera" Il Mio Sistema Il Mio Mulo |
07-04-2009, 13:04 | #23 |
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26480
|
La prima cosa da fare è provare un'altra release dei Catalyst
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
09-04-2009, 18:29 | #24 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Cioè fatemi capire.
1.Devo installare i symbols nella cartella c:\windows\symbols 2.Essere connesso 3.Inserire il codice SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols dove chiede il path dei symbols 4.Aprire il dump. Giusto? |
09-04-2009, 19:13 | #25 | |
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26480
|
Quote:
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
|
09-04-2009, 20:56 | #26 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini040909-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01c07000 PsLoadedModuleList = 0xfffff800`01dccdb0 Debug session time: Thu Apr 9 16:01:14.580 2009 (GMT+2) System Uptime: 0 days 0:03:22.252 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8800d7139d8, 0, fffffa60012253d6, 0} Could not read faulting driver name Probably caused by : Ntfs.sys ( Ntfs!NtfsDefineNtfsMcbRange+46 ) Followup: MachineOwner --------- 6: 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: fffff8800d7139d8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffffa60012253d6, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e30080 fffff8800d7139d8 FAULTING_IP: Ntfs!NtfsDefineNtfsMcbRange+46 fffffa60`012253d6 837b0801 cmp dword ptr [rbx+8],1 MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe CURRENT_IRQL: 1 TRAP_FRAME: fffffa600b395d40 -- (.trap 0xfffffa600b395d40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffffffffff rbx=0000000000000000 rcx=fffff8800d7139d0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffffa60012253d6 rsp=fffffa600b395ed0 rbp=fffffa80049cb010 r8=0000000000000000 r9=0000000000000001 r10=0000000000000400 r11=fffffa600b395f80 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc Ntfs!NtfsDefineNtfsMcbRange+0x46: fffffa60`012253d6 837b0801 cmp dword ptr [rbx+8],1 ds:3650:00000000`00000008=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001c6b361 to fffff80001c5c350 STACK_TEXT: fffffa60`0b395c48 fffff800`01c6b361 : 00000000`00000050 fffff880`0d7139d8 00000000`00000000 fffffa60`0b395d40 : nt!KeBugCheckEx fffffa60`0b395c50 fffff800`01c5aed9 : 00000000`00000000 fffffa80`049cd800 00000000`00000000 fffff880`0d7139d0 : nt!MmAccessFault+0x1371 fffffa60`0b395d40 fffffa60`012253d6 : fffff980`00000000 fffff980`11540598 00000000`00000000 00000000`00000080 : nt!KiPageFault+0x119 fffffa60`0b395ed0 fffffa60`0122260b : fffff880`0d7139d0 fffff880`0d70d6a0 fffff980`11540598 fffffa80`03d13601 : Ntfs!NtfsDefineNtfsMcbRange+0x46 fffffa60`0b395fa0 fffffa60`012230c1 : fffffa80`03d13650 fffff880`0d70d6a0 00000000`00000000 fffffa60`0b396190 : Ntfs!NtfsLookupAllocation+0x3eb fffffa60`0b396110 fffffa60`01223b14 : fffffa80`03d13650 fffffa80`049cb010 fffff880`0d70d6a0 00000000`00000000 : Ntfs!NtfsPrepareSimpleBuffers+0x141 fffffa60`0b3961e0 fffffa60`01221963 : 00000000`00000000 fffffa80`03d13650 fffffa60`0b3962b0 ffffffff`ffffffff : Ntfs!NtfsPrepareBuffers+0xc4 fffffa60`0b396260 fffffa60`012173ec : fffffa80`03d13650 fffffa80`049cb010 fffff880`0d70d6a0 fffff880`0d70d6a0 : Ntfs!NtfsNonCachedIo+0x1c3 fffffa60`0b3963e0 fffffa60`01218b68 : fffffa80`03d13650 fffffa80`049cb010 fffffa60`0b396501 fffffa80`00000001 : Ntfs!NtfsCommonRead+0x60c fffffa60`0b396550 fffffa60`00c9ae17 : fffffa80`049cb3b0 fffffa80`049cb010 fffffa80`06b5aa30 fffffa80`0460f010 : Ntfs!NtfsFsdRead+0x1b8 fffffa60`0b396600 fffffa60`00c9a0dd : fffffa80`04f591c0 00000000`00000403 fffffa80`06b5aa00 fffffa80`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227 fffffa60`0b396670 fffff800`01c53b80 : fffffa80`08002a20 fffffa80`08002a20 fffff6fc`40063eb0 fffffa80`086c4588 : fltmgr!FltpDispatch+0xcd fffffa60`0b3966d0 fffff800`01e74c66 : fffffa80`08002960 fffffa80`08002a21 fffffa80`049cd800 00000000`00000001 : nt!IoPageRead+0x130 fffffa60`0b396710 fffff800`01e5799b : 00000000`00000001 00000000`00000001 fffffa80`085be440 00000000`0000007f : nt!MiPfExecuteReadList+0xde fffffa60`0b396770 fffff800`0200beb1 : 00000000`00000000 fffff880`0d0d1a30 fffff880`0d0ce000 fffffa60`0b396908 : nt!MmPrefetchPages+0x10f fffffa60`0b3967c0 fffff800`020357a9 : fffff880`00000000 00000000`00000000 00000000`00000132 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x211 fffffa60`0b3968c0 fffff800`02035a62 : 00000000`00000000 fffffa60`0b396ca0 fffffa60`0b396a08 fffff880`0d0ce001 : nt!PfpPrefetchRequestPerform+0x2f9 fffffa60`0b396960 fffff800`02035cc6 : fffffa60`0b396a08 00000000`00000001 fffffa80`08afa2b0 00000000`00000000 : nt!PfpPrefetchRequest+0x171 fffffa60`0b3969d0 fffff800`020483f8 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`0442ee01 : nt!PfSetSuperfetchInformation+0x1a5 fffffa60`0b396ab0 fffff800`01c5bdf3 : fffffa80`0770ebb0 00000000`00000000 00000000`00000001 00000000`0001cf76 : nt!NtSetSystemInformation+0x8fb fffffa60`0b396c20 00000000`773a70ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0442f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773a70ea STACK_COMMAND: kb FOLLOWUP_IP: Ntfs!NtfsDefineNtfsMcbRange+46 fffffa60`012253d6 837b0801 cmp dword ptr [rbx+8],1 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: Ntfs!NtfsDefineNtfsMcbRange+46 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1 FAILURE_BUCKET_ID: X64_0x50_Ntfs!NtfsDefineNtfsMcbRange+46 BUCKET_ID: X64_0x50_Ntfs!NtfsDefineNtfsMcbRange+46 Followup: MachineOwner --------- 6: 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: fffff8800d7139d8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffffa60012253d6, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: fffff8800d7139d8 FAULTING_IP: Ntfs!NtfsDefineNtfsMcbRange+46 fffffa60`012253d6 837b0801 cmp dword ptr [rbx+8],1 MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe CURRENT_IRQL: 1 TRAP_FRAME: fffffa600b395d40 -- (.trap 0xfffffa600b395d40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffffffffff rbx=0000000000000000 rcx=fffff8800d7139d0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffffa60012253d6 rsp=fffffa600b395ed0 rbp=fffffa80049cb010 r8=0000000000000000 r9=0000000000000001 r10=0000000000000400 r11=fffffa600b395f80 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc Ntfs!NtfsDefineNtfsMcbRange+0x46: fffffa60`012253d6 837b0801 cmp dword ptr [rbx+8],1 ds:3650:00000000`00000008=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001c6b361 to fffff80001c5c350 STACK_TEXT: fffffa60`0b395c48 fffff800`01c6b361 : 00000000`00000050 fffff880`0d7139d8 00000000`00000000 fffffa60`0b395d40 : nt!KeBugCheckEx fffffa60`0b395c50 fffff800`01c5aed9 : 00000000`00000000 fffffa80`049cd800 00000000`00000000 fffff880`0d7139d0 : nt!MmAccessFault+0x1371 fffffa60`0b395d40 fffffa60`012253d6 : fffff980`00000000 fffff980`11540598 00000000`00000000 00000000`00000080 : nt!KiPageFault+0x119 fffffa60`0b395ed0 fffffa60`0122260b : fffff880`0d7139d0 fffff880`0d70d6a0 fffff980`11540598 fffffa80`03d13601 : Ntfs!NtfsDefineNtfsMcbRange+0x46 fffffa60`0b395fa0 fffffa60`012230c1 : fffffa80`03d13650 fffff880`0d70d6a0 00000000`00000000 fffffa60`0b396190 : Ntfs!NtfsLookupAllocation+0x3eb fffffa60`0b396110 fffffa60`01223b14 : fffffa80`03d13650 fffffa80`049cb010 fffff880`0d70d6a0 00000000`00000000 : Ntfs!NtfsPrepareSimpleBuffers+0x141 fffffa60`0b3961e0 fffffa60`01221963 : 00000000`00000000 fffffa80`03d13650 fffffa60`0b3962b0 ffffffff`ffffffff : Ntfs!NtfsPrepareBuffers+0xc4 fffffa60`0b396260 fffffa60`012173ec : fffffa80`03d13650 fffffa80`049cb010 fffff880`0d70d6a0 fffff880`0d70d6a0 : Ntfs!NtfsNonCachedIo+0x1c3 fffffa60`0b3963e0 fffffa60`01218b68 : fffffa80`03d13650 fffffa80`049cb010 fffffa60`0b396501 fffffa80`00000001 : Ntfs!NtfsCommonRead+0x60c fffffa60`0b396550 fffffa60`00c9ae17 : fffffa80`049cb3b0 fffffa80`049cb010 fffffa80`06b5aa30 fffffa80`0460f010 : Ntfs!NtfsFsdRead+0x1b8 fffffa60`0b396600 fffffa60`00c9a0dd : fffffa80`04f591c0 00000000`00000403 fffffa80`06b5aa00 fffffa80`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227 fffffa60`0b396670 fffff800`01c53b80 : fffffa80`08002a20 fffffa80`08002a20 fffff6fc`40063eb0 fffffa80`086c4588 : fltmgr!FltpDispatch+0xcd fffffa60`0b3966d0 fffff800`01e74c66 : fffffa80`08002960 fffffa80`08002a21 fffffa80`049cd800 00000000`00000001 : nt!IoPageRead+0x130 fffffa60`0b396710 fffff800`01e5799b : 00000000`00000001 00000000`00000001 fffffa80`085be440 00000000`0000007f : nt!MiPfExecuteReadList+0xde fffffa60`0b396770 fffff800`0200beb1 : 00000000`00000000 fffff880`0d0d1a30 fffff880`0d0ce000 fffffa60`0b396908 : nt!MmPrefetchPages+0x10f fffffa60`0b3967c0 fffff800`020357a9 : fffff880`00000000 00000000`00000000 00000000`00000132 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x211 fffffa60`0b3968c0 fffff800`02035a62 : 00000000`00000000 fffffa60`0b396ca0 fffffa60`0b396a08 fffff880`0d0ce001 : nt!PfpPrefetchRequestPerform+0x2f9 fffffa60`0b396960 fffff800`02035cc6 : fffffa60`0b396a08 00000000`00000001 fffffa80`08afa2b0 00000000`00000000 : nt!PfpPrefetchRequest+0x171 fffffa60`0b3969d0 fffff800`020483f8 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`0442ee01 : nt!PfSetSuperfetchInformation+0x1a5 fffffa60`0b396ab0 fffff800`01c5bdf3 : fffffa80`0770ebb0 00000000`00000000 00000000`00000001 00000000`0001cf76 : nt!NtSetSystemInformation+0x8fb fffffa60`0b396c20 00000000`773a70ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0442f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773a70ea STACK_COMMAND: kb FOLLOWUP_IP: Ntfs!NtfsDefineNtfsMcbRange+46 fffffa60`012253d6 837b0801 cmp dword ptr [rbx+8],1 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: Ntfs!NtfsDefineNtfsMcbRange+46 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1 FAILURE_BUCKET_ID: X64_0x50_Ntfs!NtfsDefineNtfsMcbRange+46 BUCKET_ID: X64_0x50_Ntfs!NtfsDefineNtfsMcbRange+46 Followup: MachineOwner Cosa può essere. Ultima modifica di ezio : 10-04-2009 alle 11:55. |
09-04-2009, 22:14 | #27 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini040709-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01c0f000 PsLoadedModuleList = 0xfffff800`01dd4db0 Debug session time: Tue Apr 7 01:05:01.554 2009 (GMT+2) System Uptime: 0 days 3:01:01.309 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80001c86d69, 0, ffffffffffffffff} Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 2 instance(s) of page corruption, target is likely to have memory corruption. 7: 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: fffff80001c86d69, 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 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: nt!MiUnlinkFreeOrZeroedPage+89 fffff800`01c86d69 49890cc0 mov qword ptr [r8+rax*8],rcx EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e38080 ffffffffffffffff CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: SearchFilterHos CURRENT_IRQL: 2 BAD_PAGES_DETECTED: 2 LAST_CONTROL_TRANSFER: from fffff80001c3de47 to fffff80001c64350 STACK_TEXT: fffffa60`0edf5098 fffff800`01c3de47 : 00000000`0000001e ffffffff`c0000005 fffff800`01c86d69 00000000`00000000 : nt!KeBugCheckEx fffffa60`0edf50a0 fffff800`01c641a9 : fffffa60`0edf57d8 fffffa80`010b7890 fffffa60`0edf5880 00000000`00059283 : nt! ?? ::FNODOBFM::`string'+0x29317 fffffa60`0edf56a0 fffff800`01c62d8d : fffffa80`0698b6c0 fffff800`01cb7b8f fffffa80`088d20e0 fffffa60`0edf58e8 : nt!KiExceptionDispatch+0xa9 fffffa60`0edf5880 fffff800`01c86d69 : fffffa80`04ab6e70 fffffa80`00000000 fffffa60`0edf5ca0 fffffa80`00000004 : nt!KiGeneralProtectionFault+0xcd fffffa60`0edf5a10 fffff800`01c86aca : 00000000`00000003 00000000`00000000 00000000`00000003 00000000`00000bdc : nt!MiUnlinkFreeOrZeroedPage+0x89 fffffa60`0edf5a50 fffff800`01c86356 : fffffa80`06544c50 00000000`00000005 00000000`40000003 fffff680`00005c30 : nt!MiRemoveAnyPage+0xda fffffa60`0edf5aa0 fffff800`01c74044 : 00000000`00000001 00000000`00b87000 fffff680`00005c38 fffffa60`00000000 : nt!MiResolveDemandZeroFault+0x176 fffffa60`0edf5b30 fffff800`01c62ed9 : 00000000`00000001 fffffa80`0638f4f0 00000000`00000001 00000000`00b70000 : nt!MmAccessFault+0x2054 fffffa60`0edf5c20 00000000`7799762c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119 00000000`0011ec68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7799762c STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 2 instance(s) of page corruption, target is likely to have memory corruption. 7: kd> lmvm Unknown_Module start end module name Ultima modifica di ezio : 10-04-2009 alle 11:56. |
10-04-2009, 11:51 | #28 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Ne ho analizzato un'altro vecchio
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini040309-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01c17000 PsLoadedModuleList = 0xfffff800`01ddcdb0 Debug session time: Fri Apr 3 11:24:07.182 2009 (GMT+2) System Uptime: 0 days 0:10:19.855 Loading Kernel Symbols ............................................................... ................................................................ ............... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050033, 6f8, fffff80001c6c10f} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050033 Arg3: 00000000000006f8 Arg4: fffff80001c6c10f Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SearchIndexer.e CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001c6c0ee to fffff80001c6c350 STACK_TEXT: fffff800`030f5d28 fffff800`01c6c0ee : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx fffff800`030f5d30 fffff800`01c6a938 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e fffff800`030f5e70 fffff800`01c6c10f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8 fffffa60`0d547f10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xf STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b8 fffff800`01c6a938 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8 Followup: MachineOwner Ultima modifica di ezio : 10-04-2009 alle 11:57. |
11-04-2009, 21:23 | #29 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Niente ancora?
|
15-04-2009, 19:12 | #30 |
Senior Member
Iscritto dal: May 2007
Città: DiSaronno Originale
Messaggi: 2374
|
BSOD al risveglio dall'ibernazione. Non avviene spesso, di media una volta a settimana:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini041509-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\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 x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0x82015000 PsLoadedModuleList = 0x8212cc70 Debug session time: Wed Apr 15 16:50:41.281 2009 (GMT+2) System Uptime: 5 days 5:28:39.900 Loading Kernel Symbols ............................................................... ................................................................ ............................................. Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 110b, 80d0007, 8467df08} Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VBoxNetFlt.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys Unable to load image \SystemRoot\system32\DRIVERS\VMNetSrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VMNetSrv.sys *** ERROR: Module load completed but symbols could not be loaded for VMNetSrv.sys GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.sys *** WARNING: Unable to verify timestamp for msrpc.sys *** ERROR: Module load completed but symbols could not be loaded for msrpc.sys *** WARNING: Unable to verify timestamp for avipbb.sys *** ERROR: Module load completed but symbols could not be loaded for avipbb.sys *** WARNING: Unable to verify timestamp for vmm.sys *** ERROR: Module load completed but symbols could not be loaded for vmm.sys *** WARNING: Unable to verify timestamp for VBoxDrv.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys *** WARNING: Unable to verify timestamp for ATKACPI.sys *** ERROR: Module load completed but symbols could not be loaded for ATKACPI.sys *** ERROR: Module load completed but symbols could not be loaded for spldr.sys *** WARNING: Unable to verify timestamp for avgntflt.sys *** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys *** WARNING: Unable to verify timestamp for Rtlh86.sys *** ERROR: Module load completed but symbols could not be loaded for Rtlh86.sys *** WARNING: Unable to verify timestamp for VBoxUSBMon.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxUSBMon.sys *** WARNING: Unable to verify timestamp for xpvcom.sys *** ERROR: Module load completed but symbols could not be loaded for xpvcom.sys *** WARNING: Unable to verify timestamp for NETw4v32.sys *** ERROR: Module load completed but symbols could not be loaded for NETw4v32.sys *** WARNING: Unable to verify timestamp for rimmptsk.sys *** ERROR: Module load completed but symbols could not be loaded for rimmptsk.sys *** WARNING: Unable to verify timestamp for rimsptsk.sys *** ERROR: Module load completed but symbols could not be loaded for rimsptsk.sys *** WARNING: Unable to verify timestamp for al9b0j30.SYS *** ERROR: Module load completed but symbols could not be loaded for al9b0j30.SYS *** WARNING: Unable to verify timestamp for tap0901.sys *** ERROR: Module load completed but symbols could not be loaded for tap0901.sys *** WARNING: Unable to verify timestamp for avgio.sys *** ERROR: Module load completed but symbols could not be loaded for avgio.sys *** WARNING: Unable to verify timestamp for RTKVHDA.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys *** WARNING: Unable to verify timestamp for drmk.sys *** ERROR: Module load completed but symbols could not be loaded for drmk.sys *** WARNING: Unable to verify timestamp for ssmdrv.sys *** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys *** WARNING: Unable to verify timestamp for smserial.sys *** ERROR: Module load completed but symbols could not be loaded for smserial.sys *** WARNING: Unable to verify timestamp for Fs_Rec.SYS *** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS *** WARNING: Unable to verify timestamp for Null.SYS *** ERROR: Module load completed but symbols could not be loaded for Null.SYS *** WARNING: Unable to verify timestamp for Msfs.SYS *** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS *** WARNING: Unable to verify timestamp for SynMini.sys *** ERROR: Module load completed but symbols could not be loaded for SynMini.sys *** WARNING: Unable to verify timestamp for SYNSAM.SYS *** ERROR: Module load completed but symbols could not be loaded for SYNSAM.SYS *** WARNING: Unable to verify timestamp for SynCamd.sys *** ERROR: Module load completed but symbols could not be loaded for SynCamd.sys *** WARNING: Unable to verify timestamp for SynPin.sys *** ERROR: Module load completed but symbols could not be loaded for SynPin.sys *** WARNING: Unable to verify timestamp for SynPipe.sys *** ERROR: Module load completed but symbols could not be loaded for SynPipe.sys *** WARNING: Unable to verify timestamp for SynScan.sys *** ERROR: Module load completed but symbols could not be loaded for SynScan.sys *** WARNING: Unable to verify timestamp for HIDPARSE.SYS *** ERROR: Module load completed but symbols could not be loaded for HIDPARSE.SYS *** WARNING: Unable to verify timestamp for asyncmac.sys *** ERROR: Module load completed but symbols could not be loaded for asyncmac.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys *** WARNING: Unable to verify timestamp for TSDDD.dll *** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll *** WARNING: Unable to verify timestamp for cdd.dll *** ERROR: Module load completed but symbols could not be loaded for cdd.dll *** WARNING: Unable to verify timestamp for spsys.sys *** ERROR: Module load completed but symbols could not be loaded for spsys.sys *** WARNING: Unable to verify timestamp for nwifi.sys *** ERROR: Module load completed but symbols could not be loaded for nwifi.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for peauth.sys - *** WARNING: Unable to verify timestamp for secdrv.SYS *** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS *** WARNING: Unable to verify timestamp for RaInfo.sys *** ERROR: Module load completed but symbols could not be loaded for RaInfo.sys *** WARNING: Unable to verify timestamp for lmimirr.sys *** ERROR: Module load completed but symbols could not be loaded for lmimirr.sys *** WARNING: Unable to verify timestamp for LMIRfsDriver.sys *** ERROR: Module load completed but symbols could not be loaded for LMIRfsDriver.sys *** WARNING: Unable to verify timestamp for hiber_dumpata.sys *** ERROR: Module load completed but symbols could not be loaded for hiber_dumpata.sys *** WARNING: Unable to verify timestamp for hiber_atapi.sys *** ERROR: Module load completed but symbols could not be loaded for hiber_atapi.sys Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+2b6d ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000007, Attempt to free pool which was already freed Arg2: 0000110b, (reserved) Arg3: 080d0007, Memory contents of the pool block Arg4: 8467df08, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 8467df08 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3 STACK_TEXT: 88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e 88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f 88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16 WARNING: Stack unwind information not available. Following frames may be wrong. 88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d 88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8 88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447 88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d 88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349 88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04 88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad 88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b 88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93 88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100 88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83 88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b 88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0 88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515 88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe 88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd 88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+2b6d 8c790b6d ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VBoxNetFlt+2b6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0 FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000007, Attempt to free pool which was already freed Arg2: 0000110b, (reserved) Arg3: 080d0007, Memory contents of the pool block Arg4: 8467df08, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 8467df08 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3 STACK_TEXT: 88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e 88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f 88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16 WARNING: Stack unwind information not available. Following frames may be wrong. 88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d 88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8 88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447 88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d 88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349 88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04 88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad 88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b 88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93 88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100 88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83 88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b 88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0 88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515 88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe 88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd 88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+2b6d 8c790b6d ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VBoxNetFlt+2b6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0 FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000007, Attempt to free pool which was already freed Arg2: 0000110b, (reserved) Arg3: 080d0007, Memory contents of the pool block Arg4: 8467df08, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 8467df08 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3 STACK_TEXT: 88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e 88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f 88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16 WARNING: Stack unwind information not available. Following frames may be wrong. 88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d 88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8 88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447 88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d 88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349 88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04 88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad 88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b 88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93 88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100 88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83 88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b 88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0 88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515 88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe 88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd 88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+2b6d 8c790b6d ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VBoxNetFlt+2b6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0 FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000007, Attempt to free pool which was already freed Arg2: 0000110b, (reserved) Arg3: 080d0007, Memory contents of the pool block Arg4: 8467df08, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 8467df08 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3 STACK_TEXT: 88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e 88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f 88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16 WARNING: Stack unwind information not available. Following frames may be wrong. 88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d 88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8 88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447 88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d 88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349 88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04 88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad 88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b 88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93 88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100 88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83 88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b 88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0 88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515 88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe 88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd 88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+2b6d 8c790b6d ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VBoxNetFlt+2b6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0 FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000007, Attempt to free pool which was already freed Arg2: 0000110b, (reserved) Arg3: 080d0007, Memory contents of the pool block Arg4: 8467df08, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868 Unable to read MiSystemVaType memory at 8212c420 8467df08 BUGCHECK_STR: 0xc2_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3 STACK_TEXT: 88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e 88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f 88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16 WARNING: Stack unwind information not available. Following frames may be wrong. 88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d 88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8 88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447 88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d 88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349 88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04 88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad 88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b 88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93 88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100 88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83 88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b 88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0 88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170 88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515 88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe 88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd 88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+2b6d 8c790b6d ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: VBoxNetFlt+2b6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0 FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d Followup: MachineOwner --------- Non ho capito come si fa l'analyze -v
__________________
Dell XPS 9570 Powered by Arch Linux || Motorola One Vision Ho concluso con raffaelev, Iceworld, stebru, Dichy, AXIP, Quakeman e Swampo Ultima modifica di jeremy.83 : 15-04-2009 alle 19:23. |
15-04-2009, 21:00 | #31 | |
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26480
|
Rispondo un po' in ritardo per via delle vacanze di Pasqua
Quote:
Crim, i tuoi crash sono molteplici e non si riesce ad individuare una fonte precisa del problema. Io proverei un test approfondito delle ram con memtest in versione autoavviabile da CD (ricordo che hai provato Everest, ma i test eseguiti da Windows possono non essere veritieri). Data la tua configurazione, penserei anche all'alimentatore...
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
|
15-04-2009, 21:24 | #32 | |
Senior Member
Iscritto dal: May 2007
Città: DiSaronno Originale
Messaggi: 2374
|
Quote:
Posso sovrascrivere Virtualbox senza cancellare le macchine virtuale o devo per forza disinstallare tutto? Mi dispiacerebbe perchè sto provando Win 7 solo su macchina virtuale....
__________________
Dell XPS 9570 Powered by Arch Linux || Motorola One Vision Ho concluso con raffaelev, Iceworld, stebru, Dichy, AXIP, Quakeman e Swampo |
|
16-04-2009, 14:28 | #33 |
Senior Member
Iscritto dal: Nov 2008
Città: Verona
Messaggi: 767
|
E' normale che nella cartella "Minudump" non abbia nessun file, anche se mi è apparsa un aaschermata blu la settimana scorsa? Si cancellano automaticamente dopo qualche tempo?
__________________
CASE: Cooler Master CM690; POWER SUPPLY: Corsair TX650W; MOTHERBOARD: Asus P5Q Pro; CPU: Core 2 Quad Q6600 @ 3.0Ghz + AC Freezer 7 PRO; VGA: Sapphire HD 7850 1GB OC; HD: Seagate Barracuda 500GB; RAM: Corsair DDR2 800Mhz 2X2GB MONITOR: Samsung T200 |
16-04-2009, 15:31 | #34 | |
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26480
|
Quote:
Utilizzando Pulitura Disco o programmi come cCleaner potresti aver eliminato i file dump, verifica anche che la scheda "Avvio e Ripristino" sia configurata come nello screen in prima pagina.
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
|
16-04-2009, 16:03 | #35 |
Senior Member
Iscritto dal: Nov 2008
Città: Verona
Messaggi: 767
|
La scheda "avvio e ripristino" è configurata come nello screen. Uso CCleaner abbastanza regolarmente, ma non trovo la voce apposita in modo da togliere il segno di spunta se presente. Sai qual'è la voce corrispondente?
__________________
CASE: Cooler Master CM690; POWER SUPPLY: Corsair TX650W; MOTHERBOARD: Asus P5Q Pro; CPU: Core 2 Quad Q6600 @ 3.0Ghz + AC Freezer 7 PRO; VGA: Sapphire HD 7850 1GB OC; HD: Seagate Barracuda 500GB; RAM: Corsair DDR2 800Mhz 2X2GB MONITOR: Samsung T200 |
16-04-2009, 17:38 | #36 |
Member
Iscritto dal: Feb 2006
Messaggi: 249
|
Ecco il mio debug:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini041509-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0x81e50000 PsLoadedModuleList = 0x81f67c70 Debug session time: Wed Apr 15 16:23:31.126 2009 (GMT+2) System Uptime: 3 days 21:14:09.843 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fada2de9, 2, 1, 8abd3dd1} Probably caused by : hardware ( usbehci!EHCI_IncPendingTransfer+d ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fada2de9, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 8abd3dd1, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81f87868 Unable to read MiSystemVaType memory at 81f67420 fada2de9 CURRENT_IRQL: 2 FAULTING_IP: usbehci!EHCI_IncPendingTransfer+d 8abd3dd1 0083f9015674 add byte ptr [ebx+745601F9h],al CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: 8b72f9e0 -- (.trap 0xffffffff8b72f9e0) ErrCode = 00000002 eax=86842a4c ebx=86842bf0 ecx=00040000 edx=86842bf0 esi=84d0b954 edi=10000001 eip=8abd3dd1 esp=8b72fa54 ebp=8b72fa54 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 usbehci!EHCI_IncPendingTransfer+0xd: 8abd3dd1 0083f9015674 add byte ptr [ebx+745601F9h],al ds:0023:fada2de9=?? Resetting default scope MISALIGNED_IP: usbehci!EHCI_IncPendingTransfer+d 8abd3dd1 0083f9015674 add byte ptr [ebx+745601F9h],al LAST_CONTROL_TRANSFER: from 8abd3dd1 to 81eaad24 STACK_TEXT: 8b72f9e0 8abd3dd1 badb0d00 86842bf0 86113028 nt!KiTrap0E+0x2ac 8b72fa54 8abd537e 86114164 86842a4c 84d0b954 usbehci!EHCI_IncPendingTransfer+0xd 8b72fa80 8abd56b5 86114164 86842a4c 84d0b754 usbehci!EHCI_sMode_Transfer+0xca 8b72faa0 8abd7b25 86114164 86842a4c 84d0b754 usbehci!EHCI_BulkTransfer+0x1b 8b72fac4 807c68e9 86114164 86842a4c 84d0b754 usbehci!EHCI_SubmitTransfer+0x5b 8b72faec 807c6b97 86113002 86842898 84d0b690 USBPORT!MPf_SubmitTransfer+0x67 8b72fb00 807bf3ef 861130e0 86842898 84d0b690 USBPORT!MPx_SubmitTransfer+0x35 8b72fb2c 807c1e22 38496573 00000004 00000010 USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x16f 8b72fb60 807c51db 86113028 00000000 31627573 USBPORT!USBPORT_Core_iSubmitTransferToMiniport+0x194 8b72fbcc 81e221f4 86113028 00000000 861130e8 USBPORT!USBPORT_Core_ProcessScatterGatherList+0x660 8b72fbf8 81e223dc 8555db78 86113028 85091728 hal!HalBuildScatterGatherList+0x1ba 8b72fc28 807c2d1f 862c1a68 86113028 85091728 hal!HalGetScatterGatherList+0x26 8b72fc7c 807c5f3e 86113028 86113ad0 00000200 USBPORT!USBPORT_Core_iMapTransfer+0x315 8b72fcc0 807bf274 86113028 86113ad0 86113002 USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x397 8b72fce8 81f06450 86113adc 34776478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x274 8b72fd50 81f04edd 00000000 0000000e a9bcb990 nt!KiRetireDpcList+0x147 8b72fd54 00000000 0000000e a9bcb990 a8bcf8af nt!KiIdleLoop+0x49 STACK_COMMAND: kb FOLLOWUP_IP: usbehci!EHCI_IncPendingTransfer+d 8abd3dd1 0083f9015674 add byte ptr [ebx+745601F9h],al SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: usbehci!EHCI_IncPendingTransfer+d FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED_usbehci.sys BUCKET_ID: IP_MISALIGNED_usbehci.sys Followup: MachineOwner --------- 2: kd> lmvm hardware start end module name 2: kd> .trap 0xffffffff8b72f9e0 ErrCode = 00000002 eax=86842a4c ebx=86842bf0 ecx=00040000 edx=86842bf0 esi=84d0b954 edi=10000001 eip=8abd3dd1 esp=8b72fa54 ebp=8b72fa54 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 usbehci!EHCI_IncPendingTransfer+0xd: 8abd3dd1 0083f9015674 add byte ptr [ebx+745601F9h],al ds:0023:fada2de9=?? 2: kd> lmvm hardware start end module name mobo: p5e64 ws evolution cpu: q9450 gpu: ati 4850 ram: corsair ddr3 il problema a quanto mi par di capire e' il driver usb, giusto? Come posso provare a risolvere? bsod random....a volte uno ogni 4 giorni altre volte un paio a distanza di poche ore.... grazie |
16-04-2009, 19:25 | #37 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Mi potresti dare un linle per memtest? Io ho scaricato una versione che si masterizza su CD ma vorrei essere sicuro che sia quella giusta.
Ieri ho avuto 3 BSOD in sequenza. Praticamente stavo facendo questo: Stavo testando una chiavetta per vedere la TV con il programma Cyberlink Powercinema. Ogni volta che arrivava alla scansione al 99% dei canali avevo il BSOD. Posso postare i 3 risultati dell'analisi. Può servire per tracciare il problema? Come ali uso un Corsair 850W che dovrebbe essere più che sufficiente. Aspetto una risp così in caso posto anche i risultati dei 3 dump sequenziali. |
16-04-2009, 19:41 | #38 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Ecco i 3 crash dump sequenziali dovuti a ctberlink powercinema:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini041309-03.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01c64000 PsLoadedModuleList = 0xfffff800`01e29db0 Debug session time: Mon Apr 13 21:38:54.904 2009 (GMT+2) System Uptime: 0 days 0:06:44.608 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa600ec2fff8, 2, 1, fffff80001c3599e} Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.sys Probably caused by : sptd.sys ( sptd+40f68 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffa600ec2fff8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80001c3599e, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e8d080 fffffa600ec2fff8 CURRENT_IRQL: 2 FAULTING_IP: hal!memcpy+25e fffff800`01c3599e 48894118 mov qword ptr [rcx+18h],rax CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffffa6001b4c970 -- (.trap 0xfffffa6001b4c970) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0779461a2ad90091 rbx=0000000000000000 rcx=fffffa600ec2ffe0 rdx=fffffffff6ce6000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001c3599e rsp=fffffa6001b4cb08 rbp=0000000000000002 r8=0000000000000540 r9=000000000000002a r10=e8b4204e95a33476 r11=fffffa600ec2fac0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc hal!memcpy+0x25e: fffff800`01c3599e 48894118 mov qword ptr [rcx+18h],rax ds:e010:fffffa60`0ec2fff8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001cb90ee to fffff80001cb9350 STACK_TEXT: fffffa60`01b4c828 fffff800`01cb90ee : 00000000`0000000a fffffa60`0ec2fff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffffa60`01b4c830 fffff800`01cb7fcb : 00000000`00000001 00000000`00000001 fffffa80`06ef5100 fffffa60`0ec2fac0 : nt!KiBugCheckDispatch+0x6e fffffa60`01b4c970 fffff800`01c3599e : fffff800`01c20cb6 fffffa60`0ec2fac0 00000000`00000002 fffffa80`08cf78a0 : nt!KiPageFault+0x20b fffffa60`01b4cb08 fffff800`01c20cb6 : fffffa60`0ec2fac0 00000000`00000002 fffffa80`08cf78a0 fffffa80`0477dbc0 : hal!memcpy+0x25e fffffa60`01b4cb10 fffff800`01c2052a : fffffa80`071803c0 fffffa60`0ec2fa00 fffffa80`074832a0 00000000`0000ff90 : hal!HalpDmaSyncMapBuffers+0x1be fffffa60`01b4cbc0 fffff800`01c2371f : fffffa80`071803c0 fffffa60`0ec2fac0 fffffa80`074832a0 00000000`0000ff90 : hal!HalpDmaFlushScatterTransfer+0xae fffffa60`01b4cc10 fffff800`01c22695 : fffffa80`046f2840 fffffa60`0ec2fac0 00000000`0000ff90 fffffa80`08cf78a0 : hal!IoFlushAdapterBuffers+0xaf fffffa60`01b4cc50 fffffa60`04fa5a47 : fffffa80`06ef51a0 fffffa80`06ef5050 fffff800`01c22610 00000000`00000000 : hal!HalPutScatterGatherList+0x85 fffffa60`01b4ccb0 fffffa60`04fa6420 : fffffa60`31466d64 fffffa80`04a78010 fffff800`32466d64 fffffa80`c0000120 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x577 fffffa60`01b4cd90 fffffa60`04fa3872 : fffffa80`33585043 fffffa80`06ef51a0 fffffa80`06ef6088 fffffa80`06ef51a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514 fffffa60`01b4ce00 fffffa60`04f9018b : fffffa80`31636f49 fffffa80`06ef6088 fffffa60`0dd2ca02 fffffa80`06ef51a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a fffffa60`01b4ce50 fffffa60`00a4ff68 : fffffa80`06c6f000 00000000`34776478 fffffa60`0dd2ca60 fffffa80`06ef5f00 : USBPORT!USBPORT_Xdpc_Worker+0x26f fffffa60`01b4cea0 fffffa80`06c6f000 : 00000000`34776478 fffffa60`0dd2ca60 fffffa80`06ef5f00 00000000`00000f44 : sptd+0x40f68 fffffa60`01b4cea8 00000000`34776478 : fffffa60`0dd2ca60 fffffa80`06ef5f00 00000000`00000f44 fffffa60`01b4cf70 : 0xfffffa80`06c6f000 fffffa60`01b4ceb0 fffffa60`0dd2ca60 : fffffa80`06ef5f00 00000000`00000f44 fffffa60`01b4cf70 00000000`ffffff01 : 0x34776478 fffffa60`01b4ceb8 fffffa80`06ef5f00 : 00000000`00000f44 fffffa60`01b4cf70 00000000`ffffff01 00000000`00000000 : 0xfffffa60`0dd2ca60 fffffa60`01b4cec0 00000000`00000f44 : fffffa60`01b4cf70 00000000`ffffff01 00000000`00000000 00000000`00000000 : 0xfffffa80`06ef5f00 fffffa60`01b4cec8 fffffa60`01b4cf70 : 00000000`ffffff01 00000000`00000000 00000000`00000000 fffffa80`06ef6088 : 0xf44 fffffa60`01b4ced0 00000000`ffffff01 : 00000000`00000000 00000000`00000000 fffffa80`06ef6088 fffffa60`01b1e180 : 0xfffffa60`01b4cf70 fffffa60`01b4ced8 00000000`00000000 : 00000000`00000000 fffffa80`06ef6088 fffffa60`01b1e180 fffffa60`01b21580 : 0xffffff01 STACK_COMMAND: kb FOLLOWUP_IP: sptd+40f68 fffffa60`00a4ff68 ?? ??? SYMBOL_STACK_INDEX: c SYMBOL_NAME: sptd+40f68 FOLLOWUP_NAME: MachineOwner MODULE_NAME: sptd IMAGE_NAME: sptd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3c13 FAILURE_BUCKET_ID: X64_0xA_sptd+40f68 BUCKET_ID: X64_0xA_sptd+40f68 Followup: MachineOwner Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini041309-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01c46000 PsLoadedModuleList = 0xfffff800`01e0bdb0 Debug session time: Mon Apr 13 21:31:01.294 2009 (GMT+2) System Uptime: 0 days 0:14:36.038 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa600fb83ff8, 2, 1, fffff80001c1799e} Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for sptd.sys Probably caused by : sptd.sys ( sptd+40f68 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffa600fb83ff8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80001c1799e, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e6f080 fffffa600fb83ff8 CURRENT_IRQL: 2 FAULTING_IP: hal!memcpy+25e fffff800`01c1799e 48894118 mov qword ptr [rcx+18h],rax CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffffa6001b45740 -- (.trap 0xfffffa6001b45740) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=47d043183822f5b8 rbx=0000000000000000 rcx=fffffa600fb83fe0 rdx=fffffffff5faa000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001c1799e rsp=fffffa6001b458d8 rbp=0000000000000002 r8=0000000000001000 r9=0000000000000080 r10=af2e728fa3751754 r11=fffffa600fb83000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc hal!memcpy+0x25e: fffff800`01c1799e 48894118 mov qword ptr [rcx+18h],rax ds:4010:fffffa60`0fb83ff8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001c9b0ee to fffff80001c9b350 STACK_TEXT: fffffa60`01b455f8 fffff800`01c9b0ee : 00000000`0000000a fffffa60`0fb83ff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffffa60`01b45600 fffff800`01c99fcb : 00000000`00000001 00000000`00000001 fffffa80`06cdc100 fffffa60`0fb83000 : nt!KiBugCheckDispatch+0x6e fffffa60`01b45740 fffff800`01c1799e : fffff800`01c02cb6 fffffa60`0fb82ac0 00000000`00000002 fffffa80`08780e10 : nt!KiPageFault+0x20b fffffa60`01b458d8 fffff800`01c02cb6 : fffffa60`0fb82ac0 00000000`00000002 fffffa80`08780e10 00000000`00000000 : hal!memcpy+0x25e fffffa60`01b458e0 fffff800`01c0252a : fffffa80`04f6c570 00000000`00000500 fffffa80`0723c5a0 00000000`0000fa50 : hal!HalpDmaSyncMapBuffers+0x1be fffffa60`01b45990 fffff800`01c0571f : fffffa80`04f6c570 fffffa60`0fb82ac0 fffffa80`0723c5a0 00000000`0000ff90 : hal!HalpDmaFlushScatterTransfer+0xae fffffa60`01b459e0 fffff800`01c04695 : fffffa80`04528170 fffffa60`0fb82ac0 00000000`0000ff90 fffffa80`08780e10 : hal!IoFlushAdapterBuffers+0xaf fffffa60`01b45a20 fffffa60`051aea47 : fffffa80`06cdc1a0 fffffa80`06cdc050 fffff800`01c04610 00000000`00000000 : hal!HalPutScatterGatherList+0x85 fffffa60`01b45a80 fffffa60`051af420 : fffffa60`31466d64 fffffa80`046ff810 fffff800`32466d64 fffffa80`c0000120 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x577 fffffa60`01b45b60 fffffa60`051ac872 : fffffa80`33585043 fffffa80`06cdc1a0 fffffa80`06cdd088 fffffa80`06cdc1a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514 fffffa60`01b45bd0 fffffa60`0519918b : fffffa80`31636f49 fffffa80`06cdd088 00000000`00000002 fffffa80`06cdc1a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a fffffa60`01b45c20 fffffa60`00a4ef68 : fffffa80`06c87000 00000000`34776478 00000000`00000000 fffffa80`06cdcbf0 : USBPORT!USBPORT_Xdpc_Worker+0x26f fffffa60`01b45c70 fffffa80`06c87000 : 00000000`34776478 00000000`00000000 fffffa80`06cdcbf0 00000000`00000f44 : sptd+0x40f68 fffffa60`01b45c78 00000000`34776478 : 00000000`00000000 fffffa80`06cdcbf0 00000000`00000f44 fffffa60`01b45d40 : 0xfffffa80`06c87000 fffffa60`01b45c80 00000000`00000000 : fffffa80`06cdcbf0 00000000`00000f44 fffffa60`01b45d40 fffffa60`01b21c01 : 0x34776478 STACK_COMMAND: kb FOLLOWUP_IP: sptd+40f68 fffffa60`00a4ef68 ?? ??? SYMBOL_STACK_INDEX: c SYMBOL_NAME: sptd+40f68 FOLLOWUP_NAME: MachineOwner MODULE_NAME: sptd IMAGE_NAME: sptd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3c13 FAILURE_BUCKET_ID: X64_0xA_sptd+40f68 BUCKET_ID: X64_0xA_sptd+40f68 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini041309-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0xfffff800`01c1b000 PsLoadedModuleList = 0xfffff800`01de0db0 Debug session time: Mon Apr 13 21:14:50.602 2009 (GMT+2) System Uptime: 0 days 0:21:24.325 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80001c92d69, 0, ffffffffffffffff} Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 7 instance(s) of page corruption, target is likely to have memory corruption. 7: 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: fffff80001c92d69, 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 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: nt!MiUnlinkFreeOrZeroedPage+89 fffff800`01c92d69 49890cc0 mov qword ptr [r8+rax*8],rcx EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e44080 ffffffffffffffff CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: audiodg.exe CURRENT_IRQL: 2 BAD_PAGES_DETECTED: 7 LAST_CONTROL_TRANSFER: from fffff80001c49e47 to fffff80001c70350 STACK_TEXT: fffffa60`0ea60098 fffff800`01c49e47 : 00000000`0000001e ffffffff`c0000005 fffff800`01c92d69 00000000`00000000 : nt!KeBugCheckEx fffffa60`0ea600a0 fffff800`01c701a9 : fffffa60`0ea607d8 fffffa80`0182f550 fffffa60`0ea60880 00000000`00080fc7 : nt! ?? ::FNODOBFM::`string'+0x29317 fffffa60`0ea606a0 fffff800`01c6ed8d : 00000000`00000300 fffffa80`08ee9260 fffffa60`0ea60890 fffffa80`07e35040 : nt!KiExceptionDispatch+0xa9 fffffa60`0ea60880 fffff800`01c92d69 : fffffa80`0941e640 fffff700`00000000 00000000`00000f19 00000000`00000004 : nt!KiGeneralProtectionFault+0xcd fffffa60`0ea60a10 fffff800`01c92aca : 00000000`00000047 00000000`00000000 00000000`00000047 00000000`000025ce : nt!MiUnlinkFreeOrZeroedPage+0x89 fffffa60`0ea60a50 fffff800`01c92356 : fffffa80`07e35330 00000000`00000005 00000000`40000047 fffff680`00012b48 : nt!MiRemoveAnyPage+0xda fffffa60`0ea60aa0 fffff800`01c80044 : 00000000`00000001 00000000`0256a000 fffff680`00012b50 fffffa60`0ea60ca0 : nt!MiResolveDemandZeroFault+0x176 fffffa60`0ea60b30 fffff800`01c6eed9 : 00000000`00000001 00000000`00000000 fffffa60`00000001 00000000`02563cbc : nt!MmAccessFault+0x2054 fffffa60`0ea60c20 00000000`1000dd72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119 00000000`00cae988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1000dd72 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 7 instance(s) of page corruption, target is likely to have memory corruption. Cmq la mia config è : CPU: i7 965 VGA: GTX295 Ram : 2x2GB Dominator DHX 1600 2 HD (1 raptor 150GB + 500GB Maxtor) MB: Asus P6T Deluxe Ali: Corsair 850W DVD: Optiar/Sony Masterizzatore. Ultima modifica di ezio : 17-04-2009 alle 06:53. |
17-04-2009, 20:52 | #39 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Dopo ieri e oggi senza BSOD stasera mentre navigavo è uscito questo :
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Dump BSOD\Mini041709-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506 Machine Name: Kernel base = 0xfffff800`01e5c000 PsLoadedModuleList = 0xfffff800`02021db0 Debug session time: Fri Apr 17 21:46:24.587 2009 (GMT+2) System Uptime: 0 days 9:58:37.766 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffffa6001063fd8, 0, ffffffffffffffff} Unable to load image \SystemRoot\system32\DRIVERS\yk60x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for yk60x64.sys *** ERROR: Module load completed but symbols could not be loaded for yk60x64.sys Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption. 6: 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: fffffa6001063fd8, 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 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: tcpip!RtlCleanupTimerWheelEntry+0 fffffa60`01063fd8 ff255a560b00 jmp qword ptr [tcpip!_imp_RtlCleanupTimerWheelEntry (fffffa60`01119638)] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002085080 ffffffffffffffff CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 BAD_PAGES_DETECTED: 1 LAST_CONTROL_TRANSFER: from fffff80001e8ae67 to fffff80001eb0650 STACK_TEXT: fffffa60`01b43eb8 fffff800`01e8ae67 : 00000000`0000001e ffffffff`c0000005 fffffa60`01063fd8 00000000`00000000 : nt!KeBugCheckEx fffffa60`01b43ec0 fffff800`01eb04a9 : fffffa60`01b445f8 00000000`00000000 fffffa60`01b446a0 00000000`c0000241 : nt! ?? ::FNODOBFM::`string'+0x29317 fffffa60`01b444c0 fffff800`01eaf08d : fffffa60`01b1e180 fffff800`01eb3175 00000000`00000001 00000000`00000002 : nt!KiExceptionDispatch+0xa9 fffffa60`01b446a0 fffffa60`01063fd8 : fffffa60`010647d5 00000000`00000000 00000000`00000000 00000000`c0000241 : nt!KiGeneralProtectionFault+0xcd fffffa60`01b44838 fffffa60`010647d5 : 00000000`00000000 00000000`00000000 00000000`c0000241 fffffa80`06971010 : tcpip!RtlCleanupTimerWheelEntry fffffa60`01b44840 fffffa60`01065e8a : fffffa80`06aa3560 fffffa80`06971010 fffffa80`0833ac10 00000000`00000000 : tcpip!TcpShutdownTcb+0xb5 fffffa60`01b44900 fffffa60`010663c8 : fffffa80`062a2440 fffffa60`0113ff20 fffffa80`06971010 00000000`00000000 : tcpip!TcpCloseTcbOlmNotifyTerminateComplete+0x2a fffffa60`01b449a0 fffffa60`010663e9 : fffffa80`065c0a10 00000000`00000002 ffff0000`045cdf37 fffffa60`010f5695 : tcpip!TcpCloseTcb+0x78 fffffa60`01b44a00 fffffa60`05e809a8 : 00000000`00000000 00000000`000003b2 fffffa80`067d9010 fffffa60`01b44ba0 : tcpip!TcpTlConnectionCloseEndpoint+0x9 fffffa60`01b44a30 fffffa60`05e8045f : fffffa80`065c0a10 00000000`00000002 00000000`000003b2 00000000`000003b2 : tdx!TdxShutdownEndpointConnection+0xcc fffffa60`01b44a80 fffffa60`0106631f : fffffa80`07f3b500 00000000`d3650910 fffffa60`01b44e40 00000000`00000000 : tdx!TdxDisconnectConnectionTlRequestComplete+0x143 fffffa60`01b44ad0 fffffa60`010650dc : fffffa80`06971010 fffffa80`06971010 fffffa80`06971010 00000000`00000001 : tcpip!TcpDisconnectTcbComplete+0x5f fffffa60`01b44b50 fffffa60`01056523 : 00000000`d365090f fffffa60`01b44e40 00000000`00000010 fffffa80`06971010 : tcpip!TcpFinAcknowledged+0xac fffffa60`01b44ba0 fffffa60`010749ca : fffffa80`05881f00 fffffa80`00000010 00000000`00000000 fffffa60`01b44e20 : tcpip!TcpTcbCarefulDatagram+0x6e3 fffffa60`01b44d80 fffffa60`0107591f : fffffa80`05881f00 fffffa80`05881f00 fffffa80`05887000 00000000`00000000 : tcpip!TcpTcbReceive+0x51a fffffa60`01b44f30 fffffa60`0106efd7 : fffffa80`076030a2 fffffa80`05887000 fffffa80`05887000 fffffa80`058853e6 : tcpip!TcpMatchReceive+0x19f fffffa60`01b45030 fffffa60`0104d23d : fffffa80`058853e6 00000000`00da7a64 fffffa80`05885000 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x377 fffffa60`01b450c0 fffffa60`0105841d : fffffa80`04bf2270 fffffa60`0113ff20 fffffa60`01b45280 fffffa60`025819ec : tcpip!TcpNlClientReceiveDatagrams+0x6d fffffa60`01b450f0 fffffa60`01051009 : 00000000`00000000 00000000`00000003 fffffa80`078d8010 fffffa80`058b34c0 : tcpip!IppDeliverListToProtocol+0x4d fffffa60`01b451b0 fffffa60`0105069e : fffffa60`0113ff20 fffffa80`0760309a 00000000`00000000 fffffa60`01b45270 : tcpip!IppProcessDeliverList+0x59 fffffa60`01b45220 fffffa60`0105c2e6 : fffffa80`070d91a0 fffffa80`05887000 fffffa80`065ad080 fffffa60`01035178 : tcpip!IppReceiveHeaderBatch+0x23e fffffa60`01b45310 fffffa60`0105b875 : fffffa80`078cfba0 00000000`00000000 00000000`00000001 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x8d6 fffffa60`01b454f0 fffffa60`010743b3 : fffffa80`078d8010 fffffa60`01b45628 fffffa80`078d8010 fffffa60`00f70000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x265 fffffa60`01b455d0 fffffa60`00fa933c : fffffa80`078d25b0 fffffa80`073b0680 fffffa60`01b45700 fffffa80`070d91a0 : tcpip!FlReceiveNetBufferListChain+0xd3 fffffa60`01b45620 fffffa60`00f72266 : fffffa60`01b45780 fffffa60`01b45790 00000000`00000001 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0xac fffffa60`01b45670 fffffa60`00e06867 : fffffa80`070d91a0 00000000`00000002 fffffa80`073b0680 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 fffffa60`01b45af0 fffffa60`02581c42 : fffffa80`07525000 00000000`003c0100 00000000`00000000 fffff800`00000400 : ndis!NdisMIndicateReceiveNetBufferLists+0x67 fffffa60`01b45b30 fffffa80`07525000 : 00000000`003c0100 00000000`00000000 fffff800`00000400 00000023`00000001 : yk60x64+0x17c42 fffffa60`01b45b38 00000000`003c0100 : 00000000`00000000 fffff800`00000400 00000023`00000001 00000000`00000400 : 0xfffffa80`07525000 fffffa60`01b45b40 00000000`00000000 : fffff800`00000400 00000023`00000001 00000000`00000400 fffffa80`07525b38 : 0x3c0100 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption. Ultima modifica di ezio : 18-04-2009 alle 16:37. |
18-04-2009, 17:04 | #40 | ||
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26480
|
@Crimsom:
Questo è il link a memtest: http://www.memtest.org/#downiso Scarica e masterizza su cd o dvd l'iso autoavviabile (Download diretto). Prova anche a disinstallare DaemonTools e utilizzare un solo modulo di ram alla volta. Quote:
Quote:
Prova anche a disinstallare tutte le voci sotto "Controller USB (Universal Serial Bus)" in Gestione Dispositivi, verranno reinstallate al riavvio del sistema. Se il problema persiste esegui anche il comando sfc /scannow da Start-->Esegui (potrebbe richiederti il dvd d'installazione di Vista).
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
||
Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 03:38.