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.