On Thu, 11/14/2024 9:42 PM, Ant wrote:
OMG! MS finally fixed the annoying StartMenuExperienceHost.exe crashes
with https://www.reddit.com/r/Windows10/comments/1grc2k9/well_ill_be_damned_this_update_actually_fixed_the/Â .
I haven't noticed them too and my Start Menu hasn't reorganized my customizations before 11/12/2024's updates for over a couple days so
far. Crossing my antenna(e/s). ;)
It probably helps when influencers write articles about it.
https://www.edtittel.com/blog/startmenuexperiencehost-exe-knocks-relimon-over.html
To put your observation in perspective, the item in question is a
"High friction" item, and the problems will come back some day.
Just as a Windows Update could be slow, or the File Explorer could
develop a F5 Refresh bug. It's just the nature of the beast.
Or a Context Menu issue (newly added item affects stability).
Those are places you expect trouble.
When your icons start flying around on the taskbar, like tiny
birds, that's a symptom too of how the Task Bar is as stable
as quick sand. The root cause there, is some sort of memory issue,
but I don't know any more about it than that. It seems the thing
must have a static allocation of some sort, or a "thing" that
cannot expand on its own. The best thing to do if the icons
fly around, is click the desktop (not a flying icon), press alt-F4
and select "Reboot". If it's a transient case, that will be enough.
*******
I had actual crashes on my machine here (machine halts, no breadcrumbs),
but as near as I can determine, it's related to some sort of address map issue. I use a separate NIC card (an Intel), plus I have a cheap video card fitted, and the iGPU is turned off, and my Reliability Monitor has been clean for weeks.
That was enough changes to the hardware, for the symptoms to stop.
[Picture]
https://i.postimg.cc/jdm8vYTH/reliability-daily-driver-wallace.gif
But that was also a very expensive fix. The total cost, I won't go into, because I don't want to know what the total was. The machine has a different processor now. Testing reveals there is nothing wrong at all, with the
original processor, but I'm also not moving it back.
Yes, the Reliability Monitor is a dandy tool, but it also cannot help
if the crash type is "Halt". HALT is an instruction an Intel processor
can run. In this case, apparently no interrupts are raised because
as far as I know, you can escape from a Halt on a core, via an Interrupt
raised by hardware. Only a purposeful attempt to park the hardware,
results in what I was experiencing. Even the USB and PS/2 ports were
turned off (presumably so I could not wake the system by banging on the keyboard).
Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)
