Tellus

Yeah i have tried earlier drivers still with the exact same result, this is however not limited to Aida, HWiNFO64 behaves in a similar way and so does other cpu/mb HW monitoring SW as well. Some from the HWiNFO side (their users) claim its due to polling of a bus frequency that freaks out software in 1803 but if there is any truth to that i don't know. For now i'm using no HW monitoring at all and everything is running perfectly with no issues at all regardless of videodriver but as soon as i run some kind of HW monitoring for cpu/mb it freaks out regardless of video driver. I have even had this exact same behavior with an intel gpu on a different system. Bit sad though since i even purchased a new license for aida just to see if an upgrade helped but obviously it didn't. A sure fire way to get this lockup is to run chrome and browse the web for a while, places like facebook (i know, i know...) seem to speed up the frequency of events, this while using monitoring SW Edit: Tried to disable "periodic polling" under "CPU clock measurement" in HWiNFO64 and it stopped the crashing.

Having the same issue here, aida64 will crash experience shell host & desktop window manager. Older video drivers do not help and there is no error message from aida64 itself. Running windows 1709 this does not happen but in 1803 it does. Edit: Running the following hardware; GTX 1080 R7 1800x Asrock x370 Professional gaming with P4.40 PinnaclePi uefi 2x8GB Corsair Vengeance b-die DDR4 Multiple SSD's Cleaning up video drivers with DDU does not help either, only thing that prevents the crashing is not running Aida64 at all. The only error message i can dig up is the following from event viewer; Event 4101 Display driver nvlddmkm stopped responding and has successfully recovered.