écran bleu qui s'affiche

nn nn j'ai pas de clavier ou souris branché
j'ai Eset nod32
j'ai fais analyse et j'ai copier Crash dump analyse
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 12/10/2017 01:23:32 your computer crashed
crash dump file: C:\Windows\Minidump\101217-22588-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFE36510BF)
Bugcheck code: 0xD1 (0xFFFFFFFFC6D39B10, 0x2, 0x8, 0xFFFFFFFFC6D39B10)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 01/01/1980 00:14:59 your computer crashed
crash dump file: C:\Windows\Minidump\010180-23992-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x410BF)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFFE367C06A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 01/01/1980 00:11:01 your computer crashed
crash dump file: C:\Windows\Minidump\010180-22276-01.dmp
This was probably caused by the following module: btl2cascoif.sys (Unloaded_BtL2caScoIf.+0x2B10)
Bugcheck code: 0xD1 (0xFFFFFFFFCD602B10, 0x2, 0x8, 0xFFFFFFFFCD602B10)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\btl2cascoif.sys
product: Ralink L2CAP_SCO Interface at Bluetooth Stack for Windows 7
company: Ralink Corporation
description: Bluetooth L2CAP_SCO Interface Profile 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: btl2cascoif.sys (Bluetooth L2CAP_SCO Interface Profile Driver, Ralink Corporation).
Google query: Ralink Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 01/01/1980 00:05:38 your computer crashed
crash dump file: C:\Windows\Minidump\010180-20997-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x410BF)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFC, 0x2, 0x0, 0xFFFFFFFFE3694023)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 01/01/1980 00:02:23 your computer crashed
crash dump file: C:\Windows\Minidump\010180-22183-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4AA7)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFFE368506A)
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.

nn aucun péri^hérique branchés ,,j vais essayer le lien que tu m'a envoyer