Blue screen Windows Vista 64 con rendering

Pubblicità
P

Pandorino

Utente Attivo
Messaggi
20
Reazioni
0
Punteggio
25
Salve,
da un mesetto circa il pc va in crash quando è in esecuzione un programma di rendering. Il pc ha quasi 2 anni ed è sempre stato piuttosto "stabile".
Non saprei se e come associare i crash a modifiche del software (driver, nuovi programmi...) ma ho utilizzato WhoCrashed per analizzare le possibile cause.
Thk
Allego il file dell'analisi

[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: PC-PC
windows version: Windows Vista Service Pack 1, 6.0, build: 6001
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6439911424 total
VM: 2147352576, free: 1999994880
[/FONT]

[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Sun 01/05/2011 12.48.45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050111-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x55410)
Bugcheck code: 0xA (0xFFFFFA60205EC7F8, 0xC, 0x0, 0xFFFFF800020C04E8)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 01/05/2011 12.48.45 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA60205EC7F8, 0xC, 0x0, 0xFFFFF800020C04E8)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 30/04/2011 10.17.54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini043011-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x55410)
Bugcheck code: 0xA (0xFFFFFA60218AF7F8, 0xC, 0x0, 0xFFFFF800020B12CD)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 29/04/2011 18.46.20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042911-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x55410)
Bugcheck code: 0xA (0xFFFFFA60205EC7F8, 0xC, 0x0, 0xFFFFF8000207C771)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 27/04/2011 7.29.25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042711-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x55410)
Bugcheck code: 0xC5 (0xFFFFF800221A5228, 0x2, 0x0, 0xFFFFF80002145363)
Error: [FONT=Segoe UI, Arial]DRIVER_CORRUPTED_EXPOOL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 14/04/2011 16.54.09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini041411-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x55410)
Bugcheck code: 0xA (0xFFFFFA8100000155, 0xC, 0x0, 0xFFFFF8000206CF72)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]
 
Ciao,
ho provato a risolvere il problema seguendo il primo suggerimento, ma arrivava puntuale il blue screen, poi... mi sono accorto per caso :blush: che non non avevo ancora installato il Service Pack 2 di Vista. Ho lasciato passare un po' di tempo per verificare la stabilità e sembra che sia tornato tutto a posto. Speriamo...
 
Ciao,
"a volte ritornano"!
Dopo circa sette mesi riecco i crash.
==================================================
Dump File : Mini122711-02.dmp
Crash Time : 27/12/2011 11.15.29
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff960`20245e5e
Parameter 2 : 00000000`00000008
Parameter 3 : fffff960`20245e5e
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122711-02.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================

==================================================
Dump File : Mini122711-01.dmp
Crash Time : 27/12/2011 10.48.45
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa80`2517b3c0
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`0274e44b
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122711-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================

==================================================
Dump File : Mini120511-02.dmp
Crash Time : 05/12/2011 17.13.23
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff800`226c1c7f
Parameter 2 : 00000000`0000000c
Parameter 3 : 00000000`00000008
Parameter 4 : fffff800`226c1c7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120511-02.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================

==================================================
Dump File : Mini120511-01.dmp
Crash Time : 05/12/2011 11.46.25
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`201a560c
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`028c839a
Parameter 4 : 00000000`00000000
Caused By Driver : HIDPARSE.SYS
Caused By Address : HIDPARSE.SYS+aa81040
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120511-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================

==================================================
Dump File : Mini120111-01.dmp
Crash Time : 01/12/2011 19.00.58
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff960`20351910
Parameter 2 : 00000000`00000001
Parameter 3 : fffff960`0018b0b3
Parameter 4 : 00000000`00000002
Caused By Driver : Msfs.SYS
Caused By Address : Msfs.SYS+6fabd40
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini120111-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================

Cosa posso fare?
Thk
 
controlla la ram con memtest86+ scarica la iso e mettila su cd o su pen e fai girare prima con tutti i banchi poi a banchi alterni per trovare il colpevole

---------- Post added at 12:33 ---------- Previous post was at 12:29 ----------

P.s. gli stop sono sempre gli stessi quindi potresti avere un banco di ram che fa come gli pare
 
Ciao
ho controllato la ram con Memtest86+, facendogli fare 11 passaggi a tutti i banchi insieme: non ha trovato errori.
Scusa, quando dici di far girare a banchi alterni, intendi uno alla volta tolti tutti gli altri o che devo toglierne uno e lasciare gli altri due per il test (ne ho tre in totale)?
 
Ciao
non ho ancora avuto modo di testare i banchi di ram singolarmente, nel frattempo ecco un altro crash
==================================================
Dump File : Mini122911-01.dmp
Crash Time : 29/12/2011 13.17.10
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff800`22673c7f
Parameter 2 : 00000000`0000000c
Parameter 3 : 00000000`00000008
Parameter 4 : fffff800`22673c7f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122911-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================
 
guarda leggendo un pò qua e un pò la su forum stranieri consigliano una passata di hdtune fare una scansione per verificare se vi fossero cluster danneggiati. Altra cosa che potresti fare è disabilitare temporaneamente il file di paging prova a seguire questa guida e vedi se si ripresenta l'errore 2 o piu’ Gb di RAM? Disabilitare la Memoria Virtuale in Vista – Disable Pagefile Virtual Memory | FAQ WINDOWS
per quanto riguarda hd tune non fare il quick scan ma uno scan completo
hd-tune-9.jpg
Clicca per espandere...
 
Ciao
grazie innanzitutto per gli aiuti.
Ho testato singolarmente i banchi ram e Memtest non mi ha dato errori.
Ho fatto la scansione completa con HdTune ed è tutto ok.
Prima di provare a disabilitare la memoria virtuale volevo sapere se questo produce un calo nei tempi di renderizzazione (che tra l'altro è la fase in cui si presentano i crash).
 
Buon Anno!
Purtroppo per il mio pc l'anno è iniziato proprio male...
Questa mattina sono arrivati implacabili altri due crash.
Questo è il secondo, del primo non ho il file dump perchè, con il file paging disabilitato, non ne è rimasta traccia.

==================================================
Dump File : Mini010212-01.dmp
Crash Time : 02/01/2012 11.00.43
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`20000d80
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`02750470
Parameter 4 : 00000000`00000002
Caused By Driver : Fs_Rec.SYS
Caused By Address : Fs_Rec.SYS+3838110
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini010212-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 300.652
==================================================
 
Non potrebbe essere un problema legato alle temperature? Dato che succede in fase di rendering io un'occhiata all'hardware la darei.
 
Pubblicità
Pubblicità
Indietro
Top