Memtest86+
Fermé
maka54
Messages postés
699
Date d'inscription
mercredi 8 avril 2009
Statut
Membre
Dernière intervention
4 décembre 2016
-
13 déc. 2013 à 19:08
maka54 Messages postés 699 Date d'inscription mercredi 8 avril 2009 Statut Membre Dernière intervention 4 décembre 2016 - 14 déc. 2013 à 15:35
maka54 Messages postés 699 Date d'inscription mercredi 8 avril 2009 Statut Membre Dernière intervention 4 décembre 2016 - 14 déc. 2013 à 15:35
A voir également:
- Memtest86+
- Memtest86+ - Télécharger - Informations & Diagnostic
- Memtest86 - Guide
- Interprétation de Memtest86+ - Forum Carte-mère/mémoire
- Memtest86 format usb ✓ - Forum Windows 10
- Erreurs trouvées par MemTest86 - Forum Carte-mère/mémoire
2 réponses
rlo73
Messages postés
2956
Date d'inscription
jeudi 12 avril 2012
Statut
Membre
Dernière intervention
25 février 2023
632
13 déc. 2013 à 23:41
13 déc. 2013 à 23:41
ça ressemble à un crash, donc probablement à une erreur de lecture/écriture de mémoire. Il faut tester les barrettes indépendamment les unes des autres.
maka54
Messages postés
699
Date d'inscription
mercredi 8 avril 2009
Statut
Membre
Dernière intervention
4 décembre 2016
80
14 déc. 2013 à 15:35
14 déc. 2013 à 15:35
Bonjour et merci de pour ton aide.
j'ai bien réalisé les tests des barrettes individuellement
voici ce qui se passe :
premiere barrette => une passe se fait a 100% puis pas longtemps apres puis ecran noir et plus rien ... (entre 10 et 15 minutes)
seconde barrette => problème identique ...
aujourd'hui, j'ai essayé avec un autre slot (pensant que celui-ci pourrait etre defectueux) => problème identique
à une différence près, le ventilateur de la carte graphique tourne à fond
il y a deux autres barettes encore, non testées mais à priori, le problème ne vient pas de là, qu'en pensez-vous ?
et j'ai l'impression que le test se coupe lorsque le cpu ou autre chose se met à trop chauffer (ce n'est qu'une hypothèse, je ne m'y connais pas du tout)
pour info le cpu monte a environ 67/68° avec des petites pointes vers les 72/73°
de ce que m'indique memtest
Avez-vous une idée ?
j'ajoute également un rapport de whoCrash qui pourrait peut etre vous aiguiller davantage :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: MAKA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Studio XPS 8000, Dell Inc., 0X231R
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6433136640 total
VM: 2147352576, free: 1925361664
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 13/12/2013 08:08:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8000001484C)
Bugcheck code: 0x50 (0xFFFFF8000001484C, 0x0, 0xFFFFF880012B429E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Fri 13/12/2013 08:07:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-20826-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800032EDA8B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13/12/2013 08:04:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-16099-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x1EBE2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880019D7BE2, 0xFFFFF88003346708, 0xFFFFF88003345F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 Sun 08/12/2013 08:50:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-20108-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880099121A8, 0xFFFFF88009911A00, 0xFFFFF880011EDFE3)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 05/12/2013 08:15:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120513-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17CA87)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000338CA87, 0xFFFFF880033E7628, 0xFFFFF880033E6E80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 02/12/2013 07:33:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-16536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF800032C7D80)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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 03/04/2013 06:35:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040313-17799-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4810000, 0xFFFFFA8006431010)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Wed 27/03/2013 07:54:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032713-20779-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030DE849, 0xFFFFF880039A6F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 06/03/2013 07:38:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030613-27580-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC7D9E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E7D9E, 0xFFFFF8800A5750A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 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 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.
j'ai bien réalisé les tests des barrettes individuellement
voici ce qui se passe :
premiere barrette => une passe se fait a 100% puis pas longtemps apres puis ecran noir et plus rien ... (entre 10 et 15 minutes)
seconde barrette => problème identique ...
aujourd'hui, j'ai essayé avec un autre slot (pensant que celui-ci pourrait etre defectueux) => problème identique
à une différence près, le ventilateur de la carte graphique tourne à fond
il y a deux autres barettes encore, non testées mais à priori, le problème ne vient pas de là, qu'en pensez-vous ?
et j'ai l'impression que le test se coupe lorsque le cpu ou autre chose se met à trop chauffer (ce n'est qu'une hypothèse, je ne m'y connais pas du tout)
pour info le cpu monte a environ 67/68° avec des petites pointes vers les 72/73°
de ce que m'indique memtest
Avez-vous une idée ?
j'ajoute également un rapport de whoCrash qui pourrait peut etre vous aiguiller davantage :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: MAKA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Studio XPS 8000, Dell Inc., 0X231R
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6433136640 total
VM: 2147352576, free: 1925361664
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 13/12/2013 08:08:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8000001484C)
Bugcheck code: 0x50 (0xFFFFF8000001484C, 0x0, 0xFFFFF880012B429E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Fri 13/12/2013 08:07:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-20826-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800032EDA8B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13/12/2013 08:04:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-16099-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x1EBE2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880019D7BE2, 0xFFFFF88003346708, 0xFFFFF88003345F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 Sun 08/12/2013 08:50:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120813-20108-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880099121A8, 0xFFFFF88009911A00, 0xFFFFF880011EDFE3)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 05/12/2013 08:15:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120513-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17CA87)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000338CA87, 0xFFFFF880033E7628, 0xFFFFF880033E6E80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 02/12/2013 07:33:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-16536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF800032C7D80)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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 03/04/2013 06:35:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040313-17799-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4810000, 0xFFFFFA8006431010)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Wed 27/03/2013 07:54:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032713-20779-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030DE849, 0xFFFFF880039A6F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 06/03/2013 07:38:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030613-27580-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC7D9E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E7D9E, 0xFFFFF8800A5750A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 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 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.
