PROBLEMA windows 7 professional e bluescreen a raffica con diversi codici errore

vincenzo21

Nuovo Utente
4
0
ciao,
da qualche tempo ho problemi con il maledettissimo bluescreen of death.ho da poco aggiornato il sistema operativo passando dal caro vecchio windows xp professional 32bit che non ha mai dato problemi ne bluescreen a windows 7 professional 64bit.ovviamente la cpu è 64 bit .
da quando lo installato a ogni avvio,o appena carica windows o mentre lavoro col pc all'improvviso si manifesta quel maledetto bluescreen of death e ad ogni sua nuova manifestazione ha un diverso codice di errore,mai lo stesso.ho provato a formattare tutto e reinstallare windows e tutti i programmi da capo diverse volte ma si ripresenta sempre.ho installato who crasched per tentare di capirci qualcosa ma non ci capisco niente.
vi posto i risultati degli ultimi crash e relativo hw del pc,sperando possiate aiutarmi:
[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]Computer name: FERROVECCHIOPC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASRock, G41C-GS
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294008832 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]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 08/01/2016 10:18:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010816-19812-01.dmp
uptime: (unknown)
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Fri 08/01/2016 10:17:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:11:26
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr!FltpDispatch+0xD9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880010036E9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Gestione filtri file system Microsoft
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 Fri 08/01/2016 10:05:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010816-19171-01.dmp
uptime: 00:14:27
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x7A8003A13090, 0x2, 0x0, 0xFFFFF80002D01424)
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 07/01/2016 22:45:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010816-19906-01.dmp
uptime: 03:23:27
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (0xFFFFF88001073C11)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001073C11, 0xFFFFF88008397BA0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Gestione filtri file system Microsoft
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 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 07/01/2016 18:26:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-29265-01.dmp
uptime: 09:01:51
This was probably caused by the following module: [FONT=Segoe UI, Arial]aswmonflt.sys[/FONT] (aswMonFlt+0x4609)
Bugcheck code: 0x1A (0x5002, 0xFFFFF781C0000000, 0x53F, 0x8800053CFFFFFFFE)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: [FONT=Segoe UI, Arial]Avast Antivirus [/FONT]
company: [FONT=Segoe UI, Arial]AVAST Software[/FONT]
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: [FONT=Segoe UI, Arial]AVAST Software MEMORY_MANAGEMENT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 07/01/2016 09:24:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-19765-01.dmp
uptime: 00:06:56
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs! ?? ::FNODOBFM::`string'+0x2B49)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880082D72B8, 0xFFFFF880082D6B10, 0xFFFFF80002CB3603)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/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 a problem occurred in the NTFS file system.
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 07/01/2016 07:41:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-22281-01.dmp
uptime: 00:00:47
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002FAF909, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 07/01/2016 07:38:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-21218-01.dmp
uptime: 00:00:24
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F563DE, 0xFFFFF88002BD2720, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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 Sat 02/01/2016 09:55:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-22312-01.dmp
uptime: 00:03:05
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs!NtfsCopyReadA+0x1A8)
Bugcheck code: 0x1A (0x41284, 0xFFFFF98002A8C001, 0x0, 0xFFFFF780C0000000)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/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 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 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 02/01/2016 09:52:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-21437-01.dmp
uptime: 00:01:05
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FA8909, 0xFFFFF88004658A50, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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 Sat 02/01/2016 09:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-21531-01.dmp
uptime: 00:00:20
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002FA73DE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 01/01/2016 17:44:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-22343-01.dmp
uptime: 07:21:46
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8C565, 0xFFFFF88007736F80, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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 01/01/2016 10:22:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-19734-01.dmp
uptime: 00:18:28
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C91A81, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 01/01/2016 09:56:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-17390-01.dmp
uptime: 00:00:17
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!CmpRemoveKeyHash+0x4C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F79728, 0xFFFFF88002FDA9A8, 0xFFFFF88002FDA200)
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 Tue 29/12/2015 15:47:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-17734-01.dmp
uptime: 05:02:02
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4A (0x74BD2E09, 0x2, 0x0, 0xFFFFF88002B5ACA0)
Error: [FONT=Segoe UI, Arial]IRQL_GT_ZERO_AT_SYSTEM_SERVICE[/FONT]
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 Tue 29/12/2015 10:31:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-24609-01.dmp
uptime: 00:03:27
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k!xxxInterSendMsgEx+0xABB)
Bugcheck code: 0x19 (0x3, 0xFFFFF8800232E410, 0x77FFF8800232E410, 0xFFFFF8800232E410)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver Win32 multiutente
Bug check description: This indicates that a pool header is corrupt.
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 27/12/2015 09:16:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-17468-01.dmp
uptime: 00:00:50
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs! ?? ::FNODOBFM::`string'+0x2B49)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007542718, 0xFFFFF88007541F70, 0xFFFFF880012D4A5B)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/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 a problem occurred in the NTFS file system.
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 26/12/2015 20:28:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122615-17171-01.dmp
uptime: 00:00:21
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DFE9BC, 0xFFFFF88002697850, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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]
Conclusion

[/FONT]
[FONT=Segoe UI, Arial]18 crash dumps have been found and analyzed. A third party driver has 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]aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



[/FONT]

- - - Updated - - -

nessuno può o meglio nessuno vuole darmi una mano d'aiuto a risolver il problema?

- - - Updated - - -

essuno può o meglio nessuno vuole darmi una mano d'aiuto a risolver il problema?
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,158
6,169
CPU
Intel 3570k @4.200
Scheda Madre
AsRock Z77 Extreme4
Hard Disk
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 2133
Scheda Video
AMD R9 290 TRI-X
Monitor
IIyama 28" 4K
Alimentatore
Cooler Master GX 650
Case
Corsair 600T
Sistema Operativo
Windows10x64pro
ciao,
da qualche tempo ho problemi con il maledettissimo bluescreen of death.ho da poco aggiornato il sistema operativo passando dal caro vecchio windows xp professional 32bit che non ha mai dato problemi ne bluescreen a windows 7 professional 64bit.ovviamente la cpu è 64 bit .
da quando lo installato a ogni avvio,o appena carica windows o mentre lavoro col pc all'improvviso si manifesta quel maledetto bluescreen of death e ad ogni sua nuova manifestazione ha un diverso codice di errore,mai lo stesso.ho provato a formattare tutto e reinstallare windows e tutti i programmi da capo diverse volte ma si ripresenta sempre.ho installato who crasched per tentare di capirci qualcosa ma non ci capisco niente.
vi posto i risultati degli ultimi crash e relativo hw del pc,sperando possiate aiutarmi:
[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]Computer name: FERROVECCHIOPC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASRock, G41C-GS
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294008832 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]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 08/01/2016 10:18:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010816-19812-01.dmp
uptime: (unknown)
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Fri 08/01/2016 10:17:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:11:26
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr!FltpDispatch+0xD9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880010036E9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Gestione filtri file system Microsoft
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 Fri 08/01/2016 10:05:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010816-19171-01.dmp
uptime: 00:14:27
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x7A8003A13090, 0x2, 0x0, 0xFFFFF80002D01424)
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 07/01/2016 22:45:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010816-19906-01.dmp
uptime: 03:23:27
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (0xFFFFF88001073C11)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001073C11, 0xFFFFF88008397BA0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Gestione filtri file system Microsoft
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 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 07/01/2016 18:26:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-29265-01.dmp
uptime: 09:01:51
This was probably caused by the following module: [FONT=Segoe UI, Arial]aswmonflt.sys[/FONT] (aswMonFlt+0x4609)
Bugcheck code: 0x1A (0x5002, 0xFFFFF781C0000000, 0x53F, 0x8800053CFFFFFFFE)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: [FONT=Segoe UI, Arial]Avast Antivirus [/FONT]
company: [FONT=Segoe UI, Arial]AVAST Software[/FONT]
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: [FONT=Segoe UI, Arial]AVAST Software MEMORY_MANAGEMENT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 07/01/2016 09:24:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-19765-01.dmp
uptime: 00:06:56
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs! ?? ::FNODOBFM::`string'+0x2B49)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880082D72B8, 0xFFFFF880082D6B10, 0xFFFFF80002CB3603)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/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 a problem occurred in the NTFS file system.
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 07/01/2016 07:41:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-22281-01.dmp
uptime: 00:00:47
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002FAF909, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 07/01/2016 07:38:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010716-21218-01.dmp
uptime: 00:00:24
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F563DE, 0xFFFFF88002BD2720, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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 Sat 02/01/2016 09:55:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-22312-01.dmp
uptime: 00:03:05
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs!NtfsCopyReadA+0x1A8)
Bugcheck code: 0x1A (0x41284, 0xFFFFF98002A8C001, 0x0, 0xFFFFF780C0000000)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/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 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 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 02/01/2016 09:52:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-21437-01.dmp
uptime: 00:01:05
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FA8909, 0xFFFFF88004658A50, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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 Sat 02/01/2016 09:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-21531-01.dmp
uptime: 00:00:20
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002FA73DE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 01/01/2016 17:44:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-22343-01.dmp
uptime: 07:21:46
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8C565, 0xFFFFF88007736F80, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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 01/01/2016 10:22:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-19734-01.dmp
uptime: 00:18:28
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C91A81, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 01/01/2016 09:56:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010116-17390-01.dmp
uptime: 00:00:17
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!CmpRemoveKeyHash+0x4C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F79728, 0xFFFFF88002FDA9A8, 0xFFFFF88002FDA200)
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 Tue 29/12/2015 15:47:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-17734-01.dmp
uptime: 05:02:02
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4A (0x74BD2E09, 0x2, 0x0, 0xFFFFF88002B5ACA0)
Error: [FONT=Segoe UI, Arial]IRQL_GT_ZERO_AT_SYSTEM_SERVICE[/FONT]
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 Tue 29/12/2015 10:31:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122915-24609-01.dmp
uptime: 00:03:27
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k!xxxInterSendMsgEx+0xABB)
Bugcheck code: 0x19 (0x3, 0xFFFFF8800232E410, 0x77FFF8800232E410, 0xFFFFF8800232E410)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver Win32 multiutente
Bug check description: This indicates that a pool header is corrupt.
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 27/12/2015 09:16:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122715-17468-01.dmp
uptime: 00:00:50
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs! ?? ::FNODOBFM::`string'+0x2B49)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007542718, 0xFFFFF88007541F70, 0xFFFFF880012D4A5B)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/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 a problem occurred in the NTFS file system.
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 26/12/2015 20:28:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122615-17171-01.dmp
uptime: 00:00:21
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DFE9BC, 0xFFFFF88002697850, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
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]
Conclusion

[/FONT]
[FONT=Segoe UI, Arial]18 crash dumps have been found and analyzed. A third party driver has 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]aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



[/FONT]

- - - Updated - - -

nessuno può o meglio nessuno vuole darmi una mano d'aiuto a risolver il problema?

- - - Updated - - -

essuno può o meglio nessuno vuole darmi una mano d'aiuto a risolver il problema?
se hai fretta vai da un tecnico pagando visto che sei in forum e visto il giorno sabato magari qualcuno ha una vita sociale e non sta sul forum a dare una mano!

la soluzione è semplice rimuovi avast e vedi se va meglio è lui quello che da problemi.
 

Entra

oppure Accedi utilizzando