BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL windows 10 pls send halp

Bonjour,
j'ai récemment update mon pc que j'ai monté il y a deux ans en y rajoutant 8Gb pour arriver à 16. pendant la réinstallation j'ai découvert que ma carte graphique ne marchait plus sur le port PCIe 3.0, donc depuis elle tourne normalement sur le 2.0

et depuis que j'ai tout remis, j'ai des bsod randoms, DRIVER_IRQL_NOT_LESS_OR_EQUAL
ou IRQL_NOT_LESS_OR_EQUAL

ma config :



Je vous poste ici le résultat de whocrashed


merci à ceux qui répondront :)



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

Computer name: LEO-PC
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: MS-7816, MSI, Z87-G43 (MS-7816)
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 16579190784 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 30/05/2016 11:48:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\053016-24578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF000E6B3A774, 0x2, 0x0, 0xFFFFF800616F6C35)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 29/05/2016 20:17:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\053016-22140-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!Win32FreePool+0x1A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8005D04F04A, 0xFFFFD00022E54AE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
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 Sat 28/05/2016 14:52:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052816-24546-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xBEDE5)
Bugcheck code: 0xD1 (0x0, 0x9, 0x1, 0xFFFFF80165B2EDE5)
Error: DRIVER_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 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.
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. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 27/05/2016 10:11:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052716-21359-01.dmp
This was probably caused by the following module: cmudaxp.sys (cmudaxp+0x6601)
Bugcheck code: 0xD1 (0x100000, 0x2, 0x8, 0x100000)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\cmudaxp.sys
product: C-Media Audio Driver (WDM)
company: C-Media Inc
description: C-Media Audio WDM Driver
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.
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: cmudaxp.sys (C-Media Audio WDM Driver, C-Media Inc).
Google query: C-Media Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 25/05/2016 21:58:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052616-20906-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x2D0C3)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8014A5E9B73, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.
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. KMODE_EXCEPTION_NOT_HANDLED



On Mon 23/05/2016 21:27:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052316-22203-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x58, 0x2, 0x0, 0xFFFFF800450F697D)
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.
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 21/05/2016 22:36:37 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052216-21609-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xEF (0xFFFFE000F5AC8080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 16/05/2016 21:29:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051616-21515-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680FBC5BF18, 0xF8800001A7C5A867, 0xFFFFE00205F1DE50)
Error: MEMORY_MANAGEMENT
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 Thu 12/05/2016 20:04:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051216-21796-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip!FlpParsePacket+0xDB)
Bugcheck code: 0x7F (0x8, 0xFFFFF802DFB0FE70, 0xFFFFD0011BBD6210, 0xFFFFF8018A7CE42B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 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 Thu 12/05/2016 19:35:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051216-21515-01.dmp
This was probably caused by the following module: afd.sys (afd!AfdPoll64+0x2CA)
Bugcheck code: 0xD1 (0xFFFFE000791E4018, 0x2, 0x0, 0xFFFFF80186FA1E7A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de fonction connexe pour WinSock
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.





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

11 crash dumps have been found and analyzed. Only 10 are included in this report. 3 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:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
cmudaxp.sys (C-Media Audio WDM Driver, C-Media Inc)

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.