Everyday, like clockwork, my PC completely freezes up at 20:07. Multiple instances of Windows Error Reporting occur in my task manager, the CPU maxes out, everything slows down until the mouse stops moving and everything stops working. There is no BSoD or error message, the PC just locks up.
I've been through my scheduled tasks and can't find anything around 20:07.
What do I do? Thank you!
Hi.
Think I would do two things out of the gate. One, run a secondary AV product to do a scan of your entire storage system, something like MalwareBytes. (Malwarebytes.com)
I would then to a clean boot boot, say twenty minutes before 20:07, and see if this still happens.
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
I recognize this may sound crazy but is there a chance your line input is being impacted at this time, something that is impacting voltage to the point where your PSU output is impacted. A very large pump turning on, a programmed electrical furnace or heater.
To help determine if it is an outside influence you could disconnect from the internet, set the clock to 20:00 and see if it occurs at 20:07. (disconnecting from Internet prevents it syncing with the Internet clocks and getting the real time. You could disable syncing with Internet clocks)
Thanks for your help!
I ran malwarebytes and it didn't flag anything up.
I changed my clock and the problem occurred at 20:07 everytime. (I did notice that it would only crash when setting my clock to 19:55 and no later, despite the actual crash happening dead on 20:07 each time.)
I then did a clean boot and still experienced the same problems.
Any thoughts? Thank you!
Wow. So no exterior influence.
If you look in event viewer (all categories) is anything showing as started just moments before the crash.
I'm wondering if you used Autoruns by sysinternals if it would show this mystery start.
https://docs.microsoft.com/en-us/sys...loads/autoruns
Autoruns does not take prisoners, you say delete it does. I would have a system image made by a tool like Macrium Reflect.
Backup and Restore with Macrium Reflect
If with this only delete things you've researched.
Something must be set to check with the mothership at exactly 20:07. The clean boot is supposed to eliminate all third party.
How long ago did this start?
I guess a less aggressive next step would be a boot to Safe Mode kicked of by holding shift key down and clicking restart.
Boot to Advanced Startup Options in Windows 10
See if it occurs in this mode.
In event viewer I found thousands of instances of Windows Error Reporting that show up in mass during the crash. They all say the same thing:
Fault bucket , type 0
Event Name: WindowsNonFatalSuspectedDeadlock
Response: Not available
Cab Id: 0
Problem signature:P1: 2
P2: Unknown
P3: Geolocation.dll
P4: GetGeopositionOperationImpl
P5: 420000
P6: Windows:evices::Geolocation::GetGeopositionOperationImpl::InitializeAndStart
P7:
P8:
Any idea what this 'Geolocation' is? Could this be the problem.
(Also, the problem seemed to start after the windows fall creators update.)
UPDATE: I disabled geolocation.dll in services and the problem appears to be fixed!!!!
You should definitely report this to Feedback Hub. It's very likely caused by some of Microsoft's own code, or a fitness device like a FitBit. See NirSoft's page on the geolocation dll at Windows 10 DLL File Information - Geolocation.dll. This shows what calls it (very little) and what it calls in turn (a lot!). You might try disabling location services in Windows 10 to see if that stops the problem from recurring. There's a TenForums tutorial for that: Turn On or Off Location Services in Windows 10.
HTH,
--Ed--
Last edited by EdTittel; 16 Mar 2018 at 17:20. Reason: Shorten URL
Excellent news and I'm glad the forum could help.
I agree with Ed I would report this both too Windows and Google.
Maybe uninstalling and re-installing will fix, at least you know the villain.
Thank you so much for your help!
Quote