Vista/7 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni

[Alexietto]

Originariamente inviato da Alexietto

Salve ragazzi,
stavo sbirciando in giro in cerca di info che avrebbero potuto aiutarmi nel problema che da un pò di tempo (a random) affligge il mio PC. Giocando a Skayrim; Kingdoms of Amalur: Reckoning (Giochi scaricati e crakkati) mi da sto benedetto BlueScreen ogni tanto, giocando a GTAIV va tutto bene Fifa12 Ok Battlefild3 ok, oggi mi ha rifatto per 2 volte sto BlueScreen.. Mi aiutate ad identificare il problema??

Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7601.2.1.0.768.3
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004A60038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\071812-21153-01.dmp
C:\Users\Alessio\AppData\Local\Temp\WER-53305-0.sysdata.xml

I dati del mio PC sono
Win 7 home premium
4 GB RAM
Processore AMD Athlon(tm) II x4 635 processor 2.90 Ghz
Scheda Grafica GeForce GT320 V Driver 301.42


Non sono molto pratico con il Pc se servono altre info ditemelo!!

Grazie.

Allego immagine di bluescreenview, riuscite a capire qualcosa??
ditemi se serve altro!!!

Grazie!!
http://imageshack.us/photo/my-images...maginehry.png/

[Eress]

Per iniziare controlla la ram scollegando un banco alla volta

[Alexietto]

Non sono molto pratico con il Pc...

che significa un banco alla volta??

[Eress]

Usi il pc con un banco scollegato alla volta, spero sia più chiaro adesso

[Alexietto]

Se è un problema che ci devo mettere le mani lo porto all' assistenza visto che è in garanzia. Quindi non è un problema dovuto che ne so a qualche errore di sistema?

[Eress]

In questi casi per saperlo bisogna andare per esclusione, per quello bisogna prima testare l'HW per poi passare al possibile problema driver o altro. Intanto se hai antivirus/firewall esterni, disattivali

[Giulio_P]

purtroppo il mio problema rimane: non era l'hd esterno!!! sempre il solito power disk failure....

==================================================
Dump File : 072812-30560-01.dmp
Crash Time : 28.07.2012 09:53:03
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`04ec4060
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`044406c0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072812-30560-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 908.640
==================================================

[Eress]

A sto punto è l'HD interno l'hai controllato?

[Giulio_P]

ma si certo, piu' volte e con diversi programmi.
andando su internet trovo che e' un problema di driver, ma vorrei sapere quali... forse scheda madre? bios? controller usb?

[Eress]

Magari il controller sata.....

[Giulio_P]

Originariamente inviato da Eress

Magari il controller sata.....

eh cosa bisogna fare per quello`?

[Eress]

Devi cercare il driver aggiornato

[Giulio_P]

Originariamente inviato da Eress

Devi cercare il driver aggiornato

eh na parola....

[lcpreben]

Salve a tutti, ogni volta che gioco ad Alan Wake mi crasha tutto, ma non capisco l'origine del problema. Il PC + a frequenze standard.

072912-19921-01.dmp 29/07/2012 18:02:38 0x00000124 00000000`00000000 fffffa80`04e7f6f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a4f4c NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.17017 (win7_gdr.120503-2030) x64 ntoskrnl.exe+4a4f4c C:\Windows\Minidump\072912-19921-01.dmp 4 15 7600 262.144

A cosa corrisponde quel "ntoskrnl.exe+4a4f4c"?

[Eress]

Dovresti iniziare aggiornando o cambiando driver video. Poi dai anche una controllata alla ram

[lcpreben]

Originariamente inviato da Eress

Dovresti iniziare aggiornando o cambiando driver video. Poi dai anche una controllata alla ram

Il driver video è l'ultimo, aggiornato poco tempo fa.
Per la RAM avevo fatto un Memtest, non c'erano problemi...

[Eress]

Se col vecchio driver non avevi sti problemi, rimettilo subito

[Jeremy01]

3 BSOD durante vari giochi nel giro di una settimana: mi aiutate a trovare la causa?
(p.s. mem ok oc rock solid da un anno e ritestato)

BSOD 1

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


Loading Dump File [C:\Windows\Minidump\072212-14757-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`04405000 PsLoadedModuleList = 0xfffff800`04649670
Debug session time: Sun Jul 22 16:02:55.437 2012 (UTC + 2:00)
System Uptime: 0 days 4:38:39.361
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff8000448f257}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+b7 )

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: 0000000000000000, 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: fffff8000448f257, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046b3100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+b7
fffff800`0448f257 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=0000000000014ad9
rdx=fffffa8003dc6620 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000448f257 rsp=fffff80000b9c560 rbp=0000000000000000
 r8=fffffa800aca0780  r9=0000000000000083 r10=fffff800045f6e80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertTimerTable+0xb7:
fffff800`0448f257 488b4500        mov     rax,qword ptr [rbp] ss:0018:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004483769 to fffff800044841c0

STACK_TEXT:  
fffff800`00b9c288 fffff800`04483769 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c290 fffff800`044823e0 : fffff800`00b9cc58 00000000`00000000 fffffa80`0967b402 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c3d0 fffff800`0448f257 : ffffffff`fffe7960 fffff800`0448ee3c fffff800`00b9c600 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c560 00000000`00000000 : fffff800`00b9c608 00000000`00000002 00000000`00105a83 fffff800`0448ec7d : nt!KiInsertTimerTable+0xb7


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+b7
fffff800`0448f257 488b4500        mov     rax,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+b7

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+b7

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

BSOD 2

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


Loading Dump File [C:\Windows\Minidump\072412-14133-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0440e000 PsLoadedModuleList = 0xfffff800`04652670
Debug session time: Tue Jul 24 21:23:26.498 2012 (UTC + 2:00)
System Uptime: 0 days 3:11:01.715
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, fffff80004494f0b}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )

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: 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: fffff80004494f0b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046bc100
 0000000000000024 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+22b
fffff800`04494f0b 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:  fffff80000b9c350 -- (.trap 0xfffff80000b9c350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004494f0b rsp=fffff80000b9c4e8 rbp=fffff8800c956a58
 r8=fffff80004602001  r9=0000000000000003 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`04494f0b 418b4624        mov     eax,dword ptr [r14+24h] ds:0001:00000000`00000024=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000448c769 to fffff8000448d1c0

STACK_TEXT:  
fffff800`00b9c208 fffff800`0448c769 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c210 fffff800`0448b3e0 : fffff800`045ffe80 fffffa80`03d02278 fffff800`0462a2e0 fffff880`0c956a58 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c350 fffff800`04494f0b : fffff800`045ffe80 fffff800`0460dcc0 fffff800`00b9cc58 00000000`00000002 : nt!KiPageFault+0x260
fffff800`00b9c4e8 fffff800`00b9c600 : fffff880`0c956a50 fffff800`00b9c600 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x22b
fffff800`00b9c568 fffff880`0c956a50 : fffff800`00b9c600 00000000`00000000 00000000`00000000 00000000`00000009 : 0xfffff800`00b9c600
fffff800`00b9c570 fffff800`00b9c600 : 00000000`00000000 00000000`00000000 00000000`00000009 00000000`00000000 : 0xfffff880`0c956a50
fffff800`00b9c578 00000000`00000000 : 00000000`00000000 00000000`00000009 00000000`00000000 00000000`0000000f : 0xfffff800`00b9c600


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+22b
fffff800`04494f0b 418b4624        mov     eax,dword ptr [r14+24h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+22b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

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

BSOD 3

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


Loading Dump File [C:\Windows\Minidump\080112-16504-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`04451000 PsLoadedModuleList = 0xfffff800`04695670
Debug session time: Wed Aug  1 18:04:43.432 2012 (UTC + 2:00)
System Uptime: 0 days 2:50:58.650
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, fffff800044d7f0b}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Dispatch+1dc )

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: fffff800044d7f0b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046ff100
 0000000000000024 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+22b
fffff800`044d7f0b 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:  fffff8800351b350 -- (.trap 0xfffff8800351b350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003d0b210 rbx=0000000000000000 rcx=fffffa8009602210
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800044d7f0b rsp=fffff8800351b4e8 rbp=fffffa800b2fe758
 r8=fffff880009f4301  r9=0000000000000002 r10=00000000000000c1
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`044d7f0b 418b4624        mov     eax,dword ptr [r14+24h] ds:00000000`00000024=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800044cf769 to fffff800044d01c0

STACK_TEXT:  
fffff880`0351b208 fffff800`044cf769 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0351b210 fffff800`044ce3e0 : fffffa80`074491a0 fffff880`05da1f99 fffffa80`0ab88450 fffffa80`0b2fe758 : nt!KiBugCheckDispatch+0x69
fffff880`0351b350 fffff800`044d7f0b : fffffa80`079471a0 00000000`00000009 00000000`0000001b fffffa80`040299f0 : nt!KiPageFault+0x260
fffff880`0351b4e8 fffffa80`0a09d340 : fffffa80`0b2fe750 fffffa80`0946e200 fffff880`05da0af4 00000000`00000102 : nt!KiTimerWaitTest+0x22b
fffff880`0351b568 fffffa80`0b2fe750 : fffffa80`0946e200 fffff880`05da0af4 00000000`00000102 00000000`00000004 : 0xfffffa80`0a09d340
fffff880`0351b570 fffffa80`0946e200 : fffff880`05da0af4 00000000`00000102 00000000`00000004 fffffa80`094431b0 : 0xfffffa80`0b2fe750
fffff880`0351b578 fffff880`05da0af4 : 00000000`00000102 00000000`00000004 fffffa80`094431b0 fffffa80`09443680 : 0xfffffa80`0946e200
fffff880`0351b580 00000000`00000000 : fffff880`0351b608 00000000`00000002 00000000`000a08c1 fffff800`044dac7d : USBPORT!USBPORT_Dispatch+0x1dc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Dispatch+1dc
fffff880`05da0af4 eb6d            jmp     USBPORT!USBPORT_Dispatch+0x24b (fffff880`05da0b63)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  USBPORT!USBPORT_Dispatch+1dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Dispatch+1dc

BUCKET_ID:  X64_0xA_USBPORT!USBPORT_Dispatch+1dc

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

[Eress]

Difficile, potrebbe essere un problema HW, comunque dal secondo problema con usbport.sys se hai qualcosa usb collegato mentre giochi, scollegalo

[Jeremy01]

Originariamente inviato da Eress

Difficile, potrebbe essere un problema HW, comunque dal secondo problema con usbport.sys se hai qualcosa usb collegato mentre giochi, scollegalo

ho provato a lasciare solo il mouse e la tastiera ma mi è ricapitato