Windows 10: Continuous freezing - event viewer showing floods of 5379 as well as periodic 4672, 4624, 4798

Processor: IntelR CoreTM i3-2350M CPU @ 2.30GHz 2.30 GHz

64-bit operating system, x64-based processor

RAM: 8.00 GB

Edition: Windows 10 Home

Version: 20H2

OS Build: 19042.662

Experience: Windows Feature Experience Pack 120.2212.551.0


My 2012 HP G6-series laptop has had continuous freezing which lasts anywhere from several seconds to several minutes.

When viewing the event logs at the time of these freezes, there is always a corresponding security event, most commonly a flood of dozens of 5379, but there are also 4672, 4624, 4798 which seems to freeze for less time than 5379.


I have exhausted most of the troubleshooting steps that are available online.

• I've ensured Windows and all drivers are up to date
• I've defragged the hard drive
• The hard drive and memory tests have all come back 'ok'
• I don't have advAPI or Intel RST
• I added a new RAM stick doubling RAM from 4GB to 8GB
• I created a new local account in case the existing one was corrupt
• I attempted a clean boot
• I disabled my USB drives despite not having anything plugged into them ever
• Finally, I did a full reset and clean install of Windows

All that is possibly left to do is to replace the hard drive, but the scans did not show any issues with the HD.

:)

 

Event 4672 & 4624 & 5379 PC Freezing

I have had this for a while now but it seems to have gotten worse recently. My PC has been freezing (1-4 seconds every hour or so) and the only thing that I can tie in is these Events happening at the same time as the freeze all the time.

Events 4672 (Special privileges assigned to new logon) and 4624 (An account was successfully logged on) happen together 3 times and Event 5379 (Credential Manager credentials were read) happens 9 times and i'm positive this is what is causing this.

Anyone have any thoughts as to why this causes a lockup?

 

Intermittent temporary freezes-Event Viewer shows dozens of event 5379

Did you guys ever resolve this? I currently am facing the same issue.





It starts with the sequence of events: 4624, 4672, 4798, then several hundred 5379's.

It seems to get especially crippled when performing HDD reads/writes. I am not sure where the bottleneck is - I have a USB hub on my desk behind my monitor, which I think just has USB2.0 devices, while my monitor stands have USB3.0 ports which go directly to the USB 3.0 ports on my PC case/mb access at the back.

I have tried using the process monitors, task managers, all that stuff from sysinternals, and nothing really yields a valid lead for me to follow. Any ideas?

Thanks!

 

Event Viewer Spam Causing PC Stutter - Events 5379, 4624, 4672 -- Security Audits

Hi,

Since getting my new PC, I have experienced these instances of noticeable stutter when browsing, gaming, or simply being on the desktop. The best way to describe it is as a very brief but noticeable micro-stutter/micro-freeze, the screen does not flash and
audio does not cut out. It lasts for about half a second, but it is very noticeable and annoying, especially when playing games. After spending hours troubleshooting, I have ended up finding the cause. These stutters happen at the exact same logs are generated
in the Event Viewer application. These logs are listed under the "Audit Success" column and I currently have about 5000 of these logs just in the last 24 hours. Out of these logs, there are 3 particular Event ID logs that correlate with my stuttering: Event
ID: 4624, 4672, and 5379. The 4624 and 4672 occur more frequently than the 5379 and the stutter resulting from them is less severe. The 5379 event however, results in the worst stuttering. This is probably because the 5379 event is logged about 300 times during
instances of stutter. Event Viewer shows event 5379 being logged around 300 times at the exact same time interval (For example 300 entries all at 1:00:00PM or 2:37:51PM etc etc).

The events themselves have different descriptions for why they're occuring:

Event 4624:

An account was successfully logged on.

Subject:

Security ID: SYSTEM

Account Name: DESKTOP-N2CELSJ$

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: 0x358

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.

Event 4672:

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

Event 5379:

Credential Manager credentials were read.

Subject:

Security ID: DESKTOP-N2CELSJ\bback

Account Name: bback

Account Domain: DESKTOP-N2CELSJ

Logon ID: 0x85277

Read Operation: Enumerate Credentials

This event occurs when a user performs a read operation on stored credentials in Credential Manager.

Screenshots:









I'm really at a loss of how to fix this. If anyone has any suggestions or has experienced this before please tell me how I should go about solving this. Thank you.