Irql_not _less_or_ equal

Bonjour j'ai essayer de chercher la reponse avec les autres sujets ouverts mais en vain pouvez vous m'aider svp ?
Ca fait plusieurs fois que j'ai l'erreur irql not less or equal

J'ai fait un rapport whocrashed le voici mais je ne m'y connais pas vrm donc je ne comprend pas grand chose

Merci d'avances pour vos reponses

On Wed 18/03/2020 11:14:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031820-10812-01.dmp
This was probably caused by the following module: ai.sys (AI+0x1586)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80376117772)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ai.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote AI pour NT
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a 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 18/03/2020 11:14:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: iastorac.sys (iaStorAC+0x912B3)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80376117772)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iastorac.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Tue 03/03/2020 22:10:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030320-11406-01.dmp
This was probably caused by the following module: iastorac.sys (0xFFFFF8063CDE2D36)
Bugcheck code: 0xD1 (0xC8, 0x2, 0x0, 0xFFFFF8063CDE2D36)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iastorac.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 01/03/2020 21:53:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030120-11453-01.dmp
This was probably caused by the following module: iastorac.sys (0xFFFFF8035DAC2D36)
Bugcheck code: 0xD1 (0xC8, 0x2, 0x0, 0xFFFFF8035DAC2D36)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iastorac.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 23/02/2020 22:54:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022320-11265-01.dmp
This was probably caused by the following module: iastorac.sys (0xFFFFF802431E2D36)
Bugcheck code: 0xD1 (0xC8, 0x2, 0x0, 0xFFFFF802431E2D36)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iastorac.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 28/12/2019 06:41:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122819-78203-01.dmp
This was probably caused by the following module: kbdclass.sys (0xFFFFF804028CF470)
Bugcheck code: 0x7A (0xFFFFAE06FBABFD18, 0xFFFFFFFFC000000E, 0x2002057DD860, 0xFFFFF804028CF470)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\kbdclass.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de la classe Clavier
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a 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.