=> symptômes : Pleins de bluescreen je navigue plusieurs heures et dans c'est plusieurs heures j'ai au moins 10 bluescreen différents
=> manipulations effectuées : Memtest , Whocrashed
=> configuration matériel : ??
- marque ET modèle exact du PC : PC MONTER
- processeur : I5 2320 3 ghZ
- mémoire vive : 8 go balistics sport 1333 mhz
- carte graphique : HD 7850 2 GO VERSION OC
- carte mère : MSI Z68 S - G43
- alimentation : Ocz modulaire 620 W
- autre : Je me disais que sa allait passé mais la j'en peux vraiment plus j'arrive plus a navigué normalement toujours des bluescreens . S'il vous plait dites moi que faire

Le rapport whocrached

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 01/11/2012 21:48:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-13462-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB2B)
Bugcheck code: 0xBE (0xFFFFF88007A69B2B, 0x22EE89121, 0xFFFFF80004FA16A0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Thu 01/11/2012 21:48:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS!HidNotifyPresence+0x65EA)
Bugcheck code: 0xBE (0xFFFFF88007A69B2B, 0x22EE89121, 0xFFFFF80004FA16A0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Thu 01/11/2012 17:10:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-14508-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF88001233290)
Bugcheck code: 0x50 (0xFFFFFA80471B2BA4, 0x1, 0xFFFFF88001233290, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Thu 01/11/2012 13:55:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-13525-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x22, 0x10000000, 0x0, 0x0)
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 Thu 01/11/2012 13:46:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-14664-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF8000386406F)
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 Wed 31/10/2012 22:53:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-15381-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFF80013888EA0, 0x8, 0xFFFFF80013888EA0, 0x2)
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 Wed 31/10/2012 22:45:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-14726-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF88001708BB1)
Bugcheck code: 0x50 (0xFFFFFA8016FB8078, 0x0, 0xFFFFF88001708BB1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 31/10/2012 15:30:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-17815-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x99, 0x80C26, 0x0, 0x168EA6)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 Wed 31/10/2012 13:36:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-14055-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001A4B9C7)
Bugcheck code: 0xD1 (0xFFFFFAA009947BA8, 0x2, 0x0, 0xFFFFF88001A4B9C7)
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 Wed 31/10/2012 12:31:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-14352-01.dmp
This was probably caused by the following module: npfs.sys (0xFFFFF8800426301C)
Bugcheck code: 0x50 (0xFFFFFA80171EA0B0, 0x0, 0xFFFFF8800426301C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
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 31/10/2012 12:23:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-11949-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFFA80197FC070, 0x2, 0x0, 0xFFFFF8000386F2D9)
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 30/10/2012 18:58:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103012-12183-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880057B6698, 0xFFFFF880057B5EF0, 0xFFFFF800038EC074)
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 Tue 30/10/2012 11:41:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103012-12916-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF8800715455D)
Bugcheck code: 0x50 (0xFFFFF8A042C83B20, 0x0, 0xFFFFF8800715455D, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Tue 30/10/2012 11:07:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103012-13681-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003867480, 0x0, 0x4)
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 30/10/2012 11:05:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103012-13135-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000388F6D6, 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.

--------------------------------------------------
------------------------------

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

23 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

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.

=> système d'exploitation : W7 / 64 bites

Dit moi , c'est quand la dernière fois que t'a fais une mise à jours ?

y'a des probleme de partout , direct x , reseau , driver usb...

Perso je ne me serai pas casser la tête , un petit formatage direct

Mais c'est impossible j'ai tous a jour .

UP

Je suis dans le même cas que toi , et je ne sais pas quoi faire , les écrans bleus apparaissent comme ça , un jour j'en ai 10 , et la semaine qui suit j'ai plus rien .
Je te conseille le formatage , mais pour moi , ça n'y a rien fait ...
Il se peut que ce soit: les rams (memtest ne détecte pas tout)
Ou le disque dur , qui peut-être endommagé.