Sporadic short freezes accompanied by 4624 and 4672 events


  1. Posts : 5
    Win 7 Enterprise 64
       #1

    Sporadic short freezes accompanied by 4624 and 4672 events


    Hi,

    I have read the 2 other relevant threads in SevenForums (as well as many others on other sites) but I still have not found a solution to this issue.

    My Lenovo T530 will randomly freeze an application for a couple of seconds at a time. The behavior is per application ie: Outlook may freeze but I can still use Chrome. Or Chrome may freeze but Acrobat still works. It can happen to pretty much any application at any unexpected time - sometimes a few times in an hour and sometimes once every few hours. The "freeze time" varies from barely noticeable to ~5 seconds.

    I have definitely connected these freezes to events 4624 (An account was successfully logged on) and 4672 (Special privileges assigned to new logon) that appear in the event viewer under the Security Logs section but it is not clear to me what may cause them.

    I have performed most of the tests/SFC/device driver/bios upgrade/malware scans that have been recommended (with no change). I have not completely ruled out some strange HDD issue - but I am not sure why such behavior would just start one day (when the laptop had been working perfectly for 8 months). Also there are intensive HDD tasks that produce no errors. The symptoms are not getting worse - it has been the same since it started happening.

    Thanks in advance for any suggestions.

    A sample Security Auditing 4624 event is pasted below:

    ______________________________________________
    An account was successfully logged on.

    Subject:
    Security ID: SYSTEM
    Account Name: <edited>-LT-W7$
    Account Domain: <edited>
    Logon ID: 0x3e7

    Logon Type: 5

    New Logon:
    Security ID: SYSTEM
    Account Name: SYSTEM
    Account Domain: NT AUTHORITY
    Logon ID: 0x3e7
    Logon GUID: {00000000-0000-0000-0000-000000000000}

    Process Information:
    Process ID: 0x484
    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 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.
      My Computer


  2. Posts : 5
    Win 7 Enterprise 64
    Thread Starter
       #2

    More info


    I have also now noticed that these events are immediately preceded by a 7036 event: "The Windows Error Reporting Service service entered the running state."

    Not sure if this is causing the slowdown or is a response to some other event that is causing the slowdown. There is some relation since the logon 4624 event is from: Process Name: C:\Windows\System32\services.exe - which activates the error reporting service.

    Is there a way to know why the Windows Error Reporting Service activates?

    Happy to receive any suggestions.

    Thanks

    GF
      My Computer


  3. Posts : 5
    Win 7 Enterprise 64
    Thread Starter
       #3

    Probably solved


    I think I might have solved the problem - I say "think" since there are moments of unresponsiveness but these seem to be limited to Outlook and specific IMAP servers so the problem is probably connectivity related for these.

    After noticing that the Windows Error Reporting Service was part of the freeze process I looked into this to see if maybe one of these reports would explain the error. In the "action center" I found a list of around 7 errors that had not been reported (for some reason) - and some were over a year old. I tried to re-report them and the process failed. So I simply archived each of them. And that was that (!) - since then the Error Reporting Service has not started (as far as I can see) and no big freezes.

    So I'm guessing the issue was the Error Reporting Service waking up for some reason and then freezing everything while it tried to unsuccessfully send a whole bunch of old reports.

    To access the reports: "You’ll find a list of all crash reports behind the link “View problems to report” in the Maintenance section. If you type “view problems” in the Windows Start Menu search prompt, you will probably get quicker access the Action Center applet. Clicking on “View technical details”, will then display the information in the corresponding .wer file." - from Windows Error Reporting (WER) ? View .wer files - 4sysops.

    Marking as solved - hope this helps anyone with similar issues.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:56.
Find Us