non saprei prova ma se puoi visto i sospetti vedi se con un disco diverso cambia la situazione
Ho aggiornato tutti i driver e installato W10 ma la situazione non cambia. Ho avuto anche un altro tipo di crash. ti incollo il risultato di whocrashed
[FONT=Segoe UI, Arial]
Welcome to WhoCrashed (HOME EDITION) v 5.51
[/FONT]
[FONT=Segoe UI, Arial]
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.
[/FONT]
[FONT=Segoe UI, Arial]
To obtain technical support visit www.resplendence.com/support
[/FONT][FONT=Segoe UI, Arial]
Click here to check if you have the latest version or if an update is available.
[/FONT][FONT=Segoe UI, Arial]
Just click the Analyze button for a comprehensible report ...
[/FONT][FONT=Segoe UI, Arial]
Home Edition Notice
[/FONT]
[FONT=Segoe UI, Arial]
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.
[/FONT]
[FONT=Segoe UI, Arial]
System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]
Computer name: LUCA-PC
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, H170 Pro4S
CPU: GenuineIntel Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8523608064 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 Wed 30/12/2015 20:10:24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\123015-14015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680EF636850, 0xA9C0000217693867, 0xFFFFE0008B150870)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]
On Wed 30/12/2015 17:52:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\123015-14640-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF6BFFF5ED580, 0xE, 0xD)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
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.
[/FONT]
[FONT=Segoe UI, Arial]
On Wed 30/12/2015 17:46:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\123015-15687-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x82B, 0x1F001EF5CC0, 0xFFFFD00026071000)
Error: [FONT=Segoe UI, Arial]FAULTY_HARDWARE_CORRUPTED_PAGE[/FONT]
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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]
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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]Grazie mille per il tuo aiuto
- - - Updated - - -
non saprei prova ma se puoi visto i sospetti vedi se con un disco diverso cambia la situazione
L'amico che mi ha aiutato a montare il PC mi ha detto che potrebbe essere causato dal fatto che abbiamo installato windows da un altro PC.
Abbiamo scollegato l'hard disk da un altro computer, abbiamo collegato l'ssd del computer preso in esame e abbiamo installato windows 7 Ultimate. Una volta finito, abbiamo ricollegato tutto com'era prima e l'ssd riposta nel nuovo PC. Tutto questo perchè quest'ultimo non è dotato di lettore CD.
Può essere che sia questo il motivo?
