crash pc e riavvio

aug90

Utente Attivo
284
16
CPU
Intel Core i5 4690 @ 3.50GHz
Dissipatore
stock
Scheda Madre
ASRock H97 Pro4
HDD
Samsung SSD 850 EVO 500GB + Western Digital WDC WD5000AAKS-00A7B2
RAM
8,00GB Dual-Channel DDR3 @ 798MHz
GPU
3072MB ATI AMD Radeon R9 280
Audio
INTEGRATA
Monitor
Sync Master BX2331
PSU
650w
Case
zalman
OS
Windows 10 Pro 64-bit
[FONT=Segoe UI, Arial]Salve ragazzi..
I consigli sono bene accetti :)

Da un po di tempo il pc inizia a fare il furbetto, prima durante il normale utilizzo e ora solo ed esclusivamente mentre gioco a GW2.
Mi spiego meglio: tempo fa il pc andava in crash totalmente random, mentre si accendeva, mentre scrivevo su word, mentre navigavo su internet ecc.

Ora invece va in crash solo ed esclusivamente con guild wars 2.

Ho appena aggiornato i driver della scheda video (geforce 550ti).

Non credo sia un problema di SO perchè lo faceva prima con win7 e con linux e lo fa ancora con win8.

La temperatura della scheda video raggiunge gli 88°C mentre gioco ma non penso sia colpa sua in quanto anche con altri giochi raggiunge queste temperature e non succede nulla.

sto scaricando memtest86 anche se con il tool integrato di windows non ho trovato problemi alla ram.

[/FONT][FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]computer name: MATTEO-PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Phenom(tm) 9950 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4293382144 total
VM: 2147352576, free: 1926987776


[/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]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 06/01/2013 19.54.24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010613-23790-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0xA (0xFFFFF88002CD44B8, 0x2, 0x0, 0xFFFFF801B592084E)
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 06/01/2013 19.54.24 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ndis.sys[/FONT] (ndis!NdisGroupActiveProcessorCount+0x205)
Bugcheck code: 0xA (0xFFFFF88002CD44B8, 0x2, 0x0, 0xFFFFF801B592084E)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver NDIS 6.30
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 03/01/2013 20.43.14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010313-12495-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0xA (0x30D8B, 0xD, 0x0, 0xFFFFF8027C6C2002)
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 03/01/2013 19.50.14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010313-19359-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x38479)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007CA2479, 0xFFFFF8800A849588, 0xFFFFF8800A848DC0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 03/01/2013 10.47.11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010313-18330-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]netio.sys[/FONT] (NETIO+0x5E11)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88001771E11, 0xFFFFF88012274548, 0xFFFFF88012273D80)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\WINDOWS\system32\drivers\netio.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 01/01/2013 19.32.13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010113-12355-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x1A (0x41284, 0x5DAF7001, 0x2F8F1, 0xFFFFF70001080000)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/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 a severe memory management error occurred.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 31/12/2012 16.40.36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\123112-12370-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (0xFFFFF88007C4B661)
Bugcheck code: 0x50 (0xFFFFF8A00A20DA50, 0x0, 0xFFFFF88007C4B661, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 29/12/2012 18.00.20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122912-12542-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8023AD9B13D, 0xFFFFF8800FE1AD20, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 28/12/2012 20.06.51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122812-12526-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0xA (0x7, 0x2, 0x1, 0xFFFFF8034B090832)
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 28/12/2012 18.38.56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122812-20061-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A00134A700, 0xFFFFF8A00CE81CB1, 0x31D0D8C0)
Error: [FONT=Segoe UI, Arial]POOL_CORRUPTION_IN_FILE_AREA[/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 a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 28/12/2012 12.56.06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122812-12776-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0xD1 (0xFFFFF10009EC6C40, 0x2, 0x1, 0xFFFFFA8003C28FF9)
Error: [FONT=Segoe UI, Arial]DRIVER_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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 27/12/2012 23.52.13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122812-16879-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFFA8004EAB8CB)
Error: [FONT=Segoe UI, Arial]DRIVER_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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 27/12/2012 21.59.09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122712-17284-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x139 (0x3, 0xFFFFF88002AFF650, 0xFFFFF88002AFF5A8, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_SECURITY_CHECK_FAILURE[/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: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 27/12/2012 18.17.50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122712-20326-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (0xFFFFF88007C83661)
Bugcheck code: 0x50 (0xFFFFF8A006E16110, 0x0, 0xFFFFF88007C83661, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 27/12/2012 10.13.48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122712-28048-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x1A (0x41287, 0x12132, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/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 a severe memory management error occurred.
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 that cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]


consigli?
grazie
[/FONT]
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,207
6,218
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
se avevi anche problemi con linux allora credo proprio sia un difetto hardware. Magari potrebbe essere il controller della ram... è pulito lo slot?
 

Entra

oppure Accedi utilizzando

Hot: E3 2021, chi ti è piaciuto di più?

  • Ubisoft

    Voti: 15 16.5%
  • Gearbox

    Voti: 1 1.1%
  • Xbox & Bethesda

    Voti: 65 71.4%
  • Square Enix

    Voti: 3 3.3%
  • Capcom

    Voti: 5 5.5%
  • Nintendo

    Voti: 14 15.4%
  • Altro (Specificare)

    Voti: 8 8.8%

Discussioni Simili