bonjour
 
tout est a jour...voici un rapport de whocrashed =
 
 
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------
 
 
 
 
 
 
 
 
 
 
 
Computer name: DESKTOP-S0U8JG9
Windows version: Windows 10, 10.0, version 2009, build: 19044
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., H110I-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz 8664, level: 6
4 logical processors, active mask: 15
RAM: 16465944576 bytes (15,3GB)
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\WINDOWS
C:\WINDOWS\Minidump
 
On Tue 22/03/2022 15:38:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032222-35062-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80386CFD617)  
Bugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF80386CFD617)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.  
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 Tue 22/03/2022 15:38:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: gdwfpcd64.sys (gdwfpcd64+0x5C48)  
Bugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF80386CFD617)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\gdwfpcd64.sys
product: G DATA Security Software
company: G DATA Software AG
description: G DATA WFP Callout Driver (10.0)
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: gdwfpcd64.sys (G DATA WFP Callout Driver (10.0), G DATA Software AG).  
Google query: gdwfpcd64.sys G DATA Software AG DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
2 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:  
 
gdwfpcd64.sys (G DATA WFP Callout Driver (10.0), G DATA Software AG)
 
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 restauré le systeme en janvier...ccleaner + zhpcleaner = fait...gdata total sécurity , licence = aucun virus.....
 
j'ai des bsod 10 a 15 fois/mois...
 
je suis désespéré    
 
 
 
 

C'est GData qui provoque le plantage de ton PC.
Essaye de le réinstaller.