Forum-seven : Communauté francaise de Windows 7

Bonjour, j'ai acheté un nouveau pc il y a quelques mois mais je n'arrête pas d'avoir des blue screen, parfois 4 à 5 fois par jour!
Et ce depuis le début, j'ai même réinstallé le tout à l'état d'"usine" et dés la première heure d'utilisation, un blue screen est apparu.
De plus, en vérifiant les températures avec Speedfan, l'une d'elle atteint 59°C sans raison et même après le démarrage.
Je suis un peu désespérée là, surtout que le service après vente ne m'aide pas du tout. Si vous avez des conseils ou des pistes, qui contacter, que puis-je faire si je veux retourner le pc au magasin,...

Voilà le rapport Who Crashed:

System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 5359386624 total
VM: 2147352576, free: 1976631296



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 16/02/2011 13:59:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-20264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003095F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


On Wed 16/02/2011 13:59:17 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003095F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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 which cannot be identified at this time.


On Wed 16/02/2011 13:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x60999, 0x0, 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 which cannot be identified at this time.


On Sun 06/02/2011 12:17:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020611-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030A4F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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.

Merci d'avance!

Bonjour,
Fais un test de mémoire vive.
Deux solutions possibles

Avec Vista et Sept.
Dans le panneau de configuration, Outils d'administration, Diagnostic de mémoire Windows, choisis parmi les deux options proposées. Cette opération se fera au redémarrage.

Avec Memtest
Voir sur ce site : http://www.memtest86.com/
Il faut graver un CD ou l'installer sur une clé USB bootable.
@+

Voilà je viens de faire un test de mémoire vive et rien n'a été détecté...

Salut

si le pc n'a que quelque mois, un retour en SAV peut s'avérer judicieux.
Sauvegarde tes données auparavant

Il n'y a pas de raisons qu'ils ne le reprennent pas, surtout si tu as toujours eu ces écrans bleus dès l'achat ....

@+

Merci pour vos conseils, je vais essayer de le ramener cette semaine, en espérant que je saurai les convaincre!
Depuis hier, les blue screen arrivent même au démarrage!

Nouveau rapport Who crashed, dernier espoir :s

System Information (local)
--------------------------------------------------------------------------------

computer name: SOPHIE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 5359386624 total
VM: 2147352576, free: 1975742464



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 27/02/2011 13:59:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022711-18111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9BD30)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800024A4D30, 0xFFFFF880027C7778, 0xFFFFF880027C6FD0)
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 which cannot be identified at this time.


On Sun 27/02/2011 13:59:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1AEBF)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800024A4D30, 0xFFFFF880027C7778, 0xFFFFF880027C6FD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 which cannot be identified at this time.


On Sun 27/02/2011 13:53:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022711-15865-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9BD30)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030F0D30, 0xFFFFF880039C0848, 0xFFFFF880039C00A0)
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 which cannot be identified at this time.


On Sun 27/02/2011 13:51:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022711-17487-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5953)
Bugcheck code: 0x24 (0x190477, 0xFFFFF8800B1B7D38, 0xFFFFF8800B1B7590, 0xFFFFF800030E59EC)
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 which cannot be identified at this time.


On Sun 27/02/2011 12:28:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022711-18189-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9BD30)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030F2D30, 0xFFFFF880039C06E8, 0xFFFFF880039BFF40)
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 which cannot be identified at this time.


On Sat 26/02/2011 12:19:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022611-26192-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9BD30)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030B4D30, 0xFFFFF880039C0718, 0xFFFFF880039BFF70)
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 which cannot be identified at this time.


On Sat 26/02/2011 09:47:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022611-17113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9B9EC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030E99EC, 0xFFFFF880039C06F8, 0xFFFFF880039BFF50)
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 which cannot be identified at this time.


On Wed 23/02/2011 10:11:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022311-28095-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030E5F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


On Tue 22/02/2011 20:40:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022211-15116-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x949, 0x2, 0x0, 0xFFFFF800030B0F2F)
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 which cannot be identified at this time.


On Fri 18/02/2011 14:14:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021811-14523-01.dmp
This was probably caused by the following module: netbt.sys (netbt+0x2E410)
Bugcheck code: 0x19 (0x20, 0xFFFFF88003FAE410, 0xFFFFF88003FAF3B0, 0x5FAE410)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\netbt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MBT Transport driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 16/02/2011 15:47:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-14913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030A7F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


On Wed 16/02/2011 13:59:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-20264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003095F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


On Wed 16/02/2011 13:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x60999, 0x0, 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 which cannot be identified at this time.


On Sun 06/02/2011 12:17:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020611-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030A4F9E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 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.