J'ai régulièrement des écrans bleus avec reboot de l'ordinateur qui apparaissent pendant l'utilisation d'Ableton Live 10. Mon PC est neuf, tous les drivers sont à jours et même après reformatage et réinstallation de Windows 10 le problème persiste.
J'ai d'abord pensé à un problème de pilotes avec ma carte son externe mais j'ai récemment changé de carte, désinstallé correctement les pilotes de l'ancienne et le problème est toujours là.
Les écrans bleus arrivent toujours pendant une session Ableton Live 10 mais de façon aléatoire. Il arrive qu'il n'y ai pas de BSOD pendant plusieurs heures d'utilisation tout comme il est possible qu'au bout de 15 minutes un écran bleu survienne.
En espérant trouver une solution ici, voici les résultats de ma dernière analyse Whocrashed.
Merci d'avance !
-------
System Information (local)
Computer name: DESKTOP-0FRH7MN
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING PRO CARBON AC (MS-7B17)
CPU: GenuineIntel Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz Intel8664, level: 6
16 logical processors, active mask: 65535
RAM: 34290765824 bytes (31,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 23/03/2020 18:36:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032320-7046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8064F0899E3, 0xFFFFD3095AA07F50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 21/03/2020 16:18:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032120-7640-01.dmp
This was probably caused by the following module: hal.dll (hal+0x47FF8)
Bugcheck code: 0x124 (0x0, 0xFFFFDC880EBA7028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Wed 18/03/2020 17:44:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031820-8656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xA (0x5C, 0x2, 0x0, 0xFFFFF8020B114C96)
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.