PDA

View Full Version : ERRORE SCHERMATA BLU


mouse200
22-09-2011, 23:45
Salve, ho un comune (almeno credo) problema con il nuovo pc.
la configurazione è questa:

Masterizzatore Interno Blu-Ray LG BH10LS30 10x BR/DVD/CD Sata Bulk nero

Monitor 3D Lcd 23" Asus VG236HE FullHD 100000:1 400cd/m² 2ms HDMI DVI Nero + Nvidia 3d kit

Tastiera wireless Logitech Keyboard K350 Nero

Hard Disk Interno Western Digital Caviar Blue 500GB 3.5" 7200rpm 16MB SATA3 WD5000AAKX

RAM DDR3 Corsair Vengeance CMZ8GX3M2A1600C9 1600MHz 8GB (2x4GB) CL9

CPU Intel Core i5-2500K 3.30GHz Socket 1155 95W con GPU Sandy Bridge Boxed BX80623I52500K

Alimentatore PC Corsair Enthusiast Series TX650 V2 650W 80Plus Bronze

Dissipatore CPU Arctic Cooling Freezer 13 Socket Intel Amd

Case Midi Cooler Master CM 690 II Advanced Nvidia Edition ATX Nero

SSD Crucial RealSSD M4 64GB 2.5" Lettura 415MB/s Scrittura 95MB/s Sata3 CT064M4SSD2

VGA Asus GeForce ENGTX580 DCII/2DIS/1536MD5 GTX 580 Core 782MHz Memory GDDR5 4008MHz 1536MB 2xDVI-I HDMI DisplayPort

Scheda Madre Gigabyte GA-Z68X-UD3H-B3 rev. 1.0 Socket 1155 Intel Z68 DDR3 SATA3 USB3 ATX


Il problema è la solita schermata blu di errore che compare ormai non troppo raramente.
C'è poco da fare o in qualche modo si può risolvere?

Test con WhoCrashed.

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8572231680 total
VM: 2147352576, free: 1978830848



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 22/09/2011 17:54:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092211-8517-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0xD400)
Bugcheck code: 0xD1 (0xFFFFFA804F877254, 0x2, 0x1, 0xFFFFF88001558400)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 15/09/2011 19:16:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-5428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0xC84784B7, 0x2, 0x0, 0xFFFFF8800165F418)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 15/09/2011 16:10:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-5444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFF9004978FAE4, 0x1, 0xFFFFF800032D8530, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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.


On Sun 11/09/2011 16:15:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091111-6832-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0xFFFFF880062A500E, 0x2, 0x0, 0xFFFFF8800FFADD33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 02/08/2011 00:08:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080211-7098-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1796E8)
Bugcheck code: 0x116 (0xFFFFFA800905C010, 0xFFFFF8801003A6E8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 280.26
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 280.26
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR

Il mio pc deve stare acceso per ore e ore intere, ma purtroppo mentre gioco o faccio qualcos'altro, mi succede questa fastidiosissima cosa.
A volte capita 2-3 volte nel giro di qualche minuto, a volte invece sta buono per ore intere, ma diciamo che la media è di 1-2 volte al giorno.

A voi esperti! io c'ho capito poco e niente >_<

p.s. : mi scuso se ho sbagliato sezione.

sirHydra
23-09-2011, 00:13
Per caso stai utilizzando zonealarm?

mouse200
23-09-2011, 00:26
no , non so nemmeno cosa sia

Mister D
23-09-2011, 20:37
Ciao,
sono tutti errori tipici di quando si overclocca il fsb per aumentare la frequenza della ram o solo del procio. Se invece hai tutto a default allora il problema potrebbe essere un modulo di ram fallato. Provane uno alla volta con memtest. Alcune schede madri hanno un opzione del bios per attivare il memtest all'avvio. Se non ce l'hai scarica le versione per il windows e prova. Almeno possiamo escludere problemi sulle ram se dovesse superare il test.