domematrix
14-03-2014, 12:36
Nonostante io abbia sfruttato a pieno il tasto search del forum (anche con la noiosa pausa di 60 secondi per ogni ricerca), abbia letto i regolamenti delle varie sezioni che mi sono d'interesse e avendo cercato il mio modello di laptop ed il problema in sè di come risolvere il mio problema, giungo alla conclusione che: nessuno ha mai avuto un portatile come questo, su questo portatile nessuno ha mai avuto un bsod e non credo di infrengere regolamenti se posto qui.
riporto dal vecchio thread tutto quello che avevo scritto con gl'ultimi aggiornamenti.
----------------------------------
ho comprato meno di 1 mese fà il computer portatile citato nel titolo, un Asus N56VV con windows 8 64 bit.
Il tempo vuole che questo pc appena superati i 10 giorni di vita (qundi troppo tardi per rispedire il pc indietro) mi inizia a crashare il sistema dandomi il blue screen, incazzato nero perchè windows 8 non mi piaceva, il computer rendeva meno di quanto io mi aspettassi (era un pò lentuccio per essere un'i7), presi la decisione di cambiare sistema operativo! Sul vecchio pc avevo windows home edition, quindi pensavo di mettere quel cd e farlo partire al massimo (convinto che gli aggiornamenti automatici avrebbero fatto tutto, ed anche risolto il problema).
Concludo dicendo che, la home edition che avevo era a 32 bit (porca miseria!) quindi un'amico mi ha dato la sua PK per windows ultimate da un pc che era rotto e che quindi non usava. Mi dà il cd con tutto sopra, installo tutto, faccio fare aggiornamenti automatici (alcuni driver li ho dovuti scaricare ed installare a mano), il sistema operativo è a 64 bit ma, nonostante questi grossi cambiamenti, tutt'ora mi dà il bsod. Leggendo su internet ho trovato un programma che mi ha dato questi risultati:
---------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: INFAMIA
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: N56VV, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8470122496 total
VM: 2147352576, free: 1917321216
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 12/03/2014 18:25:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-20935-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600014778B)
Bugcheck code: 0x50 (0xFFFFF994C06DAD78, 0x0, 0xFFFFF9600014778B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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 Wed 12/03/2014 18:25:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!W32pArgumentTable+0x1C6F)
Bugcheck code: 0x50 (0xFFFFF994C06DAD78, 0x0, 0xFFFFF9600014778B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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 09/03/2014 22:13:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-20514-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80063B7210, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sat 08/03/2014 23:48:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-20810-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880031A940C)
Bugcheck code: 0x50 (0xFFFFFA900705E400, 0x0, 0xFFFFF880031A940C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Sat 08/03/2014 11:33:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-36098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A008907A10, 0xFFFFF80008907A10, 0xFFFFF8A008907A10)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 08/03/2014 10:52:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-19718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8006310860, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sat 08/03/2014 10:00:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-20092-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6C92)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000136C92, 0xFFFFF8800B302B30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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.
On Sat 08/03/2014 09:23:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-20311-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880031A25B3)
Bugcheck code: 0x50 (0xFFFFF8B00A93BC00, 0x0, 0xFFFFF880031A25B3, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Sat 08/03/2014 03:23:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030714-38859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF81010D327D0, 0x1, 0xFFFFF8000314CABA, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 07/03/2014 22:10:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030714-23696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFA818641DB2B, 0x0, 0xFFFFF80002E707AF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
13 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
--------------------------------------------------------------------
Avendo perso la garanzia (non sapevo si perdesse se formattavi il pc) posso tranquillamente aprirlo e smontarlo (cosa che ancora non ho fatto per una questione di personale tranquillità) ma, leggendo sempre in rete, ho trovato che molte persone hanno risolto togliendo e rimettendo la ram. Io sinceramente non sò bene come si può vedere/capire/modificare una ram semplicemente togliendola e rimettendola, vabbè tralasciando i miei giudizi voi cosa ne pensate? come risolvo?
Per favor non datemi cose da leggere in inglese che sono una frana, e se è possibile essere specifici su quello che devo fare perchè sono anche un bel pò tonto!
Se avete bisogno di altre info sono qui.
Normalmente mi crasha il pc quando attivo sia skype che lol.exe, ma non crasha subito, all'improvviso prende e si fà blu.
Grazie in anticipo,
cordiali saluti
Domenico.
-------------------------------------------------------------------------
Ho fatto partire memtest86+-4.10 da cd-R, spengo il pc e riavvio facendo partire come primo boot il cd, entra in memtest ma una volta arrivato lì non fà ALCUNA operazione. Ovvero, ho le tabelle L1 cache L2 cache e tutto, ma non compie nessuna operazione! Ho lasciato il pc tutta la notte acceso con memtest attivo e così come lo avevo lasciato la notte così l'ho ritrovato il mattino dopo! E, soprattutto, avevo letto che per uscire da memtest dovevo premere "ESC" , ma non ha avuto nessun risultato! Il pc l'ho dovuto spegnere manualmente. Attendo risposta perchè non sò come uscirne... :-/
Se ho sbagliato qualcosa nel post per favore ditemelo che lo modifico, ma pls non chiudete! Ho ancora problemi di crash :-/
riporto dal vecchio thread tutto quello che avevo scritto con gl'ultimi aggiornamenti.
----------------------------------
ho comprato meno di 1 mese fà il computer portatile citato nel titolo, un Asus N56VV con windows 8 64 bit.
Il tempo vuole che questo pc appena superati i 10 giorni di vita (qundi troppo tardi per rispedire il pc indietro) mi inizia a crashare il sistema dandomi il blue screen, incazzato nero perchè windows 8 non mi piaceva, il computer rendeva meno di quanto io mi aspettassi (era un pò lentuccio per essere un'i7), presi la decisione di cambiare sistema operativo! Sul vecchio pc avevo windows home edition, quindi pensavo di mettere quel cd e farlo partire al massimo (convinto che gli aggiornamenti automatici avrebbero fatto tutto, ed anche risolto il problema).
Concludo dicendo che, la home edition che avevo era a 32 bit (porca miseria!) quindi un'amico mi ha dato la sua PK per windows ultimate da un pc che era rotto e che quindi non usava. Mi dà il cd con tutto sopra, installo tutto, faccio fare aggiornamenti automatici (alcuni driver li ho dovuti scaricare ed installare a mano), il sistema operativo è a 64 bit ma, nonostante questi grossi cambiamenti, tutt'ora mi dà il bsod. Leggendo su internet ho trovato un programma che mi ha dato questi risultati:
---------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: INFAMIA
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: N56VV, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8470122496 total
VM: 2147352576, free: 1917321216
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 12/03/2014 18:25:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-20935-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600014778B)
Bugcheck code: 0x50 (0xFFFFF994C06DAD78, 0x0, 0xFFFFF9600014778B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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 Wed 12/03/2014 18:25:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!W32pArgumentTable+0x1C6F)
Bugcheck code: 0x50 (0xFFFFF994C06DAD78, 0x0, 0xFFFFF9600014778B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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 09/03/2014 22:13:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-20514-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80063B7210, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sat 08/03/2014 23:48:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-20810-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880031A940C)
Bugcheck code: 0x50 (0xFFFFFA900705E400, 0x0, 0xFFFFF880031A940C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Sat 08/03/2014 11:33:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-36098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A008907A10, 0xFFFFF80008907A10, 0xFFFFF8A008907A10)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 08/03/2014 10:52:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-19718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8006310860, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sat 08/03/2014 10:00:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-20092-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6C92)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000136C92, 0xFFFFF8800B302B30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
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.
On Sat 08/03/2014 09:23:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-20311-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880031A25B3)
Bugcheck code: 0x50 (0xFFFFF8B00A93BC00, 0x0, 0xFFFFF880031A25B3, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Sat 08/03/2014 03:23:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030714-38859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF81010D327D0, 0x1, 0xFFFFF8000314CABA, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 07/03/2014 22:10:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030714-23696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFA818641DB2B, 0x0, 0xFFFFF80002E707AF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
13 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
--------------------------------------------------------------------
Avendo perso la garanzia (non sapevo si perdesse se formattavi il pc) posso tranquillamente aprirlo e smontarlo (cosa che ancora non ho fatto per una questione di personale tranquillità) ma, leggendo sempre in rete, ho trovato che molte persone hanno risolto togliendo e rimettendo la ram. Io sinceramente non sò bene come si può vedere/capire/modificare una ram semplicemente togliendola e rimettendola, vabbè tralasciando i miei giudizi voi cosa ne pensate? come risolvo?
Per favor non datemi cose da leggere in inglese che sono una frana, e se è possibile essere specifici su quello che devo fare perchè sono anche un bel pò tonto!
Se avete bisogno di altre info sono qui.
Normalmente mi crasha il pc quando attivo sia skype che lol.exe, ma non crasha subito, all'improvviso prende e si fà blu.
Grazie in anticipo,
cordiali saluti
Domenico.
-------------------------------------------------------------------------
Ho fatto partire memtest86+-4.10 da cd-R, spengo il pc e riavvio facendo partire come primo boot il cd, entra in memtest ma una volta arrivato lì non fà ALCUNA operazione. Ovvero, ho le tabelle L1 cache L2 cache e tutto, ma non compie nessuna operazione! Ho lasciato il pc tutta la notte acceso con memtest attivo e così come lo avevo lasciato la notte così l'ho ritrovato il mattino dopo! E, soprattutto, avevo letto che per uscire da memtest dovevo premere "ESC" , ma non ha avuto nessun risultato! Il pc l'ho dovuto spegnere manualmente. Attendo risposta perchè non sò come uscirne... :-/
Se ho sbagliato qualcosa nel post per favore ditemelo che lo modifico, ma pls non chiudete! Ho ancora problemi di crash :-/