comment allez-vous ?Je me permet de demander votre aide puisque depuis une semaine , mon pc freeze en étant en jeu / ou en allant sur youtube..de gros gros freeze qui dure 20s voir +
De plus quand suis en vocal via discord , doit déco toute les 5 minutes parce que d'un coup je n'entends plus rien...
Voici le rapport FRST :
Frst : https://pjjoint.malekal.com/files.php?i ... 12k12z6x15
Addition : https://pjjoint.malekal.com/files.php?i ... d15u12q7g5
Shot : https://pjjoint.malekal.com/files.php?i ... 12e7h15f13
Voici le rapport de whocrashed puisque j'ai eu 2 écran bleu (de ma faute ) j'ai lancé 2 jeux en même temps ^^
Merci de votre aide ! Pc analyser via Malwarebytes Anti-Malware (MBAM) / AdwCleaner / antispyware et CrystalDiskInfo , rien de méchant ...On Wed 31/01/2018 21:24:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013118-27937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x9F (0x3, 0xFFFFC104A01A6060, 0xFFFFE28064B9B8F0, 0xFFFFC104A37CCAF0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
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 31/01/2018 21:24:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!MmTrimAllSystemPagableMemory+0x113C7)
Bugcheck code: 0x9F (0x3, 0xFFFFC104A01A6060, 0xFFFFE28064B9B8F0, 0xFFFFC104A37CCAF0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\121017-16812-01.dmp