Ecran bleu, memory problem, où trouver le rapport

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

Computer name: ADMIN-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: GA-MA790FXT-UD5P, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 12882272256 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 12/07/2016 14:49:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-39764-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0xA (0xFFFFFA8020705010, 0x2, 0x1, 0xFFFFF80003B7B4E6)
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 12/07/2016 14:49:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x870A) 
Bugcheck code: 0xA (0xFFFFFA8020705010, 0x2, 0x1, 0xFFFFF80003B7B4E6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 12/07/2016 08:45:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-36161-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80011D3C60, 0xFFFF, 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 that cannot be identified at this time. 



On Fri 08/07/2016 09:33:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070816-27253-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80011D3C60, 0xFFFF, 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 that cannot be identified at this time. 



On Fri 08/07/2016 09:03:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070816-29530-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80011D3C60, 0xFFFF, 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 that cannot be identified at this time. 



On Tue 05/07/2016 10:51:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070516-29874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80011D3C60, 0xFFFF, 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 that cannot be identified at this time. 



On Tue 05/07/2016 09:40:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070516-33836-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x104F3) 
Bugcheck code: 0xA (0xFFFFFA8020864010, 0x2, 0x1, 0xFFFFF80003B494E6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). 
Google query: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL



On Thu 23/06/2016 22:00:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062416-35396-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78BE9) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80011D3C60, 0xFFFF, 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 that cannot be identified at this time. 



On Fri 10/06/2016 17:34:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061116-39390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0xA (0xFFFFFA80206FD010, 0x2, 0x1, 0xFFFFF80003B7A4E6)
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 Sat 04/06/2016 15:52:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060416-29390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0xA (0xFFFFFA80206F0010, 0x2, 0x1, 0xFFFFF80003B494E6)
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. 





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

26 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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.)
unknown_module_00000000`00003731.sys 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.