Toggle sidebar Toggle sidebar

ASUS aiuto: BSOD irrisolvibile

I

i_spot_the_not

Utente Attivo
50
0
Ciao,
la mia configurazione è:
- Asus Rampage II Gene
- i7 920
- 6GB DDR3 Gskill Trident 1600 6-7-6-18
- HD3870X2
- 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.

ADDED: Le ultime BSOD sono le più recenti; l'errore più frequente è An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval.



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
---------
 
I

i_spot_the_not

Utente Attivo
50
0
2
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
---------
 
I

i_spot_the_not

Utente Attivo
50
0
3
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
---------
 
I

i_spot_the_not

Utente Attivo
50
0
4
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
  ---------
 
I

i_spot_the_not

Utente Attivo
50
0
5
Dump non analizzabile con il tool microsoft. Inserisco quanto ottenuto con Blue Screen view.

Codice: 
   [SIZE=1]Dump File [/SIZE][SIZE=1]Crash Time [/SIZE][SIZE=1]Bug Check String [/SIZE][SIZE=1]Bug Check Code [/SIZE][SIZE=1]Parameter 1 [/SIZE][SIZE=1]Parameter 2 [/SIZE][SIZE=1]Parameter 3 [/SIZE][SIZE=1]Parameter 4 [/SIZE][SIZE=1]Caused By Driver [/SIZE][SIZE=1]Caused By Address [/SIZE][SIZE=1]File Description [/SIZE][SIZE=1]Product Name [/SIZE][SIZE=1]Company [/SIZE][SIZE=1]File Version [/SIZE][SIZE=1]Processor [/SIZE][SIZE=1]Computer Name [/SIZE][SIZE=1]Full Path [/SIZE][SIZE=1]Processors Count [/SIZE][SIZE=1]Major Version [/SIZE][SIZE=1]Minor Version [/SIZE][SIZE=1]032410-17160-01.dmp[/SIZE][SIZE=1]25/03/2010 00:04:20[/SIZE][SIZE=1]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/SIZE][SIZE=1]0x1000007e[/SIZE][SIZE=1]ffffffff`c0000005[/SIZE][SIZE=1]fffff880`012cc2ed[/SIZE][SIZE=1]fffff880`03b2b648[/SIZE][SIZE=1]fffff880`03b2aea0[/SIZE][SIZE=1]iaStor.sys[/SIZE][SIZE=1]iaStor.sys+2b7ec[/SIZE][SIZE=1]x64[/SIZE][SIZE=1]C:\Windows\minidump\032410-17160-01.dmp[/SIZE][SIZE=1]8[/SIZE][SIZE=1]15[/SIZE][SIZE=1]7600 [/SIZE]

[URL=http://img24.imageshack.us/i/captureqj.png/][IMG]http://img24.imageshack.us/img24/7610/captureqj.png[/IMG][/URL]

6
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
   ---------
Scusate per la lunghezza del post e se ho dovuto dividerlo, ma non ci stava tutto.

Grazie per l'aiuto! Spero mi riusciate ad aiutare a trovare una soluzione.

I SPOT THE NOT
 
G

greensheep85

Bannato a Vita
1,275
87
mmm li dice che è legato a questi due file iaStorV.sys e wmpnetwk.exe

il secondo è legato a windows media player network
prova a controllare questa applicazione

toglilo proprio dai processi tra i services.msc
 
I

i_spot_the_not

Utente Attivo
50
0
Ho disabilitato il servizio di windows media player network.
Le ultime bsod sono le più recenti. Purtroppo alcune BSOD e i freeze non creano il dump, quindi l'elenco non è completo. L'ultimo errore l'ho avuto diverse volte: An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval.

Grazie
 
Devi accedere o registrarti per rispondere qui.

Entra

Hai dimenticato la password?
oppure Accedi utilizzando
Discord Ufficiale Entra ora!