Windows 10 not playing nice...
Jun. 5th, 2016 11:00 amStaying connected to the network all the time has the downside of letting Microsoft have its way with my operating system and working tools (Office). As a result, I end up not having the slightest idea of what might be the cause of a problem, and since the "fixes" offered by Microsoft often are too arcane even for me... well... there's little to do other than grit one's teeth.
The latest "fun 'n games" started a couple of weeks ago, with Windows 10 showing me a sad face emoticon upon shutdown, further informing me that a problem has been found, but that I shouldn't worry, because information was being collected, whereupon the system would go ahead and restart for me.
Did I mention I was shutting the machine down? Sure I did. So why does Microsoft propose restarting my machine?
It turns out it doesn't matter, because several hours after informing me that the information-collection effort was complete, the machine had not restarted, requiring me to shut it down hard, with the old hold-my-finger-on-the-power-button trick.
That said, Microsoft does try to be helpful, by letting you know what error you might want to learn more about. Over the course of several days, I was informed of the following errors:
Or better yet, figure out how to fix it and Make. It. Stop.
I would be... grateful.
The latest "fun 'n games" started a couple of weeks ago, with Windows 10 showing me a sad face emoticon upon shutdown, further informing me that a problem has been found, but that I shouldn't worry, because information was being collected, whereupon the system would go ahead and restart for me.
Did I mention I was shutting the machine down? Sure I did. So why does Microsoft propose restarting my machine?
It turns out it doesn't matter, because several hours after informing me that the information-collection effort was complete, the machine had not restarted, requiring me to shut it down hard, with the old hold-my-finger-on-the-power-button trick.
That said, Microsoft does try to be helpful, by letting you know what error you might want to learn more about. Over the course of several days, I was informed of the following errors:
- BAD POOL CALLER
- KMODE EXCEPTION NOT HANDLED
- IRQ NOT LESS OR EQUAL
- REFERENCE BY POINTER
- UNEXPECTED KERNEL MODE TRAP
Or better yet, figure out how to fix it and Make. It. Stop.
I would be... grateful.