Solved What the hell is happening to my computer?

[Its No Use]

So recently a bunch of crazy shit was happening to my computer (which never happened before when I began using it in March) and I have no idea how to solve this. I couldn't put this in a dedicated sub-forum because all the problems I'm about the describe seem to be in multiple categories.

1. Computer wakes up at random times automatically
I don't exactly know why my computer does this, but it wakes up sometimes as I sleep. Maybe it has something to do with the task scheduler??

2. Computer sometimes spontaneously crashes upon waking up?
I have no idea why the hell this happened, but it happened twice. I looked at the crash logs and I got Error 41, meaning there was no reason why it crashed.

3. Windows File Viewer breaks as uptime goes on.
This is the weirdest one. Crazy things start happening to the Windows Explorer (explorer.exe) as the computer goes on before restarting... or crashing. Mainly it's the file viewer. Most icons in the file viewer will stop loading entirely and either have no icon or the "blank file" icon. Contents in the sidebar take forever the load (they don't even load at all) and have minimal items when it's supposed to have subfolders, which will never load.

I was told that in order to fix this, I had to delete iconcache.db. I did that, but I had to restart my computer in order for it to work. Restarting my computer even without this works just as fine, so I don't understand why this was necessary. Besides, it was only temporary before the file viewer started glitching out again.

I do remember the file viewer fixing itself without having to restart the computer, but I have no idea what I did to fix it and I'm not even sure if I could do it again.

4. Restarting explorer.exe completely breaks the file viewer until restarting

Other things I tried to do to fix the problem above was deleting explorer.exe and restarting it, but that only made it worse. Trying to open up the file viewer (doesn't apply when it opens up to save/open a file) results in getting the "remote procedure call failed to execute" error.

I of course looked this up and did the steps to fix it, but I didn't really have to do them in order to fix it; I just needed to restart my computer.

For all of these problems I thought there was a huge virus wreaking havoc on my hardware, so I did a scan with ESET, but it didn't find any threats.

 

[torchwood]

Hi Its No Use,

Lets start by running a couple of repair tools

from an elevated command mode

sfc /scannow

then
KB947821
https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness

REBOOT

then goto
C >> windows > logs > CBS ..... then zip the top text file and bottom SURT reports
Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Help Forums

Roy

 

[Megahertz07]

I had some problems with my Z170 Gigabyte MB. It has been solved with a BIOS update.
Update your BIOS.
- Computer wakes up at random times automatically - Check BIOS power settings
- Computer sometimes spontaneously crashes upon waking up - No more issue after BIOS update

As Roy suggested, SFC may solve the other issues.
I would also do a check disk (chkdsk C: /f) prior of the SFC.

 

[Its No Use]

Okay, they're all fixed I guess.

I still couldn't figure it out for problem #1, though. #2 doesn't happen anymore.

#3 and #4 were caused by this process called dllhost.exe? I found out through the Windows Task Manager and saw that it was using up a LOT of CPU for some reason. By deleting the process, the Windows File Viewer worked normally again. What the hell is this program, why is it consuming my computer resources, and why is it breaking my file viewer?

 

[torchwood]

Hi Its NoUse,

have a look in event manager

1. Open Event viewer and right click on Custom View and click on 'create custom view
2. Under the Filter Tab ; check "By Source" and from the Event sources dropdown select Kernel-Power, Power-Troubleshooter. Also check all the Event Levels.
3. Just above the Task Category you have space to enter the Event ID.. This is important as you dont need all the information except for entering sleep and resuming from sleep. Just enter 42,1

or from an elevated command prompt
powercfg -lastwake will tell you what woke the computer up last time



Roy