System is restarting while working with VS 2010 and Vault

[sujith]

Hi,
System is restarting while working with VS 2010 and Vault.

OS- Windows 7 Prof
Vault- V 5.0.4
Visual Studio 2010

Sometimes system is getting restarted while working with Visual Studie-2010 and Vault client. Its getting hanged for a minute and getting restarted without showing any error or information message. We can't do any operation at the time of system getting hanged. After resarted the system I am getting a popup asking "check for solution".
The error message in that popup is

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: 887EB0E0
BCP2: 90E199B0
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011211-18174-01.dmp
C:\Users\Sujith\AppData\Local\Temp\WER-115440-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

But when I check for the xml file it is not available in that place.
Somebody please help me to resolve this issue. Thanks in advance.

[lbauer]

When you say the "system" is restarting, do you mean Visual Studio crashes and you need to restart it? Or does the entire machine crash and need to be rebooted?

Is this a new problem? Was Vault/Visual Studio working properly before?

Are you using the Enhanced or Classic Client integration?

What are you doing in Visual Studio and Vault when this crash happens?

Is there anything in the Windows Event viewer that could provide some clues?

Are there any client-side logs that cover the time of the crash? Look in your temp directory fo VaultGUICLient.txt or VaultVSIPClient.txt?

[Mike Dimmick]

A 'blue screen of death' is never caused directly by user-mode code. It indicates that a device driver or hardware did something wrong. Windows stops the system (with an automatic restart) as MS feels it is safer to halt early rather than carry on and potentially corrupt user data. It's certainly possible that the sequence of steps carried out by user-mode programs revealed a problem in the driver.

Bug Check code 0x116 is a VIDEO_TDR_ERROR. It indicates that a) the video device driver hung and b) that it didn't recover when the watchdog timer tried to fix the problem automatically. You should see if a newer device driver is available from the video card or chipset manufacturer, or for laptops, try the laptop manufacturer. If the laptop manufacturer doesn't have a newer driver or doesn't officially support Windows 7, and there isn't one available from the chipset manufacturer, try laptopvideo2go.com.

Visual Studio 2010 uses Windows Presentation Foundation, which relies on graphics card 3D acceleration through DirectX. I've seen a number of different technologies reveal driver problems when they adopted DirectX rendering (e.g. Java, Flash).