Probleme de ports usb
Résolu
Usernovis
Messages postés
75
Date d'inscription
Statut
Membre
Dernière intervention
-
billmaxime Messages postés 50581 Date d'inscription Statut Contributeur Dernière intervention -
billmaxime Messages postés 50581 Date d'inscription Statut Contributeur Dernière intervention -
bonjour
j'ai un nouveau pc dell g15 sous windows 11 , mes ports usb ne fonctionnent pas correctement , des fois ils connectent pas mes disques dur externe je dois redemarrer le pc a chaque fois pour qu ils connectent mes disque dur , y a t il une solution a ce probleme
Merci
j'ai un nouveau pc dell g15 sous windows 11 , mes ports usb ne fonctionnent pas correctement , des fois ils connectent pas mes disques dur externe je dois redemarrer le pc a chaque fois pour qu ils connectent mes disque dur , y a t il une solution a ce probleme
Merci
A voir également:
- Sessapart.sys
- Clé usb non détectée - Guide
- Usb show - Télécharger - Sauvegarde
- Hp usb disk storage format tool - Télécharger - Stockage
- Formater clé usb - Guide
- Clé usb - Accueil - Stockage
17 réponses
salut
j'ai un nouveau pc dell g15 sous windows 11
comme le pc est neuf, je pense qu'il serait judicieux de le renvoyer au SAV
regarde quand même dans le Gestionnaire de périphériques si tu n'as pas d'alertes (? ou /!\) jaune
poste 1 capture d'écran de ton Gestionnaire de périphériques --> clique ici
@+
j'ai un nouveau pc dell g15 sous windows 11
comme le pc est neuf, je pense qu'il serait judicieux de le renvoyer au SAV
regarde quand même dans le Gestionnaire de périphériques si tu n'as pas d'alertes (? ou /!\) jaune
poste 1 capture d'écran de ton Gestionnaire de périphériques --> clique ici
@+
re
tu n'as pas d'alertes dans le gestionnaire de périphériques
tu as le souci sur tous tes ports USB?
tu as le souci avec n'importe quel DD externe?
@+
tu n'as pas d'alertes dans le gestionnaire de périphériques
tu as le souci sur tous tes ports USB?
tu as le souci avec n'importe quel DD externe?
@+
oui le problème est sur tous les port usb quand ils fonctionnent pas je dois redémarrer le pc et ils fonctionnent après
des fois quand ils bug j'ai un ecran bleu avec un pourcentage ,puis le pc redemarre
des fois quand ils bug j'ai un ecran bleu avec un pourcentage ,puis le pc redemarre
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
re
des fois quand ils bug j'ai un ecran bleu avec un pourcentage ,puis le pc redemarre
tu peux me donner le message?
si tu ne te souviens pas du message/code d'erreur, fais ceci:
télécharge et exécute WhoCrashed --> clique ici
poste le rapport via 1 copier/coller dans ta réponse
ton pc est bien sous W11, et n'a jamais été sous W10?
@+
des fois quand ils bug j'ai un ecran bleu avec un pourcentage ,puis le pc redemarre
tu peux me donner le message?
si tu ne te souviens pas du message/code d'erreur, fais ceci:
télécharge et exécute WhoCrashed --> clique ici
poste le rapport via 1 copier/coller dans ta réponse
ton pc est bien sous W11, et n'a jamais été sous W10?
@+
re
mon pc était sur windows 10
ok
exécute la manipulation avec WhoCrashed , et poste le rapport --> clique ici
si tu as des questions...
@+
mon pc était sur windows 10
ok
exécute la manipulation avec WhoCrashed , et poste le rapport --> clique ici
si tu as des questions...
@+
voici le rapport
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: MYPC
Windows version: Windows 10, 10.0, version 2009, build: 22000
Windows dir: C:\WINDOWS
Hardware: Dell G15 5510, Dell Inc., 0VKDJ6
CPU: GenuineIntel Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 16943685632 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11359-01.dmp
This was probably caused by the following module: sessapart.sy.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sy.sys .
Google query: sessapart.sy.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: sessapart.sys.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sys.sys .
Google query: sessapart.sys.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 12:57:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-15281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFF94811A7E2900, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
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 27/02/2022 12:37:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-14562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFFD80366AF8610, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 19:43:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF93857B3B4100, 0xFFFFF886CC86F700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 16:40:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF8006272D4040, 0xFFFFF801743B7700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 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:
sessapart.sy.sys
sessapart.sys.sys
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.
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: MYPC
Windows version: Windows 10, 10.0, version 2009, build: 22000
Windows dir: C:\WINDOWS
Hardware: Dell G15 5510, Dell Inc., 0VKDJ6
CPU: GenuineIntel Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 16943685632 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11359-01.dmp
This was probably caused by the following module: sessapart.sy.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sy.sys .
Google query: sessapart.sy.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: sessapart.sys.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sys.sys .
Google query: sessapart.sys.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 12:57:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-15281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFF94811A7E2900, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
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 27/02/2022 12:37:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-14562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFFD80366AF8610, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 19:43:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF93857B3B4100, 0xFFFFF886CC86F700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 16:40:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF8006272D4040, 0xFFFFF801743B7700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 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:
sessapart.sy.sys
sessapart.sys.sys
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.
Voici le rapport :
System Information (local)
--------------------------------------------------------------------------------
Computer name: MYPC
Windows version: Windows 10, 10.0, version 2009, build: 22000
Windows dir: C:\WINDOWS
Hardware: Dell G15 5510, Dell Inc., 0VKDJ6
CPU: GenuineIntel Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 16943685632 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11359-01.dmp
This was probably caused by the following module: sessapart.sy.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sy.sys .
Google query: sessapart.sy.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: sessapart.sys.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sys.sys .
Google query: sessapart.sys.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 12:57:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-15281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFF94811A7E2900, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
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 27/02/2022 12:37:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-14562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFFD80366AF8610, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 19:43:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF93857B3B4100, 0xFFFFF886CC86F700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 16:40:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF8006272D4040, 0xFFFFF801743B7700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 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:
sessapart.sy.sys
sessapart.sys.sys
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.
System Information (local)
--------------------------------------------------------------------------------
Computer name: MYPC
Windows version: Windows 10, 10.0, version 2009, build: 22000
Windows dir: C:\WINDOWS
Hardware: Dell G15 5510, Dell Inc., 0VKDJ6
CPU: GenuineIntel Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 16943685632 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11359-01.dmp
This was probably caused by the following module: sessapart.sy.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sy.sys .
Google query: sessapart.sy.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 13:02:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: sessapart.sys.sys (0xFFFFF804796E5EB0)
Bugcheck code: 0xCE (0xFFFFF804796E5EB0, 0x10, 0xFFFFF804796E5EB0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
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: sessapart.sys.sys .
Google query: sessapart.sys.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
On Sun 27/02/2022 12:57:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-15281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFF94811A7E2900, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
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 27/02/2022 12:37:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-14562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0xCA (0x2, 0xFFFFD80366AF8610, 0x0, 0x0)
Error: PNP_DETECTED_FATAL_ERROR
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 the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 19:43:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4164C0)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF93857B3B4100, 0xFFFFF886CC86F700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/02/2022 16:40:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022422-11562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416220)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF8006272D4040, 0xFFFFF801743B7700)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 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:
sessapart.sy.sys
sessapart.sys.sys
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.
je n'arrive pas a poster le rapport en faisant un copie coller
voici le lien : https://www.cjoint.com/c/LBBpEMleEW4
voici le lien : https://www.cjoint.com/c/LBBpEMleEW4
re
ok, fais ceci:
branche le pc sur le secteur
quitte tous tes programmes en cours
dans recherche, tape CMD et clique sur --> exécuter en tant qu'administrateur
dans la fenêtre qui s'ouvre, tape/copie-colle --> sfc /scannow
ATTENTION: il y a 1 espace entre sfc et/
laisse bosser le pc
à la fin du scan, regarde s'il a/n'a pas trouvé/réparé de fichiers système
si tu as des questions...
@+
ok, fais ceci:
branche le pc sur le secteur
quitte tous tes programmes en cours
dans recherche, tape CMD et clique sur --> exécuter en tant qu'administrateur
dans la fenêtre qui s'ouvre, tape/copie-colle --> sfc /scannow
ATTENTION: il y a 1 espace entre sfc et/
laisse bosser le pc
à la fin du scan, regarde s'il a/n'a pas trouvé/réparé de fichiers système
si tu as des questions...
@+
j'ai fait la commande j'ai ce message :
Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.
Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.
re
ok, dans le rapport de Whocrashed, je vois ceci:
Google query: sessapart.sys.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
ça peut être 1 pilote mal installé
fais ceci:
télécharge DriversCloud sur ton bureau --> clique ici
exécute le en tant qu'administrateur (clic droit)
poste l'URL de la page de recherche des pilotes via 1 copier/coller dans ta réponse en restant connecté sur DriversCloud
si tu as des questions...
@+
ok, dans le rapport de Whocrashed, je vois ceci:
Google query: sessapart.sys.sys DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
ça peut être 1 pilote mal installé
fais ceci:
télécharge DriversCloud sur ton bureau --> clique ici
exécute le en tant qu'administrateur (clic droit)
poste l'URL de la page de recherche des pilotes via 1 copier/coller dans ta réponse en restant connecté sur DriversCloud
si tu as des questions...
@+
voici l'URL demandé : https://www.driverscloud.com/fr/configuration/72670439-1/resume
voici la page des pilotes voici lien :https://www.driverscloud.com/fr/services/72670439-60/trouver-les-pilotes
voici la page des pilotes voici lien :https://www.driverscloud.com/fr/services/72670439-60/trouver-les-pilotes
re
l'URL est invalide pour les 2 liens... --> L'url www.driverscloud.com/fr/services/72670439-60/trouver-les-pilotes est invalide
tu dois être connecté sur Driverscloud quand tu postes l'URL de la page de recherche des pilotes
si tu as des questions...
@+
l'URL est invalide pour les 2 liens... --> L'url www.driverscloud.com/fr/services/72670439-60/trouver-les-pilotes est invalide
tu dois être connecté sur Driverscloud quand tu postes l'URL de la page de recherche des pilotes
si tu as des questions...
@+
