je viens vous demandez en aide car début Février des problèmes sont survenue, je suis donc aller chez l'informaticien qui ma fait un reformatage. Les écrans bleus ont disparus puis sont réapparus mais trés peu souvent (grosse session de jeu 6h+) et maintenant depuis quelque jours je ne peux plus jouer aux jeux. Je joue 10-15 min puis écran bleu ou écran bloquer.
J'ai fais une analyse avec whocrashed, les voici ci dessous.
En espérant que vous pourriez m'aider
Merci d'avance.Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: USER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X2 550 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4294156288 total
VM: 2147352576, free: 1880809472
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 30/03/2014 20:25:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-17581-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000004.sys (Unloaded_Unknown_Module_00000000`00000004+0x6)
Bugcheck code: 0xA (0x2B, 0x2, 0x0, 0xFFFFF80002C81289)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`00000004.sys .
Google query: unknown_module_00000000`00000004.sys IRQL_NOT_LESS_OR_EQUAL
On Sun 30/03/2014 20:25: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: 0xA (0x2B, 0x2, 0x0, 0xFFFFF80002C81289)
Error: IRQL_NOT_LESS_OR_EQUAL
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 28/03/2014 23:00:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032914-21652-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD010, 0x2, 0x1, 0xFFFFF80002CFF7FE)
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 Thu 20/03/2014 19:17:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032014-16879-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD010, 0x2, 0x1, 0xFFFFF80002C997FE)
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 Sun 16/03/2014 17:47:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031614-45255-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002CA5150)
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 Sun 09/03/2014 12:20:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030914-23524-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C3C5FE, 0xFFFFF88002811E40, 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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 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:
unknown_module_00000000`00000004.sys
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.
