PROBLEMA Crash per Errore Memoria

  • Autore discussione Autore discussione Baxa
  • Data d'inizio Data d'inizio
Pubblicità

Baxa

Utente Attivo
Messaggi
176
Reazioni
3
Punteggio
53
Salve a tutti, ho preso da 5-6 mesi un pc nuovo , assemblato su vostro consiglio :figo: ma ogni tanto mi si presenta la tipica blu screen prima del crash e ho deciso ora di risolvere il problema perchè inizia a essere piuttosto fastidioso, ci sono settimane in cui non capita ed altre in cui capita magari 2-3 volte.non sono riuscito a capire se dipende da qualche programma che apro dato che mi sembra un errore abbastanza random. vi lascio un report di crash preso con WhoCrashed.

Codice:
[FONT=Segoe UI][SIZE=4][B]System Information (local)[/B][HR][/HR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000]computer name: BAX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, H97 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8521900032 total


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=4][B][HR][/HR]Crash Dump Analysis[/B][HR][/HR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dump directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 12/08/2015 12:53:25 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\081215-15163-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x748C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800808CB10, 0xFFFFFA800808CDF0, 0xFFFFF800031C5E20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 12/08/2015 12:53:25 GMT your computer crashed[/B]
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800808CB10, 0xFFFFFA800808CDF0, 0xFFFFF800031C5E20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Fri 07/08/2015 23:12:11 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\080815-24242-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x748C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007B57060, 0xFFFFFA8007B57340, 0xFFFFF80003195E20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Mon 03/08/2015 21:05:07 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\080315-21637-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x748C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800806CB10, 0xFFFFFA800806CDF0, 0xFFFFF800031C3E20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 30/06/2015 22:43:19 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\070115-17487-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x748C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800807EB10, 0xFFFFFA800807EDF0, 0xFFFFF800031C8E20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Mon 08/06/2015 01:15:27 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\060815-18486-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x748C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008086B10, 0xFFFFFA8008086DF0, 0xFFFFF8000317EE20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Mon 25/05/2015 10:27:21 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\052515-17752-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x748C0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008442B10, 0xFFFFFA8008442DF0, 0xFFFFF80003186E20)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Sun 17/05/2015 01:00:10 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\051715-14648-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=atikmpag.sys"]atikmpag.sys[/URL][/COLOR][/SIZE][/FONT] (atikmpag+0xB848) 
Bugcheck code: 0x116 (0xFFFFFA80071BF260, 0xFFFFF88003B68848, 0x0, 0x2)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+VIDEO_TDR_ERROR"]VIDEO_TDR_ERROR[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\atikmpag.sys
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=AMD%20driver"]AMD driver[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Advanced%20Micro%20Devices,%20Inc."]Advanced Micro Devices, Inc.[/URL][/COLOR][/SIZE][/FONT]
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. 
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.). 
Google query: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=atikmpag.sys+Advanced%20Micro%20Devices,%20Inc.+VIDEO_TDR_ERROR"]Advanced Micro Devices, Inc. VIDEO_TDR_ERROR[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 28/04/2015 21:23:41 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\042815-15974-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x72A40) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80078E5710, 0xFFFFFA80078E59F0, 0xFFFFF80003186940)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Tue 21/04/2015 23:02:29 GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\042215-15865-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x72A40) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008004B30, 0xFFFFFA8008004E10, 0xFFFFF800031C9940)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_OBJECT_TERMINATION"]CRITICAL_OBJECT_TERMINATION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


[/COLOR][/SIZE][/FONT]
 
Usa Orthos lanciare quanti ne servono per saturare tutti i core. Impostarlo in modo da verificare l'affidabilità della memoria.
 
non riesco a trovare nessun link attivo da cui scaricare il programma, nemmeno quello nel forum va.
 
va bene cosi'?

Codice:
Using CPU #1Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
Test 8, 4000 Lucas-Lehmer iterations of M18274367 using 1024K FFT length.
Test 9, 4000 Lucas-Lehmer iterations of M18274369 using 1024K FFT length.
Test 10, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
Test 11, 4500 Lucas-Lehmer iterations of M17432577 using 1024K FFT length.
Test 12, 4500 Lucas-Lehmer iterations of M17432575 using 1024K FFT length.
Test 13, 4500 Lucas-Lehmer iterations of M17115073 using 1024K FFT length.
Test 14, 4500 Lucas-Lehmer iterations of M16815071 using 1024K FFT length.
Test 15, 4500 Lucas-Lehmer iterations of M16515073 using 1024K FFT length.
Test 16, 4500 Lucas-Lehmer iterations of M16515071 using 1024K FFT length.
Test 17, 4500 Lucas-Lehmer iterations of M16297569 using 1024K FFT length.
Test 18, 4500 Lucas-Lehmer iterations of M15997567 using 1024K FFT length.
Self-test 1024K passed!
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
Test 13, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Test 14, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
Test 15, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
Test 16, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
Test 17, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
Test 18, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
Test 19, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
Test 20, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.
Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length.
Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length.
Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length.
Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length.
Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length.
Test 9, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT length.
Torture Test ran 36 minutes 22 seconds - 0 errors, 0 warnings.
Execution halted.
 
ciao non usare orthos che serve per la cpu bensì memtest da scaricare sul sito e da mettere su cd o pen
 
Scarica memtestx86+ da questo link:
Memtest86+ - Advanced Memory Diagnostic Tool
Masterizza la iso su un cd/dvd o crea una pendrive avviabile, e fai partire il memtest per 5-6 ore.
Sarebbe bene se hai le ram in dual channel testare un banco alla volta. Gli errori rilevati devono essere pari a 0!!!

- - - Updated - - -

ciao non usare orthos che serve per la cpu bensì memtest da scaricare sul sito e da mettere su cd o pen

Eccolo!!! Federico... Abbiamo risposto assieme XD
:lol:
 
Or those con dimensione large va bene anche per la memoria e se ne lancinanti quanti sono i core e assegni manualmente i processi ai core é anche rapido.
 
Pubblicità
Pubblicità
Indietro
Top