New
#11
What software do you have running on your PC?
For example, I found a conflict between Malwarebytes Anti-Malware and Norton Internet Security, causing my PC to lock up.
And you may want to increase the RAM voltage a bit when you update the BIOS.
Since you had already overclocked the machine before (though you disabled that now), don't forget to reset CMOS before updating BIOS.
Finally, if your PC freezes again, then reboot and launch the Event Viewer (which you can get to from Computer Management). Take a look at which events were taking place just before the freezeup. Let us know if you spot any errors or anything else unusual.
I usually have Steam, Skype, Mozilla, sometimes Spotify, and a random game running (not for a while because of the freezing).
I'll increase the RAM voltage to about 1.54 - 1.55 volts.
But how exactly do I reset CMOS? I never owned a proper PC (cheap laptops always), so I don't know about that yet. *EDIT* I had the default settings before updating BIOS, is that enough?
I'll surely check out Event Viewer and take a screenshot if it freezes.
Last edited by Finish3r; 11 Oct 2016 at 06:55.
Ok, I didn't get a proper screenshot, but here's what I found:
Critical: Kernel-Power, exactly when it freezed
Error: AppReadiness, multiple times; just seconds before freeze
Warning: e1iexpress (Intel Gigabit LAN), complained about being disconnected, also just before freeze
Maybe the "Kernel-Power" -thing has something to do with the freezes?
*EDIT*Just wanted to let you know, that I just ran Advanced SystemCare, and it found a good amount of errors. Now they are fixed, but I don't yet know if it will not freeze again
Last edited by Finish3r; 11 Oct 2016 at 07:23.
Okay, 10 freezes later: I reset everything in BIOS to optimized defaults.
Can the problem be caused by the mobo's single pin connections? I know I have something wrong there, because I can't start up my PC without turning off the PSU first, and then starting it back up.
Aha!
App Readiness errors, eh?
App Readiness lockups are an uncommon but known problem that has been reported to Microsoft.
service now causes lockups? : Windows10
and also here, where some fixes are discussed:
http://answers.microsoft.com/en-us/w...27c1d28?page=1
The particular error(s) in the Event Viewer should show you (in Details?) just which apps App Readiness was trying and failing to initialize.
To repair all that software, you can do it with the usual tools, sfc /scannow and DISM.
You can also try to disable or uninstall all the universal apps you don't use, and then run App Readiness manually from now on. That is, disable the service except when you really need to initialize a newly installed universal app. Enable it just for that, and then disable it again.
Windows 10 freezes randomly - update 14393.222 - Page 2 - Windows 10 Forums
Glad to hear that this is something that is easily fixable.
I just edited registry and now let's hope for the best
*EDIT* The problem seemed to be ShellExperienceHost -related, according to Event Viewer.
I deleted something from the registry, related to the ShellExperienceHost -thing, can't remember what (my short-term memory is pretty bad ).
I did everything what a solution told me to do, and now I just hope that I'm able to use this PC properly.
Just crashed 2 times, under one minute. A new record
Now it gives me different errors in Event Viewer;
Critical: Kernel-Power
Error: Eventlog 2 times, DistributedCOM 2 times
Warning: Kernel-PnP (The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000.), e1iexpress
DistributedCOM is the problem now?
Well, just crashed again..
This time Event Viewer gave me these errors:
Kernel-PnP: "The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000."
Kernel-Power "The system was reset before it was turned off properly. This could be because the system crashed or stopped responding."
And something related to DistributedCom. Event ID was 10016.
I see those driver problems and EventID 10016- things just before/right when it crashed. Maybe fixing these will solve the crashing?
If you have Fast Startup enabled (which is the default), please disable it.