Dota 2 make my window restart almost every 5-10 minutes

Hi yuanzz :)

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

OS Name    Microsoft Windows 7 Ultimate
Version    6.1.7600 Build 7600

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

A stop ox116 is a graphics/display related BSOD.
Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer running hot? Let us see. Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following Screenshots and Files - Upload and Post in Seven Forums .

Sometimes the latest 320.49 WHQL display driver is troublesome. Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

______________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800c4bd010, fffff880061da700, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+8ed700 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c4bd010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880061da700, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+8ed700
fffff880`061da700 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03b90b48 fffff880`04ac2cbc : 00000000`00000116 fffffa80`0c4bd010 fffff880`061da700 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03b90b50 fffff880`04a96867 : fffff880`061da700 fffffa80`0ac39000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03b90b90 fffff880`04ac2acb : fffffa80`ffffd87b 00000000`00000000 fffffa80`0c4bd010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03b90c40 fffff880`04b91ec1 : fffffa80`077c7640 00000000`00000080 00000000`00000000 fffffa80`0ab8e410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03b90cc0 fffff800`0352d166 : 00000000`01ca6ddb fffffa80`0aa52b60 fffffa80`066e5040 fffffa80`0aa52b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03b90d00 fffff800`03268486 : fffff800`03402e80 fffffa80`0aa52b60 fffff800`03410c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b90d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8ed700
fffff880`061da700 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8ed700

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`058ed000 fffff880`063d2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you got the BSOD during Furmark, it is most possible that the GPU is faulty. As you are saying that it is a new PC, get the GPU changed.