New
#51
Please help !
I haven't given up yet
It's been busy (here and in real life) and I need to sit down and work through it. Don't run away!
Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.
You have some problems with the Performance Counters.
Please open an Elevated Command Prompt, and run the following command
lodctr /r
Wait 15 minutes, then reboot - wait another 15 minutes, then post a new set of event logs.
If I'm reading it right, this has cured a fair number of problems.
One remaining one that concerns me is a 'Crash dump initialization failed!' error every boot - see here for MS's only word on the subject... Event ID 46 logged when you start a computer - but it does seem to be a common error in Macs.
The backup errors are present..
Another error indicates that you may need to uninstall and reinstall .NET 4 (and/or 4.5)Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {1a18cd3f-4aef-44d6-838c-1a06ac868f8c}
The Windows Defender service is complaining that the service can't start because the executable is missing? This may also be because of permissions problems.
Hopefully those pointers will get you going?
I do not use swapfile at all. What's the point of using it when I have 64 GB RAM. I don't want to kill my SSD's.
This backup errors seems to be interesting.
Windows Defender is working fine. .NET Framework 4/4.5 was removed and reinstalled. I don't see any issues with it (GeForce Experience is using it and it's working fine).
Please reboot a couple of times, and then post a new set of Event logs - we'll see what still needs attention.