Article ID: 308362 - Last Review: October 30, 2006 - Revision: 2.1

Error Message Appears When You Start Laplink PCsync Version 2.0 on Windows XP

View products that this article applies to.

This article was previously published under Q308362

SYMPTOMS

After you install Laplink PCsync version 2.0 and specify the USB transfer software, when you try to start the PCsync program, the computer displays the following error message and then spontaneously restarts:

*** Fatal System Error: 0x000000d1 (0x0000000A,0x00000002,0x00000000,0xFC37664A)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 (http://support.microsoft.com/kb/322389/EN-US/ ) How to Obtain the Latest Windows XP Service Pack

This update is available on the Microsoft Windows Update Web site.

Collapse this imageExpand this image

Download the "Windows XP Application Compatibility Update" now (http://windowsupdate.microsoft.com/)

Release Date: October 25, 2001

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (http://support.microsoft.com/kb/119591/EN-US/ ) How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. The English version of this fix should have the following file attributes or later:

   Date         Time   Version      Size       File name     Platform
   ------------------------------------------------------------------   
   24-Sep-2001  16:10  5.1.2600.14  1,229,824  Acgenral.dll  i386   
   24-Sep-2001  16:10  5.1.2600.14    370,688  Aclayers.dll  i386   
   24-Sep-2001  16:10  5.1.2600.14     45,568  Aclua.dll     i386   
   24-Sep-2001  16:10  5.1.2600.14    204,288  Acspecfc.dll  i386   
   24-Sep-2001  16:10  5.1.2600.14    148,480  Acverfyr.dll  i386   
   24-Sep-2001  16:10  5.1.2600.14    105,472  Acxtrnal.dll  i386   
   12-Oct-2001  21:56                 189,750  Apphelp.sdb   i386   
   24-Sep-2001  16:11                  81,408  Apps.chm      i386   
   10-Oct-2001  11:22  5.1.2600.15  1,181,184  D3d8.dll      i386   
   12-Oct-2001  21:56                   8,140  Drvmain.sdb   i386   
   12-Oct-2001  21:56                 134,388  Msimain.sdb   i386   
   12-Oct-2001  16:08  6.4.2600.0     356,352  Qdvd.dll      i386   
   12-Oct-2001  21:56               1,032,922  Sysmain.sdb   i386   
   12-Oct-2001  19:04  5.6.0.6914     483,379  Vbscript.dll  i386

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

Back to the top