well its been 30 days once again, and it didnt crash, the change made was that i've disabled the hybrid shut down. since apparently when you tell windows to shut down, it actually doesn't? it goes into a sudo sleepmode :l so i disabled that, and it hasnt crashed in a month :V
but why only it happens after 30 days? no idea. how that manifests 2-3 days ahead as the computer lagging? not sure =l. but the result seems to be that it would cause a corrupted hybrid sleep file after a while and it'd cause a crash :V
I had to do that on my laptop, as a couple of the devices relating to graphics would stop working unless I rebooted. Haven't had any problematic devices after disabling Fast Boot.
I had to do that on my laptop, as a couple of the devices relating to graphics would stop working un
Maybe a scheduled update or system check/anti virus check, or any other program wants to run itself to do the task it is supposed to do every 30 days or on a set day on every month! And this can be even a virus, and not just a listed program!
I can only think, that said program runs itself, and doesn't care about system processes getting less memory and cpu resources...or whatever. The specific nature of lagging and then the crash happening after 30 days feels like a program/virus running a scheduled update/thing. Locate the extra program if you can, and get rid of it or turn off it's scheduled task...and hopefully that will work out for you! I can only think about this, without seeing the actual system/problem. Good luck! Hope you can solve the problem for good!
"But why only it happens after 30 days?" Maybe a scheduled update or system check/anti virus check,
Well, I would not have expected that to work but then again I've never owned a computer that wasn't a desktop so I'm used to different kinds of weirdness. Nice to see that it looks okay so far
Well, I would not have expected that to work but then again I've never owned a computer that wasn't
Hybrid apparently combines sleep mode with hibernation mode and apparently the process of updating the ram image before nodding off is using a file structure in which there is no actual start of the file, nor an end to the file, hence a type of wrap around file, when the end of the file is reached, it resets to finishing the write to the start of the file.
As to why it's crashing, probably picks up a pointer error and things go awry, the length of time is probably related to when it wraps around or how many times it's wrapped around.
I've had nothing but problems with Windows' "hybrid shutdown", or "Fast Startup" as 10 calls it, and I hate that 10 has it enabled by default. Just a couple days after a fresh install, there will be all sorts of problems if I don't disable it
I've had nothing but problems with Windows' "hybrid shutdown", or "Fast Startup" as 10 calls it, and
This makes sense. hybrid shutdown keeps basically everything in memory from reboot to reboot including any errors or memory leaks that may have been caused by other programs. i guess 30 days is just how long it took those errors to catch up and cause system instability.
congrats on finding and fixing the issue.
This makes sense. hybrid shutdown keeps basically everything in memory from reboot to reboot includi
I thought I was the only one! So that's what happening to my computer, it's lagging. Every time I boot up my computer, it feels like it's running slow. Thought it was slow because of those broken updates.
I thought I was the only one! So that's what happening to my computer, it's lagging. Every time I bo
