Buongiorno ragazzi
volevo chiedervi un aiuto , non so piu come fare per risolvere questo problema
il mio computer molte volte si riavvia da solo ( appena entra in windows , comincio ad utilizzarlo e dopo circa 1 minuto , si riavvia) con relativa schermata blu
mentre a volte si riavvia ancor prima di arrivare in windows bloccandosi sulla schermata iniziale
io ho fatto un analisi con Whocrashed e mi ha trovato 19 dump
ora li posto sperando che possiate aiutarmi ( non so se sia l'antivirus, la grafica , i driver o l'hard disk, ma quest'ultimo l'ho riparato gia con chkdsk ) aiutatemi per piacere non so piu
dove sbattere la testa , oggi invece non ha riscontrato problemi
Welcome to WhoCrashed (Professional Edition) v 4.01
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit
www.resplendence.com/supportClick here to check if you have the latest version or if an update is available.
Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network...
System Information (local)
computer name: SERMAR
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3488600064 total
VM: 2147352576, free: 1942065152
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 10/01/2014 08.54.47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011114-28189-01.dmp
uptime: 00:04:05
This was probably caused by the following module: ntkrpamp.exe (nt!KiBugCheck2+0x0)
Bugcheck code: 0x1 (0xFFFFFFFF9063DD46, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe APC_INDEX_MISMATCH
On Fri 10/01/2014 08.54.47 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:04:05
This was probably caused by the following module: ntkrpamp.exe (nt!KiBugCheck2+0x0)
Bugcheck code: 0x1 (0xFFFFFFFF9063DD46, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe APC_INDEX_MISMATCH
On Thu 09/01/2014 16.10.57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011014-35973-01.dmp
uptime: 00:03:11
This was probably caused by the following module: cmdguard.sys (cmdguard+0x247AB)
Bugcheck code: 0x139 (0x3, 0xFFFFFFFF81A172AC, 0xFFFFFFFF81A17258, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\cmdguard.sys
product: COMODO Internet Security Sandbox Driver
company: COMODO
description: COMODO Internet Security Sandbox Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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: cmdguard.sys (COMODO Internet Security Sandbox Driver, COMODO).
Google query: COMODO KERNEL_SECURITY_CHECK_FAILURE
On Thu 09/01/2014 16.08.37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010914-34273-01.dmp
uptime: (unknown)
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Mon 06/01/2014 17.10.56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010814-27814-01.dmp
uptime: 00:02:36
This was probably caused by the following module: cmdguard.sys (cmdguard+0x247AB)
Bugcheck code: 0x139 (0x3, 0xFFFFFFFF9E13B2FC, 0xFFFFFFFF9E13B2A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\cmdguard.sys
product: COMODO Internet Security Sandbox Driver
company: COMODO
description: COMODO Internet Security Sandbox Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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: cmdguard.sys (COMODO Internet Security Sandbox Driver, COMODO).
Google query: COMODO KERNEL_SECURITY_CHECK_FAILURE
On Sat 04/01/2014 20.21.53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-24804-01.dmp
uptime: 00:05:45
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x44841)
Bugcheck code: 0x139 (0x3, 0xFFFFFFFFB96B336C, 0xFFFFFFFFB96B3318, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 311.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 311.06
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_SECURITY_CHECK_FAILURE
On Tue 17/12/2013 17.45.41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121713-31949-01.dmp
uptime: 00:00:55
This was probably caused by the following module: rdyboost.sys (rdyboost!SmdMdlCleanup+0x11)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF81E2FCB7, 0xFFFFFFFF8D785B28, 0xFFFFFFFF8D7856F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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.
On Tue 17/12/2013 17.44.15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121713-26941-01.dmp
uptime: 00:02:02
This was probably caused by the following module: fltmgr.sys (fltmgr!FreeTargetedIoCtrl+0x4F)
Bugcheck code: 0x139 (0x3, 0xFFFFFFFF8D7ED5CC, 0xFFFFFFFF8D7ED578, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
Bug check description: The kernel has detected the corruption of a critical data structure.
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.
On Thu 12/12/2013 10.42.14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121213-24336-01.dmp
uptime: 00:05:51
This was probably caused by the following module: sptd.sys (sptd+0x18DDF)
Bugcheck code: 0xD1 (0x4F494644, 0x2, 0x8, 0x4F494644)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
product: SCSI Pass Through Direct
company: Duplex Secure Ltd.
description: SCSI Pass Through Direct Host
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.
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: sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.).
Google query: Duplex Secure Ltd. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 08/12/2013 18.57.13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-26426-01.dmp
uptime: 00:03:23
This was probably caused by the following module: intelppm.sys (intelppm!SetFFHThrottleState+0x19)
Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF915C8048, 0xFFFFFFFF83012A8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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.
On Sun 08/12/2013 13.56.12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-30357-01.dmp
uptime: 00:06:34
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0xE, 0xFFFFFFFF89F9C218, 0x21BEF94D, 0x21BEF96D)
Error: BAD_POOL_HEADER
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe BAD_POOL_HEADER
On Fri 06/12/2013 18.24.14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120613-27721-01.dmp
uptime: 00:02:07
This was probably caused by the following module: ntkrpamp.exe (nt!KiBugCheck2+0x0)
Bugcheck code: 0xA (0xFFFFFFFFBB7FFFE4, 0x2, 0x1, 0xFFFFFFFF81C7A368)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Fri 06/12/2013 09.04.56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120613-31184-01.dmp
uptime: 00:02:44
This was probably caused by the following module: ntkrpamp.exe (nt!PpmPerfFeedbackCounterRead+0x37)
Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF917A53D2, 0xFFFFFFFF8BE84C48, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 03/12/2013 19.33.58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120313-29187-01.dmp
uptime: 05:57:14
This was probably caused by the following module: intelppm.sys (intelppm!SetFFHThrottleState+0x19)
Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF82FCD048, 0xFFFFFFFF8BE12A8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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.
On Mon 02/12/2013 12.41.56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-37237-01.dmp
uptime: 00:02:23
This was probably caused by the following module: cmdguard.sys (cmdguard+0x3571C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81ECD02F, 0xFFFFFFFFAB933488, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\cmdguard.sys
product: COMODO Internet Security Sandbox Driver
company: COMODO
description: COMODO Internet Security Sandbox Driver
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.
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: cmdguard.sys (COMODO Internet Security Sandbox Driver, COMODO).
Google query: COMODO KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Conclusion
19 crash dumps have been found and analyzed. Only 15 are included in this report. 5 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation)
cmdguard.sys (COMODO Internet Security Sandbox Driver, COMODO)
sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.)
hal.sys
ntkrpamp.exe
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.