Nicom06
-
Nbre de contenus
2 -
Inscription
-
Dernière visite
Messages posté(e)s par Nicom06
-
-
Bonjour à tous,
J'ai depuis 3 semaines un nouveau pc portable Laptop 15 bw-019 sur Win 10. (1709)
J'ai de plus en plus de BSOD à la sortie de veille, des fois immédiatement ou après quelques minutes.
J'ai ré installer windows depuis le menu "recommencer à 0", ainsi que les pilotes via l'outil HP Support Assitant et le problème persiste.
Je ne suis pas du tout expert en informatique, j'ai fait beaucoup de recherche mais je tourne en rond...
Je vous remercie d'avance de toute votre aide.
Bonne journée
Voici ci dessous les messages Whocrashed.
Révélation
System Information (local)
Computer name: LAPTOP-N0AT890N
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: HP Laptop 15-bw0xx, HP, 8331
CPU: AuthenticAMD AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G AMD586, level: 21
2 logical processors, active mask: 3
RAM: 8017076224 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 25/10/2017 13:42:36 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-12890-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xEFF5C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8040AFAFF5C, 0x1, 0x4C2F701)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a kernel-mode program 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 standard 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 Wed 25/10/2017 13:42:36 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xEFF5C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8040AFAFF5C, 0x1, 0x4C2F701)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a kernel-mode program 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 standard 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 Wed 25/10/2017 13:33:15 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-10640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x50 (0xFFFFFFFF8B48406A, 0x2, 0xFFFFF80081773F1C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 25/10/2017 12:35:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-12859-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x13549)
Bugcheck code: 0xD1 (0x10007A0BA, 0x2, 0x1, 0xFFFFF803CCF1940C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0316467.inf_amd64_3d8fbd78102e53d7\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 25/10/2017 12:21:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-11500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x7F (0x8, 0xFFFFD700E11229B0, 0x0, 0xFFFFF8031BD8125C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
6 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have 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:
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
rtwlane.sys (Realtek PCIE NDIS Driver 52490 27170, Realtek Semiconductor Corporation )
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 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.
BSOD Ecran Bleu SORTIE DE VEILLE, PC NEUF
dans Windows
Posté(e)
Delta et calisto06 merci de vos messages et
J'ai bien mis les pilotes de la carte graphique à jour en suivant la procédure du lien. Mais j'ai toujours des plantages.
Calisto06, je ne peux pas modifier les paramètre du mode : J ai un message indiquant : "les informations de votre mode de gestion de l'alimentation ne sont pas disponibles".
Je vais faire tourner le PC qques jours en mode sans échec pour voir.
Merci encore pour votre aide.