Helo guys, I have recently moved from w8.1x64 to win10. Although I upgraded first, but afterwards, i installed it clean. I am experiencing some problems however, which I am hoping, you could help me to solve.
Problem is, that sometimes i cannot shutdown or reboot my computer. I normally hit start -> shut down / restart. Restarting message is shown up for a couple of seconds, then the screen goes blank, however fans, mobo, cpu continue to run - I can still read the cpu temperature from motherboards lcd. This indicates to me, that system is actually not shut down. This occurs only sometimes unfortunatelly, thus i am not able to track down the reason causing it.
Do you have any ideas, what to check / how to monitor (maybe check) some windows logs to track this down ?
Some background, desription of my system: MSI Z97-G7 Mobo, i7 4790K, Corsair Vengeance DDR3 2x8GB 2133mhz memory(running on xmp), Samsung 240pro 256GB, Asus PCE-ac68 wifi card From software, i am using: Windows 10x64, Office 2013, Symantec Cloud anti-virus, Firefox, GTA V
Reinstall windows 10: I just did that, 3 days ago, because of this issue. It was happening on 8.1, but not that often. Maybe once a month, what i considered "normal".
Be patient with Windows 10, it's only been in development for two years or so, and been in beta testing for about a year now, and that's not a lot of time for Microsoft to get a product to a level of stability and features that is what consumers expect.
There are a lot of issues with Windows 10 in comparison to Windows 8.1. Windows 8.1 in standard version had no compressed system image, so the performance of Windows 8.1 is better than that of Windows 10. Windows 10 is pretty slow in comparison, but has a slimmer image, so it takes less space on storage. They traded in performance for that. Windows 10 is also enormously bloated with all of the spyware "features". You can disable Cortana, but in fact, Cortana will still run in the background, and will keep on consuming those resources, whether you want it or not. After a few weeks now, Windows 10 performance has slowed down considerably already, and a system refresh has turned out to be a necessary thing to do every couple of weeks. There are also quite a lot of features that are present in Windows 8.1 that aren't in Windows 10, and that are really annoying. One example is the fact that a synced folder, like the OneDrive folder, can't be stored on removable media in Windows 10, unless you create a VHD on that medium. It's one of those things: Microsoft tries to sell devices with very little internal storage due to the tablet form factor, and even their overpriced Surface Book doesn't have additional storage in the keyboard dock, which is strange because everyone else does it (maybe that's why Lenovo is still the largest PC vendor, may also be that they insert a rootkit of their own next to the Intel ME rootkit that comes standard with all Intel based devices lolz, maybe that Lenovo rootkit is like the Wi-Fi router and IoT botnet that protects the infected devices from NSA spying and viri and other malware...).
Windows 10 is still a bit of a mess, reminiscent of Windows Vista in many respects, limited hardware compatibility in comparison to Windows 7 and 8.1, definitely less performance than Windows 8.1, etc... it's a weird release to announce as the "final Windows version", if that is the definitive Windows customers have to put up with, that's disconcerting to be honest... and then there's the problems with Windows Update, from NSA experiments showing up as "test updates" to hacked update servers and botched security certificates... it's a bit of a serious mess for the moment, and it will take some time before Microsoft stabilizes everything and patches the faults and lacking features, but usually, just like Canonical with Ubuntu, they get things pretty stable by the time the next release comes out and everything starts all over again lolz...
Nah, it's the "feature" that Windows suspends instead of shutting down. It's easily fixed by going to the boot settings and setting Windows to really shut down and reboot instead of doing the suspend thingy. That suspend thingy is highly dependent on a perfect textbook power state implementation by the hardware manufacturer, and in practice, that's utopia lol
Streetguru, it was happening in 8 as well, but only after heavy day of working, gaming & video-editing, thus i thought that is ok. Since win10 it started happening reguralry, while I am still not able to simulate why.
Zoltan, could you show me, where to turn this off ? Is that the fancy thing, that close programs, stores your booted kernel with loaded drivers on ssd and then turns pc of ? Next time kernel isn't loaded from scratch, rather previous session restorred ? Some kind of kernel-hibernation ?
ps: for power supply, i am using Seasonic P760 platinum series
btw: Couldn't norton antivirus be the issue ? I think, the problem escallated after installing it, but there's no way to proove. Some kinds of windows logs, maybe ?
I don't think I've ever run into that, maybe on this Lenovo Pre-built I had to install 7 onto, I think it was a pain getting it to boot from a Gparted live USB
I actually can tell you how to shut it off, because it's the first thing I have to do when running Windows in a virtual container (which - as everyone knows - is the only way I really recommend running Windows, but that's another matter lol).
You go to the control panel (search control panel), and you'll get the Windows 7 type control panel. Click on system and security, then power options, then on the left "Choose what the power buttons do". Then scroll to the bottom, and uncheck "Turn on fast start-up". That'll solve the issue.
More thoroughly though, it's most probably a UEFI settings thingy that can be solved with some experimentation. I would look into that, maybe there is a BIOS update for your machine also that solves some issues.
I've never really had any UEFI problems on any machine, except one that came without Windows, an Acer Chromebook that I once experimented with.
Many linux users that have problems with UEFI, overthink the whole thing and get problems while they expect problems. I'm not saying there haven't been problems, especially with the DEB based distros having to catch up for some two years to UEFO secure boot, but with modern bleeding edge distros, everything always kinda just worked just fine on every machine I got. Maybe I just got lucky lol.
BIOS updates are very important though, many boards, desktop and laptop, are just thrown onto the market with less than adequate testing, and then problems are solved afterwards with BIOS updates, or not in some cases lol.
Hardware quality is a huge issue nowadays, with the PC market is disarray and such. Many peripherals, like HID devices, don't have standards compliant features, like what happens ever more often, is that device descriptors do not parse in *nix systems. For Windows, that's not a problem because there are no safety precautions in Windows against manipulations with HID devices, but in *nix systems, there are certain rules as to how much memory every aspect of such a device should use. That includes the device descriptor, which should not exceed a certain amount, and to be honest, there is no valid reason ever to make it exceed an already ample standard amount. Yet this is something that happens ever more often. A popular fix is to increase the number of usages or similar, but that's a dirty fix. A better fix is to fix it at driver level, with a kernel module, but that's too advanced stuff for most users, even though it's not that hard to do, it's something most users will not venture into. Linux kernel devs should pay more attention to these issues, so that it's dealt with in a general way, like all devices that don't parse because of an exceeding descriptor, should automatically be patched by the internal kernel driver logic. That requires a degree of cooperation that is simply not present any more in the x86 branch of the Linux Kernel dev group. It's something that we do see with the ARM group though. Maybe it'll come as Linus Torvalds wants to expand the linux core dev group like he announced at LnuxCon Berlin two days ago... we'll see...
the machine would not fully shut down, it would like only go into hibernate mode, so it would just boot right back into windows when turned on, I guess I could have unplugged it, but I think I had to hold down like alt or shirt as I was going to shut it down to get it to really turn off.
That's a known issue, it's because some power states are not entirely supported either by the OS or by the UEFI. This happened a lot on Intel machines because Intel was very slow in releasing driver code that handled this. What you would have is a machine not shutting down completely after X was killed, or a machine refusing to boot through to X after hibernation. I had that once on a very bleeding edge Fedora install, but I just disabled some power options, and it worked again. By now though, on recent kernels in Linux, and probably since last week's Intel update for Windows 10, things should now work normally.