Driver étrange provoquant des blue screen

Merci beaucoup pour ton aide!

J'apporte quelques nouvelles en plus du rapport (désolé pour le pavé).

Je reviens sur ce que j'ai dit à propos du lien entre les blue screen et ce driver, le crash a eu lieu à 15h12 et l'installation presque 2 minutes après. Ce driver s'installe simplement à chaque démarrage et n'est probablement pas la cause du problème principal, même si ça m'intrigue beaucoup honnêtement.

Entre temps, je suis allé fouiller dans regedit et me suis rendu compte qu'il y avait deux versions des drivers de mon processeur installées, j'ai supprimé les deux et redémarré mon PC qui a réinstallé la plus récente uniquement.

J'ai également fait l'analyse RegRun Reanimator qui a détecté un driver probablement malveillant (rien à voir avec celui sur mes screens) que j'ai supprimé directement car il ne me servait à rien de toute façon.

Le problème est donc peut-être réglé, mais je n'en aurais le cœur net que si je n'ai pas de blue screen pendant 3-4j. Je renverrai un message si c'est le cas, mais sinon encore merci pour ton aide, je ne connaissais pas WhoCrashed et cela risque de m'être utile!

Il y a 5 crashs sur le rapport, celui du 05/09 est dû à une surchauffe, les 4 autres sont arrivés quand je jouais à League of Legends sans aucune surchauffe. J'ai dû changer un paramètre pour activer les rapports complets à l'avenir, mais je crois que ceux-là ne le sont pas.

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 09/09/2024 15:12:40 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\090924-49265-01.dmp (Minidump) Bugcheck code: 0xD1(0xFFFFA18B9F980CB0, 0x2, 0x0, 0xFFFFF800907BA9A8)Bugcheck name:DRIVER_IRQL_NOT_LESS_OR_EQUALBug check description:This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.



On Sun 08/09/2024 00:40:59 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\090824-51953-01.dmp (Minidump) Bugcheck code: 0x1000007E(0xFFFFFFFFC0000005, 0xFFFFF80778EA8E99, 0xFFFFA5846D10E5F8, 0xFFFFBF80F96FF920)Bugcheck name:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MBug check description:This indicates that a system thread generated an exception which the error handler did not catch.Analysis:This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues





On Fri 06/09/2024 13:06:50 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\090624-57296-01.dmp (Minidump) Bugcheck code: 0xA(0x8, 0x2, 0x0, 0xFFFFF805460440EE)Bugcheck name:IRQL_NOT_LESS_OR_EQUALBug 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.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.



On Thu 05/09/2024 16:59:57 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\090524-56937-01.dmp (Minidump) Bugcheck code: 0x1A(0x403, 0xFFFF8E00D5BDD540, 0x8100000054651867, 0xFFFF8E80D5BDD540)Bugcheck name:MEMORY_MANAGEMENTBug check description:This indicates that a severe memory management error occurred. Analysis:The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit. This is possibly a software problem. This is likely a case of memory corruption.
This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues





On Wed 04/09/2024 18:40:09 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\090424-55531-01.dmp (Minidump) Bugcheck code: 0x1000007E(0xFFFFFFFFC0000005, 0xFFFFF8034D4A8E99, 0xFFFFDE8038D0E5F8, 0xFFFFF803526AC920)Bugcheck name:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MBug check description:This indicates that a system thread generated an exception which the error handler did not catch.Analysis:This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues





 

Conclusion

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider 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 suggestions displayed in the bugcheck analysis above.

The analysis process took 0:00:55 (h:mm:ss).

Je n'ai plus de clé USB chez moi malheureusement, si le problème persiste j'en achèterai une et ferai le test!