View Full Version : Aiuto BSOD frequenti
i_spot_the_not
20-02-2010, 10:34
Ciao,
sto continuamente avendo BSOD con Windows 7 64bit.
Ho utilizzato il tool bluescreenview per visualizzare i dump del sistema.
Innanzitutto non so per che motivo ma ne trovo solo 2, comunque:
http://img200.imageshack.us/img200/625/bsod1.th.jpg (http://img200.imageshack.us/i/bsod1.jpg/)
http://img64.imageshack.us/img64/3940/bsod2.th.jpg (http://img64.imageshack.us/i/bsod2.jpg/)
Cosa può essere? :cry:
Sono disperato: computer nuovo...... :muro:
Grazie mille
EDIT: Memtest ok, HD tune ok, no overclock, windows installato 4 giorni fa (lo faceva anche con le installazioni precedenti), il BSOD si verifica in momenti casuali, durante installazioni, durante la navigazione o con il pc abbandonato a se stesso accesso.
Il Bruco
20-02-2010, 11:50
Prova ad usare il PC disistallando la o le schede di rete, vedi se ti da ancora dei BSOD.
Se così funge reinstalla il tutto, cercando dei driver aggiornati.
i_spot_the_not
20-02-2010, 12:25
La scheda video è una ATI 3870X2 (che usavo anche con la configurazione precedente), sempre con Windows 7 64bit e con cui non avevo problemi.
Comunque i BSOD (o i freeze) li ho avuti sia coi driver che installa automaticamente windows (che riconosce la scheda video), sia con quelli scaricati dal sito Ati.
Grazie
In questi casi è meglio seguire la guida (http://www.hwupgrade.it/forum/showthread.php?t=1955371) all'estrazione del file dmp
Il Bruco
20-02-2010, 19:13
La scheda video è una ATI 3870X2 (che usavo anche con la configurazione precedente), sempre con Windows 7 64bit e con cui non avevo problemi.
Comunque i BSOD (o i freeze) li ho avuti sia coi driver che installa automaticamente windows (che riconosce la scheda video), sia con quelli scaricati dal sito Ati.
Grazie
Ho scritto scheda di Rete non scheda Video.
L'errore viene da ntoskrnl.exe che serve a ottimizzare automaticamente memoria, Internet, e CPU
Per cui se Memtest ok, HD tune ok, no overclock,
Rimane la scheda di rete che usi per navigare in Internet.
i_spot_the_not
22-02-2010, 22:54
Ciao,
ho fatto quanto mi avete detto entrambi.
i risultati sono stati 4 bsod, due causate dagli hdd (che nel frattempo sono diventati con error nella schermata di boot) e due penso dalla rete.
BSOD 1: HDD
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
---------
BSOD 2: HDD
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
---------
BSOD 3: Scheda di rete (?)
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
---------
BSOD 4: Scheda di rete (?)
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
---------
Probabilmente quindi dovrò cambiare gli hard disk, ma per la scheda di rete cosa faccio? è quella integrata sulla scheda madre (ASUS RAMPAGE II GENE) e ho aggiornato i driver tra la BSOD 3 e la BSOD 4, prendendoli direttamente dal sito asus.
Che cosa potrei fare?
Grazie mille
Ispotthenot
i_spot_the_not
27-02-2010, 13:07
Nuova BSOD che non ha generato un minidump... strano.
Nessuno sa interpretare quanto scritto sopra?
Aiutoooo
Grazie
Il tuo problema sembra riconducibile almano a questo driver Iastorv.sys (http://dllinfo.dll-free-download.org/i/45368-iastorv.sys.html) driver .sys e questo processo WMPNetwk.exe (http://www.technixupdate.com/what-is-wmpnetwkexe-can-i-stop-it/)
i_spot_the_not
27-02-2010, 15:22
Provvederò a disabilitare il servizio di media player per evitare il primo tipo di problema;
L'altro problema può a questo punto essere provocato dai dischi danneggiati e non dal driver? Ho notato che mi viene segnalato un errore sullo status del disco all'avvio del PC, nella schermata che mostra anche lo status del raid (Bootable)
Infatti potrebbe anche trattarsi di un problema HW
i_spot_the_not
27-02-2010, 23:12
Breve test di "vita quotidiana" con due HDD WD Caviar Black 500GB, il sistema non da BSOD. Dovrei tuttavia provarli ancora un po', perchè le BSOD o i freeze li ho avuti in situazioni di normalità (navigazione web, elaborazione file doc o xls) e non di stress.
Grazie
i_spot_the_not
28-02-2010, 14:52
Ho avuto una nuova BSOD anche con degli hdd nuovi.
Non so se ho disabilitato il media player network sharing perchè il tutorial che mi hai messo è per una versione precedente di mediaplayer. Tuttavia ti preciso che non avevo mai aperto media player.
L'errore sembrava diverso, tuttavia non sono riuscito a leggere e non trovo il minidump; il sintomo uguale: iniziale rallentamento del mouse, crash di crome, crash del pc.
Dove posso trovare il dump se la cartella minidump non esiste?
NOTA: avevo impostato save to kernel e non to debug file, quindi è per questo che non ho la cartella. Non esiste comunque un modo per recuperare quel file?
fabbri.fili
06-09-2010, 15:17
Ciao,
sto continuamente avendo BSOD con Windows 7 64bit.
Ho utilizzato il tool bluescreenview per visualizzare i dump del sistema.
Innanzitutto non so per che motivo ma ne trovo solo 2, comunque:
http://img200.imageshack.us/img200/625/bsod1.th.jpg (http://img200.imageshack.us/i/bsod1.jpg/)
http://img64.imageshack.us/img64/3940/bsod2.th.jpg (http://img64.imageshack.us/i/bsod2.jpg/)
Cosa può essere? :cry:
Sono disperato: computer nuovo...... :muro:
Grazie mille
EDIT: Memtest ok, HD tune ok, no overclock, windows installato 4 giorni fa (lo faceva anche con le installazioni precedenti), il BSOD si verifica in momenti casuali, durante installazioni, durante la navigazione o con il pc abbandonato a se stesso accesso.
cerca di fotografare la pagina iniziale di bluscreenwiever in modo da vedere anche il secondo file che dà il problema, perchè se ci fai caso i primi due file sono evidenziati di rosa, prova a fare una foto con quelli, selezionando naturalmente tutte le schermate blu, solo evidenziando la riga del bsod di blu
cerca di fotografare la pagina iniziale di bluscreenwiever in modo da vedere anche il secondo file che dà il problema, perchè se ci fai caso i primi due file sono evidenziati di rosa, prova a fare una foto con quelli, selezionando naturalmente tutte le schermate blu, solo evidenziando la riga del bsod di blu
controlla la data dell'ultimo post ;)
controlla la data dell'ultimo post ;)
:rotfl: :rotfl:
fabbri.fili
06-09-2010, 17:49
controlla la data dell'ultimo post ;)
ho letto, sembra non avere l'ora di windows in regola, o mi sbaglio?
ho letto, sembra non avere l'ora di windows in regola, o mi sbaglio?
:rotfl: :rotfl: :rotfl: :rotfl: :rotfl: :rotfl: :rotfl: :rotfl:
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.