BSOD (Blue Screen Of Death) capire di cosa si parla

pasta

Praticamente il PC non stava facendo nulla di rilevante:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump102911-36613-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:Windowssymbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`03890670
Debug session time: Sat Oct 29 19:33:50.858 2011 (UTC + 2:00)
System Uptime: 0 days 8:34:07.075
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {24, 2, 0, fffff800036d06cb}

Probably caused by : nwifi.sys ( nwifi!ExtSTAReceivePacket+a9e )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800036d06cb, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038fa100
0000000000000024 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+22b
fffff800`036d06cb 418b4624        mov     eax,dword ptr [r14+24h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b350 -- (.trap 0xfffff8800371b350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a76f700 rbx=0000000000000000 rcx=fffffa800aaa4960
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800036d06cb rsp=fffff8800371b4e8 rbp=fffffa800a961c28
r8=fffff880009f4301  r9=0000000000000004 r10=0000000000000013
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`036d06cb 418b4624        mov     eax,dword ptr [r14+24h] ds:00000000`00000024=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800036c71e9 to fffff800036c7c40

STACK_TEXT:  
fffff880`0371b208 fffff800`036c71e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b210 fffff800`036c5e60 : fffffa80`0c7af4f0 fffff880`01d170eb fffffa80`09fed8d0 fffffa80`0a961c28 : nt!KiBugCheckDispatch+0x69
fffff880`0371b350 fffff800`036d06cb : fffffa80`04cd3a70 00000000`00000041 00000000`00000000 1100d3dc`e1bc7170 : nt!KiPageFault+0x260
fffff880`0371b4e8 fffffa80`0a93c854 : fffffa80`0a961c20 fffff880`009f2180 00000000`00000001 00000000`00000102 : nt!KiTimerWaitTest+0x22b
fffff880`0371b568 fffffa80`0a961c20 : fffff880`009f2180 00000000`00000001 00000000`00000102 fffff880`0314fc46 : 0xfffffa80`0a93c854
fffff880`0371b570 fffff880`009f2180 : 00000000`00000001 00000000`00000102 fffff880`0314fc46 00000000`00000000 : 0xfffffa80`0a961c20
fffff880`0371b578 00000000`00000001 : 00000000`00000102 fffff880`0314fc46 00000000`00000000 fffffa80`09fe8010 : 0xfffff880`009f2180
fffff880`0371b580 00000000`00000102 : fffff880`0314fc46 00000000`00000000 fffffa80`09fe8010 fffffa80`0a93c850 : 0x1
fffff880`0371b588 fffff880`0314fc46 : 00000000`00000000 fffffa80`09fe8010 fffffa80`0a93c850 fffffa80`0a93c850 : 0x102
fffff880`0371b590 fffff880`0314f3f2 : 00000000`00000103 00000000`00000001 fffffa80`09fe8010 fffff880`0371b8a8 : nwifi!ExtSTAReceivePacket+0xa9e
fffff880`0371b670 fffff880`0312f053 : fffffa80`0c7af4f0 00000000`00000000 00000000`0000ff02 00000000`00000000 : nwifi!ExtSTAReceivePacket+0x24a
fffff880`0371b6c0 fffff880`0312f808 : fffffa80`08185010 fffffa80`0b776770 fffffa80`0b776770 fffffa80`0b776770 : nwifi!Pt6RepackRecvNBL+0x9ef
fffff880`0371b910 fffff880`01c62900 : fffff880`0371b960 00000000`00000000 00000000`00000000 fffff880`01d1736f : nwifi!Pt6Receive+0x2b0
fffff880`0371b970 fffff800`036056e5 : fffffa80`07ebb000 00000000`00000d00 00000000`00000000 00000000`00000000 : ndis!NdisFIndicateReceiveNetBufferLists+0x80
fffff880`0371b9b0 fffff880`03f42301 : 00000000`00000000 fffff880`04cbad40 fffff880`04cbb5b8 fffffa80`079c9000 : hal!HalpDmaReturnToScatterPool+0x4d
fffff880`0371ba00 00000000`00000000 : fffff880`04cbad40 fffff880`04cbb5b8 fffffa80`079c9000 00000000`00000000 : 0xfffff880`03f42301


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!ExtSTAReceivePacket+a9e
fffff880`0314fc46 4881c4a0000000  add     rsp,0A0h

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  nwifi!ExtSTAReceivePacket+a9e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0xA_nwifi!ExtSTAReceivePacket+a9e

BUCKET_ID:  X64_0xA_nwifi!ExtSTAReceivePacket+a9e

Followup: MachineOwner
---------

Le085

Dal log sembrerebbe un problema di instabilità hardware oppure un problema da ricondurre al driver wifi.

tom1

sono sempre driver

RIC3

ottima guida!

RIC3

ma si devi scaricare un programma?se si dove si trova?

tom1

Puoi scaricare questo

Blue screen of death (STOP error) information in dump files.

pasta

Eress ha scritto:

Prova ad aggiornare il tuo Wireless-N USB Network Adapter

ok grazie, è la prima cosa che farò.....in serata però ho avuto anche questo:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump102911-16832-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:Windowssymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0361d000 PsLoadedModuleList = 0xfffff800`03862670
Debug session time: Sat Oct 29 21:44:50.697 2011 (UTC + 1:00)
System Uptime: 0 days 0:40:26.541
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1, 2, 0, fffff800036a5b28}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1c8 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800036a5b28, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038cc100
0000000000000001 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+1c8
fffff800`036a5b28 488b4500        mov     rax,qword ptr [rbp]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff80003836f70
rdx=fffffa8009a60268 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800036a5b28 rsp=fffff80000b9c560 rbp=0000000000000001
r8=fffffa8009bf5530  r9=000000000000009b r10=fffff8000380fe80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!KiInsertTimerTable+0x1c8:
fffff800`036a5b28 488b4500        mov     rax,qword ptr [rbp] ss:0018:00000000`00000001=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800036991e9 to fffff80003699c40

STACK_TEXT:  
fffff800`00b9c288 fffff800`036991e9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c290 fffff800`03697e60 : 00000000`40a00088 00000000`0003b3f1 fffffa80`04cb2d30 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c3d0 fffff800`036a5b28 : ffffffff`fffe7960 fffff800`036a55fc fffff800`0380fe80 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c560 00000000`00000000 : fffff800`00b9c608 00000000`00000002 00000000`00025f9a fffff800`036a543d : nt!KiInsertTimerTable+0x1c8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+1c8
fffff800`036a5b28 488b4500        mov     rax,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+1c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+1c8

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+1c8

Followup: MachineOwner
---------

tom1

sempre driver, se continua di questo passo direi di formattare

pasta

tom1 ha scritto:

sempre driver, se continua di questo passo direi di formattare

mi sapresti dire quale driver ha causato il crash?....almeno inizio agendo su quello (come ho fatto per il precedente crash in cui ho aggiornato i drivers del wifi...almeno come prova)

tom1

è dato dal processo ntkrnlmp.exe ed è riconducibile ad un driver che non si è avviato correttamente, il driver non è definito

pasta

nenahce tramite questo si capisce?

tom1

no quello è un processo di windows , se crea lui i bsod puoi solo formattare

RIC3

ok...ho scaricato il programma ,ma non ho capito come si usa! ho questo screen:

Che devo fare?

pasta

mmmH, vorrei sapere almeno sulla base di cosa, altrimenti dopo il format potrei riavere lo stesso problema :cheazz:

tom1

RIC3 ha scritto:

ok...ho scaricato il programma ,ma non ho capito come si usa! ho questo screen:

Che devo fare?

ma hai avuto dei bsod?

pasta ha scritto:

mmmH, vorrei sapere almeno sulla base di cosa, altrimenti dopo il format potrei riavere lo stesso problema :cheazz:

non c'è di solito si parla di nuovo hardware e quindi nuovi driver che non sono stati installati a dovere

RIC3

tom1 ha scritto:

ma hai avuto dei bsod?

no ,però vorrei sapere quella stringa in rosso che significa per esempio?

tom1

nulla

RIC3

e quando succede un bsod che dovrebbe uscire?

tom1

un log con errore e causa

RIC3

ok,capito!