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

[Almighty1]

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.

Just responded by email after running in Safe Mode it did complete all the way to restart this time. I am on Windows Professional 24H2 Build 26120.3653 Beta now.

[Wagnard]

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.

Just responded by email after running in Safe Mode it did complete all the way to restart this time. I am on Windows Professional 24H2 Build 26120.3653 Beta now.

Ah Insider preview. Probably a microsoft issue than.
I'll still check the logs tomorrow but note that this is a beta OS so things like that are to be expected.

[Almighty1]

I emailed you a test version for new logs.

Just responded by email after running in Safe Mode it did complete all the way to restart this time. I am on Windows Professional 24H2 Build 26120.3653 Beta now.

Ah Insider preview. Probably a microsoft issue than.
I'll still check the logs tomorrow but note that this is a beta OS so things like that are to be expected.

Yes, since the newer build works fine. What was weird was when the problem happened, it only happened in Safe Mode, didn't know people get BSOD's in Safe Mode.

[Wagnard]

Just responded by email after running in Safe Mode it did complete all the way to restart this time. I am on Windows Professional 24H2 Build 26120.3653 Beta now.

Ah Insider preview. Probably a microsoft issue than.
I'll still check the logs tomorrow but note that this is a beta OS so things like that are to be expected.

Yes, since the newer build works fine. What was weird was when the problem happened, it only happened in Safe Mode, didn't know people get BSO's in Safe Mode.

Yeah as weird as it sound, safe mode can BSOD. For your logs, from what I see there is something wrong with the permission of "C:\ProgramData\Intel\" or one if the directories in it as DDU returned an access denied on the operations done in this folder.
That permission error is not what made it crash at that moment but it could be a sign that you have other permission wrong elsewhere.

[Almighty1]

Ah Insider preview. Probably a microsoft issue than.
I'll still check the logs tomorrow but note that this is a beta OS so things like that are to be expected.

Yes, since the newer build works fine. What was weird was when the problem happened, it only happened in Safe Mode, didn't know people get BSO's in Safe Mode.

Yeah as weird as it sound, safe mode can BSOD. For your logs, from what I see there is something wrong with the permission of "C:\ProgramData\Intel\" or one if the directories in it as DDU returned an access denied on the operations done in this folder.
That permission error is not what made it crash at that moment but it could be a sign that you have other permission wrong elsewhere.

I think the hard part is figuring out which directory under it needs to be fixed.Not even sure how to fix this one since I need to figure out exactly which drivers created each directory under it as there is:
DAL,
DSA,
GCC,
GFXInstaller,
iCLS Client,
Installer,
IntelSGXPSW,
Logs,
PackageCache,
Uploader

since it's not as easy as deleting the entire C:\ProgramData\Intel folder but I would still need to figure out what Intel drivers created those directories.

[Wagnard]

Yes, since the newer build works fine. What was weird was when the problem happened, it only happened in Safe Mode, didn't know people get BSO's in Safe Mode.

Yeah as weird as it sound, safe mode can BSOD. For your logs, from what I see there is something wrong with the permission of "C:\ProgramData\Intel\" or one if the directories in it as DDU returned an access denied on the operations done in this folder.
That permission error is not what made it crash at that moment but it could be a sign that you have other permission wrong elsewhere.

I think the hard part is figuring out which directory under it needs to be fixed.Not even sure how to fix this one since I need to figure out exactly which drivers created each directory under it as there is:
DAL,
DSA,
GCC,
GFXInstaller,
iCLS Client,
Installer,
IntelSGXPSW,
Logs,
PackageCache,
Uploader

since it's not as easy as deleting the entire C:\ProgramData\Intel folder but I would still need to figure out what Intel drivers created those directories.

The intel folder itself could be the problem too.
You could try to boot into safe mode, rename the intel folder, create a new one manually, then copy the stuff that was in the old Intel folder in the new one.
If lucky, it may work. But who knows what other folders elsewhere on your system that could maybe not be configured correctly.

[Almighty1]

Yeah as weird as it sound, safe mode can BSOD. For your logs, from what I see there is something wrong with the permission of "C:\ProgramData\Intel\" or one if the directories in it as DDU returned an access denied on the operations done in this folder.
That permission error is not what made it crash at that moment but it could be a sign that you have other permission wrong elsewhere.

I think the hard part is figuring out which directory under it needs to be fixed.Not even sure how to fix this one since I need to figure out exactly which drivers created each directory under it as there is:
DAL,
DSA,
GCC,
GFXInstaller,
iCLS Client,
Installer,
IntelSGXPSW,
Logs,
PackageCache,
Uploader

since it's not as easy as deleting the entire C:\ProgramData\Intel folder but I would still need to figure out what Intel drivers created those directories.

The intel folder itself could be the problem too.
You could try to boot into safe mode, rename the intel folder, create a new one manually, then copy the stuff that was in the old Intel folder in the new one.
If lucky, it may work. But who knows what other folders elsewhere on your system that could maybe not be configured correctly.

That's why I said if I can figure out what created each of the above, then it's easier to basically axe the entire Intel folder and let the Intel drivers installers recreate them after a uninstall/reinstall. You are right that it's hard to figure out what is configured wrong but what user is DDU using to access the folders?

[Wagnard]

I think the hard part is figuring out which directory under it needs to be fixed.Not even sure how to fix this one since I need to figure out exactly which drivers created each directory under it as there is:
DAL,
DSA,
GCC,
GFXInstaller,
iCLS Client,
Installer,
IntelSGXPSW,
Logs,
PackageCache,
Uploader

since it's not as easy as deleting the entire C:\ProgramData\Intel folder but I would still need to figure out what Intel drivers created those directories.

The intel folder itself could be the problem too.
You could try to boot into safe mode, rename the intel folder, create a new one manually, then copy the stuff that was in the old Intel folder in the new one.
If lucky, it may work. But who knows what other folders elsewhere on your system that could maybe not be configured correctly.

That's why I said if I can figure out what created each of the above, then it's easier to basically axe the entire Intel folder and let the Intel drivers installers recreate them after a uninstall/reinstall. You are right that it's hard to figure out what is configured wrong but what user is DDU using to access the folders?

DDU run as administrator, but in most case it will use the "system" credentials to do it's things.

[Almighty1]

The intel folder itself could be the problem too.
You could try to boot into safe mode, rename the intel folder, create a new one manually, then copy the stuff that was in the old Intel folder in the new one.
If lucky, it may work. But who knows what other folders elsewhere on your system that could maybe not be configured correctly.

That's why I said if I can figure out what created each of the above, then it's easier to basically axe the entire Intel folder and let the Intel drivers installers recreate them after a uninstall/reinstall. You are right that it's hard to figure out what is configured wrong but what user is DDU using to access the folders?

DDU run as administrator, but in most case it will use the "system" credentials to do it's things.

Does it basically use TrustedInstaller?

Maybe this will fix things...
https://www.elevenforum.com/t/add-reset ... -11.21237/

[Wagnard]

That's why I said if I can figure out what created each of the above, then it's easier to basically axe the entire Intel folder and let the Intel drivers installers recreate them after a uninstall/reinstall. You are right that it's hard to figure out what is configured wrong but what user is DDU using to access the folders?

DDU run as administrator, but in most case it will use the "system" credentials to do it's things.

Does it basically use TrustedInstaller?

Maybe this will fix things...
https://www.elevenforum.com/t/add-reset ... -11.21237/

No it use really "system" for *most* things.