Visualizza allegato 252451 Visualizza allegato 252452 Visualizza allegato 252453 Visualizza allegato 252454 Visualizza allegato 252455 ciao a tutti da un po di tempo il mio pc fa delle schermate blu e non mi riesce di capire il perche.. ho cabiato l'hd pensando fosse quello ma niente ho staccato un hub usb ma niente, ho passato memory test e dice che dovrebbero essere ok le ram..ho fatto un report se puo essere utile e qualche foto delle schermate..
Welcome to WhoCrashed (HOME EDITION) v 5.52
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) 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 (or black) 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/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: DESKTOP-H7R26FR
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASRock, H170M Pro4S
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8249655296 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 12/07/2017 12:10:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071217-12375-01.dmp
This was probably caused by the following module:
ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA39FCC5CCA325573, 0x0, 0x9A58077A13B0597A, 0x102)
Error:
CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
On Wed 12/07/2017 12:10:00 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: 0x109 (0xA39FCC5CCA325573, 0x0, 0x9A58077A13B0597A, 0x102)
Error:
CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
On Wed 12/07/2017 11:42:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071217-14187-01.dmp
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 Tue 11/07/2017 22:23:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071217-17312-01.dmp
This was probably caused by the following module:
ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFC6800005AC10, 0x800000, 0x0)
Error:
MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 09/07/2017 20:19:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070917-35265-01.dmp
This was probably caused by the following module:
peauth.sys (peauth+0x7BCE6)
Bugcheck code: 0x50 (0xFFFFE001CD734D52, 0x0, 0xFFFFF8010699BCE6, 0x0)
Error:
PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\peauth.sys
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: Protected Environment Authentication and Authorization Export Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 02/07/2017 16:27:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070917-23468-01.dmp
This was probably caused by the following module:
ntfs.sys (NTFS!NtfsFlushAndPurgeScb+0xA0)
Bugcheck code: 0xDE (0x2, 0xFFFF8001E327A3B8, 0xFFFF8001E325A3B8, 0x25850D8C0)
Error:
POOL_CORRUPTION_IN_FILE_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product:
Sistema operativo Microsoft® Windows®
company:
Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in 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 02/07/2017 09:45:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070217-43812-01.dmp
This was probably caused by the following module:
ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFB7814FF11FB8, 0x8, 0x7)
Error:
MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 02/07/2017 09:40:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070217-40406-01.dmp
This was probably caused by the following module:
ntfs.sys (NTFS!NtfsCleanupIrpContext+0x2E8)
Bugcheck code: 0x50 (0xFFFFC805A4DF6628, 0x2, 0xFFFFF800A3F401AE, 0x2)
Error:
PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product:
Sistema operativo Microsoft® Windows®
company:
Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
8 crash dumps have been found and analyzed.
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.
