BSOD au démarrage

Signaler
Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020
-
Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020
-
Bonjour/bonsoir,

J’ai fait des mises à jour Windows il y’a trois jours et tous se passait bien jusqu’à hier en sortant mon pc d’une mise en veille.

J’ai eu un redémarrage suivi d’un BSOD. J’ai tout de suite regardé sur Driver Booster l’état de mes pilotes et je les mis à jour (rien de bien méchant)
Après la maj de ces pilotes mon ordi à redémarré avec un joli écran bleu où on pouvait lire : « Critical process died ». Le BSOD en question s’affiche au démarrage et m’empêche donc d’ouvrir le bureau.

J’ai tenté dans un premier temps un point de restauration mais j’ai eu un bsod en plein chargement, je relance la machine pour refaire une récupération et mon point de restauration a disparu et il est impossible de supprimer les mises à jour de qualité.
Je lance donc une réinitialisation de mon pc mais Windows n’y arrive pas. Je me décide alors de réinstaller Windows avec une clé bootable, la réinstallation se passe bien, une fois sur le bureau je lance Windows Update et paf un nouveau bsod et cette fois ci avec un nouveau stopcode : « IRQL NOT LESS OR EQUAL »

J’ai testé mes deux barrettes de ram en les changeant de slot en vain. Et j’ai eu un nouveau BSOD (encore) : « System Exception not handled ».

J’aimerai bien vous faire un rapport sur WhoCrashed mais comme je l’ai dit, je n’arrive pas à accéder à mon bureau même en mode sans échec.

Je commence à être cours d’idée et j’ai surtout l’impression d’avoir fait pire que mieux :). C’est pourquoi je vous demande votre avis et votre aide ! Merci d’avance !

En espérant que vous ayez survécu à mon pavé je vous souhaite une bonne soirée/bonne journée

Ma config (moins d'un an)

Carte mère : Aorus B450 pro
CPU : AMD Ryzen 5 3600 X
Carte Graphique : Geforce RTX 2060 super
Alim : Corsair VS650
SSD : LDLC F8 Plus M.2 2280 PCIE NVME 480GB
RAM : DDR4 2400MHz 8g(x2)
BIOS : Version F41 (compatible avec mon cpu sur le site Gigabyte)




Configuration: Windows / Firefox 79.0

7 réponses

Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020

Bon de mon côté ça avance un peu, j'ai pu avoir accès à mon bureau et à lancer memtest mais il n'a rien trouvé d'anormal (je pensais que le problème venait de ma RAM vu que mes stopcodes sont différents), j'ai donc lancer une analyse sur Whocrashed :

Welcome to WhoCrashed (HOME EDITION) v 6.65


This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice


This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)


Computer name: DESKTOP-TB02JHJ
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: B450 AORUS PRO, Gigabyte Technology Co., Ltd., B450 AORUS PRO-CF
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17105780736 bytes (15,9GB)



Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 04/09/2020 18:33:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090420-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x295F6B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF80510895F6B, 0xFFFFEF88432A3288, 0xFFFFD800675C6920)
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 Fri 04/09/2020 18:33:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rtwlane_13.sys (rtwlane_13+0x3470E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000096, 0xFFFFF80510895F6B, 0xFFFFEF88432A3288, 0xFFFFD800675C6920)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rtwlane_13.sys
product: Realtek PCIEWireless LAN PCI-E NIC
company: Realtek Semiconductor Corporation
description: Realtek PCIE NDIS Driver 28199
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: rtwlane_13.sys (Realtek PCIE NDIS Driver 28199, Realtek Semiconductor Corporation ).
Google query: rtwlane_13.sys Realtek Semiconductor Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Fri 04/09/2020 17:25:11 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090420-3281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0xA (0x84B8, 0x2, 0x0, 0xFFFFF80121C248A8)
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 Fri 04/09/2020 17:06:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090420-3390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x50 (0xFFFFD60800000000, 0x2, 0xFFFFF8064E8256E0, 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 Fri 04/09/2020 17:05:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090420-3296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80270225A38, 0xFFFFF00429259C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\090420-3718-01.dmp



Conclusion


6 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

rtwlane_13.sys (Realtek PCIE NDIS Driver 28199, 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.

J'ai l'impression que c'est mon driver realtek qui fait merder mon pc, j'aurais besoin de votre avis s'il vous plaît.

Voila les nouvelles, je vous souhaite un bon week end !
Messages postés
180093
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
29 septembre 2020
22 159
Salut,

C'est le pilote de la carte Realtek qui plante effectivement.

C4est quelle mise à jour qui a été installée ?
Si c'est des mises à jour de qualité / Cumulative.
Désinstalle les, voir : https://www.malekal.com/desinstaller-mise-a-jour-de-windows/


Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020

Bonsoir

Merci pour ta réponse

Il y'a eu du nouveau après que j'ai posté ce message
J'ai réussi à mettre à jour mon pilote realtek depuis DriverCloud dans la soirée et mon ordi est devenu un peu plus stable, en revanche j'ai toujours des bsod mais qui cette fois ci semble venir de Nvidia.
Le nouveau stopcodes que j'ai à chaque BSOD est le : IRQL not less Or equal et l'élement ayant échoué : NVLDDMKM.SYS


J'ai donc refais une analyse WhoCrashed :


Welcome to WhoCrashed (HOME EDITION) v 6.65


This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice


This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)


Computer name: DESKTOP-TB02JHJ
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: B450 AORUS PRO, Gigabyte Technology Co., Ltd., B450 AORUS PRO-CF
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17125642240 bytes (15,9GB)



Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 06/09/2020 13:48:50 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!memset+0x967AA)
Bugcheck code: 0x50 (0xFFFFEE8000000000, 0x0, 0xFFFFF80123613BB8, 0xB)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Sat 05/09/2020 23:05:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090520-6109-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80051C9610F)
Bugcheck code: 0xD1 (0x3FFC17158C, 0x2, 0x0, 0xFFFFF80051C9610F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 452.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 452.06
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 452.06 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 05/09/2020 16:46:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090520-6281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x295F6B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF80637295F6B, 0xFFFF830013287288, 0xFFFFBF00411C6920)
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 Sat 05/09/2020 16:39:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090520-5093-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xE5E20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF8014422320C, 0xFFFFFD8B3BE89678, 0xFFFFA801AABC6920)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
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 Fri 04/09/2020 19:07:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090420-6171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x74 (0x2, 0xFFFF8B0A804C8A20, 0x2, 0xFFFFFFFFC000014C)
Error: BAD_SYSTEM_CONFIG_INFO
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 there is an error in the registry.
This bug check indicates there is a problem related to your registry.
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 corrupted:
C:\Windows\Minidump\090620-6125-01.dmp



Conclusion


6 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 452.06 , NVIDIA 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.



C'est donc un pilote Nvidia qui pose problème maintentant mais je ne sais pas lequel ni où le trouver.
Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020



Mon problème viendrait donc d'une de ces mises à jours ?
Ma version de Windows est : 2004 (version du système d'exploitation 19041.450) au passage
Messages postés
180093
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
29 septembre 2020
22 159
ha mais tu as eu plein de mise à jour Realtek... c'est surement l'une d'elle.
Désinstalle les.

et oui si pas mieux, faire une mise à jour des pilotes avec DriversCloud : Mettre à jour ses pilotes avec driversCloud
Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020



Je supprime la première je suppose ?
Messages postés
180093
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
29 septembre 2020
22 159
ha tu ne peux pas désinstaller les mises à jour de pilotes
Essaye un driverscloud comme indiqué précédemment.
ET si pas mieux, oui désinstalle la dernière mise à jour de Windows.
Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020

DriverCloud me dit que je suis à jour (pareil pour DriverBooster) je vais donc désinstaller la dernière mise à jour

Je te tiendrais au courant, merci pour tes conseils ;)
Messages postés
7
Date d'inscription
mardi 25 août 2020
Statut
Membre
Dernière intervention
6 septembre 2020

Bon... ça n'a pas marché, j'ai eu un bsod : Kernel Heap corruption