Hi and Welcome to SF!!!
Stop code 116 is usually related to graphic card. The first thing to try is to re-install the graphic card
driver.
When upgrading your graphic
driver you MUST remove all traces of the current
driver. In order to do that we recommend using
Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Read this article for more detail for more tests to try:
http://www.sevenforums.com/crash-loc...eshooting.html
The best thing to try is to try another graphic card on your system to see if it make any differences.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.915\090610-31106-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02ea4e50
Debug session time: Mon Sep 6 23:56:00.839 2010 (UTC + 7:00)
System Uptime: 0 days 0:04:41.852
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80065ee4e0, fffff880105e1f08, 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+700f08 )
Followup: MachineOwner
--------- Regard,
Tuan