Bonsoir à tous. En ces temps de confinement j'ai décidé d'utiliser le pc que ma femme avait fait monter dans une boutique mais qui flanche plus ou moins régulièrement. Elle est médecin et ne l'utilise que pour la bureautique et le logiciel dédié aux consultations. Rien d'extraordinaire mais elle a du se résoudre à reprendre son vieux portable qui rame mais ne plante pas. J'ai utilisé quelques manipulations pour supprimer tous les logiciels médicaux qui étaient installés et réparer windows. Malheureusement, cela ne suffit pas. Il plante à des moments différents, quand on l'utilise ou pas et des écrans bleus apparaissent ;) J'ai lu plusieurs post et j'ai décidé de vous demander de l'aide. Voici le dernier rapport Whocrashed: System Information (local) Computer name: DESKTOP-3K88R1C Windows version: Windows 10 , 10.0, build: 18363 Windows dir: C:\WINDOWS Hardware: B450 AORUS M, Gigabyte Technology Co., Ltd. CPU: AuthenticAMD AMD Ryzen 3 2200G with Radeon Vega Graphics AMD8664, level: 23 4 logical processors, active mask: 15 RAM: 6388080640 bytes (5,9GB) Crash Dump Analysis Crash dumps are enabled on your computer. Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Sun 22/03/2020 22:53:31 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032220-29078-01.dmp This was probably caused by the following module: dxgmms2.sys (0xFFFFF8073D3FD2AC) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8073D3FD2AC, 0xFFFF80854D4DF658, 0xFFFF80854D4DEEA0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\drivers\dxgmms2.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. 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 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. On Sun 22/03/2020 22:53:31 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\MEMORY.DMP This was probably caused by the following module: dxgmms2.sys (0xFFFFF8073D3FD2AC) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8073D3FD2AC, 0xFFFF80854D4DF658, 0xFFFF80854D4DEEA0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED file path: C:\WINDOWS\system32\drivers\dxgmms2.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. The crash took place in a 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. On Sun 22/03/2020 21:09:25 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032220-6125-01.dmp This was probably caused by the following module: win32kbase.sys (0xFFFFE75977C0636D) Bugcheck code: 0x50 (0xFFFFE759786C4B73, 0x2, 0xFFFFE75977C0636D, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\WINDOWS\system32\win32kbase.sys product: Système d’exploitation Microsoft® Windows® company: Microsoft Corporation description: Pilote du noyau Base Win32k Bug check description: This indicates that invalid system memory has been referenced. 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 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. On Sun 22/03/2020 21:07:16 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032220-28703-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x12F994) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8077292F994, 0xFFFF82042566F518, 0xFFFFC20119A98930) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 a system thread generated an exception which the error handler did not catch. 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 Sun 22/03/2020 14:26:05 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032220-5281-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380) Bugcheck code: 0xA (0xFFFFDA8A4FFC6AFC, 0x2, 0x0, 0xFFFFF8026F47A95A) 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. On Sun 22/03/2020 13:01:05 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032220-8328-01.dmp This was probably caused by the following module: ae2500w764.sys (0xFFFFF80E8FA0D85C) Bugcheck code: 0xC4 (0x2000, 0xFFFFF80E8FA0D85C, 0x0, 0x484D4342) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\WINDOWS\system32\drivers\ae2500w764.sys product: Broadcom 802.11 Network Adapter wireless driver company: Broadcom Corporation description: Broadcom 802.11 Network Adapter wireless driver Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. 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: ae2500w764.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation). Google query: ae2500w764.sys Broadcom Corporation DRIVER_VERIFIER_DETECTED_VIOLATION Conclusion 6 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: ae2500w764.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation) Merci d'avance.

Bon courage et croisons les doigts ensemble.

Bonjour. Alors l'installation ne s'est pas faites et j'ai eu ce message: Arrgghhh!!!!!

Bon nous allons essayer ceci en dernier recours : 1) Si votre W10 est connecté à un domaine (compte Microsoft par exemple), changez pour un compte local. 2) Redémarrez le PC 3) Déconnectez-vous d’Internet avant de faire la mise à jour (désactivez le Wi-Fi ou retirez le câble Ethernet) et puis relancez l’installation de Windows 10. Bon courage.

Plantage et écran bleu!! - Page 2

Réponse 21 / 23
heraultais34600 Messages postés 776 Statut Membre 97

Bon courage et croisons les doigts ensemble.
0
Réponse 22 / 23
steus Messages postés 18 Statut Membre

Bonjour.
Alors l'installation ne s'est pas faites et j'ai eu ce message:

Arrgghhh!!!!!
0
Réponse 23 / 23
heraultais34600 Messages postés 776 Statut Membre 97

Bon nous allons essayer ceci en dernier recours :

1) Si votre W10 est connecté à un domaine (compte Microsoft par exemple), changez pour un compte local.
2) Redémarrez le PC
3) Déconnectez-vous d’Internet avant de faire la mise à jour (désactivez le Wi-Fi ou retirez le câble Ethernet) et puis relancez l’installation de Windows 10.
Bon courage.
0

Plantage et écran bleu!! - Page 2

Discussions similaires

Newsletters