When the reality is more cpu/memory usually cleared things up. In the old times a good defrag did not hurt either.
People blame themselves when a lot of the time it is rubish software/hardware.
Then you have the other side of that coin. The yes clickers. If it asks a question just answer it however you need to do for whatever it is you wanted to work. Surprising number of dark patterns on that gem... Then they hand it to you and expect a miracle in 5 mins. Sorry this is the first time I have every seen something like this it may take me a few mins to figure out what is wrong before I can even begin to fix it.
Oh yeah, like when I have to fix the smartphones of people who have been using them for years while I do not own or use a smartphone. I will fix it, but I've got to learn how to launch/exit an application first ;-)
Many people (hi mum!) are surprised that you may take a few minutes to calmly observe, probe, assess, read and think a bit before engaging in the actual fixing. It never occurred to them that one may do something else than clicking, more or less randomly and as fast as possible, when something shows up. And do not worry about your example altering their future behaviour, it will unshakeably go on as it always went :-)
But that phone ran an Android version from before Google started seriously cracking down on apps running background services without restrictions. Modern Android is pretty robust in this regard — with a few exceptions, an app can't run in the background without showing a notification ("foreground service" is how the API calls it).
There wasn't much self-blame. She just assumes that technology is like that, complicated, unreliable, slow, and full of magic. It's nice when it works, but not a huge loss when it doesn't. She would also indefinitely quietly put up with things not working until someone asks and finds out, then I'd fix it.