Le rapport WHOCRASHED (alors le plantage du 30 a eu lieu dans des conditions étranges lors d'un essai de mise en veille profonde, alors que j'avais l'outil 'verifier' qui tournait - je ne suis pas sûr qu'il soit représentatif de mon soucis!)
Comme tu peux constater les BSOD ne sont pas légion. Ca arrive de temps en temps sans que j'ai réussi à identifier une séquence de reproduction. Ce qui est certain c'est qu'à chaque fois le PC était en Veille (écran éteint).Depuis le 29,à part le cas "spécial" du 30, je n'ai pas eu de nouveau BSOD.
Note: Je n'ai qu'un MEMORY.DMP (le dernier). Je n'ai pas pensé à les archiver, et ils sont écraser à chaque crash.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 7.06
--------------------------------------------------------------------------------
WhoCrashed is a comprehensible crash dump analyzer. It analyzes the system crashes of your computer or a remote computer on the network.
If your computer has displayed a blue (or black) screen of death or rebooted suddenly then your system may have crashed because of a malfunctioning device driver or because of a hardware failure. WhoCrashed will go to great lengths to help you find the root cause of the problem and a solution if available. It will analyze the crash dump files on your system or a system on the network with the single click of a button. In case the problem is caused by a malfunctioning driver, it will tell you what drivers are likely to be responsible for crashing your computer. In case of a hardware failure, it will tell you the most likely root cause and how to fix the problem.
When the analysis process is complete, WhoCrashed will write a report that offers suggestions on how to proceed in any situation, including internet links which will help you further troubleshoot any detected problems.
WhoCrashed will do great efforts to find out why your system crashed and what can be done to remedy the problem.
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: NEWKATELL
Windows version: Windows 11, 10.0, version 2009, build: 22635 (x64)
Windows dir: C:\WINDOWS
Hardware: VivoBook S15 X530UN, ASUSTeK COMPUTER INC., X530UN
CPU: GenuineIntel Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz 8664, level: 6
Processor count: 8 logical processors, active mask: 255
RAM: 16266.6MB
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 30/05/2024 15:53:55 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\053024-17781-01.dmp (Minidump)
Bugcheck code: 0xCE(0xFFFFF802BD1C64D0, 0x10, 0xFFFFF802BD1C64D0, 0x2)
Bugcheck name: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Driver or module in which error occurred: Netwtw06.sys (Unloaded_Netwtw06.sys+0x1264D0)
Description: Intel® Wireless WiFi Link Driver
Product: Intel® Wireless WiFi Link Adapter
Company: Intel Corporation
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. 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:
Netwtw06.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Netwtw06 Intel Corporation DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Thu 30/05/2024 15:53:55 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0xCE(0xFFFFF802BD1C64D0, 0x10, 0xFFFFF802BD1C64D0, 0x2)
Bugcheck name: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Driver or module in which error occurred: Netwtw06.sys (Unloaded_Netwtw06.sys+0x1264D0)
Description: Intel® Wireless WiFi Link Driver
Product: Intel® Wireless WiFi Link Adapter
Company: Intel Corporation
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. 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:
Netwtw06.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Netwtw06 Intel Corporation DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Wed 29/05/2024 15:41:05 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\052924-108406-01.dmp (Minidump)
Bugcheck code: 0xEF(0xFFFFD783F46C4140, 0x0, 0xFFFFD783F46C4140, 0x0)
Bugcheck name: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Tue 28/05/2024 15:50:03 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\052824-113359-01.dmp (Minidump)
Bugcheck code: 0xEF(0xFFFFB48CF9B16100, 0x0, 0xFFFFB48CF9B16100, 0x0)
Bugcheck name: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
On Sat 25/05/2024 12:01:06 your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\052524-22984-01.dmp (Minidump)
Bugcheck code: 0x3B(0xC0000006, 0xFFFFF805682A6BF2, 0xFFFFFC8C6AD26290, 0x0)
Bugcheck name: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 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:
netwtw06.sys (Intel® Wireless WiFi Link Driver, Intel 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 suggestions displayed in the bugcheck analysis above.
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.
The analysis process took 0:00:16 (h:mm:ss).
).