2BrightSparks

[derektom]

SyncBackPro had been working fine for months but upon rebooting after the Windows XP Pro host system crashed, SyncBackPro 5.4.0.7 (latest version at this time) crashes immediately upon launch. Faulting module is mstask.dll (Microsoft's scheduler?).

Here is what I see in Event Viewer.

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 4/6/2009
Time: 11:58:21 AM
User: N/A
Computer: KELLY
Description:
Faulting application SyncBackPro.exe, version 5.4.0.7, faulting module mstask.dll, version 5.1.2600.2180, fault address 0x00005065.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 53 79 6e ure Syn
0018: 63 42 61 63 6b 50 72 6f cBackPro
0020: 2e 65 78 65 20 35 2e 34 .exe 5.4
0028: 2e 30 2e 37 20 69 6e 20 .0.7 in
0030: 6d 73 74 61 73 6b 2e 64 mstask.d
0038: 6c 6c 20 35 2e 31 2e 32 ll 5.1.2
0040: 36 30 30 2e 32 31 38 30 600.2180
0048: 20 61 74 20 6f 66 66 73 at offs
0050: 65 74 20 30 30 30 30 35 et 00005
0058: 30 36 35 065


Any suggestions?

Thanks in advance for any feedback!

Cheers,
Derek

[derektom]

I just discovered that Explorer crashes if I try to run System Tools > Scheduled Tasks. Again, the culprit is mstask.dll.

Would appreciate any suggestions for overcoming this issue!

Thanks,
Derek

[Dave Wilkins]

The scheduler is obviously broken (now where have I heard that before?). You might be able to stop it crashing things if you disable the service, but that would obviously prevent you from scheduling profiles (unless you got a 3rd-party one). You've obviously got schedules set up or SyncBackPro wouldn't be referencing mstask.dll

It might be simply that file is corrupt. Try cross-checking the version you presumably have stashed at

C:\windows\system32\dllcache\

with the one at

C:\windows\system32\

I have two such copies on XP Pro SP3, both 269KB, dated 27/07/2007 and both have an SHA1 hash of 4E6DBF96CE93086CD3CF4FE4B781D1B849B02508. It is thus identical in both places. Check yours? If they're different, maybe copy the one from the cache over the live one? But there may be onward dependencies which are where the fault really is.

Otherwise it's either re-install the OS or perhaps follow that MS link - oh, wait, it's a broken link (now where have I heard that before?) - OK, try Google...
_________________
Regards,

Dave Wilkins

2BrightSparks Pte Ltd
www.2brightsparks.com
Power with Ease - Indispensable Utility Software

[derektom]