FY( - this post is turning into a book.
The analysis of the Admin log file is at the end :0)
The key here may be in your statement that:
However, just like there are no dump files, there are no indications of anything going wrong before the crashes
First I have to state that most problems fall into one of these 3 categories:
- 3rd party program problems
- hardware problems
- Windows problems
The absence of errors (this is a general statement and does not apply to all situations) often means that Windows doesn't see a problem. And, if it doesn't see a problem, then it's not likely that the problem is with 3rd party stuff or Windows stuff (remember, this is an over-simplification).
So, in most cases, this means it's most likely a hardware problem (but can also be due to compatibility or low-level driver issues) - so that's where we start the troubleshooting.
Please start with these free hardware diagnostics: http://www.carrona.org/hwdiag.html
Next, you have an older computer that may not be supported by the manufacturer any longer.
As such, you have to wonder about the compatibility of this system with W10 - as the last updates date from 2012.
Unfortunately, the best test for compatibility is to install the old OS and see if everything works there.
If there's a BIOS update, it is scary to do.
But if incompatibility is suspect, then flashing the BIOS may be very important. W10 communicates with the BIOS much more than previous OS's
Windows systems are a complex interaction of parts - so failures can be simple to figure out, or they can be so complex that you want to rip out your hair.
I have followed the release of many OS's, and have been actively helping out on the forums since around the time that XP was released.
Most often the problems that I see are caused by outdated software/3rd party programs.
The easiest test for this is a Clean Boot ( http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows ), but it doesn't find everything.
If the Clean Boot doesn't fix things, then we have to discuss the various repair/recovery options.
I have deliberately made the warnings for BIOS flashes and Driver Verifier as forbidding as I can - because there is a danger in doing them improperly.
FWIW - I have never had a bad BIOS flash (but have come close due to poor documentation).
I have seen problems rebooting from Driver Verifier (but haven't seen one in the last year or two that hasn't been solved by my suggestions). The most often quoted solution is that they booted to Safe Mode and then turned Driver Verifier off there.
Finally, what I do with the Admin reports is:
- I look for repeated errors, particularly in the time just before a Critical Error happened (that's why I tend to ask for the reports to be generated immediately after the event - the Critical Error serves as a marker for me to look for).
- I look for other errors that may be related, or that may interfere with the log file (such as multiple Comodo errors, or services still running after uninstalling things).
I'll post some things to help clean out the log (and may fix some things).
Then we'll see if the system still has problems - and if needed, I'll ask for another Admin logfile
To stop Media Center tasks from running (and then failing) delete this registry key (as with any deletion, backup the key first):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\Media Center
Once you've deleted the above registry key do the following:
- Go to the Windows\System32\Tasks\Microsoft\Windows folder and delete the Media Center folder (as with any deletion, backup the folder first).
- Then delete the Task Scheduler Library...Microsoft...Windows...Media Center task folder within the Task Scheduler (I don't think that you can back this up, but you can export the tasks individually).
The BlueStacks services are still running.
Have you tried disabling them in services.msc?
As for the problems with Comodo:
- please ensure that it's uninstalled
- then run this free tool to remove any leftovers: http://forums.comodo.com/install-setup-configuration-faq-cis-b141.0/-t71897.0.html (I have not used this tool myself, read the directions/cautions carefully)
IMO this is the most serious of your problems.
I'd also suggest checking in services.msc for any Comodo services and disable them.
This is my canned speech for removing troublesome drivers.
Give it a try for removing the Comodo stuff if you can't get rid of it otherwise
Please note that cmdagent is an executable - NOT a driver ( I mention this because the canned speech is for drivers and not for executables - so I made changes, but may have missed something):
1) Create a Restore Point using System Restore
2) Create a Repair disc (Recovery Drive in Win8.1/10):
Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
Win 10 - Go to Start (press the "Win" key) and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx) and use it to disable any instances of cmdagent that are starting (or any other Comodo entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of cmdagent (or any other Comodo entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of cmdagent or any other Comodo entries are disabled.
7) EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (cmdagent) or the program name (Comodo). Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this guide).
8) Search the system to locate the cmdagent file and rename it to cmdagent.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).
9) Test to be sure that the device is working OK and that any BSOD's/errors have stopped.
In the event that the system doesn't boot:
1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename cmdagent.BAD to cmdagent.exe
ren C:\Windows\System32\drivers\cmdagent.BAD C:\Windows\System32\drivers\cmdagent.exe
2) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.
I also see some sidebyside entries for Adobe and Avast
Please uninstall them completely.
Then download a fresh copy of the latest, W10 compatible version and install that.
Then we wait and see what happens.
While waiting, please run these free hardware diagnostics: http://www.carrona.org/hwdiag.html
Edited by usasma, 13 August 2016 - 08:20 AM.