Customer receives error message including the string “External Exception: C0000006”

1. Ask customer if it is happening on multiple computers
   1. If yes, check the Recommended Network Troubleshooting#toc3 settings on the server - especially the NIC Hibernation
   2. Can check on the client machines as well
   3. If continues to occur, explain to customer this error is a connectivity error
   4. Explain they need to get a network tech out to check the Server NIC, Cable, Router/Switch
2. If no, check the Power Management settings on the client machine - specifically the NIC Hibernation
3. If continues to occur, explain to customer this error is a connectivity error
4. Explain they need to get a network tech out to check the client machine NIC, Cable, and probably the rest of the network

If the steps in Resolution 1 have been taken and there is not an issue with the network connection between server and client, find out if the a Terminal Server or Application Server is being used. If so, it's possible the issue is being caused by File Control Blocks (FCB) for programs being accessed directly over a network share.

Symptoms:

• White Process Names in Task Manager
• Random Crashing with exception code c0000006 in Event Viewer

Cause:

See MS KB 2536487

http://support.microsoft.com/kb/2536487

This is an Issue with how FCB (File Control Blocks) for programs being accessed directly over a network share on a 2008 32bit+ RDS/Term server .

Example:

On a 2012 R2 RDS server the end user launches \\Appservername\share\Program.exe

Solution:

If the application running over a network share, try moving Control.exe and related files to the Terminal Server and try running the application locally to see if the symptoms go away.

The files needed for this are as follows:

• Control.exe
• Control_Options.txt (optional)
• CyrRptViewer.exe
• libeay32.dll
• MSVCR100.DLL
• ssleay32.dll
• SystemConfig.mdb
• SystemData.mdb
• Dictionaries Folder