Windows 10: Discuss the uses of 'registry cleaners', 'disk cleaners', 'optimizers'

I just did a fast search and I found this:
What is the dxgkrnl.sys file?

HTH

 

Thanks BunnyJ,
Nothing new to be learned there unfortunately. I know what dxgkrnl.sys is and that it gets loaded in or put on the system files by a variety of programs, however the question I keep asking and which almost seems like asking a FreeMason in house secrets is. What and how is driving the loading of that file? And so far nobody knows or is willing to say.
All I know is I have up to 6 versions on my system, with file sizes ranging from 250Kb to 1.9Mg and as it so happens it tries to load 6 times at final booting and fails 5 times. So what the heck is driving that repeated loading? And not even consistently either as each log file shows a differing order for when files are loaded.
It remains a mistery and seemingly a MS secret that those that know won't share with the world.

Frustratingly yours

 

It's a DirectX driver file and if you don't need or use DirectX you can uninstall it. There are instructions on how to do this in that link.

 

And this is a challenging comment. Judgemental at the same time. Moreover, this question does not fit in the discussion of the current thread. You should have made a separate thread for this question. Still we can try to answer to your question provided you provide adequate information.

Bootlogging is enabled for troubleshooting. That means, if bootlogging is enabled, there is a trouble. What is it? The behavior of the driver is highly influenced by the nature of the issue. We need to know the issue it at first.

Boot logging creates a file, ntbtlog.txt. Collect it and upload it here. It will tell us what is actually going on.

Till now we dont have any of the basic information. At that point we can only the basic thing. That is, If you are running the computer in safe mode, none of the DirectX components including dxgkrnl.sys will load at all.
But if it happens in normal mode, then there is some issue relating to the display environment (which contains a lot of hardware, software and environmental variables; DirectX is almost never the main soure of the issue reported to be caused by it).
After that, troubleshooting may be started, but definitely in a different thread. Create a new one, give me the link to that one.

We are neither interested nor responsible for the activities of the other forums.
Right direction for you is, create a new thread. Explain the issue properly, attach the Ntbtlog.txt file (will be found in C drive), give me a link.