Logitech gaming software causes BSOD on Windows 7 x64 Ultimate

[DLz]

Hi, as the title says, everytime I start my PC for the first time, I get a BSOD due to logitech drivers. I'm sure that the problem are the drivers because without them I don't get any error or BSOD and everything works fine.
From the windows log event this is the first warning that is shown: Impossible to load the driver \Driver\WUDFRd for the device Root\WPD\0000.
I thinks this is the error that causes the BSOD. When the logitech software is not installed, I still get this error but i don't get the BSOD. The error is from the Kernel-PnP.
I would like to know if there is a solution, if anyone else with logitech gaming panel and windows 7 x64 ultimate has this problem and if this happens also on windows 10 x64 systems.
Thanks

- System
- Provider
[ Name] Microsoft-Windows-Kernel-PnP
[ Guid] {9C205A39-1250-487D-ABD7-E831C6290539}
EventID 219
Version 0
Level 3
Task 212
Opcode 0

Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2017-03-25T13:03:04.897609500Z
EventRecordID 19901

Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 52



Channel System
Computer DL

- Security
[ UserID] S-1-5-18
- EventData
DriverNameLength 13
DriverName Root\WPD\0000
Status 3221226341
FailureNameLength 14
FailureName \Driver\WUDFRd
Version 0

 

[ICIT2LOL]

Ok my friend please follow these
SYSTEM SPECS
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
*(pretyped to save time)
&

Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions

so that we have enough information to be going on.

Edit: I did mean to add that the \Driver\WUDFRd you referenced is not known to be a Logitec fault in particular but more likely to be a Windows update issue but we do need that other info first please.