Windows 11 Lengthy Boot

The link to process explorer info brings me to an index page by first letter of the blog as far as I can tell. I don't know what to look for.

Boot trace - what would I be looking for there? I could be wrong but this issue doesn't seem like a boot problem.

Also I believe that the ethernet stuff is a result of whatever else is going on and not the cause given that everything checked out with the card and driver.

A system or event trace might be useful to someone, but I don't have the expertise to know how to use it or what to even look for. I think we're running out of ideas and options.

In the PE info I saved I notice there was an RTSS third party process that was invoked via dllhost.dll during the event. But I think it was a victim as well because I removed it and the freeze still happens. Also the dllhost initiation for that has gone away as a result of the removal. I think the main reason for looking at dllhost in the first place was to make sure it was in the correct location and not a virus.

Could be ping spikes which we see in Ethernet connections on Windows 10 and 11:

https://thegeekpage.com/ping-spikes-in-windows-...

https://internet-access-guide.com/ethernet-lag-...

https://conscioushacker.io/ethernet-lag-spikes/

https://www.reddit.com/r/GeForceNOW/comments/w8...

https://www.reddit.com/r/HomeNetworking/comment...

https://windowsreport.com/ethernet-spiking-task...

(Avoid ad links which intrude into editorial copy, especially DO NOT INSTALL Restoro, PC Repair Tool and Reimage ads)

____________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Ok - I'll look at that. I kinda lost track of the fact that if I pull out he ethernet cable my problem disappears. So - definitely related to network related activities and processes. The 73 second pulse, both the exact timing and the length of time in between seems important - but I don't why, and I an imagine even if other people experience something like this the timing would vary. So doing a search on 73 second performance pulses probably isn't going to get me anywhere.

I'll check out the ping thing.

B

It's a trending issue in Windows 11, with wifi but also ethernet. So your graph sure looks like it might apply.

Definitely will check it out.