Non, rien de particulier : tu le fait tourné genre 30 mn et tu vérifie si y'a pas des erreurs qui remonte
d'accord, et bien le pc à eu le temps de faire 6 fois le test, puis BSOD... et j'ai remarqué pendant la phase de test que tout le RGB CORSAIR avait des saccades c'est normal ?
voici le rapport de Whocrashed :
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Fri 09/04/2021 20:38:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040921-6328-01.dmp
This was probably caused by the following module:
Vous devez être
connecté pour voir les liens.
(nt+0x3F5C50)
Bugcheck code: 0xA (0x141583DB00, 0xF, 0x1, 0xFFFFF806599F1DC7)
Error:
Vous devez être
connecté pour voir les liens.
file path: C:\Windows\system32\ntoskrnl.exe
product:
Vous devez être
connecté pour voir les liens.
company:
Vous devez être
connecté pour voir les liens.
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.
On Fri 09/04/2021 20:38:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module:
Vous devez être
connecté pour voir les liens.
(cpuz150_x64+0x4455)
Bugcheck code: 0xA (0x141583DB00, 0xF, 0x1, 0xFFFFF806599F1DC7)
Error:
Vous devez être
connecté pour voir les liens.
file path: C:\Windows\temp\cpuz150\cpuz150_x64.sys
product:
Vous devez être
connecté pour voir les liens.
company:
Vous devez être
connecté pour voir les liens.
description: CPUID Driver
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.
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: cpuz150_x64.sys (CPUID Driver, CPUID).
Google query:
Vous devez être
connecté pour voir les liens.
On Fri 09/04/2021 15:59:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040921-5500-01.dmp
This was probably caused by the following module:
Vous devez être
connecté pour voir les liens.
(nt+0x3F5C50)
Bugcheck code: 0xD1 (0xFFFFF8047D3FD0A1, 0x2, 0x8, 0xFFFFF8047D3FD0A1)
Error:
Vous devez être
connecté pour voir les liens.
file path: C:\Windows\system32\ntoskrnl.exe
product:
Vous devez être
connecté pour voir les liens.
company:
Vous devez être
connecté pour voir les liens.
description: NT Kernel & System
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 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. 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:
Vous devez être
connecté pour voir les liens.
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
Vous devez être
connecté pour voir les liens.
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.