Windows 10: Windows 10 freezing every couple minutes.

I've been having this issue for a while now where my PC just freezes, CTRL ALT DEL doesn't work, nothing does. After about a minutes everything goes back to normal, then a few minutes later it freezes again. Ive run the sfc /scannnow and another one that fixed windows update issues. Also ran the troubleshooter under control panel for Background Intelligent Transfer Service and it says it fixed an issue but the freezing continues to happen. It's super annoying and I can't figure out what to do to fix it.


12 - Event Log
----------------------------------

1201 - Time : 11/1/2020 21:09:19
1202 - Source : Application Error
1203 - Description : Faulting application name: RazerCortex.exe, version: 9.11.9.1287, time stamp: 0x5f7fda69
Faulting module name: sqlcipher.dll, version: 3.15.2.0, time stamp: 0x59671333
Exception code: 0xc0000005
Fault offset: 0x0006a1bd
Faulting process id: 0x1b78
Faulting application start time: 0x01d6b0bd2ab39317
Faulting application path: C:\Program Files x86\Razer\Razer Cortex\RazerCortex.exe
Faulting module path: C:\Program Files x86\Razer\Razer Cortex\sqlcipher.dll
Report Id: e80c5d23-60f7-4668-b478-fd070dee3e8e
Faulting package full name:
Faulting package-relative application ID:

1201 - Time : 11/1/2020 21:09:19
1202 - Source : .NET Runtime
1203 - Description : Application: RazerCortex.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at <Module>.SQLiteHelper.{dtor}SQLiteHelper*
at <Module>.__GetLanguagesChar*, Char*, Void Int32, Int32
at RazerCortex.DBLib.__GetLanguagesSystem.String, System.String, RazerCortex.LanguageDataCallback
at RazerCortex.DBLanguageResource.SetLanguageTagSystem.String
at RazerCortex.RazerCortexBootstrapper+<InitializeShell>d__14.MoveNext
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNextSystem.Object
at System.Threading.ExecutionContext.RunInternalSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean
at System.Threading.ExecutionContext.RunSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run
at System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation+<>c.<.cctor>b__8_0System.Object
at System.Windows.Threading.ExceptionWrapper.InternalRealCallSystem.Delegate, System.Object, Int32
at System.Windows.Threading.ExceptionWrapper.TryCatchWhenSystem.Object, System.Delegate, System.Object, Int32, System.Delegate
at System.Windows.Threading.DispatcherOperation.InvokeImpl
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContextSystem.Object
at System.Threading.ExecutionContext.RunInternalSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean
at System.Threading.ExecutionContext.RunSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean
at System.Threading.ExecutionContext.RunSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object
at MS.Internal.CulturePreservingExecutionContext.RunMS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object
at System.Windows.Threading.DispatcherOperation.Invoke
at System.Windows.Threading.Dispatcher.ProcessQueue
at System.Windows.Threading.Dispatcher.WndProcHookIntPtr, Int32, IntPtr, IntPtr, Boolean ByRef
at MS.Win32.HwndWrapper.WndProcIntPtr, Int32, IntPtr, IntPtr, Boolean ByRef
at MS.Win32.HwndSubclass.DispatcherCallbackOperationSystem.Object
at System.Windows.Threading.ExceptionWrapper.InternalRealCallSystem.Delegate, System.Object, Int32
at System.Windows.Threading.ExceptionWrapper.TryCatchWhenSystem.Object, System.Delegate, System.Object, Int32, System.Delegate
at System.Windows.Threading.Dispatcher.LegacyInvokeImplSystem.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32
at MS.Win32.HwndSubclass.SubclassWndProcIntPtr, Int32, IntPtr, IntPtr
at MS.Win32.UnsafeNativeMethods.DispatchMessageSystem.Windows.Interop.MSG ByRef
at System.Windows.Threading.Dispatcher.PushFrameImplSystem.Windows.Threading.DispatcherFrame
at System.Windows.Threading.Dispatcher.PushFrameSystem.Windows.Threading.DispatcherFrame
at System.Windows.Application.RunDispatcherSystem.Object
at System.Windows.Application.RunInternalSystem.Windows.Window
at System.Windows.Application.RunSystem.Windows.Window
at RazerCortex.App.Main

1201 - Time : 11/1/2020 22:37:01
1202 - Source : Service Control Manager
1203 - Description : The Background Intelligent Transfer Service service terminated with the following service-specific error:
The class is configured to run as a security id different from the caller

1201 - Time : 11/1/2020 22:37:01
1202 - Source : Microsoft-Windows-Bits-Client
1203 - Description : The BITS service failed to start. Error 0x80004015.

1201 - Time : 11/1/2020 22:24:37
1202 - Source : Service Control Manager
1203 - Description : A timeout was reached 30000 milliseconds while waiting for the GraphicsPerfSvc service to connect.

1201 - Time : 11/1/2020 21:23:02
1202 - Source : EventLog
1203 - Description : The previous system shutdown at 9:21:41 PM on ‎11/‎1/‎2020 was unexpected.

1201 - Time : 11/1/2020 21:18:37
1202 - Source : Service Control Manager
1203 - Description : The AppX Deployment Service AppXSVC service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

1201 - Time : 11/1/2020 21:18:37
1202 - Source : Service Control Manager
1203 - Description : A timeout was reached 30000 milliseconds while waiting for the AppX Deployment Service AppXSVC service to connect.

1201 - Time : 11/1/2020 15:16:23
1202 - Source : DCOM
1203 - Description : DCOM got error "1053" attempting to start the service BITS with arguments "Unavailable" in order to run the server:
{4991D34B-80A1-4291-83B6-3328366B9097}

1201 - Time : 11/1/2020 15:15:59
1202 - Source : Service Control Manager
1203 - Description : The Background Intelligent Transfer Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

1201 - Time : 11/1/2020 15:15:59
1202 - Source : Service Control Manager
1203 - Description : A timeout was reached 30000 milliseconds while waiting for the Background Intelligent Transfer Service service to connect.

----------------------------------

End of file - 51929 Bytes.

:)

 

Borderlands freezes and thaws

I'm positive the steps I took above fixed it. I went through 10 rounds in the underdome (well over an hour of gameplay) without a single freeze. Previously, I couldn't play 15 minutes without at least one freeze.

 

Windows 7 freezes for 1 minute

My custom built rig has lately, in the past 2 months or so, been having these spits of freezing. It will freeze for exactly 1 minute: always 1 minute, every time. I can time it down to the second.

The weird thing is that when it freezes, some programs seem to be immune to it. When playing a full screen game, video and audio will freeze (though not always at the same time, sometimes one or the other will lag). Playing a 3D game in windowed mode seems to be immune to it however. Windows explorer and Firefox always seems to freeze, but Windows Messenger (including video call) will work as normal even while everything else is frozen. After a minute has passed, everything is back to normal. It happens at irregular intervals: sometimes it will happen then happen again 30 seconds later, and sometimes I can go hours without the problem.

It's a bit bizarre and I'm not sure what is causing it. The fact that it is always exactly 1 minute makes me think it's some dumb program checking for an update or something, but I can't pin it down.

Any ideas appreciated.

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.