Je viens vers vous pour avoir de l'aide concernant des BSDO sur mon asus tuf A15.
Presque dès le début de son achat il y a 1 an environ, j'en ai toujours eu mais étrangement jamais lorsque je jouais et de plus assez rarement. Donc finalement cela ne me déranger pas plus que ça car j'utilise majoritairement cet ordi pour le jeu.
J'ai remarqué que les BSOD ont souvent lieu lorsque je télécharge un jeu sur Steam par exemple ou que je suis sur firefox en navigation sur internet.
Depuis 2 /3 jours j'ai décidé de chercher les causes plus sérieusement et d'essayer de régler ça.
Donc j'ai lu pleins de dossiers sur Malekal et j'ai suivis les recommandations / test à effectuer.
D'ailleurs bravo pour votre site qui est une mine d'infos bien expliquée pour les débutants comme moi !
D'abord voici le rapport Whocrash :
Code : Tout sélectionner
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------
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: LAPTOP-H3A9AIJP
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: ASUS TUF Gaming A15 FA506IV_TUF566IV, ASUSTeK COMPUTER INC., FA506IV
CPU: AuthenticAMD AMD Ryzen 7 4800H with Radeon Graphics 8664, level: 23
16 logical processors, active mask: 65535
RAM: 16556584960 bytes (15,4GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 30/01/2022 12:32:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013022-27281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x0, 0xFFFFF8026E678026, 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 Sun 30/01/2022 12:32:26 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+0x400EF)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x0, 0xFFFFF8026E678026, 0x2)
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 Sun 30/01/2022 09:19:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013022-27875-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF803414A20F0)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF803414A20F0, 0x0, 0xFFFFF8034101)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 30/01/2022 03:49:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013022-9046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0xFC (0xFFFFEE60041542F0, 0x81000003F7966863, 0xFFFF8A0D8AF08F80, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
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 30/01/2022 02:07:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013022-9093-01.dmp
This was probably caused by the following module: rtwlane.sys (0xFFFFF803A71B58E8)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFF000, 0x2, 0x8, 0xFFFFF803A71B58E8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\rtwlane.sys
product: Realtek PCIEWireless LAN PCI-E NIC
company: Realtek Semiconductor Corporation
description: Realtek PCIE NDIS Driver 89512 39686
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: rtwlane.sys (Realtek PCIE NDIS Driver 89512 39686, Realtek Semiconductor Corporation ).
Google query: rtwlane.sys Realtek Semiconductor Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 30/01/2022 02:00:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013022-9031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0xA (0x20, 0x2, 0x1, 0xFFFFF80675A9A36E)
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.
--------------------------------------------------------------------------------
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:
rtwlane.sys (Realtek PCIE NDIS Driver 89512 39686, 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.
Depuis ces réinstallations, j'ai encore des BSDO mais étrangement sans aucun dump files. Ils n'apparaisent pas/plus dans l'analyse Whocrash ...
Le dernier BDSO date de ce matin avec le code d'arrêt" Page fault in nonpaged area" et a eu lieu lorsque j'ai lancé pour la première fois OCCT.. Parfois c'est aussi IRQL NOT LESS OR EQUAL.
J'ai donc stressé l'ordi avec OCCT, rien n'est resorti (enfin je crois, pas simple d'analyser tous ça ne connaissant pas grand chose à l'informatique...) J'ai regardé l'état de mes disques avec CrystalDiskInfo : rien à signaler.
J'ai fait un Memtest86 pendant plus de 3h30 (4 cycles) sur ma Mémoire, toujours pas erreur...
J'ai fait aussi le CHKDSK, rien à signaler.
Enfin j'ai regardé aussi l'observateur d'évènements et là j'ai vu que j'avais énormement d'erreurs critique : Kernel-power id 41. Depuis le 29 janvier par exemple de 5 à 13 erreurs critique par jours ! Par contre j'ai réussi a mettre en lien quelques une de ces erreurs critique entrainant parfois un black screen avec une autre erreur : Echec de l'audit "Microsoft Windows security audit" évènement 4625. Je n'ai pas la moindre idée de ce que c'est mais je vous donne l'info si jamais...
Comme vous pouvez le voir j'ai essayé de trouver la solution par moi même mais là je me perds de plus en plus dans toutes ces infos que je lis et j'ai beau avoir testé pleins de choses je n'arrive pas à résoudre ces crashs
Au moins depuis la réinstalations des pilotes je n'ai plus le très régulier BSDO ntoskrnl.exe et ntkrnlmp.exe (du moins pour l'instant..)
Il me reste peut être un reinitialisation / remise a zero de windows à faire ?
Pendant l'écriture de ce message j'ai eu 3 kernelpower id 41. Les trois semblant être liés à l'échec d'audit "Microsoft Windows security audit" évènement 4625 car cela a eu lieu en même temps (10 sec d'ecart). Le premier a provoqué un black screen j'ai dû reboot l'ordi, les deux autres BSDO IRQL NOT LESS OR EQUAL....
Désolé pour ce très long message, et merci d'avance pour les courageux qui vont tenter de m'aider. Je suis prêt à reprendre du début étape par étape toutes démarches que vous me poposerez !
Cordialement,
Drazg
