Display Driver Uninstaller (DDU) v18.1.0.0 causes GSOD in Safe Mode

[Almighty1]

I am having a problem with Display Driver Uninstaller (DDU) v18.1.0.0 under Windows 11 24H2 Build 26120.3585 Beta. It appears in Safe Mode when I have it set for GPU, Intel, Clean and Restart. It is causing a GSOD with the WIN32K_ATOMIC_CHECK_FAILURE error which appears to be consistent as it is doing it as part of the Cleaning process. DDU works fine in Regular mode all the way to the restart. In both instances, it is with the Internet disconnected.

[Wagnard]

I am having a problem with Display Driver Uninstaller (DDU) v18.1.0.0 under Windows 11 24H2 Build 26120.3585 Beta. It appears in Safe Mode when I have it set for GPU, Intel, Clean and Restart. It is causing a GSOD with the WIN32K_ATOMIC_CHECK_FAILURE error which appears to be consistent as it is doing it as part of the Cleaning process. DDU works fine in Regular mode all the way to the restart. In both instances, it is with the Internet disconnected.

If I understand correctly, it happen during the cleaning process. If so can you tell me at what part approximately ? straight at the beginning or more like at the registry cleanup or directory cleanup.

[Almighty1]

I am having a problem with Display Driver Uninstaller (DDU) v18.1.0.0 under Windows 11 24H2 Build 26120.3585 Beta. It appears in Safe Mode when I have it set for GPU, Intel, Clean and Restart. It is causing a GSOD with the WIN32K_ATOMIC_CHECK_FAILURE error which appears to be consistent as it is doing it as part of the Cleaning process. DDU works fine in Regular mode all the way to the restart. In both instances, it is with the Internet disconnected.

Is the issue appearing when you are cleaning or when you are restarting ?

Hard to say but I have to say it was cleaning because when I used DriverStore Explorer, there was still the 31.0.101.2134 Intel drivers in the system while earlier versions before that were gone. In the past when DDU in involved, there are usually no remains.

Have another question, when running DDU in Safe Mode, is run as Administrator needed? Thanks!

[Wagnard]

I am having a problem with Display Driver Uninstaller (DDU) v18.1.0.0 under Windows 11 24H2 Build 26120.3585 Beta. It appears in Safe Mode when I have it set for GPU, Intel, Clean and Restart. It is causing a GSOD with the WIN32K_ATOMIC_CHECK_FAILURE error which appears to be consistent as it is doing it as part of the Cleaning process. DDU works fine in Regular mode all the way to the restart. In both instances, it is with the Internet disconnected.

Is the issue appearing when you are cleaning or when you are restarting ?

Hard to say but I have to say it was cleaning because when I used DriverStore Explorer, there was still the 31.0.101.2134 Intel drivers in the system while earlier versions before that were gone. In the past when DDU in involved, there are usually no remains.

Have another question, when running DDU in Safe Mode, is run as Administrator needed? Thanks!

DDU required administrator yeah, but it should tell you if it's missing the right.

Can you zip the DDU logs folder (located within the DDU folder) and send it at [email protected] I'll give it a look just in case I see something.

[Wagnard]

Is the issue appearing when you are cleaning or when you are restarting ?

Hard to say but I have to say it was cleaning because when I used DriverStore Explorer, there was still the 31.0.101.2134 Intel drivers in the system while earlier versions before that were gone. In the past when DDU in involved, there are usually no remains.

Have another question, when running DDU in Safe Mode, is run as Administrator needed? Thanks!

DDU required administrator yeah, but it should tell you if it's missing the right.

Can you zip the DDU logs folder (located within the DDU folder) and send it at [email protected] I'll give it a look just in case I see something.

But for that sort of BOSD, if your system is overclocked (including memory) try to set it a default and see if the issue still happen)

[Almighty1]

Is the issue appearing when you are cleaning or when you are restarting ?

Hard to say but I have to say it was cleaning because when I used DriverStore Explorer, there was still the 31.0.101.2134 Intel drivers in the system while earlier versions before that were gone. In the past when DDU in involved, there are usually no remains.

Have another question, when running DDU in Safe Mode, is run as Administrator needed? Thanks!

DDU required administrator yeah, but it should tell you if it's missing the right.

Can you zip the DDU logs folder (located within the DDU folder) and send it at [email protected] I'll give it a look just in case I see something.

Just e-mailed it a minute ago as requested. Thanks!

[Almighty1]

Hard to say but I have to say it was cleaning because when I used DriverStore Explorer, there was still the 31.0.101.2134 Intel drivers in the system while earlier versions before that were gone. In the past when DDU in involved, there are usually no remains.

Have another question, when running DDU in Safe Mode, is run as Administrator needed? Thanks!

DDU required administrator yeah, but it should tell you if it's missing the right.

Can you zip the DDU logs folder (located within the DDU folder) and send it at [email protected] I'll give it a look just in case I see something.

But for that sort of BOSD, if your system is overclocked (including memory) try to set it a default and see if the issue still happen)

It's a Dell XPS 15 9570 notebook computer so the system is running stock as overclocking is not even possible as a option.

[Wagnard]

DDU required administrator yeah, but it should tell you if it's missing the right.

Can you zip the DDU logs folder (located within the DDU folder) and send it at [email protected] I'll give it a look just in case I see something.

But for that sort of BOSD, if your system is overclocked (including memory) try to set it a default and see if the issue still happen)

It's a Dell XPS 15 9570 notebook computer so the system is running stock as overclocking is not even possible as a option.

OK, I have an Asus laptop too with the same Intel driver installed. Ill give it a shot. Maybe its just a Dell software panicking when the GPU is removed. Ill let you know later today.

[Almighty1]

But for that sort of BOSD, if your system is overclocked (including memory) try to set it a default and see if the issue still happen)

It's a Dell XPS 15 9570 notebook computer so the system is running stock as overclocking is not even possible as a option.

OK, I have an Asus laptop too with the same Intel driver installed. Ill give it a shot. Maybe its just a Dell software panicking when the GPU is removed. Ill let you know later today.

I am using the generic Intel drivers as Dell latest driver is still the 27.xx even with the security fixes.

[Wagnard]

It's a Dell XPS 15 9570 notebook computer so the system is running stock as overclocking is not even possible as a option.

OK, I have an Asus laptop too with the same Intel driver installed. Ill give it a shot. Maybe its just a Dell software panicking when the GPU is removed. Ill let you know later today.

I am using the generic Intel drivers as Dell latest driver is still the 27.xx even with the security fixes.

I emailed you a test version for new logs.