Server 2008R2 SP1 Task Scheduler Engine Has Stopped Working (APPCRASH)


  • When our primary domain administrator account is logged into this particular server only, after a variable period of time, the task scheduler engine will crash with the following information:

    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: taskeng.exe
      Application Version: 6.1.7601.17514
      Application Timestamp: 4ce79d2c
      Fault Module Name: msvcrt.dll
      Fault Module Version: 7.0.7601.17744
      Fault Module Timestamp: 4eeb033f
      Exception Code: c0000005
      Exception Offset: 00000000000027de
      OS Version: 6.1.7601.
      Locale ID: 1033
      Additional Information 1: 5fb3
      Additional Information 2: 5fb30332e166f610c2aca200ca407dc5
      Additional Information 3: bef3
      Additional Information 4: bef3b6202a3561e7a739ca9e475d355b

    The event viewer shows this:

    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          7/13/2012 9:27:30 AM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.COM
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: taskeng.exe
    P2: 6.1.7601.17514
    P3: 4ce79d2c
    P4: msvcrt.dll
    P5: 7.0.7601.17744
    P6: 4eeb033f
    P7: c0000005
    P8: 00000000000027de

    Other windows accounts (some who are domain admins and some who are not) can be logged in for weeks at a time and this never happens.  When the error comes up, if you click OK, everything is fine.  The service itself never stops, starts or restarts, but if the domain admin is logged in and the task scheduler crashes, scheduled tasks (even those setup to run as a different user) fail to run and get stuck in a QUEUED state.  If I say OK to the error or log off of the account, the tasks will then run.

    I have spent a lot of time trying to figure this out and have had no luck.  Any ideas are greatly appreciated.

    Friday, July 13, 2012 2:48 PM

All replies

  • Hello,

    1. Taskeng.exe or msvcrt.dll might be corrupt. I would firstly run SFC /scannow to scan the system integration and fix any corruption. If it finds any corrupted components, I’d run In-place upgrade to repair Windows.

    2. Then, I’d temporarily disable all tasks. And check if Task Scheduler still crashes without tasks. You can also export the tasks and delete them. If there be no more crashes, then one of the tasks caused the tasking.exe to crash.

    How to export tasks

    3. Can you delete this account and re-build it? This might be an account problem.


    Monday, July 16, 2012 8:11 AM
  • SFC /SCANNOW says there are no issues.  I can't disable the tasks because quite a few of them run frequently throughout the day and have to run.  The account in question is the default/built in domain administrator account and so I cannot just "rebuild" it.  At this point what I am going to do is I am going to just re-create all the tasks in question and see what happens.  I will provide an update after this is done.
    Tuesday, July 17, 2012 2:08 PM