|
|||||||
|
|
|
 |
|
|
Strumenti |
07-04-2010, 16:33
|
#461 | |
|
Senior Member
Iscritto dal: Jun 2007
Messaggi: 520
|
Quote:
1° il driver stampante era sbagliato(riconosceva una stampante hp come modello 4100..invece di 4180) 2° non mi riconosceva nessun driver per una penna usb wireless(il driver indicato non era compatibile con seven) 3° il driver del mouse(razer lachesis) sia caricato in automatico che dal sito produttore era causa (certa) del mio bluescreen. Ho scoperto la causa(spero definitiva) utilizzando il comando verifier.exe da : start-esegui-digita verifier.exe lo apri come admin,dovrebbe darti i risultati di eventuali driver sbagliati. Googla il termine e fatti un'idea.
__________________
Case CM 690 ll-Ali CM silent pro M700-MB ASUS Prime Z370-A-CPU Intel Core i5-8600K- NOCTUA NH-D9L-G SKILL F4-2800C17S-8GIS 32gb -Sapphire RX 580 Nitro plus CT500MX500ssd4-ssd samsung 850 evo 500 gb-hd seagate 1 tb- samsung C27FG73 - logitec G502-corsair K70 lux - Os win11 pro 64 bit |
|
|
|
|
07-04-2010, 17:40
|
#462 | |
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Quote:
|
|
|
|
|
|
07-04-2010, 22:30
|
#463 |
|
Member
Iscritto dal: Oct 2009
Messaggi: 147
|
Ciao,
la mia configurazione è: - Asus Rampage II Gene - i7 920 - 6GB DDR3 Gskill Trident 1600 6-7-6-18 - Windows 7 64 ultimate Ho avuto e sto avendo diverse BSOD, nonostante abbia cercato in disperati modi di porvi rimedio. Tra questi ho: - aggiornato tutti i driver di sistema (inclusi chipset, raid, lan) - sostituito gli hdd (2xraptor;1xmaxtor;3xWDR3) - provato con un banco di altra ram perfettamente funzionante su un altro PC. In aggiunta ho: - eseguito test sugli hdd. Questi ultimi nuovi. - eseguito diversi memtest sulle ram, senza ottenere errori. - reinstallato il tutto più volte. - eliminto raid e triple channel, utilizzando configurazioni singolo disco e singolo banco di ram. Nonostante tutto, non riesco a risolvere o individuare il problema. Quello che si verifica è questo: > rallentamento del mouse e "scattosità" dello stesso; > sfarfallio del monitor > freeze o BSOD. All'avvio è possibile avere un errore su uno o più dischi del raid ("correggibile" con il tool "Rapid Storage Technology" o con il vecchio intellimatrix) Posso aggiungere che mi è successo che, in occasione di un rallentamento con "scattosità" del mouse, avessi salvato 2 file per evitare di perderli. I file erano presenti sul desktop prima del freeze. In seguito al freeze, uno dei due file non era presente, l'altro era corrotto. Ora non mi resta altro che postare i dump e sperare nel vostro aiuto. 1 Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021910-20326-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Fri Feb 19 19:26:19.431 2010 (GMT+1)
System Uptime: 0 days 20:37:43.461
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc5001bd40, ffffffffc0000185, bdd2b880, fffff8a0037a87a8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc5001bd40, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000000bdd2b880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a0037a87a8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c0000185
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wmpnetwk.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880098cd720 -- (.trap 0xfffff880098cd720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80059c0e90 rbx=0000000000000000 rcx=fffffa8008a47ad0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d540a2 rsp=fffff880098cd8b0 rbp=0000000000000000
r8=0000000000000ced r9=fffff8a0037a2040 r10=0000000000000000
r11=fffff8a0037a87a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiRelocateImagePfn+0x3a:
fffff800`02d540a2 4d3923 cmp qword ptr [r11],r12 ds:a850:fffff8a0`037a87a8=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002af5438 to fffff80002a81f00
STACK_TEXT:
fffff880`098cd408 fffff800`02af5438 : 00000000`0000007a fffff6fc`5001bd40 ffffffff`c0000185 00000000`bdd2b880 : nt!KeBugCheckEx
fffff880`098cd410 fffff800`02a73d8b : fffffa80`08894010 fffff880`098cd580 fffff800`02c0cb40 00800000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34cde
fffff880`098cd4f0 fffff800`02a9cda4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff8a0`034105c0 : nt!MiIssueHardFault+0x28b
fffff880`098cd5c0 fffff800`02a7ffee : 00000000`00000000 00000000`000095de 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`098cd720 fffff800`02d540a2 : fffffa80`059c0e90 fffffa80`059c0e00 fffffa80`08a60000 fffffa80`08a845c1 : nt!KiPageFault+0x16e
fffff880`098cd8b0 fffff800`02a734ac : fffffa80`001c19a0 fffffa80`059c0f50 00000000`00000000 fffffa80`08410400 : nt!MiRelocateImagePfn+0x3a
fffff880`098cd910 fffff800`02a73d8b : fffffa80`059c0e90 fffff880`098cda80 fffffa80`08a4dec8 fffffa80`08a4db30 : nt!MiWaitForInPageComplete+0x89c
fffff880`098cd9f0 fffff800`02a9d09b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`098cdac0 fffff800`02a7ffee : 00000000`00000000 00000000`006b3dd4 00000000`00000001 000007fe`fe6bd900 : nt!MmAccessFault+0x14bb
fffff880`098cdc20 00000000`76d6548f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`009be4e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6548f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34cde
fffff800`02af5438 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34cde
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021910-20326-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Fri Feb 19 19:26:19.431 2010 (GMT+1)
System Uptime: 0 days 20:37:43.461
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc5001bd40, ffffffffc0000185, bdd2b880, fffff8a0037a87a8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc5001bd40, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000000bdd2b880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a0037a87a8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c0000185
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wmpnetwk.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880098cd720 -- (.trap 0xfffff880098cd720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80059c0e90 rbx=0000000000000000 rcx=fffffa8008a47ad0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d540a2 rsp=fffff880098cd8b0 rbp=0000000000000000
r8=0000000000000ced r9=fffff8a0037a2040 r10=0000000000000000
r11=fffff8a0037a87a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiRelocateImagePfn+0x3a:
fffff800`02d540a2 4d3923 cmp qword ptr [r11],r12 ds:a850:fffff8a0`037a87a8=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002af5438 to fffff80002a81f00
STACK_TEXT:
fffff880`098cd408 fffff800`02af5438 : 00000000`0000007a fffff6fc`5001bd40 ffffffff`c0000185 00000000`bdd2b880 : nt!KeBugCheckEx
fffff880`098cd410 fffff800`02a73d8b : fffffa80`08894010 fffff880`098cd580 fffff800`02c0cb40 00800000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34cde
fffff880`098cd4f0 fffff800`02a9cda4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff8a0`034105c0 : nt!MiIssueHardFault+0x28b
fffff880`098cd5c0 fffff800`02a7ffee : 00000000`00000000 00000000`000095de 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`098cd720 fffff800`02d540a2 : fffffa80`059c0e90 fffffa80`059c0e00 fffffa80`08a60000 fffffa80`08a845c1 : nt!KiPageFault+0x16e
fffff880`098cd8b0 fffff800`02a734ac : fffffa80`001c19a0 fffffa80`059c0f50 00000000`00000000 fffffa80`08410400 : nt!MiRelocateImagePfn+0x3a
fffff880`098cd910 fffff800`02a73d8b : fffffa80`059c0e90 fffff880`098cda80 fffffa80`08a4dec8 fffffa80`08a4db30 : nt!MiWaitForInPageComplete+0x89c
fffff880`098cd9f0 fffff800`02a9d09b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`098cdac0 fffff800`02a7ffee : 00000000`00000000 00000000`006b3dd4 00000000`00000001 000007fe`fe6bd900 : nt!MmAccessFault+0x14bb
fffff880`098cdc20 00000000`76d6548f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`009be4e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6548f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34cde
fffff800`02af5438 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34cde
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022110-18517-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02ca5e50
Debug session time: Sun Feb 21 19:14:11.640 2010 (GMT+1)
System Uptime: 0 days 0:08:27.671
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...
Unable to load image \SystemRoot\system32\DRIVERS\iaStorV.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorV.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800124435d, fffff88003932858, fffff880039320b0}
Probably caused by : iaStorV.sys ( iaStorV+2b35d )
Followup: MachineOwner
---------
5: 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: fffff8800124435d, The address that the exception occurred at
Arg3: fffff88003932858, Exception Record Address
Arg4: fffff880039320b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
iaStorV+2b35d
fffff880`0124435d 88907e010000 mov byte ptr [rax+17Eh],dl
EXCEPTION_RECORD: fffff88003932858 -- (.exr 0xfffff88003932858)
ExceptionAddress: fffff8800124435d (iaStorV+0x000000000002b35d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000017e
Attempt to write to address 000000000000017e
CONTEXT: fffff880039320b0 -- (.cxr 0xfffff880039320b0)
rax=0000000000000000 rbx=fffffa8006bbc398 rcx=0000000000000001
rdx=0000000000000001 rsi=fffffa80062edc00 rdi=fffffa800681f818
rip=fffff8800124435d rsp=fffff88003932a98 rbp=0000000000000080
r8=fffffa800681f760 r9=0000000000000003 r10=0000000000000120
r11=fffffa8006bbc398 r12=0000000000000000 r13=fffff88001249e64
r14=0000000000000000 r15=fffff880009b7040
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
iaStorV+0x2b35d:
fffff880`0124435d 88907e010000 mov byte ptr [rax+17Eh],dl ds:002b:00000000`0000017e=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000000000017e
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d100e0
000000000000017e
FOLLOWUP_IP:
iaStorV+2b35d
fffff880`0124435d 88907e010000 mov byte ptr [rax+17Eh],dl
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff88001244858 to fffff8800124435d
STACK_TEXT:
fffff880`03932a98 fffff880`01244858 : fffffa80`062edcf0 00000000`00000080 fffffa80`06bdd798 fffff880`01238b74 : iaStorV+0x2b35d
fffff880`03932aa0 fffffa80`062edcf0 : 00000000`00000080 fffffa80`06bdd798 fffff880`01238b74 fffff880`009b7040 : iaStorV+0x2b858
fffff880`03932aa8 00000000`00000080 : fffffa80`06bdd798 fffff880`01238b74 fffff880`009b7040 00000000`00000000 : 0xfffffa80`062edcf0
fffff880`03932ab0 fffffa80`06bdd798 : fffff880`01238b74 fffff880`009b7040 00000000`00000000 fffffa80`062edce0 : 0x80
fffff880`03932ab8 fffff880`01238b74 : fffff880`009b7040 00000000`00000000 fffffa80`062edce0 fffffa80`074b9b40 : 0xfffffa80`06bdd798
fffff880`03932ac0 fffff880`009b7040 : 00000000`00000000 fffffa80`062edce0 fffffa80`074b9b40 fffffa80`062edc00 : iaStorV+0x1fb74
fffff880`03932ac8 00000000`00000000 : fffffa80`062edce0 fffffa80`074b9b40 fffffa80`062edc00 00000000`00000080 : 0xfffff880`009b7040
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: iaStorV+2b35d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStorV
IMAGE_NAME: iaStorV.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49dcd76d
STACK_COMMAND: .cxr 0xfffff880039320b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_iaStorV+2b35d
BUCKET_ID: X64_0x7E_iaStorV+2b35d
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022210-23415-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 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e50
Debug session time: Mon Feb 22 21:36:54.587 2010 (GMT+1)
System Uptime: 0 days 0:22:44.618
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...
Unable to load image \SystemRoot\system32\DRIVERS\iaStorV.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorV.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800130835d, fffff88003932818, fffff88003932070}
Probably caused by : iaStorV.sys ( iaStorV+2b35d )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800130835d, The address that the exception occurred at
Arg3: fffff88003932818, Exception Record Address
Arg4: fffff88003932070, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
iaStorV+2b35d
fffff880`0130835d 88907e010000 mov byte ptr [rax+17Eh],dl
EXCEPTION_RECORD: fffff88003932818 -- (.exr 0xfffff88003932818)
ExceptionAddress: fffff8800130835d (iaStorV+0x000000000002b35d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000017e
Attempt to write to address 000000000000017e
CONTEXT: fffff88003932070 -- (.cxr 0xfffff88003932070)
rax=0000000000000000 rbx=fffffa8006955890 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80062e7cf0 rdi=fffffa8006487800
rip=fffff8800130835d rsp=fffff88003932a58 rbp=0000000000000080
r8=fffffa8006487760 r9=0000000000000000 r10=0000000000000048
r11=fffffa8006955890 r12=0000000000000000 r13=fffff8800130de64
r14=0000000000000000 r15=fffff880009b7040
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
iaStorV+0x2b35d:
fffff880`0130835d 88907e010000 mov byte ptr [rax+17Eh],dl ds:002b:00000000`0000017e=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000000000017e
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cff0e0
000000000000017e
FOLLOWUP_IP:
iaStorV+2b35d
fffff880`0130835d 88907e010000 mov byte ptr [rax+17Eh],dl
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff88001308858 to fffff8800130835d
STACK_TEXT:
fffff880`03932a58 fffff880`01308858 : 00000000`00000002 00000000`00000000 fffffa80`07703a2b fffff800`02acb516 : iaStorV+0x2b35d
fffff880`03932a60 00000000`00000002 : 00000000`00000000 fffffa80`07703a2b fffff800`02acb516 fffff880`009b7040 : iaStorV+0x2b858
fffff880`03932a68 00000000`00000000 : fffffa80`07703a2b fffff800`02acb516 fffff880`009b7040 00000000`00000000 : 0x2
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: iaStorV+2b35d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStorV
IMAGE_NAME: iaStorV.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49dcd76d
STACK_COMMAND: .cxr 0xfffff88003932070 ; kb
FAILURE_BUCKET_ID: X64_0x7E_iaStorV+2b35d
BUCKET_ID: X64_0x7E_iaStorV+2b35d
Followup: MachineOwner
---------
Dump non analizzabile con il tool microsoft. Inserisco quanto ottenuto con Blue Screen view. Codice:
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version 032410-17160-01.dmp25/03/2010 00:04:20SYSTEM_THREAD_EXCEPTION_NOT_HANDLED0x1000007effffffff`c0000005fffff880`012cc2edfffff880`03b2b648fffff880`03b2aea0iaStor.sysiaStor.sys+2b7ecx64C:\Windows\minidump\032410-17160-01.dmp8157600
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\032810-21684-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 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
Debug session time: Sun Mar 28 19:25:19.584 2010 (GMT+2)
System Uptime: 0 days 1:59:12.615
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff800`00b9c088 fffff800`02a80443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
fffff800`00b9c090 fffff800`02adc5f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff800`00b9c120 fffff800`02a23895 : fffff800`02a48460 fffff800`00b9c2d0 fffff800`02a48460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9c220 fffff800`02ad03f3 : 00000000`766b7ed2 fffff800`00b9c2d0 fffffa80`06373118 fffff800`02c4f080 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9c250 fffff800`02a95aa0 : fffff800`00b9cc00 00000000`00000000 fffff800`00b9c500 00000000`00000801 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9c3e0 fffff800`02adcba9 : 00000000`00000002 fffff880`01575abd 00000000`00000000 fffffa80`063bd008 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff800`00b9c410 fffff880`031a8f3a : fffffa80`08eb2cf0 fffff800`02c4f080 fffff800`00b9c4c0 fffffa80`063721a0 : nt!KeAcquireSpinLockRaiseToDpc+0x89
fffff800`00b9c460 fffff880`031aa131 : fffffa80`08bf21a0 fffff880`031b8e7d fffffa80`0a14d7a0 fffffa80`06372050 : USBPORT!USBPORT_AcquireEpListLock+0x2e
fffff800`00b9c490 fffff880`031c3723 : fffffa80`0a14d7a0 fffffa80`063721a0 fffffa80`06372050 fffffa80`0b285010 : USBPORT!USBPORT_ReferenceEndpoint+0x29
fffff800`00b9c4e0 fffff880`031cc2e4 : fffffa80`0b285010 fffffa80`0b285010 00000000`00000001 fffffa80`0b285010 : USBPORT!USBPORT_Ev_Rh_IntrEp_Invalidate+0xf3
fffff800`00b9c540 fffff800`02adffa6 : fffff800`00b9c600 00000000`00000001 00000000`00000000 00000000`00000000 : USBPORT!USBPORT_AsyncTimerDpc+0xb8
fffff800`00b9c570 fffff800`02adf326 : fffffa80`0b285030 00000000`0006fc08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02adfe7e : 00000010`a0353077 fffff800`00b9cc58 00000000`0006fc08 fffff800`02c4f388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02adf697 : 00000004`5601a5c1 00000004`0006fc08 00000004`5601a533 00000000`00000008 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02adc6fa : fffff800`02c4ce80 fffff800`02c5ac40 00000000`00000000 fffffa80`061f30a0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Grazie per l'aiuto! I SPOT THE NOT Ultima modifica di i_spot_the_not : 07-04-2010 alle 22:44. |
|
|
|
|
08-04-2010, 18:15
|
#464 | |
|
Senior Member
Iscritto dal: Jun 2007
Messaggi: 520
|
Quote:
__________________
Case CM 690 ll-Ali CM silent pro M700-MB ASUS Prime Z370-A-CPU Intel Core i5-8600K- NOCTUA NH-D9L-G SKILL F4-2800C17S-8GIS 32gb -Sapphire RX 580 Nitro plus CT500MX500ssd4-ssd samsung 850 evo 500 gb-hd seagate 1 tb- samsung C27FG73 - logitec G502-corsair K70 lux - Os win11 pro 64 bit |
|
|
|
|
|
09-04-2010, 10:47
|
#465 |
|
Member
Iscritto dal: Oct 2009
Messaggi: 147
|
dove trovo la cartella windows old? non la trovo.
L'installazione di 7 è stata fatta ex novo però... |
|
|
|
|
09-04-2010, 17:43
|
#466 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37089
|
Dovrebbe essere dentro C
|
|
|
|
|
09-04-2010, 19:53
|
#467 |
|
Member
Iscritto dal: Dec 2005
Città: Milano
Messaggi: 181
|
Ho visto sotto i miei occhi il problema del pc che citavo sopra, dato che il pc è di mio fratello e l'errore lo segnalava a lui...
In pratica quando si gioca, in questo caso è PES ma penso pure con gli altri giochi, si blocca l'immagine si sente un rumore di sottofondo, c'è questa schermata blu che non ho fatto ben e leggere qual'era il problema, c'era un timer e poi si è riavviato da solo, questo è il problema che segnala windows dopo essersi riavviato: Firma problema: Nome evento problema: BlueScreen Versione SO: 6.1.7600.2.0.0.256.1 ID impostazioni locali: 1040 Ulteriori informazioni sul problema: BCCode: 124 BCP1: 0000000000000000 BCP2: FFFFFA800515E028 BCP3: 00000000B2000000 BCP4: 0000000000010005 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 File che contribuiscono alla descrizione del problema: C:\Windows\Minidump\040910-13671-01.dmp C:\Users\Damiano\AppData\Local\Temp\WER-30656-0.sysdata.xml Leggere l'informativa sulla privacy online: http://go.microsoft.com/fwlink/?link...8&clcid=0x0410 Se l'informativa sulla privacy online non è disponibile, leggere quella offline: C:\Windows\system32\it-IT\erofflps.txt Niente di nuovo? Vi allego il minidump, attendo news voi che siete esperti, grazie ancora.. http://www.mediafire.com/?nt1aijblzg0
__________________
I videogiochi non influenzano i bambini. Voglio dire, se Pac-man influenzasse la gente, staremmo tutti saltando in sale scure, masticando pillole magiche e ascoltando musica elettronica ripetitiva!" (K.Wilson, Nintendo, 1989)-Qualche anno dopo nacquero i rave... |
|
|
|
|
10-04-2010, 13:36
|
#468 |
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Dopo una settimana di tregua, nuova BSOD
 Il file dump indica System_Service_Exception 0x0000003b. Usando il Driver Verify Manager di 7, salta fuori che tale atikmdag.sys (ATI Radeon Kernel Mode driver) non è provvisto di firma digitale, potrebbe essere lui la causa di tutto? |
|
|
|
|
11-04-2010, 10:34
|
#469 | |
|
Senior Member
Iscritto dal: Jun 2007
Messaggi: 520
|
Quote:
-strumenti amministrazione -visualizzatore eventi -citico oppure errore dovresti(supposizione) vedere piu' in chiaro il tipo di errore. Personalmente ieri ho avuto una 20 ina di messaggi di errore..da kernel power a windows non originale..un massacro,ora ..nulla,ho dovuto riattivare sia win7 che office student 2007(di mia figlia),non so' che altro dirti,ho gia' avvisato l'assemblatore che martedi' glielo riporto,sempre che la pausa di errori attuali non finisca. Avete osservato problemi negli update ufficiali(messaggi di errore?)
__________________
Case CM 690 ll-Ali CM silent pro M700-MB ASUS Prime Z370-A-CPU Intel Core i5-8600K- NOCTUA NH-D9L-G SKILL F4-2800C17S-8GIS 32gb -Sapphire RX 580 Nitro plus CT500MX500ssd4-ssd samsung 850 evo 500 gb-hd seagate 1 tb- samsung C27FG73 - logitec G502-corsair K70 lux - Os win11 pro 64 bit Ultima modifica di divasco : 11-04-2010 alle 10:36. Motivo: edit |
|
|
|
|
|
11-04-2010, 10:57
|
#470 | |
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Quote:
Vedo anche molti avvisi che indicano Errore nel dispositivo \Device\Harddisk1\DR1. Comincio a non capirci più una mazza, anche perché stanotte il PC mi ha sparato altre 3 BSOD in successione poi si è avviato e ha funzionato senza fare una piega. Per quanto riguarda gli aggiornamenti nessun problema. Ultima modifica di Phantom II : 11-04-2010 alle 11:01. |
|
|
|
|
|
11-04-2010, 11:08
|
#471 | |||
|
Senior Member
Iscritto dal: May 2002
Città: Nardo' (LE)
Messaggi: 4018
|
Quote:
Quote:
Quote:
__________________
15 maggio 2008  11 marzo 2013 26 febbraio 2014
|
|||
|
|
|
|
11-04-2010, 11:25
|
#472 |
|
Junior Member
Iscritto dal: Feb 2009
Messaggi: 12
|
Bhe ragazzi premetto che non sono molto pratico, ho un pc con i7 820, 5850, 4gb di ram a 1600 e un asus maximun come scheda madre, ce l'ho da due mesi ed è sempre andato bene, ma 2 giorni fa ho dovuto muovere il case per pitturare la stanza e da allora al primo start ha detto qualcosa sul bios che non ho capito e poi tre BSOD, ho scaricato bluescreenview ed ecco i risultati:
http://img6.imageshack.us/img6/4017/catturani.png http://img682.imageshack.us/img682/2741/cattura2u.png http://img339.imageshack.us/img339/9144/cattura23.png noto che negli errori c'è sempre il seguente percorso C:\Windows\system32\ntoskrnl.exe, che può essere? |
|
|
|
|
11-04-2010, 13:16
|
#473 | |||
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Quote:
Quote:
Quote:
|
|||
|
|
|
|
11-04-2010, 18:03
|
#474 | |
|
Senior Member
Iscritto dal: Jun 2007
Messaggi: 520
|
Quote:
__________________
Case CM 690 ll-Ali CM silent pro M700-MB ASUS Prime Z370-A-CPU Intel Core i5-8600K- NOCTUA NH-D9L-G SKILL F4-2800C17S-8GIS 32gb -Sapphire RX 580 Nitro plus CT500MX500ssd4-ssd samsung 850 evo 500 gb-hd seagate 1 tb- samsung C27FG73 - logitec G502-corsair K70 lux - Os win11 pro 64 bit |
|
|
|
|
|
11-04-2010, 18:16
|
#475 | |
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Quote:
|
|
|
|
|
|
11-04-2010, 18:45
|
#476 | |||
|
Senior Member
Iscritto dal: May 2002
Città: Nardo' (LE)
Messaggi: 4018
|
Quote:
Quote:
Quote:
Codice:
SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Edit: hai provato a creare un profilo utente nuovo? A volte cosi' si riesce ad isolare il problema (che, magari, e' solo qualche programma che si carica all'avvio che rompe le scatole, come successo a me l'estate scorsa)!
__________________
15 maggio 2008 11 marzo 2013 26 febbraio 2014
|
|||
|
|
|
|
11-04-2010, 20:44
|
#477 | ||||
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Quote:
Quote:
Quote:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041010-21812-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
Debug session time: Sat Apr 10 14:11:24.244 2010 (GMT+2)
System Uptime: 0 days 0:09:58.509
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800031a918f, fffff88005bc5080, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+df )
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: fffff800031a918f, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88005bc5080, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!ExFreePoolWithTag+df
fffff800`031a918f 4c8d156aaee5ff lea r10,[nt!MmIsSessionAddress <PERF> (nt+0x0) (fffff800`03004000)]
CONTEXT: fffff88005bc5080 -- (.cxr 0xfffff88005bc5080)
rax=0000000000000009 rbx=fffffa8004482e70 rcx=fffffa8004482f00
rdx=0000000000000009 rsi=0000000000000002 rdi=0000000000000000
rip=fffff800031a918f rsp=fffff88005bc5a60 rbp=0000000020646156
r8=0000000000000050 r9=fffff80003202a80 r10=0000000000000001
r11=fffffa800645d060 r12=0000000000000009 r13=fffffa8004482e80
r14=0000000003da9fff r15=0000000003da0000
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!ExFreePoolWithTag+0xdf:
fffff800`031a918f 4c8d156aaee5ff lea r10,[nt!MmIsSessionAddress <PERF> (nt+0x0) (fffff800`03004000)]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: cmdagent.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000338bf34 to fffff800031a918f
STACK_TEXT:
fffff880`05bc5a60 fffff800`0338bf34 : 00000000`0000a000 00000000`00000000 fffffa80`20646156 fffffa80`00000000 : nt!ExFreePoolWithTag+0xdf
fffff880`05bc5b10 fffff800`0338c25b : 00000000`00000000 00000000`03da0000 fffffa80`00000001 00000000`00007201 : nt!MiUnmapViewOfSection+0x294
fffff880`05bc5bd0 fffff800`03075153 : 00000000`00004826 fffff880`05bc5ca0 fffffa80`0645d060 00000000`000015ff : nt!NtUnmapViewOfSection+0x5f
fffff880`05bc5c20 00000000`76dd015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04abf6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dd015a
FOLLOWUP_IP:
nt!ExFreePoolWithTag+df
fffff800`031a918f 4c8d156aaee5ff lea r10,[nt!MmIsSessionAddress <PERF> (nt+0x0) (fffff800`03004000)]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExFreePoolWithTag+df
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88005bc5080 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!ExFreePoolWithTag+df
BUCKET_ID: X64_0x3B_nt!ExFreePoolWithTag+df
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041110-23937-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032a3e50
Debug session time: Sun Apr 11 00:56:02.607 2010 (GMT+2)
System Uptime: 0 days 0:08:54.951
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6da68000008, 0, fffff800030e9918, 5}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )
Followup: MachineOwner
---------
0: 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: fffff6da68000008, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030e9918, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330e0e0
fffff6da68000008
FAULTING_IP:
nt!MiLockProtoPoolPage+38
fffff800`030e9918 4a8b3c36 mov rdi,qword ptr [rsi+r14]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800664d0a0 -- (.trap 0xfffff8800664d0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a004614ee0 rbx=0000000000000000 rcx=000000000000003f
rdx=0000000001ef0038 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880047c02eb rsp=fffff8800664d230 rbp=fffff8800664da40
r8=fffffa80069ee038 r9=0000000000000002 r10=0000000000000025
r11=0000000080000fc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39b:
fffff880`047c02eb 488b38 mov rdi,qword ptr [rax] ds:0002:fffff8a0`04614ee0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003155b91 to fffff800030d7f00
STACK_TEXT:
fffff880`0664cae8 fffff800`03155b91 : 00000000`00000050 fffff6da`68000008 00000000`00000000 fffff880`0664cc50 : nt!KeBugCheckEx
fffff880`0664caf0 fffff800`030d5fee : 00000000`00000000 fffff8a0`04614ee0 00000000`80000000 fffffa80`0528eb60 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`0664cc50 fffff800`030e9918 : 00000000`00000000 00000000`00000000 fffff800`03262b40 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0664cde0 fffff800`030f44b7 : 00000000`00000000 fffff8a0`04487268 fffff6fc`50019220 fffff800`03262b40 : nt!MiLockProtoPoolPage+0x38
fffff880`0664ce30 fffff800`030f24d1 : fffff880`0664cf60 fffffa80`05e0b170 fffff880`0664cfe0 fffff800`030d60fd : nt!MiDispatchFault+0x8f7
fffff880`0664cf40 fffff800`030d5fee : 00000000`00000000 00000000`00000000 fffff8a0`0aa28600 fffff6fb`7e2800c8 : nt!MmAccessFault+0x8f1
fffff880`0664d0a0 fffff880`047c02eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0664d230 fffff880`047a63e7 : fffffa80`0581d401 fffffa80`06adef10 00000000`01ef0038 00000000`0000000e : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39b
fffff880`0664d320 fffff880`0471ed6a : fffffa80`0528eb60 00000000`00000200 fffff880`0664da40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`0664d370 fffffa80`0528eb60 : 00000000`00000200 fffff880`0664da40 00000000`00000000 00000000`00000001 : dxgkrnl+0x6fd6a
fffff880`0664d378 00000000`00000200 : fffff880`0664da40 00000000`00000000 00000000`00000001 fffff880`0664d998 : 0xfffffa80`0528eb60
fffff880`0664d380 fffff880`0664da40 : 00000000`00000000 00000000`00000001 fffff880`0664d998 fffff880`0664d410 : 0x200
fffff880`0664d388 00000000`00000000 : 00000000`00000001 fffff880`0664d998 fffff880`0664d410 fffffa80`05267b30 : 0xfffff880`0664da40
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
fffff880`047c02eb 488b38 mov rdi,qword ptr [rax]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
BUCKET_ID: X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041110-26359-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
Debug session time: Sun Apr 11 00:58:21.556 2010 (GMT+2)
System Uptime: 0 days 0:01:33.900
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8000336d0d0, fffff88006096e70, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+a0 )
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: fffff8000336d0d0, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006096e70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!ObpLookupDirectoryEntry+a0
fffff800`0336d0d0 8d045b lea eax,[rbx+rbx*2]
CONTEXT: fffff88006096e70 -- (.cxr 0xfffff88006096e70)
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000043 rsi=fffffa800683fcc8 rdi=fffff8a00304a3a8
rip=fffff8000336d0d0 rsp=fffff88006097850 rbp=0000000000000040
r8=0000000000000040 r9=0000000000000001 r10=fffff8a003e54480
r11=0000000000000002 r12=fffff88006097950 r13=fffff88006097a10
r14=fffff8a003e54480 r15=fffff8a003e54480
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!ObpLookupDirectoryEntry+0xa0:
fffff800`0336d0d0 8d045b lea eax,[rbx+rbx*2]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x3B
PROCESS_NAME: ObjectDock.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000336d0d0
STACK_TEXT:
fffff880`06097850 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpLookupDirectoryEntry+0xa0
FOLLOWUP_IP:
nt!ObpLookupDirectoryEntry+a0
fffff800`0336d0d0 8d045b lea eax,[rbx+rbx*2]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpLookupDirectoryEntry+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88006096e70 ; kb
FAILURE_BUCKET_ID: X64_0x3B_VRF_nt!ObpLookupDirectoryEntry+a0
BUCKET_ID: X64_0x3B_VRF_nt!ObpLookupDirectoryEntry+a0
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041110-26750-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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
Debug session time: Sun Apr 11 01:00:11.369 2010 (GMT+2)
System Uptime: 0 days 0:01:00.697
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff80003351481, fffff88006327c40, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpCheckKeyBodyAccess+a1 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80003351481, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006327c40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {ERRORE DI EXCEPTION} Istruzione non valida Si tentato di eseguire un'istruzione non valida.
FAULTING_IP:
nt!CmpCheckKeyBodyAccess+a1
fffff800`03351481 0f854400f8ff jne nt! ?? ::NNGAKEGL::`string'+0x21eba (fffff800`032d14cb)
CONTEXT: fffff88006327c40 -- (.cxr 0xfffff88006327c40)
rax=fffff8a00a98b820 rbx=fffff8a006f403e4 rcx=fffff8a00060b010
rdx=0000000000000000 rsi=fffffa800737b010 rdi=fffff8a009192bd0
rip=fffff80003351481 rsp=fffff88006328620 rbp=fffff8a009192bd8
r8=fffff8a000654660 r9=0000000000000001 r10=fffffa8003c78148
r11=fffff88006328690 r12=0000000000000002 r13=0000000000000001
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010213
nt!CmpCheckKeyBodyAccess+0xa1:
fffff800`03351481 0f854400f8ff jne nt! ?? ::NNGAKEGL::`string'+0x21eba (fffff800`032d14cb) [br=1]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x3B
PROCESS_NAME: ObjectDock.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003351481
STACK_TEXT:
fffff880`06328620 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpCheckKeyBodyAccess+0xa1
FOLLOWUP_IP:
nt!CmpCheckKeyBodyAccess+a1
fffff800`03351481 0f854400f8ff jne nt! ?? ::NNGAKEGL::`string'+0x21eba (fffff800`032d14cb)
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpCheckKeyBodyAccess+a1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88006327c40 ; kb
FAILURE_BUCKET_ID: X64_0x3B_VRF_nt!CmpCheckKeyBodyAccess+a1
BUCKET_ID: X64_0x3B_VRF_nt!CmpCheckKeyBodyAccess+a1
Followup: MachineOwner
---------
Quote:
|
||||
|
|
|
|
11-04-2010, 21:45
|
#478 | ||
|
Senior Member
Iscritto dal: May 2002
Città: Nardo' (LE)
Messaggi: 4018
|
Quote:
Quote:
Per dirti, la scorsa estate, senza apparente motivo, ogni volta che facevo il logout, veniva fuori un BSOD: la colpa era, scopri' creando un account pulito, del software di gestione dell'ATI Remote, che pure fino ad allora aveva funzionato perfettamente per circa un anno: sul nuovo utente quel software non si avviava e il problema non si presentava!
__________________
15 maggio 2008 11 marzo 2013 26 febbraio 2014
|
||
|
|
|
|
11-04-2010, 21:58
|
#479 | ||
|
Senior Member
Iscritto dal: Jan 2002
Messaggi: 6044
|
Quote:
Nel testo è riportato "Errore nel dispositivo \Device\Harddisk1\DR1" Quote:
|
||
|
|
|
|
11-04-2010, 22:31
|
#480 | ||
|
Senior Member
Iscritto dal: May 2002
Città: Nardo' (LE)
Messaggi: 4018
|
Quote:
Quote:
__________________
15 maggio 2008 11 marzo 2013 26 febbraio 2014
|
||
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 06:37.
