Anyone here a BSOD expert willing to take a gander at my logs?

Drivers are global. I can't see how a user profile would affect them.

Nor can I, but there is zero doubt that my local standard account and my other MS-Account-linked Win11 user account are not triggering BSODs when a Restart is done. I've even used BlueScreenView afterward to make absolutely sure that I was not getting one that might not have actually presented the blue screen, which has happened on occasion in the past.
 
As an aside and additional data point, I don't have any issue if I just log out from the account that's causing the BSOD on Restart and Restarting using a different account. I have yet to test this by just logging out of the account and doing a Restart on the lock screen.

I have taken the time to fire up all the programs on the desktop of the alternate MS-Account-linked Win11 user account that has admin privileges. I doubt I've hit everything that I ever use, but some things are so seldom used that I'll be damned if I could possibly remember every program, both portable and installed, that I've ever touched. Once the Fabs completes I'll log out of this account and back into that one and see if I get any change when doing a Restart.

Fabs is churning away and has snagged about 1/4 of my total data so far. Saving from an SSD to an HDD, even using USB 3.1, takes some time.
 
As an aside and additional data point, I don't have any issue if I just log out from the account that's causing the BSOD on Restart and Restarting using a different account. I have yet to test this by just logging out of the account and doing a Restart on the lock screen.

I have taken the time to fire up all the programs on the desktop of the alternate MS-Account-linked Win11 user account that has admin privileges. I doubt I've hit everything that I ever use, but some things are so seldom used that I'll be damned if I could possibly remember every program, both portable and installed, that I've ever touched. Once the Fabs completes I'll log out of this account and back into that one and see if I get any change when doing a Restart.

Fabs is churning away and has snagged about 1/4 of my total data so far. Saving from an SSD to an HDD, even using USB 3.1, takes some time.
Does this fusion app modify the login screen? I could see that happening if it was needed for the reader for the blind app. Such a thing could be tied to a user account as it might have options on who's account it is active on? Perhaps? Or do I not know what I speak off? LOL.
 
What goes on behind the scenes in any OS can be quite a mystery. My guess is that while the OS is terminating processes in preparation for the shutdown/reboot there's some global processes that handle many tasks, such as svchost.exe, that cause an issue. Since that's calling another program or DLL it's possible that is causing shutdown/restart to stop and then BSD. Normally we'll see errors about not being able to do something because of something else. But if it's close to the very end the messaging service may have already been terminated. My "theory" so to speak.
 
Does this fusion app modify the login screen?

That depends on what you mean by modify. Any screen reader can be set up to become active on the login screen, and that is a special setting because that's a secure screen. For the most part, it's not an issue, but Freedom Scientific/Vispero, the maker of Fusion, JAWS, and ZoomText does use a screen graphics driver of its own creation, and it was known to be problematic in the past.

But even now with the software gone, that didn't fix the issue with my primary Win11 user account and the BSODs.
 
What goes on behind the scenes in any OS can be quite a mystery.

You're telling me! That's one of the reasons I apply all updates. Those responsible for all the OS internals are the ones who are best positioned to know what needs to be updated, and when, to keep things working optimally. OS internals of any kind have never been my specialty. I, like you, have some very educated guesses about what's going on, but not enough knowledge, nor time to obtain it, to have definitive answers.
 
And I don't blame MS or Windows. It's the fault of sloppy programming of uninstallers that do not truly clean up after themselves. If an installer put it there the uninstaller should take it away!
Tell that to Avast/AVG and thousands of other programs.
Programming costs money. Writing an uninstall routine to completely remove an installed program is more expensive that just writing a few lines to remove references that a user can see.
Why do they care if stuff is left behind?
 
Tell that to Avast/AVG and thousands of other programs.

Uh, you're just listing examples of cautionary tales.

Writing an uninstaller should be no more challenging than writing the installer. I don't care how many sloppy companies are out there because there are plenty of examples of software houses that are thorough about cleaning up after themselves on uninstall. That's what EVERYONE SHOULD do; it's obvious that everyone doesn't do that.
 
Were these apps run on the non-crashing MS account? If so run DriverView in that account to see if they are loaded.

For the sake of complete clarity:

- The Fusion install/unintall occurred strictly on the account that was having the BSOD issues.

- That DriverView screenshot so happens to have been taken with the utility running on THE OTHER ACCOUNT. Now, mind you, I think I had logged in to "the bad account" and logged out before, so I imagine it was still loaded from there, but who knows. I'd have to try logging in only to the "good" account after a restart and seeing whether it's loaded then.
 
For the sake of complete clarity:
Just curious, when you did your initial insstall of Windows 11, did you upgrade or do a fresh install? I'm sure you may have mentioned it in the past when you posted about it but I can't recall.

It's unusual to have such an issue in a short time. The only possible explanation is if a program that isn't W11 certified may have been poking it's nose in the registry where it shouldn't have etc. I know Windows blocks certian apps from running where they know it's not compatible, but many apps can and do run and will mess things up.

Side story: That's why GPT has a protective MBR, to try and prevent non GPT aware utilities from messing with the disk. Sadly Windows doesn't have a protection mechanism like that.
 
@NviGate Systems

It was an in-place upgrade, as I have too much time and effort invested in all "the stuff" I have on the machine already to start again from scratch, even as far as only programs go.

I agree that something is really amiss here, and things kept "getting wonkier" so I finally decided there really is no point in throwing any more good effort after bad, and am restoring the system to an image I took at the beginning of April before all this mess started. I'll have to wait and see if it re-creates itself or not.
 
Did you try disabling the Fusion drivers??

No, there were other things I obviously "broke" along the way. When Windows Security started telling me that Virus & Threat Protection was "Managed by your organization" and no longer visible, that's when I bailed.

When things just keep falling apart, and unrelated to anything that seemed to have been falling apart, it's time to take a step back and take another tack.

If things fall apart again in a manner similar to what has already occurred previously, then this box will go back to Windows 10 and I'll Fabs my data back on afterward.
 
Back
Top