[SOLVED] PC Freezing when searching or opening folders (4-8 times daily).

caylerose

Distinguished
Feb 13, 2013
62
1
18,535
The past couple weeks I've been having freeze issues. I believe I've found the root cause. I notice only when I hit the windows key and search for a file, the PC will freeze for 5 seconds as well as if I open a folder.

These two Audit Success logs come up in Event Viewer(security) when this freeze occurs.

I need some trained eyes to tell me what this stuff means, because I don't know. The most I've found was an article Here

Code:
Audit Success
Event ID: 4672
Task Category: Special Logon

Special privileges assigned to new logon.

Subject:
    Security ID:        SYSTEM
    Account Name:        SYSTEM
    Account Domain:        NT AUTHORITY
    Logon ID:        0x3E7

Privileges:        SeAssignPrimaryTokenPrivilege
            SeTcbPrivilege
            SeSecurityPrivilege
            SeTakeOwnershipPrivilege
            SeLoadDriverPrivilege
            SeBackupPrivilege
            SeRestorePrivilege
            SeDebugPrivilege
            SeAuditPrivilege
            SeSystemEnvironmentPrivilege
            SeImpersonatePrivilege
            SeDelegateSessionUserImpersonatePrivilege

and

Code:
Audit Success
Event ID: 4624
Task Category: Logon

An account was successfully logged on.

Subject:
    Security ID:        SYSTEM
    Account Name:        MAINCOMPUTER$
    Account Domain:        WORKGROUP
    Logon ID:        0x3E7

Logon Information:
    Logon Type:        5
    Restricted Admin Mode:    -
    Virtual Account:        No
    Elevated Token:        Yes

Impersonation Level:        Impersonation

New Logon:
    Security ID:        SYSTEM
    Account Name:        SYSTEM
    Account Domain:        NT AUTHORITY
    Logon ID:        0x3E7
    Linked Logon ID:        0x0
    Network Account Name:    -
    Network Account Domain:    -
    Logon GUID:        {00000000-0000-0000-0000-000000000000}

Process Information:
    Process ID:        0x3cc
    Process Name:        C:\Windows\System32\services.exe

Network Information:
    Workstation Name:    -
    Source Network Address:    -
    Source Port:        -

Detailed Authentication Information:
    Logon Process:        Advapi
    Authentication Package:    Negotiate
    Transited Services:    -
    Package Name (NTLM only):    -
    Key Length:        0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The impersonation level field indicates the extent to which a process in the logon session can impersonate.

The authentication information fields provide detailed information about this specific logon request.
    - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

@Colif

What I've done so far
  1. chkdsk on all drives (no problems even chkdsk /f /r)
  2. did the DISM /Online healthcheck and that was find too
  3. this is a 4 day old windows 10 installation with latest updates
  4. made sure im an administrator account
  5. did a defrag of all drives
  6. scanned for viruses with windows defender
  7. cleared all indexes from Indexing Options (rebuild)
 
Solution
hi, see your power options if your drives arent sleeping, it takes few seconds to wake them up


if u have external drives, u can also disable usb sleep function aswell in same power plan settings

as for event id 4672, that gets logged if admin rights are invoked
in your case advapi is web based logon, while services are background processes
which means one of your background service running logged in as administrator..to do idk... app update? windows bloatware sending personal stuffs? dunno 😛
from those logs u cant really tell
hi, see your power options if your drives arent sleeping, it takes few seconds to wake them up


if u have external drives, u can also disable usb sleep function aswell in same power plan settings

as for event id 4672, that gets logged if admin rights are invoked
in your case advapi is web based logon, while services are background processes
which means one of your background service running logged in as administrator..to do idk... app update? windows bloatware sending personal stuffs? dunno 😛
from those logs u cant really tell
 
Last edited:
  • Like
Reactions: caylerose
Solution
Would make sense, I have x1 M.2 (OS), x2 HDDs (1 programs, 1 games), and x2 SSDs (vr games)

Waking up a whole hard drive would take 4-5 seconds i assume, which is the freeze time I'm seeing. Never seen such a thing before in my life, but I'll give this a try.

Screenshot-2021-01-12-081319.png


now

Screenshot-2021-01-12-081431.png