Why does Windows 10 crash?

grumpycrab

islandman wrote: »

Thankfully, even though the screen blacks out and it then reboots, when it does return at least it is recognised by the message " because your system closed down etc......." you are given the option to return to where you left off or start with new page.

FYI, that's a feature of the browser that you use, not Windows10. Which is nice. I'm sure you've done this but will ask anyway - have you got the latest updates?

AndyPix

Nick_C wrote: »

Sounds like a giant leap backwards for Windows.

I bought a new laptop yesterday so have no experience of W10 yet, but I thought this sort of problem went away with XP.

7 and 8.1 were very stable.

As is W10 - But you arent going to get people starting threads saying "My windows 10 machine didnt crash last night" are you ..


Obviously people post when they have issues - same for 7 , 8.1 and any other version

Johnmcl7

Nick_C wrote: »

Sounds like a giant leap backwards for Windows.

I bought a new laptop yesterday so have no experience of W10 yet, but I thought this sort of problem went away with XP.

7 and 8.1 were very stable.

Windows 10 is no different to 7 and 8.1 for stability, any of them can crash or be unstable if there's faulty software (particularly drivers) or hardware but none of them are inherently unstable. I've used W10 on a variety of systems without issue bar one which had a faulty software driver which worked fine after that was resolved.

Biggles

grumpycrab wrote: »

Event 41 is "The system has rebooted without cleanly shutting down first" You may get these if you use "hibernate" but not a major issue provided you don't have unsaved work when hibernating. As already said, I've seen a couple of issues with older AMD computers - patches are out for these and should be automatically installed through Windows Update.

I've never used hibernate. I notice that the first 'Event 41' listed was 6 Jan, which is the same date it installed the first Windows Update of the year.

I'm presently running HP Diagnostics, if that fails I shall see if HP are helpful; much to my surprise, they've seemed very willing to help previously, though it's nearly two years old now.....

grumpycrab

Coincidentally (or not), I'm just going to see someone with a 1.5 year old Acer Aspire desktop where W10 has blown up (possibly proceeded by a registry error message).
EDIT: if anybody re-reads this; this was a mangled UEFI boot; first attempt to fix was to run a refresh (with keep data option) which I've used before from my own W10 media. But for some reason I couldn't work out(**) the refresh option was never available. So had to do a UEFI bootrec fix which is a horrible process. But it brought the system back to how it was.

(**) PC was pre-built with W10 UEFI; perhaps there's something about these pre-builts that prevents a refresh!?

System

grumpycrab wrote: »

FYI, that's a feature of the browser that you use, not Windows10. Which is nice. I'm sure you've done this but will ask anyway - have you got the latest updates?

I am prepared to change/try another browser, but which one I ask myself.

Prof_Green

Mine never crashed, well not if it booted up, however sometimes it would not boot which is a crash of sorts, the upgrades failed too.

in the end I found removing the wifi card cured all the problems.

So maybe trying running with minimum hardware and software installed?

Mind you I had a test, ie installing the update to see if it worked, waiting for a crash is not so instant of an indication.

Prof_Green

Johnmcl7 wrote: »

Windows 10 is no different to 7 and 8.1 for stability, any of them can crash or be unstable if there's faulty software (particularly drivers) or hardware but none of them are inherently unstable. I've used W10 on a variety of systems without issue bar one which had a faulty software driver which worked fine after that was resolved.

I notice a big different from 8.1 to 10 ie from no problems to lots of probs.
Removing video card seemed to cure it.

kwikbreaks

Mine's fine but i recall reading that the intel processor security patches were buggy and causing reboots and were being backed out/replaced. I'm by no means certain that they were issued but if they were then the reported faults fit in with what i read about them being buggy. If you are getting this problem then some research along that line and rolling out of any dodgy patch may fix it.

Update
This wasn't where i read it but suggests i didnt just dream it up...
https://www.cnbc.com/2018/01/18/intel-patches-are-causing-computers-to-randomly-restart.html

were

there are three possible intel vulnerability issues. Besides the the two listed there is the Intel SA-00086 Management agent bug too, but not applicable to all cpu's. https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00086&languageid=en-fr

Perhaps patching windows with updates drivers that various manufacturers roll out may help? Bios updates? Yes, clutching at straws, but you have to start somewhere. Reseat all the cables as heat creep could have dislodged some.

Sometimes you can fault find to the cows come home and still get nowhere. It becomes substitution time. If you have 8gb half it. If it still fails, take out the first half out and put in the second 4gb. Swap the disk... you may have a old manky one floating around?

You may have an old PSU you could swap, or use another computer's, if you have a desktop? Perhaps a friend has a spare or old one? Unfortunately there is only so much you can do on a laptop.

Hardest ones are cpu and motherboard. I would run the memory tester found on linux bootable disk too.

Possibly the ultimate work around is to run linux, and have a windows 10 vm running on that