Driver IRQL not less or Equal

Salut à tous, ça fait plusieurs fois que mon PC redémarre soudainement avec le message DRIver IRQL not less or Equal j'ai fait une analyse avec whocrashed, et il semblerait que le problème vienne de ma carte son, je poste le rapport en espérant que quelqu'un puisse m'éclairer ! merci et bonne soirée :)


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
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 get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: MARC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: MS-7680, MSI, H61M-E33(B3)(MS-7680)
CPU: GenuineIntel Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8552157184 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 11/09/2017 18:58:43 your computer crashed
crash dump file: C:\WINDOWS\Minidump\091117-12437-01.dmp
This was probably caused by the following module: maudiofasttrackpro.sys (0xFFFFF80AA95B8E9B)
Bugcheck code: 0xD1 (0x9A0, 0x2, 0x0, 0xFFFFF80AA95B8E9B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\maudiofasttrackpro.sys
product: Fast Track Pro WDM Audio Streaming Driver
company: M-Audio
description: Fast Track Pro WDM Audio Streaming 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: maudiofasttrackpro.sys (Fast Track Pro WDM Audio Streaming Driver, M-Audio).
Google query: M-Audio DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 11/09/2017 18:58:43 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: maudiofasttrackpro.sys (MAudioFastTrackPro+0x18E9B)
Bugcheck code: 0xD1 (0x9A0, 0x2, 0x0, 0xFFFFF80AA95B8E9B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\maudiofasttrackpro.sys
product: Fast Track Pro WDM Audio Streaming Driver
company: M-Audio
description: Fast Track Pro WDM Audio Streaming 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: maudiofasttrackpro.sys (Fast Track Pro WDM Audio Streaming Driver, M-Audio).
Google query: M-Audio DRIVER_IRQL_NOT_LESS_OR_EQUAL





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

2 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:

maudiofasttrackpro.sys (Fast Track Pro WDM Audio Streaming Driver, M-Audio)

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.