After doing the detailed investigations on this kind of reported issues for the application, which leverages Windows Azure Cache (Preview) feature, it noticed that majority of this issue caused due to one of the below reasons.

1.Storage Account Details for maintaining the cache cluster’s runtime state :  I have noticed that developers forget to update the proper Windows Azure Storage account credential for maintaining the cache   cluster’s runtime state before deploying the Windows Azure Cache (Preview) feature enabled application to Azure Portal. So please verify, you have already modify the appropriate storage credential details for maintaining the cache cluster’s runtime state. Please refer below screen shot :

2. Inadequate Cache Size for Co-located  Role : The deployed Web/Worker Role will be recycled, if you provide the Cache Size (%) below 15% , and also, if you provide the value less than 15%, VS 2010 does gives a warning message. So please make sure you have provided the appropriate Cache size (ideally 30%) for the Co-located Role  . Please refer below screen shot for the same :

       Typically for #2,  you will  find below mentioned details from the memory crash dump for ‘CacheInstaller.exe’ from the VM:

0:000> |
.  0   id: ce0       examine       name: E:\plugins\Caching\CacheInstaller.exe

0:000> !threads
PDB symbol for clr.dll not loaded
ThreadCount:      7
UnstartedThread:  0
BackgroundThread: 6
PendingThread:    0
DeadThread:       0
Hosted Runtime:   no
                                           PreEmptive                                                   Lock
       ID  OSID        ThreadOBJ     State GC       GC Alloc Context                  Domain           Count APT Exception
   0    1   624 0000000000220850      a020 Enabled  00000000021abf48:00000000021abfd0 0000000000213a80     0 MTA Microsoft.ApplicationServer.Caching.DataCacheException (00000000020be488)
   2    2   d18 0000000000225a60      b220 Enabled  0000000000000000:0000000000000000 0000000000213a80     0 MTA (Finalizer)
   4    3   f68 000000000190f180   1009220 Enabled  0000000001d831b8:0000000001d83fd0 0000000000213a80     0 MTA (Threadpool Worker)
   5    4   c68 000000000190e9c0   1009220 Enabled  0000000001d12690:0000000001d13fd0 0000000000213a80     0 MTA (Threadpool Worker)
   7    5   f04 000000000192b120   1009220 Enabled  0000000001d7df30:0000000001d7dfd0 0000000000213a80     0 MTA (Threadpool Worker)
   8    6   5e4 000000001a8d68a0   8009220 Enabled  0000000000000000:0000000000000000 0000000000213a80     0 MTA (Threadpool Completion Port)
   9    7   bec 000000001a8e7770   100a220 Enabled  0000000000000000:0000000000000000 0000000000213a80     0 MTA (Threadpool Worker)

0:000> !pe  00000000020be488
Exception object: 00000000020be488
Exception type:   Microsoft.ApplicationServer.Caching.DataCacheException
Message:          Exception was thrown while setting cache host size
InnerException:   Microsoft.ApplicationServer.Caching.DataCacheException, Use !PrintException 00000000020be1b8 to see more.
StackTrace (generated):
    SP               IP               Function
    00000000003BC6E0 000007FF0019DB8F Microsoft_ApplicationServer_Caching_DedicatedCacheProviders!Microsoft.ApplicationServer.Caching.Configuration.AzureClusterHostConfigurationReader.SetCacheHostSize()+0x32f
    00000000003BE810 000007FF001942B8 Microsoft_ApplicationServer_Caching_Core!Microsoft.ApplicationServer.Caching.ClusterConfigReader..ctor(Microsoft.ApplicationServer.Caching.ClusterConfigElement)+0x288
    00000000003BE8B0 000007FF00193E83 Microsoft_ApplicationServer_Caching_Core!Microsoft.ApplicationServer.Caching.ClusterConfigurationFactory.GetReader(Microsoft.ApplicationServer.Caching.ClusterConfigElement)+0x153
    00000000003BE8F0 000007FF00193904 Microsoft_ApplicationServer_Caching_AzureCommon!Microsoft.ApplicationServer.Caching.AzureCommon.Package.InitializeExternalStoreIfRequired()+0x54
    00000000003BE950 000007FF00193852 CacheInstaller!Microsoft.ApplicationServer.Caching.CacheInstaller.CloudPackage.InstallAndStart()+0x12
    00000000003BE990 000007FF001802E6 CacheInstaller!Microsoft.ApplicationServer.Caching.CacheInstaller.CacheInstaller.Main(System.String[])+0x146

0:000> !do 00000000020be0b8
Name:        System.String
MethodTable: 000007fee7a76ac8
EEClass:     000007fee75fed58
Size:        254(0xfe) bytes
File:        D:\windows\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll
String:      Value of CacheSizePercentage too small. Please increase value to support at least 32 MB of Cache (user data space)

References :

Windows Azure Caching (Preview)
https://msdn.microsoft.com/en-us/library/windowsazure/hh914153.aspx

How to Use Windows Azure Caching (Preview)
https://www.windowsazure.com/en-us/develop/net/how-to-guides/cache/

Capacity Planning Considerations for Windows Azure Caching (Preview)
https://msdn.microsoft.com/en-us/library/windowsazure/hh914129.aspx

There are basically three kind of applications, Web Role, Worker Role, and VM Role, were running under Windows Azure environment, and  all the deployed applications  in Windows Azure environment will be running in separated Guest Virtual Machine (VM) with  one of the below mentioned configuration’s : 

1. Windows Guest OS Family 1 which is substantially compatible with Windows Server 2008 SP2 with  IIS 7.0
2. Windows Guest OS Family 2 which is substantially compatible with Windows Server 2008 R2 with IIS 7.5
   

You can find more details about the Operating System and supported SDK version from below mentioned web links

•  Windows Azure Guest OS Releases and SDK Compatibility Matrix
• https://msdn.microsoft.com/en-us/library/windowsazure/ee924680.aspx

 Also, please note that you  can configure the required version of Guest VM for the deployed application in the ‘ServiceConfiguration.*.cscfg’  file, and later if you need to modify the OS details after deployment, you can modify the same from the Windows Azure Portal.  Please find below mentioned web links, which could provide the detailed information about configuring the OS versions with  ‘ServiceConfiguration.*.cscfg’ file and  same from the Azure Portal

• How to Upgrade the Guest OS in the Service Configuration File
• https://msdn.microsoft.com/en-us/library/windowsazure/gg456324.aspx

 <ServiceConfiguration serviceName="<service-name>" osFamily="[1|2]” osVersion="<os-version>">
 <Role name="<role-name>">
 <Instances count="<number-of-instances>" /> 
 <ConfigurationSettings>
 <Setting name="<setting-name>" value="<setting-value>" />
 </ConfigurationSettings>
 <Certificates>
 <Certificate name="<certificate-name>" thumbprint="<certificate-thumbrint>" thumbprintAlgorithm="<algorithm>"/>
 </Certificates> 
 :
 : 
</Role>
</ServiceConfiguration>
 

• How to Upgrade the Guest OS in the Management Portal
• https://msdn.microsoft.com/en-us/library/windowsazure/gg433101.aspx

 [DataCacheException: ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises
cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts.
aso the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.)]

This issue might be happed due to hitting the Windows Azure Cache limitation, where you can not add more than 8MB data at a time. The simple workaround for this issue is to split the object into smaller chunks, i.e  you can  serialize the object into smaller byte arrays
and pass the arrays to cache as multiple objects. The same limiatation is documented in below mentioned msdn article :

• API Reference for Windows Azure Caching
  https://msdn.microsoft.com/en-us/library/windowsazure/gg278350.aspx
   

 If the size is under 8MB, and you still receive the same error then please make sure to change the DataCacheFactoryConfiguration.TransportProperties.ReceiveTimeout  to below 60 Seconds as mentioned in this blog post

Issue Details :

Windows 7 operating system crashes, while opening the multiple instances of Silverlight project through Visual Studio 2010 SP1 IDE. Troubleshoot this issue further; we have collected below data from the machine, which was crashed:

1. Windows Event Log [System Event Log]
2. Kernel Memory dump located under ‘%SystemRoot%\MEMORY.DMP’

Windows Event Log [System Event Log]

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          XXXXXXXXXXXXXXXX
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXXXX
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0x8894a008, 0x990499b0, 0x00000000, 0x00000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: XXXXXXX

Log Name:      System
Source:        EventLog
Date:          XXXXXXXXXXXXXXXXX
Event ID:      6008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXXXXXXXX
Description:
The previous system shutdown at XXXX  on XXXXXXXX was unexpected.

The above event logs indicate that, Operating System is crashed due to Bug Check 0x116. To get the more detail about this, I have reviewed the Kernel dump

Kernel Memory dump 

VIDEO_TDR_FAILURE (116)  =>  This indicate that an attempt to reset the display driver and recovered from a timeout failed (Ref Bug Check 0x116).
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 8894a008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 990499b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffffff85701510
   +0x000 Signature        : 0x52445476
   +0x004 pState           : 0x870ab638 0 ( TdrStateIdle )
   +0x008 TimeoutReason    : 2 ( TdrReasonPreemptTimeout )
   +0x010 Tick             : _ULARGE_INTEGER 0xc0
   +0x018 pAdapter         : 0x84f88000 DXGADAPTER
   +0x01c pVidSchContext   : 0x8708a4d8 _VIDSCH_CONTEXT
   +0x020 GPUTimeoutData   : _TDR_RECOVERY_GPU_DATA
   +0x038 CrtcTimeoutData  : _TDR_RECOVERY_CONTEXT::<unnamed-type-CrtcTimeoutData>
   +0x040 DbgOwnerTag      : 0x9a8439b0
   +0x048 PrivateDbgInfo   : _TDR_DEBUG_REPORT_PRIVATE_INFO
   +0xad0 pDbgReport       : 0xc9348008 _WD_DEBUG_REPORT
   +0xad4 pDbgBuffer       : 0xcd000000 Void
   +0xad8 DbgBufferSize    : 0x40c5b
   +0xadc pDumpBufferHelper : 0xcc9b8070 CTDR_DUMP_BUFFER
   +0xae0 pDbgInfoExtension : 0xcc124e08 _DXGKARG_COLLECTDBGINFO_EXT
   +0xae4 pDbgBufferUpdatePrivateInfo : 0xcd000108 Void
   +0xae8 ReferenceCount   : 0n1

The Crash occurred due to an issue with the windows display driver model (wddm), and please finds the detail about the crashing thread as below

0: kd> !thread
THREAD 86f66550  Cid 0004.01c4  Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
Not impersonating
DeviceMap                 8bc084b0
Owning Process            84f09bb0       Image:         System
Attached Process          N/A            Image:         N/A
Wait Start TickCount      20602          Ticks: 0
Context Switch Count      6865           IdealProcessor: 0            
UserTime                  00:00:00.000
KernelTime                00:00:01.232
Win32 Start Address dxgmms1!VidSchiWorkerThread (0x996444f4)
Stack Init 807adfd0 Current bd47b350 Base 807ae000 Limit 807ab000 Call 0
Priority 15 BasePriority 15 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
ChildEBP RetAddr  Args to Child             
807adb74 995c1adb 00000116 8894a008 990499b0 nt!KeBugCheckEx+0x1e (CONV: stdcall)
807adb98 995c28fa 990499b0 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d (FPO: [Non-Fpo]) (CONV: stdcall)
807adbbc 9961892c 00000000 00000102 86f01788 dxgkrnl!TdrIsRecoveryRequired+0xb8 (FPO: [Non-Fpo]) (CONV: stdcall)
807adc34 99642a32 fffffcfb 00004fa5 00000000 dxgmms1!VidSchiReportHwHang+0x3c0 (FPO: [Non-Fpo]) (CONV: stdcall)
807adc5c 99643153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68 (FPO: [Non-Fpo]) (CONV: stdcall)
807adc98 9961f8f0 807adc90 88808120 88a76008 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1 (FPO: [Non-Fpo]) (CONV: stdcall)
807add28 996444b7 86f01788 82a863e1 86f01788 dxgmms1!VidSchiScheduleCommandToRun+0xaa (FPO: [Non-Fpo]) (CONV: stdcall)
807add3c 99644573 86f01788 00000000 86f66550 dxgmms1!VidSchiRun_PriorityTable+0xf (FPO: [Non-Fpo]) (CONV: stdcall)
807add50 82c589df 86f01788 ac78a1f2 00000000 dxgmms1!VidSchiWorkerThread+0x7f (FPO: [Non-Fpo]) (CONV: stdcall)
807add90 82b0a1d9 996444f4 86f01788 00000000 nt!PspSystemThreadStartup+0x9e (CONV: stdcall)
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

0: kd> .bugcheck
Bugcheck code 00000116
Arguments 8894a008 990499b0 00000000 00000002

The 2nd parameter to bug check is 928149b0. This is the pointer into the responsible device driver module.

0: kd> u 990499b0
igdkmd32!DxgkDdiCollectDbgInfo:
990499b0 55              push    ebp
990499b1 8bec            mov     ebp,esp
990499b3 83ec20          sub     esp,20h
990499b6 8b4508          mov     eax,dword ptr [ebp+8]
990499b9 8945f4          mov     dword ptr [ebp-0Ch],eax
990499bc 8b4d0c          mov     ecx,dword ptr [ebp+0Ch]
990499bf 8b510c          mov     edx,dword ptr [ecx+0Ch]
990499c2 8955e4          mov     dword ptr [ebp-1Ch],edx

0: kd> lmvm igdkmd32
start    end        module name
9a832000 9ad2f000   igdkmd32   (pdb symbols)              Loaded symbol image file: igdkmd32.sys
    Mapped memory image file: xxxxxx\igdkmd32.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
    Image name: igdkmd32.sys
    Timestamp:        Wed May 06 23:43:40 2009 (4A01D354)
    CheckSum:         0048DF97
    ImageSize:        004FD000
    File version:     8.15.10.1749
    Product version:  8.15.10.1749
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.4 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Intel Corporation
    ProductName:      Intel Graphics Accelerator Drivers for Windows Vista(R)
    InternalName:     igdkmd32.sys
    OriginalFilename: igdkmd32.sys
    ProductVersion:   8.15.10.1749
    FileVersion:      8.15.10.1749
    FileDescription:  Intel Graphics Kernel Mode Driver
    LegalCopyright:   Copyright (c) 1998-2006 Intel Corporation

RESOLUTION

Based on the above details, we able to fix this issue by updating the ‘igdkmd32.sys’ file from https://www.intel.com/p/en_US/support/detect 

References:

• How to generate a kernel or a complete memory dump file in Windows Server 2008
  https://support.microsoft.com/kb/969028Timeout
• Detection and Recovery of GPUs through WDDM
  https://msdn.microsoft.com/en-us/windows/hardware/gg487368.aspx

Microsoft Windows service, formerly known as NT service, enables you to create a long-running executable application that runs in a separate windows session or we can configure the service to run in a user context other than a logged on user.  Users can make windows services to run automatically without any user interaction.  These features make windows service a powerful application which can be hosted on servers and remote locations where minimum user interaction is required.

       Prior to .NET environment, creating windows services was a tedious job. Earlier, windows services were created using unmanaged application like VC++ 6.0 or VB 6.0 . However after .NET, creating windows service is very easy and it hardly requires any technical knowledge. My article provides simple, easy to follow instructions on creating a simple windows service in .NET platform, which activates based on a timer value.

            To understand more about Microsoft windows service , please go through the following msdn article, Ref: https://msdn.microsoft.com/en-us/library/d56de412(VS.80).aspx , which  goes into more detail about windows service. Also , at the bottom of this article, I am providing a couple of links which explain more about windows service.

Creating a Windows Service which activates based on a timer.

I am planning to cover  the following details in this article.

1. Creating Windows Service Project Using VS Template and setting timer value.

2. Creating an Installer

3. Deploying Service.

4. Verifying whether service works

5. Un-installing service.

6. Additional Reference

I  Creating Windows Service Project Using VS Template

Please follow the steps as given below to create a windows service.

1. Open Visual Studio 2005 IDE

2. On the File menu -> New, and then Project

3. Select  Windows Service Template as shown in screen shot

4. Open  'Service1.vb' file and click 'click here to switch to code view'

5. Add following namespace at top of the Service1.vb file

           Imports System.Timers

           Imports System.Threading  

6. Add following definition just below the class definition.

           Dim oTimerCallback As TimerCallback

           Dim StartTimer As System.Threading.Timer

7. Add following code under sub  'Protected Overrides Sub OnStart(..)

           StartIt()

8. Create a new method call 'StartIt()' and add following code inside it.

   Private Sub StartIt() 

     oTimerCallback = New TimerCallback(AddressOf TestCall)

     StartTimer = New System.Threading.Timer(oTimerCallback, Nothing, 0, CType(60 * 1000, Long))

   End Sub

9. Create a new method 'TestCall' as given below in Service1.vb file.

       Private Sub TestCall(ByVal state As Object)

'add code for required operation.

'This code will execute in every 60 second.

EventLog.WriteEntry("inside TestCall VS 2005")

        End Sub

II Creating an Installer

1. Open service1.vb file inside designer windows 

2. Right click any were in Service1.vb file and select 'Add Installer' as given below

3. Once we select, 'Add Installer', Visual Studio IDE will create an installer with the default name 'ProjectInstaller.vb'. When we open ProjectInstaller.vb inside the designer window, we could see couple of controls like ServiceProcessInstaller1 and ServiceInstaller1. By selecting properties for 'ServiceInstaller1' we could see an option  'StartType' . Were we could change the service startup type by selecting one of the given option as given below.

4. For changing Service account , right click on ServiceProcessInstaller1 and change the 'Account' Property to Local System as given below

5. After creating the installer we can compile the application to create a Windows Service EXE.

III Deploying Service.

            For deploying service, either we can create a setup project (.msi) or we can use command line tool 'Installutil' which shipped with .NET Framework SDK. In this article, I am describing how to deploy our service using 'InstallUtil'. Please follow the steps as given below to deploy windows service using installutil.exe

1. Open Visual Studio Command prompt from 'Start -> Programs->Microsoft Visual Studio 2005 ->Visual Studio Tools -> Visual Studio 2005 Command Prompt'

2. Navigate to the folder where our 'Windows Service' application is compiled. Please find the screen shot

3. Type  'Installutil  <<Service Name>>.exe as given below

Note: If we select the 'Account' type as 'User', application would prompt for username and password in which context service need to run.

IV  Verifying whether service works

  To verify whether our service works, follow the steps as given below.

1. Click 'Start ->Control Panel -> Administrative Tools' , and then click Services .

2. Select our installed service [by default service name should be 'Service1' as given below

3. Right-click on Service1 and then click start

4. To verify that an event is logged in the event log [Start->Control Panel -> Administrative Tools and then click 'Event Viewer'. In the left pane, click 'Application Log', in the right pane locate the event log for our service and we could see below event information.

"inside TestCall VS 2005"

V  Un-installing service.

For un-installing service, enter following command  inside Visual Studio command prompt by navigating to the folder where our .exe is created , 'Installutil  <<Service Name>>.exe  /u' as given below

Additional Reference

1.   317421  How to create a Setup project for a Windows Service in Visual Basic .NET or in Visual Basic 2005

     https://support.microsoft.com/default.aspx?scid=kb;EN-US;317421

2.  Introduction to Windows Service Applications

      https://msdn.microsoft.com/en-us/library/aa983650(VS.71).aspx

3.   820639  The Windows Forms Timer event is not raised in a Windows service

      https://support.microsoft.com/default.aspx?scid=kb;EN-US;820639

4.   821794  Descriptions of some best practices when you create Windows Services

      https://support.microsoft.com/default.aspx?scid=kb;EN-US;821794

PrjWinService.zip

"

The application has failed to start because its side-by-side configuration s incorrect. Please see the application event log for more details.

"

To resolve this issue you can follow any one of the following suggestions.

1. Upgrade the Vista machine with SP1
2. Install the latest service pack for VC++ redistribution package which automatically update  WinSxS folder.

      Reference:

========

1. it's advisable to create a setup package for redistributing Visual C++ application. You can find complete information about creating set up package from  Visual C++ Team Blog     

2. There is a pretty good article about side-by-side installation and proper usage for sxstrace.exe by Junfeng Zhang's