PROBLEMA NTOSKRNL.EXE provoca schermate blu continue

[Astonishing95]

Come da titolo sto impazzendo perchè il computer mi crasha in continuazione e ogni volta con un errore diverso. Vi allego la schermata di BlueScreenView:

Premetto che non ci capisco niente e chiedo aiuto a qualcuno più esperto in grado di risolvermi il problema.
Grazie mille.

 

[Il cecchino Jackson]

Re: NTOSKRNL.EXE prova schermate blu continue

Posta il log di whocrashed come da regole di sezione

 

[Astonishing95]

Re: NTOSKRNL.EXE prova schermate blu continue

Posta il log di whocrashed come da regole di sezione

Si scusatemi. Ecco quì:

[FONT=Segoe UI, Arial]System Information (local)

---

[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-V1FQ3EM
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASRock, H170 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8521752576 bytes total


[/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 Sat 14/05/2016 09:07:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051416-5250-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF7 (0x2A8046702960, 0xF250ED31C428, 0xFFFF0DAF12CE3BD7, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_OVERRAN_STACK_BUFFER[/FONT]
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 Sat 14/05/2016 09:07:07 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: 0xF7 (0x2A8046702960, 0xF250ED31C428, 0xFFFF0DAF12CE3BD7, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_OVERRAN_STACK_BUFFER[/FONT]
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 12/05/2016 21:37:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051216-4390-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32kfull.sys[/FONT] (win32kfull!DeleteProperties+0x75)
Bugcheck code: 0x13A (0x6, 0xFFFFF90140800000, 0xFFFFF9014083B540, 0x0)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]
file path: C:\Windows\system32\win32kfull.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Full/Desktop Win32k Kernel Driver
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 Mon 09/05/2016 10:59:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050916-4218-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x234C6D, 0x3, 0x1B508F)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 08/05/2016 17:56:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-4593-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]aswsp.sys[/FONT] (aswSP+0x13438)
Bugcheck code: 0x4E (0x99, 0x212879, 0x2, 0x4000260002612FA)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\drivers\aswsp.sys
product: [FONT=Segoe UI, Arial]Avast Antivirus [/FONT]
company: [FONT=Segoe UI, Arial]AVAST Software[/FONT]
description: avast! self protection module
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: [FONT=Segoe UI, Arial]AVAST Software PFN_LIST_CORRUPT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sun 08/05/2016 17:38:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-4812-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (NTFS!NtfsCopyReadA+0x217)
Bugcheck code: 0x4E (0x99, 0x9EE6, 0x2, 0xE00000000008212)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver file system NT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 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 Sun 08/05/2016 14:40:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050816-4593-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (NTFS!NtfsAcquireExclusiveFcb+0x78)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80310ED2D40, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver file system NT
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 Sat 07/05/2016 07:59:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050716-5265-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF7 (0x2A81C9A458B0, 0x7FA2DA517815, 0xFFFF805D25AE87EA, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_OVERRAN_STACK_BUFFER[/FONT]
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 05/05/2016 23:13:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050616-4593-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!MiDemoteCombinedPte+0x39)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801F43A773D, 0xFFFFD0010AB23098, 0xFFFFD0010AB228B0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
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 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 05/05/2016 12:02:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050516-5156-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x246855, 0x2, 0x800020000205DD4)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]

---

Conclusion

---

[/FONT]
[FONT=Segoe UI, Arial]14 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]iastora.sys (Intel(R) Rapid Storage Technology driver - x64, Intel Corporation)[/FONT]
[FONT=Segoe UI, Arial]aswsp.sys (avast! self protection module, AVAST Software)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Disinstallo avast e installo i driver di rapid storage?? Ma quali visto che ce ne sono 5 per windows 10 sul sito della intel??

[/FONT]

 

[Il cecchino Jackson]

Re: NTOSKRNL.EXE prova schermate blu continue

mah.. driver bug.. prova ad aggiornare i drivers con driver booster 3. se ti crasha di continuo, peggio non può andare

- - - Updated - - -

fa tutto driver booster 3,basta che lo lanci e non installi le cose pubblicitarie

- - - Updated - - -

eh avast se non lo hao pagato toglilo, che ,non so se li ha rissolti, ma tempo fa era totalmente incompatibile con w10

- - - Updated - - -

anzi togliolo anche se lo hao pagato se vuoi usare il pc.
usa defender già integrato

 

[Astonishing95]

Re: NTOSKRNL.EXE prova schermate blu continue

mah.. driver bug.. prova ad aggiornare i drivers con driver booster 3. se ti crasha di continuo, peggio non può andare

- - - Updated - - -

fa tutto driver booster 3,basta che lo lanci e non installi le cose pubblicitarie

- - - Updated - - -

eh avast se non lo hao pagato toglilo, che ,non so se li ha rissolti, ma tempo fa era totalmente incompatibile con w10

- - - Updated - - -

anzi togliolo anche se lo hao pagato se vuoi usare il pc.
usa defender già integrato

Avevo già tutti i driver aggiornati... ho scaricato intel rapide storage come mi consigliava di fare WhoCrashed e quando è partita l'installazione è uscito scritto che sul pc c'era già una versione più aggiornata... come è possibile visto che sul sito della Intel quella era la più recente?? Quella che c'era l'avevo scaricata dal sito dell'AsRock...
Comunque ho disinstallato per bene avast e ho installato Avira... vediamo un pò se continuano sti crash...

 

[Il cecchino Jackson]

Re: NTOSKRNL.EXE prova schermate blu continue

no non mettere nessun av ( a parte il già integrato defender )e vedi se i crash finisocno. c'è molta disinformazione attorno a defneder su w10.

 

[deadman]

Re: NTOSKRNL.EXE prova schermate blu continue

Io ho risolto quel crash del ntoskernel solo formattando windows , anche perché non avevo av esterni...

Inviato dal mio LG-D802 utilizzando Tapatalk

 

[Astonishing95]

Re: NTOSKRNL.EXE prova schermate blu continue

Ragazzi sembrava tutto risolto invece proprio stamattina altro BSOD... quando è avvenuto stavo scambiando file dal pc all'hard disk esterno e avevo pagine internet aperte e torrent in esecuzione. In più ho attaccato delle casse audio della LinQ comprate dai cinesi che avevo staccato da un pò di giorni perchè pensavo fossero loro a causare il crash, è possibile? C'è da dire che ho avuto BSOD anche quando le casse le avevo staccate...

On Mon 16/05/2016 06:39:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051616-4578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x6F5EC, 0x0, 0x4000000002029EC)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.

 

[Il cecchino Jackson]

Re: NTOSKRNL.EXE prova schermate blu continue

Ragazzi sembrava tutto risolto invece proprio stamattina altro BSOD... quando è avvenuto stavo scambiando file dal pc all'hard disk esterno e avevo pagine internet aperte e torrent in esecuzione. In più ho attaccato delle casse audio della LinQ comprate dai cinesi che avevo staccato da un pò di giorni perchè pensavo fossero loro a causare il crash, è possibile? C'è da dire che ho avuto BSOD anche quando le casse le avevo staccate...

On Mon 16/05/2016 06:39:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051616-4578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x6F5EC, 0x0, 0x4000000002029EC)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.

L'utente su ti ha detto che ha risolto solo formattando . Se non mi confondo mi pare che il suo thread fosse abbastanza lungo, ne aveva provate tante prima

 

[Federico83]

Re: NTOSKRNL.EXE prova schermate blu continue

Ragazzi sembrava tutto risolto invece proprio stamattina altro BSOD... quando è avvenuto stavo scambiando file dal pc all'hard disk esterno e avevo pagine internet aperte e torrent in esecuzione. In più ho attaccato delle casse audio della LinQ comprate dai cinesi che avevo staccato da un pò di giorni perchè pensavo fossero loro a causare il crash, è possibile? C'è da dire che ho avuto BSOD anche quando le casse le avevo staccate...

On Mon 16/05/2016 06:39:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051616-4578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x6F5EC, 0x0, 0x4000000002029EC)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.

prova a seguire i consigli qui http://www.tomshw.it/forum/windows/573144-avvio-pulito-per-windows-8-8-1-10-a.html