PROBLEMA computer si riavvia da solo/bsod

misakabestgirl

Nuovo Utente
27
0
buona sera, ho comprato un nuovo computer con windows 10 circa a febbraio e di recente ha iniziato a presentare problemi: si è iniziato a riavviare da solo senza apparente motivo e con la comparsa di bsod con le seguenti tre scritte alternate: IRQL_NOT_LESS_OR_EQUAL KMODE_EXCEPTION_NOT_HANDLEDATTEMPTED_EXECUTE_OF_NO-EXECUTE_MEMORY. Ho provato ad aggiornare tutti i driver ma il problema sembra persistere. Qualcuno saprebbe darmi delle idee su come risolvere? Metto in allegato il registro eventi completo da febbraio, non so dipreciso le date o ore dei crash se non gli ultimi 2, avvenuti oggi: il primo alle 18:34 e il secondo poco dopo; subito dopo il primo crash windows si è aggiornato da solo(lo menziono per sicurezza). Grazie in anticipo c:
http://puu.sh/qyWF4/11133b87a8.evtx
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
buona sera, ho comprato un nuovo computer con windows 10 circa a febbraio e di recente ha iniziato a presentare problemi: si è iniziato a riavviare da solo senza apparente motivo e con la comparsa di bsod con le seguenti tre scritte alternate: IRQL_NOT_LESS_OR_EQUAL KMODE_EXCEPTION_NOT_HANDLEDATTEMPTED_EXECUTE_OF_NO-EXECUTE_MEMORY. Ho provato ad aggiornare tutti i driver ma il problema sembra persistere. Qualcuno saprebbe darmi delle idee su come risolvere? Metto in allegato il registro eventi completo da febbraio, non so dipreciso le date o ore dei crash se non gli ultimi 2, avvenuti oggi: il primo alle 18:34 e il secondo poco dopo; subito dopo il primo crash windows si è aggiornato da solo(lo menziono per sicurezza). Grazie in anticipo c:
http://puu.sh/qyWF4/11133b87a8.evtx

scarica whocrashed se puoi accedere al sistema e riporta qui il report
 
  • Mi piace
Reazioni: misakabestgirl

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
  • Mi piace
Reazioni: misakabestgirl

misakabestgirl

Nuovo Utente
27
0
fai un memtest scarica l'occorrente da qui MemTest86 - Offical Site of the x86 Memory Testing Tool e fai delle sessioni lunghe di prova
ok, ho fatto partire, lascio andare tutta sera e domani controllo se sono presenti errori o se, eventualmente, si è riavviato il pc durante il test

- - - Updated - - -

fai un memtest scarica l'occorrente da qui MemTest86 - Offical Site of the x86 Memory Testing Tool e fai delle sessioni lunghe di prova
photo_2016-08-14_13-59-34.jpg Questo è il risultato, lo ho fatto partire prima di andare a letto e quando mi son svegliato era così
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
ok, ho fatto partire, lascio andare tutta sera e domani controllo se sono presenti errori o se, eventualmente, si è riavviato il pc durante il test

- - - Updated - - -


Visualizza allegato 213724 Questo è il risultato, lo ho fatto partire prima di andare a letto e quando mi son svegliato era così

controlla tutti i driver di sistema con driverbooster3
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro

misakabestgirl

Nuovo Utente
27
0
c'è qualche driver buggato

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557408(v=vs.85).aspx

sempre whocrashed riporta il dmp facendo copia e incolla qui del report
@Federico83


On Sun 14/08/2016 18:34:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-11906-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF800B02A481A)
Error: 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 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.






On Sun 14/08/2016 18:34:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF800B02A481A)
Error: IRQL_NOT_LESS_OR_EQUAL
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.






On Sun 14/08/2016 18:14:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-14093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF801E689381A)
Error: 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 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.






On Sun 14/08/2016 16:57:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-17375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF8000851181A)
Error: 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 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.






On Sun 14/08/2016 16:50:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-13687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8005434B309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sun 14/08/2016 16:28:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-10984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80035D43309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sun 14/08/2016 15:56:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-11906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF802CEA9F81A)
Error: 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 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.






On Sun 14/08/2016 15:33:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-12000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80247EDA309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sun 14/08/2016 15:28:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-15437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803F80DD309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sat 13/08/2016 17:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081316-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF8030831881A)
Error: 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 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.
 
Ultima modifica:

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
@Federico83


On Sun 14/08/2016 18:34:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-11906-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF800B02A481A)
Error: 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 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.






On Sun 14/08/2016 18:34:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF800B02A481A)
Error: IRQL_NOT_LESS_OR_EQUAL
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.






On Sun 14/08/2016 18:14:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-14093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF801E689381A)
Error: 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 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.






On Sun 14/08/2016 16:57:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-17375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF8000851181A)
Error: 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 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.






On Sun 14/08/2016 16:50:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-13687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8005434B309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sun 14/08/2016 16:28:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-10984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80035D43309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sun 14/08/2016 15:56:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-11906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF802CEA9F81A)
Error: 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 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.






On Sun 14/08/2016 15:33:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-12000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80247EDA309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sun 14/08/2016 15:28:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081416-15437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803F80DD309, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Sat 13/08/2016 17:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081316-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF8030831881A)
Error: 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 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.

controlla lo stato del disco con crystal disck vediamo se è a rischio o se ci sono settori danneggiati.

posta tutto l'hardware connesso al pc compreso di periferiche usb
 

misakabestgirl

Nuovo Utente
27
0
controlla lo stato del disco con crystal disck vediamo se è a rischio o se ci sono settori danneggiati.

posta tutto l'hardware connesso al pc compreso di periferiche usb
@Federico83
posto i dispositivi e uno screenshot dei valori che mi dava crsystal disk. I valori di crystal disk son rimasti questi anche dopo varie volte che mi si è riavviato il pc photo_2016-08-16_16-58-45.jpg photo_2016-08-16_16-58-58.jpg photo_2016-08-16_16-59-08.jpg
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro

misakabestgirl

Nuovo Utente
27
0
@Federico83 Scusa per l'attesa, tra un impegno e l'altro non ho avuto molte occasioni di accendere il pc e mi ero completamente scordato di rispondere... Comunque pure con il pad staccato il pc crasha e ho fatto crystal disk info e questo è il risultato photo_2016-08-21_18-59-28.jpg
 

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!