New
#41
When you install programs for a single user, that works fine. When utilities or software are installed for all users, they need to run as administrator. Some installers will ask you if want the software available for all users or a single user. I didn't keep your uploaded files showing the startups but, as I recall, some were system level but most were user level.Yes, you did suggest that the software could've been installed under a single user or in a user restricted folder. I replied that I didn't know how that could be since I installed most programs in program file folders. Anyway, that didn't lead to a solution.
You said the problem occurred when you clicked on programs and features. There was a call to a module within the stack I didn't immediately recognize. I also noticed the IObit driver being loaded. Nearly everyone on this site who has ever worked with dumps for any length of time will recognize IObit software. It's a prime suspect for system BSODs and/or program crashes. A single uninstall is the quickest way to eliminate known problem software.Why did you recommend that I uninstall the IObit uninstaller? What did you see in the minidump file I sent you that indicated that IObit uninstaller was the source of the problem?
The problem with simply suppressing the startup of software doesn't necessarily stop the loading of drivers for that software as already mentioned. And therein lies the problem since the drivers may have installed filters, or "hooks" as some of us old guys refer to them, that can still cause problems. And that's why I suggest suppressing all startups except those indicated. If the problem continues after that, there's no sense continuing and you have to start uninstalling software.I started the clean boot testing by disabling ASC in msconfig / services but Explorer still crashes.
I'll send you a PM on another mater.