Windows 10: PC completely freezing up at 20:07 everyday.

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!

:)

 

PC Keeps Freezing At Completely Random Times

Thanks for replying. I attempted the first two suggestions but they did not work. The troubleshooting found nothing wrong.

I tried running that command in powershell but I kept getting this error:



I have no clue how to turn Cortana off. I have tried to turn everything having to do with it off but there is still something always running in task manager and when I try to end the task it just turns right back on instantly.

On another note, that other link you provided seemed to just be about Windows 10 freezing during the installation process while mine has already completed it.

Also, do you have any idea what that Application Popup error is, because I think that might be what is causing the problem.

Thank you for your help.

 

PC Keeps Freezing At Completely Random Times

Hello,

Thank you for posting your query in Microsoft Community.

I can imagine the inconvenience you have experienced. I will definitely help you with this.

I suggest you to disable the third party security software (if any installed) temporarily and check if it is cause to issue.

Disable Antivirus:

Antivirus software can help protect your computer against viruses and other security threats. In most cases, you shouldn't disable your antivirus software. If you have to temporarily disable it to install other software, you
should re-enable it as soon as you're done. If you're connected to the Internet or a network while your antivirus software is disabled, your computer is vulnerable to attacks.

Kindly follow the below steps and check if you are able to fix the issue.

Step 1:

I suggest you to run the System maintenance
troubleshooter and check if it fixes the issue:

Follow the steps given below:

• 
  Press Windows + X keys on the keyboard and select
  Control Panel
  
• 
  Type Troubleshooting in the search bar on the
  Control Panel.
  
• 
  Click on View all
  on the left navigation pane.
  
• 
  Click on System maintenance.
  
• 
  Click on Advanced on the
  System maintenance
  dialog box and click on Run as administrator (Enter the credentials if required).
  
• 
  Click on Next and follow onscreen instruction complete the
  System maintenance troubleshooter.
  

If issue persist, Kindly follow the below given steps and check if it helps:

Run these commands:

• 
  Press Windows key and type Powershell
  in search, right click on it and Open as administrator .
  
• 
  Type the following command in Powershell and hit enter:
  
  Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  

Also, please refer to the link by Andre Da Costa on Windows 10 freeze which gives suggestions on how to troubleshoot on this scenario.

Windows 10 Installation Freeze

Hope the above information was helpful. If you need further assistance, please do let us know and we would be happy to help you further.

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 signature1: 2
P2: Unknown
P3: Geolocation.dll
P4: GetGeopositionOperationImpl
P5: 420000
P6: Windows:*Biggrinevices::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 Turn On or Off Location Services in Windows 10.
HTH,
--Ed--

 

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!