It is definitely no hardware or any peripheral that I have, since the in-place upgrade all the things that I used to do when a freeze occured do not cause any problems anymore. All peripheral have been connected to different ports for some time, including the onces on my laptop, resulting in no problems.
In fact, since I posted the logs from the custom event viewer I did not have any freeze, of course that means nothing a.t.m.
Martijn,
You need to save the crash troubleshoot log from event viewer as .evtx and not html so we can use open saved log in event viewer to read it.
I saved the event logs as evtx, no idea where the XML format comes from...
Here is a fresh one.
Attachment 89119
I've never enabled readyboost as it is not needed.
I am wondering where it comes from, I did not have any storage devices attached at the moment of the log.
I see a lot of errors the every Win10 install has, DCOM, readyboot, they are not the problem.
What looks like a problem is your network, too many timeouts causing apps & updates to fail,
Also are you using disk encryption? There are quite a few error pertaining to encryption too. Again timeouts, and total failures.
And Shellhost with mapping.
Try checking you network drivers.
Timeouts can cause freezes as the system has to keep trying until it gets the "handshake" it needs.
DHCP Server
I do not use disk encryption.
I've installed all drivers less than a week ago, if it is the internet causing the trouble then I would think the cable is the cause. The cable isn't really new but the only one that was available for use.
This is Kernel-EventTracing Error only, nothing serious.
0xC0000188 = STATUS_LOG_FILE_FULLSession "ReadyBoot" stopped due to the following error: 0xC0000188
The next Information event gives a better explanation to it ....The real-time playback file is full. Events are not logged to the session until a real-time consumer consumes the events from the playback file. Do not stop logging events based on this error code.Source: EventWrite function (Windows)
Apparently it does not have any relation with your original issue, Sound, Mouse and Keyboard freeze.The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.
There is a Kernel Power 41 Event in the logs. If that is not self-initialized by you, then that might be relating to your issue.
What I think that .......
The issue is related to chipset. Either hardware or software.
That is why I requested you to have all the chipset elements from the manufacturer. You tested those with the drivers from a different source (Microsoft); better test with another source.
If it still remains the same, two things will remain to test. Southbridge (Motherboard) and Northbridge (Processor).
But there are all chances that I am thinking in a wrong way.
Thanks for the info Arc :)
The kernel power logs are from forced shutdowns, self initialized, after the freezes occured. There is no other way to get rid of the freezes.
Before I let Microsoft install those drivers I was using the drivers from Gigabyte, in all clean installs except the current one, there is no difference. I have reinstalled the drivers from Gigabyte in a clean install a few times without improvement.
Shouldn't a freeze have occured while I was in safe mode some time back in that case? Some time back I was having freezes every few hours, I let the system run for about 8 hours and got back with a proper behaviour of the system.If it still remains the same, two things will remain to test. Southbridge (Motherboard) and Northbridge (Processor).
Quote
