yann120
Messages postés20Date d'inscriptionmercredi 3 septembre 2008StatutMembreDernière intervention19 mai 2014
-
8 mai 2013 à 18:52
Bonjour la communauté,
j'ai tout essayé pour résoudre mon problème et je suis maintenant à bout.
je vous explique, mon ordinateur en janvier à commencé à faire des écrans bleus.
J'avais tésté mes barettes ram, un test m'ont dit qu'elles sont défectueuses. J'ai racheté une barrette mais le problème continuait.
J'ai tésté mon disque dur avec le logiciel du fabricant, le test à révélé qu'il était défectueux, je l'ai envoyé en garantie. J'ai reçu le nouveau. J'ai tout réinstallé mais les écrans bleus continuent...
Je ne sais plus quoi faire, je suis vraiment au bout du rouleau?
Le problème dur déjà depuis 5 mois!
Merci d'avance.
Yann
Voici un rapport des crash :
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: YANN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2220 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 1878249472 total
VM: 2147352576, free: 1999138816
On Wed 08/05/2013 16:43:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-41589-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028E0DE6, 0xFFFFF8800536CCE0, 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 08/05/2013 16:43:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1E82)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028E0DE6, 0xFFFFF8800536CCE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 Tue 07/05/2013 19:41:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-35209-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFEFB7DA0FFD8, 0x0, 0xFFFFF800028A1105, 0x7)
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 Tue 07/05/2013 17:14:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-20326-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001835395)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001835395)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 07/05/2013 17:09:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-26161-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x60, 0x2, 0x1, 0xFFFFF800028A646B)
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 Tue 07/05/2013 16:54:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-28064-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFF80022AF2900, 0x2, 0x0, 0xFFFFF800028AB6F5)
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 Tue 07/05/2013 16:40:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-26254-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA1DC7)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF880012C7DC7)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Tue 07/05/2013 14:56:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-46691-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004785390, 0x0, 0x0)
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 that cannot be identified at this time.
On Tue 07/05/2013 14:13:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-28407-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0x1FFFFF, 0xFFFFF8800451F4B0, 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 Mon 06/05/2013 20:59:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050613-23587-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8000266D9BC, 0xFFFFF88006DAD010, 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 Mon 06/05/2013 20:44:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050613-31808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x34 (0x50830, 0xFFFFF880046E5798, 0xFFFFF880046E4FF0, 0xFFFFF800029646E9)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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.
11 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.