Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 116 error

01 Jan 2012   #1
HenryVII

Windows 7 Home Premium
 
 
BSOD 116 error

Hi,
This evening on bootup of my PC during loading of Windows 7 Home Premium i received a BSOD error code 116 and the system reboots. This is the first time i have received such an error.

My graphics card is a Gainward GTX 580 phantom, and has been running all games perfectly since i installed it about a month ago. There is nothing particular that i have done between yesterday and today that i can think of that would trigger it (no new SW or HW installed).

i have reinstalled the video card drivers from the nvidia website but that has not solved the problem.

i have opened up the case and cant see any visible signs of dust buildup and all fans seem to be working ok. CPU temp is 39 deg C but i dont know how i can check the GPU temp.

I am running with a Corsair 620w power supply, could this be an issue? was never a problem before, also had no problems with my old gtx 295.

I am running a multi boot system on separate HDDs and tried booting with Vista but same problem.

I have the 64bit vesion of both Windows Vista and Windows 7.

Hope someone can help me out here!

my motherboard: Asus P6T6 WS revolution

Thanks in advance!


My System SpecsSystem Spec
.
01 Jan 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Welcome to SevenForums. It is difficult to determine your problem with the information provided. Please follow the http://www.sevenforums.com/crashes-d...tructions.html to give us more information to better assist you.
My System SpecsSystem Spec
01 Jan 2012   #3
scrooge

win 7 ( 64 bit)
 
 

Commonly, this error code is seen in Nvdia drivers. Are you able to start in Safe mode?

scrooge
My System SpecsSystem Spec
.

01 Jan 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

For further help with this post, you may want to refer to http://www.sevenforums.com/crashes-d...ode-116-a.html, as well.
My System SpecsSystem Spec
02 Jan 2012   #5
HenryVII

Windows 7 Home Premium
 
 

Just running the BSOD diagnostic programmes now and will upload shortly.
I was able to restart in safe mode.
I have followed the instructions under the Skyrim thread to delete and then reinstall the drivers. This usually leads to a Black Screen Of Death and i had to restore a previously frozen time point through the repair function. On one occasion this did not work, and the only way i could get further was to get through the Black screen pressing F8 to access safe mode.
I have also now updated a number of motherboard files, including the ASACPI.sys file which was dated 2005. I have not updated the BIOS.
However this has not helped and now i am back at square one.
I am unsure if it is a sofware issue or a hardware issue. I find it odd that it would be a temperature related one because it occurred only on startup and occures after the machine being idle the whole night. That said the same problem occurs on my other HDD under Vista, which leads me to think that it is unlikely to be the drivers but still not sure.
Help!!
My System SpecsSystem Spec
02 Jan 2012   #6
zigzag3143

Win 8 Release candidate 8400
 
 

Quote:
"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
My System SpecsSystem Spec
02 Jan 2012   #7
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by HenryVII View Post
Just running the BSOD diagnostic programmes now and will upload shortly.
I was able to restart in safe mode.
I have followed the instructions under the Skyrim thread to delete and then reinstall the drivers. This usually leads to a Black Screen Of Death and i had to restore a previously frozen time point through the repair function. On one occasion this did not work, and the only way i could get further was to get through the Black screen pressing F8 to access safe mode.
I have also now updated a number of motherboard files, including the ASACPI.sys file which was dated 2005. I have not updated the BIOS.
However this has not helped and now i am back at square one.
I am unsure if it is a sofware issue or a hardware issue. I find it odd that it would be a temperature related one because it occurred only on startup and occures after the machine being idle the whole night. That said the same problem occurs on my other HDD under Vista, which leads me to think that it is unlikely to be the drivers but still not sure.
Help!!
It may be bad sectors on the hard disk if you have the same problem under different operating system running from the same disk. Run Disk Check with both boxes checked for all drives containing system, program, and users files. You can schedule/run them from safe mode if needed and let it run upon restarting if it has to schedule the check for the next restart.
My System SpecsSystem Spec
02 Jan 2012   #8
HenryVII

Windows 7 Home Premium
 
 

Here we are: Files uploaded
My System SpecsSystem Spec
02 Jan 2012   #9
writhziden

Windows 7 Home Premium 64 Bit
 
 

Your BIOS is from 2008. You may want to update that once Windows is up and running again. You can find BIOS updates in the Downloads section of ASUSTeK Computer Inc. - Motherboards- ASUS P6T6 WS Revolution
Download both your current version (in case you need to flash back to it due to a problem with the new version [which is rare but does happen]) and the newest non-beta version. You want 0311 and 0905 versions. Use the BIOS utilities provided in the BIOS section for flashing the BIOS (never flash the BIOS through Windows in case something goes wrong in Windows).

You could also get the BIOS updates and utilities from another computer and then use them to flash the BIOS on your machine and see if it fixes the problems you continue to have.

Looking through your dmps now...
My System SpecsSystem Spec
02 Jan 2012   #10
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22495-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`03456670 Debug session time: Sun Jan 1 12:51:46.408 2012 (UTC - 7:00) System Uptime: 0 days 0:00:19.408 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa80088c44e0, fffff8800f3cf9c8, 0, 2} *** 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+1759c8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa80088c44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f3cf9c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f3cf9c8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`0693a9c8 fffff880`0ff2e000 : 00000000`00000116 fffffa80`088c44e0 fffff880`0f3cf9c8 00000000`00000000 : nt!KeBugCheckEx fffff880`0693a9d0 fffff880`0ff2dd0a : fffff880`0f3cf9c8 fffffa80`088c44e0 fffffa80`085e1ab0 fffffa80`0862f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0693aa10 fffff880`0f20ff07 : fffffa80`088c44e0 00000000`00000000 fffffa80`085e1ab0 fffffa80`0862f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0693aa40 fffff880`0f239b75 : 00000000`ffffffff 00000000`00000435 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0693ab20 fffff880`0f2382bb : 00000000`00000102 00000000`00000006 00000000`00000435 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0693ab50 fffff880`0f20b2c6 : ffffffff`ff676980 fffffa80`0862f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0693abf0 fffff880`0f237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0571c678 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0693ad00 fffff800`03528fee : 00000000`02bb8b28 fffffa80`085e28c0 fffffa80`03ced040 fffffa80`085e28c0 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0693ad40 fffff800`0327f5e6 : fffff880`03287180 fffffa80`085e28c0 fffff880`032920c0 fffff880`01437cb0 : nt!PspSystemThreadStartup+0x5a fffff880`0693ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f3cf9c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22245-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03206000 PsLoadedModuleList = 0xfffff800`0344b670 Debug session time: Sun Jan 1 12:55:21.628 2012 (UTC - 7:00) System Uptime: 0 days 0:00:18.517 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800644f4e0, fffff8800f37a9c8, 0, 2} *** 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+1759c8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800644f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f37a9c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f37a9c8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`028de9c8 fffff880`0fed9000 : 00000000`00000116 fffffa80`0644f4e0 fffff880`0f37a9c8 00000000`00000000 : nt!KeBugCheckEx fffff880`028de9d0 fffff880`0fed8d0a : fffff880`0f37a9c8 fffffa80`0644f4e0 fffffa80`0852d6c0 fffffa80`08611010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`028dea10 fffff880`0ff7ff07 : fffffa80`0644f4e0 00000000`00000000 fffffa80`0852d6c0 fffffa80`08611010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`028dea40 fffff880`0ffa9b75 : 00000000`ffffffff 00000000`000003eb 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`028deb20 fffff880`0ffa82bb : 00000000`00000102 00000000`00000006 00000000`000003eb 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`028deb50 fffff880`0ff7b2c6 : ffffffff`ff676980 fffffa80`08611010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`028debf0 fffff880`0ffa7e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`057e0b38 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`028ded00 fffff800`0351dfee : 00000000`0288e129 fffffa80`086128c0 fffffa80`03cd0040 fffffa80`086128c0 : dxgmms1!VidSchiWorkerThread+0xba fffff880`028ded40 fffff800`032745e6 : fffff800`033f8e80 fffffa80`086128c0 fffff800`03406cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`028ded80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f37a9c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22947-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0321c000 PsLoadedModuleList = 0xfffff800`03461670 Debug session time: Sun Jan 1 13:21:16.736 2012 (UTC - 7:00) System Uptime: 0 days 0:00:19.735 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa80088e02e0, fffff8800f3f99c8, 0, 2} *** 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+1759c8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa80088e02e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f3f99c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f3f99c8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`0673f9c8 fffff880`0ff58000 : 00000000`00000116 fffffa80`088e02e0 fffff880`0f3f99c8 00000000`00000000 : nt!KeBugCheckEx fffff880`0673f9d0 fffff880`0ff57d0a : fffff880`0f3f99c8 fffffa80`088e02e0 fffffa80`0861cab0 fffffa80`085fc010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0673fa10 fffff880`0f20ff07 : fffffa80`088e02e0 00000000`00000000 fffffa80`0861cab0 fffffa80`085fc010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0673fa40 fffff880`0f239b75 : 00000000`ffffffff 00000000`00000451 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0673fb20 fffff880`0f2382bb : 00000000`00000102 00000000`00000006 00000000`00000451 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0673fb50 fffff880`0f20b2c6 : ffffffff`ff676980 fffffa80`085fc010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0673fbf0 fffff880`0f237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`05642c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0673fd00 fffff800`03533fee : 00000000`02cea524 fffffa80`0861da10 fffffa80`03ce2040 fffffa80`0861da10 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0673fd40 fffff800`0328a5e6 : fffff800`0340ee80 fffffa80`0861da10 fffff800`0341ccc0 fffff880`01434384 : nt!PspSystemThreadStartup+0x5a fffff880`0673fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f3f99c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22136-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0321e000 PsLoadedModuleList = 0xfffff800`03463670 Debug session time: Sun Jan 1 13:26:50.221 2012 (UTC - 7:00) System Uptime: 0 days 0:00:19.110 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8008a7e010, fffff8800f3b49c8, 0, 2} *** 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+1759c8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8008a7e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f3b49c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f3b49c8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`069359c8 fffff880`0ff13000 : 00000000`00000116 fffffa80`08a7e010 fffff880`0f3b49c8 00000000`00000000 : nt!KeBugCheckEx fffff880`069359d0 fffff880`0ff12d0a : fffff880`0f3b49c8 fffffa80`08a7e010 fffffa80`08641810 fffffa80`08621010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`06935a10 fffff880`0ffb9f07 : fffffa80`08a7e010 00000000`00000000 fffffa80`08641810 fffffa80`08621010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`06935a40 fffff880`0ffe3b75 : 00000000`ffffffff 00000000`00000410 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`06935b20 fffff880`0ffe22bb : 00000000`00000102 00000000`00000006 00000000`00000410 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`06935b50 fffff880`0ffb52c6 : ffffffff`ff676980 fffffa80`08621010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`06935bf0 fffff880`0ffe1e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`08131168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`06935d00 fffff800`03535fee : 00000000`02a22e88 fffffa80`08642a10 fffffa80`03cd0040 fffffa80`08642a10 : dxgmms1!VidSchiWorkerThread+0xba fffff880`06935d40 fffff800`0328c5e6 : fffff880`03287180 fffffa80`08642a10 fffff880`032920c0 fffff880`01456cb0 : nt!PspSystemThreadStartup+0x5a fffff880`06935d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f3b49c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22198-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03256000 PsLoadedModuleList = 0xfffff800`0349b670 Debug session time: Sun Jan 1 13:49:30.173 2012 (UTC - 7:00) System Uptime: 0 days 0:00:20.172 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8008a8b010, fffff8800f3c89c8, 0, 2} *** 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+1759c8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8008a8b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f3c89c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f3c89c8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`069469c8 fffff880`0ff27000 : 00000000`00000116 fffffa80`08a8b010 fffff880`0f3c89c8 00000000`00000000 : nt!KeBugCheckEx fffff880`069469d0 fffff880`0ff26d0a : fffff880`0f3c89c8 fffffa80`08a8b010 fffffa80`0864aab0 fffffa80`08613010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`06946a10 fffff880`0f20ff07 : fffffa80`08a8b010 00000000`00000000 fffffa80`0864aab0 fffffa80`08613010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`06946a40 fffff880`0f239b75 : 00000000`ffffffff 00000000`0000044d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`06946b20 fffff880`0f2382bb : 00000000`00000102 00000000`00000006 00000000`0000044d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`06946b50 fffff880`0f20b2c6 : ffffffff`ff676980 fffffa80`08613010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`06946bf0 fffff880`0f237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0810a808 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`06946d00 fffff800`0356dfee : 00000000`02cbe6ee fffffa80`0864ba10 fffffa80`03cd0040 fffffa80`0864ba10 : dxgmms1!VidSchiWorkerThread+0xba fffff880`06946d40 fffff800`032c45e6 : fffff800`03448e80 fffffa80`0864ba10 fffff800`03456cc0 fffff880`0144a384 : nt!PspSystemThreadStartup+0x5a fffff880`06946d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f3c89c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010212-20124-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`034a6670 Debug session time: Mon Jan 2 11:12:11.546 2012 (UTC - 7:00) System Uptime: 0 days 0:00:21.545 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8008605010, fffff8800f3a99c8, 0, 2} *** 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+1759c8 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8008605010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f3a99c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f3a99c8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`063aa9c8 fffff880`0ff08000 : 00000000`00000116 fffffa80`08605010 fffff880`0f3a99c8 00000000`00000000 : nt!KeBugCheckEx fffff880`063aa9d0 fffff880`0ff07d0a : fffff880`0f3a99c8 fffffa80`08605010 fffffa80`0834c6c0 fffffa80`0832c010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`063aaa10 fffff880`0ffaef07 : fffffa80`08605010 00000000`00000000 fffffa80`0834c6c0 fffffa80`0832c010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`063aaa40 fffff880`0ffd8b75 : 00000000`ffffffff 00000000`000004ab 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`063aab20 fffff880`0ffd72bb : 00000000`00000102 00000000`00000006 00000000`000004ab 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`063aab50 fffff880`0ffaa2c6 : ffffffff`ff676980 fffffa80`0832c010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`063aabf0 fffff880`0ffd6e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0619d168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`063aad00 fffff800`03578fee : 00000000`0303e16b fffffa80`0834d8c0 fffffa80`03cd0040 fffffa80`0834d8c0 : dxgmms1!VidSchiWorkerThread+0xba fffff880`063aad40 fffff800`032cf5e6 : fffff800`03453e80 fffffa80`0834d8c0 fffff800`03461cc0 fffff880`0144fcb0 : nt!PspSystemThreadStartup+0x5a fffff880`063aad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f3a99c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010212-22448-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`03494670 Debug session time: Mon Jan 2 12:14:03.096 2012 (UTC - 7:00) System Uptime: 0 days 0:00:19.096 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8008a8a010, fffff8800f38d6e8, 0, 2} 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+1796e8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8008a8a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f38d6e8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1796e8 fffff880`0f38d6e8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`0666a9c8 fffff880`0ff24000 : 00000000`00000116 fffffa80`08a8a010 fffff880`0f38d6e8 00000000`00000000 : nt!KeBugCheckEx fffff880`0666a9d0 fffff880`0ff23d0a : fffff880`0f38d6e8 fffffa80`08a8a010 fffffa80`08665d50 fffffa80`08642010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0666aa10 fffff880`02fa9f07 : fffffa80`08a8a010 00000000`00000000 fffffa80`08665d50 fffffa80`08642010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0666aa40 fffff880`02fd3b75 : 00000000`ffffffff 00000000`00000425 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0666ab20 fffff880`02fd22bb : 00000000`00000102 00000000`00000000 00000000`00000425 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0666ab50 fffff880`02fa52c6 : ffffffff`ff676980 fffffa80`08642010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0666abf0 fffff880`02fd1e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`055d5a98 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0666ad00 fffff800`03566fee : 00000000`02b0a137 fffffa80`0866b4d0 fffffa80`03cd0040 fffffa80`0866b4d0 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0666ad40 fffff800`032bd5e6 : fffff800`03441e80 fffffa80`0866b4d0 fffff800`0344fcc0 fffff880`01243cb0 : nt!PspSystemThreadStartup+0x5a fffff880`0666ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1796e8 fffff880`0f38d6e8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1796e8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010212-25256-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03210000 PsLoadedModuleList = 0xfffff800`03455670 Debug session time: Mon Jan 2 14:23:49.754 2012 (UTC - 7:00) System Uptime: 0 days 0:00:27.754 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8008b55010, fffff8801044f6e8, 0, 2} 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+1796e8 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8008b55010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8801044f6e8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1796e8 fffff880`1044f6e8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`0462e9c8 fffff880`04325000 : 00000000`00000116 fffffa80`08b55010 fffff880`1044f6e8 00000000`00000000 : nt!KeBugCheckEx fffff880`0462e9d0 fffff880`04324d0a : fffff880`1044f6e8 fffffa80`08b55010 fffffa80`087cac00 fffffa80`086851f0 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0462ea10 fffff880`0420ff07 : fffffa80`08b55010 00000000`00000000 fffffa80`087cac00 fffffa80`086851f0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0462ea40 fffff880`04239b75 : 00000000`ffffffff 00000000`0000062a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0462eb20 fffff880`042382bb : 00000000`00000102 00000000`00000000 00000000`0000062a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0462eb50 fffff880`0420b2c6 : ffffffff`ff676980 fffffa80`086851f0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0462ebf0 fffff880`04237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`082b4738 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0462ed00 fffff800`03527fee : 00000000`0410c94d fffffa80`087a8060 fffffa80`03cd1040 fffffa80`087a8060 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0462ed40 fffff800`0327e5e6 : fffff800`03402e80 fffffa80`087a8060 fffff800`03410cc0 fffff880`01443384 : nt!PspSystemThreadStartup+0x5a fffff880`0462ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1796e8 fffff880`1044f6e8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1796e8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
Update the following drivers. To find driver updates, search google, check your hardware manufacturer sites, and you may use Driver Reference as a resource.
Code:
RtNdPt60	fffff880`08b63000	fffff880`08b6f000	Mon Dec 10 19:49:52 2007 (475dfad0)	00007faa		RtNdPt60.sys
Kone	fffff880`06ffa000	fffff880`06ffdc80	Wed Dec 10 23:56:52 2008 (4940b9b4)	00004a44		Kone.sys
Also, I recommend checking temperatures of your components using http://www.hwinfo.com/download64.html# and running logging to keep track of temperatures up until a BSOD. You can upload the .csv on here, after zipping it, for us to look at.
My System SpecsSystem Spec
Reply

 BSOD 116 error




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD error when computer goes to sleep. Unable to get error codes.
Recently I restored my computer to windows 7 after using Windows 8 for a short period of time provided by my university. I don't think the story as to why I went back is very necessary so I'll skip it and get onto my problem. Upon returning to Win7, I began to get some errors, namely my computer...
BSOD Help and Support
BSOD Memory Management Error, didn't catch error code.
Hello again, BSOD Forum, I've been free of frequent BSODs since earlier this year. Recently I must have installed some software or something else must have gone wrong, because the blue screens are back. Here is what happened earlier this year, in case anyone needs any further context: ...
BSOD Help and Support
Random BSOD stop error 0x0000001E, hardware error?
Hello, A few days ago I got a random BSOD with the 0x0..1E stop error. Now my computer will rarely boot and when it does it still randomly gets the same BSOD. I once got a 1D stop error but its mostly 1E that keeps happening. I run Windows 7 Professional 64-bit and this time I used a Windows DVD...
BSOD Help and Support
BSOD error.. Restarts, but power button stays on, graphics card error?
Hey guys, i want to thank you ahead of time for helping me. This BSOD is a pain in the butt. Intel Pentium 2.8GHZ RAM 3.5 32 bit OS Intel GG965 Express Chipset Family I have already reinstalled the operating system multiple times, i think its a faulty graphics card, but i want to be...
BSOD Help and Support
BSOD. error Custom built computer. error unknown between 0 or 1077...
Well I built this computer in september of 2011 everything was running great no problems at all until today. I left it on and went to the store came back and BSOD. My computer restarted before I could write down any information "Error code" system restore said it was a "unknown error" which...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:43.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App