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

[britechguy]

@Markverhyden

It goes back way further than that. At least back to February. I am in the process of removing Freedom Scientific Fusion at the moment, which is their JAWS screen reader and ZoomText specialty magnification software "rolled into one." I installed that around the 20th of January, and the problems seem to me to have started very shortly afterward.

The vast majority of the time the failures are with ntoskernel.

Once it's gone and I have had a few days to test, I'll report back.

 

[britechguy]

@Phillipe

The SSD passes Gsmartcontrol checks, too.

 

[Markverhyden]

@Markverhyden

It goes back way further than that. At least back to February. I am in the process of removing Freedom Scientific Fusion at the moment, which is their JAWS screen reader and ZoomText specialty magnification software "rolled into one." I installed that around the 20th of January, and the problems seem to me to have started very shortly afterward.

The vast majority of the time the failures are with ntoskernel.

Once it's gone and I have had a few days to test, I'll report back.

That time frame was lacking earlier. As I mentioned earlier I'd give a new profile a try before doing all that uninstalling.

 

[britechguy]

@Markverhyden

I needed to do that uninstalling for Fusion anyway, as version 2023 is now out, and I can report a distinct difference in behavior with Fusion now uninstalled.

Before, at Restart, for those using verbose options all of the stuff like the first Restarting, shutting down services, etc., would show up and about at the normal pace, but when the second instance of Restart and its swirling dots returned there would always be a freeze, and a very long one, where the system was still powered up but nothing was on the screen and no disc activity would be detected. Eventually I'd get the BSOD, but it took ages. Now, without Fusion, that "interminable wait" has gone away, and I am getting some BSODs (sans the actual BS, which always appears when ntoskrnl.exe is involved) from msgpioclx.sys.





I'm holding off on installing Fusion 2023 pending more experimentation.

And I'd like to be absolutely clear about what you mean by "new profile." Are you meaning create a new Win11 user to see if the behavior persists with it?

 

[trevm999]

Similar to trying with a new Windows profile, you could set up a bootable external drive with Windows and install the latest partches to see I'd you can replicate the issue still on the hardware, or if it's just how you system is currently set up.

 

[Fred Claus]

This is getting way about my expertise. But it's a good conversation, I'm learning a lot.

 

[NviGate Systems]

I'd be genuinely curious if you migrated to an Intel platform if it would stay as is or still blue screen.

You may have proverbially found the "needle in the haystack" system that 11 really struggles with.

 

[Markverhyden]

And I'd like to be absolutely clear about what you mean by "new profile." Are you meaning create a new Win11 user to see if the behavior persists with it?

Correct. I'll tend to do that when the cause of an issue is nebulous

 

[Philippe]

What about testing in safe mode?
(msgpioclx.sys -> drivers problem)

 

[britechguy]

What about testing in safe mode?
(msgpioclx.sys -> drivers problem)

I haven't, yet. But the question still is: which driver?

@Markverhyden: I've got several other accounts already on this machine for testing purposes that are very seldom used. Would testing with any of them be sufficient, or do I definitely need to create a brand spanking new account? If the latter, is there any reason to prefer local over MS-Account-linked?

 

[britechguy]

You may have proverbially found the "needle in the haystack" system that 11 really struggles with.

True, but my question is: Why now?

I would have expected an issue such as this one to present very early on, not after months of "smooth as silk" use. Because it so frequently (not always, but frequently) is also accompanied by AMD Radeon issue reporting being triggered upon restart, there's clearly at least some link to the AMD Radeon drivers, but what?

I'll soon try seeing if this happens in other accounts on the machine, or just mine. If it turns out it's a "just mine" then I'll create a brand new account and FABS my existing data over to it then nuke the original.

 

[nlinecomputers]

I suspect that Fusion software is the whole cause and like many Windows software it probably didn't fully uninstall all of its drivers.

 

[nlinecomputers]

I'm betting that if you N&P and don't load the fusion software all your problems will go away.

 

[britechguy]

I'm betting that if you N&P and don't load the fusion software all your problems will go away.

Which might be true, but based on all the other software I have and tweaks I've made over the years, a N & P is just not in the cards.

Just like many clients, I just do not want to face having to "rebuild my Windows world from scratch."

Were I to do something like an N & P it would probably be restoring my last Win 10 system image after having Fabs off my current data, then doing the "unauthorized upgrade" again.

But I'm still not there yet, either. For me there's value in pursuing this because I feel that I will likely see something similar "in the wild" at some point and if there's a way to solve it short of a N & P I'd like to know what it is.

This is a short list of why I didn't just N & P in the first place.

 

[britechguy]

@Markverhyden: Winner, winner chicken dinner!

I just logged in and shut down from a local account and another MS-Account-linked account on this machine and neither is triggering any BSOD. That pretty much confirms for me that this is a corrupt account profile issue of some sort or else what I've been seeing with BSODs should not be isolated to one account.

It now also makes me wonder if the attempts at an in-place repair install of Windows 11 was failing because I was using the profile that's had the BSODs for several months. That was part of what I was hoping it might fix, not having any inkling that it might be connected just to a single user on the machine.

I don't know whether I'll get to it today, but sometime over the next few it will be a "fabs off the data," nuke the account that BSODs from the second admin account that I have on this machine, then re-create that account again from scratch and "fabs on the data."

 

[Philippe]

But the question still is: which driver?

You may want to check which drivers are loaded by your "corrupted" profile.

DriverView: Loaded Windows Drivers List

 

[nlinecomputers]

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

 

[Markverhyden]

@Markverhyden: Winner, winner chicken dinner!

I just logged in and shut down from a local account and another MS-Account-linked account on this machine and neither is triggering any BSOD. That pretty much confirms for me that this is a corrupt account profile issue of some sort or else what I've been seeing with BSODs should not be isolated to one account.

It now also makes me wonder if the attempts at an in-place repair install of Windows 11 was failing because I was using the profile that's had the BSODs for several months. That was part of what I was hoping it might fix, not having any inkling that it might be connected just to a single user on the machine.

I don't know whether I'll get to it today, but sometime over the next few it will be a "fabs off the data," nuke the account that BSODs from the second admin account that I have on this machine, then re-create that account again from scratch and "fabs on the data."

LOL!!! Haven't heard that one in ages. Before continuing I'd make sure to launch every program you have in a "good" then try reboots. Remember that virtually every single program loads local account settings from the user hive and well as various folders. You may not have done that recently in the account. And remember that Fabs brings over the good, the bad and the ugly. So it may be possible that Fabing over y our active profile might bring the problem(s) as well.

 

[britechguy]

Before continuing I'd make sure to launch every program you have in a "good" then try reboots.

Which I definitely will do now that you mention it. I'll use the other MS-Account-linked admin account and open the various programs that I routinely use under this main account and see if that changes anything. I may try doing it "in batches" but one by one would likely drive me to distraction (though I may try that) before each Restart to see if there is a specific trigger I can zero in on.

Right now I'm in the process of Fabs-ing off everything, so at least it will be sitting there for me. Since there's 518 GB of data it will take a while.

 

[Philippe]

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

Neither do I.
But bad profile -> BSOD is strange, but it looks like it's working...