BSOD on two week old laptop

lrm537 · 28 Feb 2012

BSOD occurred while i was changing settings in the NVIDIA control panel. I had just set Google Chrome to run off the NVIDIA chip instead of the integrated chip (for no reason other than to see what, if any, difference it would make).

This is the first BSOD that i'm aware of on this system.

Any help would be greatly appreciated.

ps
I considered updating the NVIDIA card's drivers, but i'm not sure if i should use the manufacturers driver over the OEM's, as, and i may be completely wrong about this, my laptop has something called Optimus, which is responsible for switching between the graphics cards when necessary. I'm worried that the manufacturers driver may effect this somehow.
Spec

Lenovo Ideapad Z570
Windows 7 Home Premium 64
Intel Core i3-2350M CPU @ 2.30GHz Sandy Bridge
8.00 GB Dual-Channel DDR3 @ 665MHz
1024MB GeForce GT 520M

zigzag3143 · 28 Feb 2012

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

lrm537 · 28 Feb 2012

zigzag3143 said:

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

No problem.

I wouldn't normally react this quickly to something like this. Think i was worried because it's a new laptop, even though i know full well that the BSOD is not fussy about how old, or new, a system is before it's fair game.

If there's any more instances i'll post it in this thread

Thanks again

lrm

Would be interested on any thoughts regarding the Optimus tech and which driver to use, that you might have. As it is, i won't be changing anything. Just wondering, that's all.

zigzag3143 · 28 Feb 2012

lrm537 said:

zigzag3143 said:

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

No problem.

I wouldn't normally react this quickly to something like this. Think i was worried because it's a new laptop, even though i know full well that the BSOD is not fussy about how old, or new, a system is before it's fair game.

If there's any more instances i'll post it in this thread

Thanks again

lrm

Would be interested on any thoughts regarding the Optimus tech and which driver to use, that you might have. As it is, i won't be changing anything. Just wondering, that's all.

Optimus Tech?

lrm537 · 04 Mar 2012

Hi there

Just woke laptop up to find another BSOD. I really can't give you any info on what happened as it happened while it was in sleep.

I have included the BSOD information in an attachment. If any other info is required then please just ask.

edit
The only significant change made over the last few days is the AV software. I uninstalled the Kaspersky trial and installed Vipre Internet Security.

Thank you in advance for your help

lrm

writhziden · 05 Mar 2012

Just an FYI: With VIPRE installed, keep a close watch on your Event Viewer logs for Event ID: 1000 caused by SBAMSvc.exe due to faulting module SbWebFilter.dll or faulting module unknown. I am currently volunteering my time to help GFI debug this problem that I have now replicated on six different machines. It causes the system to become slow to respond with actions taking 5-10 minutes to be carried out, i.e. the time between clicking on the start menu and having the start menu show up can take 5-10 minutes. You are welcome to use VIPRE, but I thought you should be aware of this problem. For another security option, take a look at the Good and Free system security combination.

Antivirus Software:

Code:

sbamsvc.exe	c:\program files (x86)\gfi software\vipre\sbamsvc.exe	4020	8	200	1380	5/3/12 12:01 AM	5.0.5134.0	3.14 MB (3,289,032 bytes)	19/1/12 04:12 PM
sbamtray.exe	c:\program files (x86)\gfi software\vipre\sbamtray.exe	3228	8	200	1380	5/3/12 12:01 AM	5.0.5134.0	2.91 MB (3,050,352 bytes)	19/1/12 04:44 PM
sbpimsvc.exe	c:\program files (x86)\gfi software\vipre\sbpimsvc.exe	2500	8	200	1380	5/3/12 12:00 AM	5.0.5134.0	169.36 KB (173,424 bytes)	19/1/12 04:11 PM

Code:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\lrm537\Windows_NT6_BSOD_jcgriff2\030512-24538-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`0325f670
Debug session time: Sun Mar  4 15:33:29.620 2012 (UTC - 7:00)
System Uptime: 0 days 21:56:11.479
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff88001739c83}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001739c83, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c9100
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisReturnPackets+73
fffff880`01739c83 488b7910        mov     rdi,qword ptr [rcx+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800cfc0980 -- (.trap 0xfffff8800cfc0980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000098 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001739c83 rsp=fffff8800cfc0b10 rbp=0000000000000001
 r8=fffffa800ab5de30  r9=0000000000000001 r10=fffffa800ab5d020
r11=fffffa800ab5db30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!NdisReturnPackets+0x73:
fffff880`01739c83 488b7910        mov     rdi,qword ptr [rcx+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030961e9 to fffff80003096c40

STACK_TEXT:  
fffff880`0cfc0838 fffff800`030961e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0cfc0840 fffff800`03094e60 : fffffa80`0d239b00 00000000`00000000 fffffa80`0a29e1a0 fffffa80`07831240 : nt!KiBugCheckDispatch+0x69
fffff880`0cfc0980 fffff880`01739c83 : fffffa80`0ab5d000 fffff880`016859a4 fffffa80`0ab5dac0 fffffa80`0a27d1a0 : nt!KiPageFault+0x260
fffff880`0cfc0b10 fffff880`05f9088e : fffffa80`0d36f580 00000000`00000000 fffffa80`0ab5dac0 fffffa80`10668d10 : ndis!NdisReturnPackets+0x73
fffff880`0cfc0b60 fffffa80`0d36f580 : 00000000`00000000 fffffa80`0ab5dac0 fffffa80`10668d10 fffffa80`0ab5db30 : HssDrv+0x188e
fffff880`0cfc0b68 00000000`00000000 : fffffa80`0ab5dac0 fffffa80`10668d10 fffffa80`0ab5db30 fffff880`01742f1f : 0xfffffa80`0d36f580


STACK_COMMAND:  kb

FOLLOWUP_IP: 
HssDrv+188e
fffff880`05f9088e ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  HssDrv+188e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HssDrv

IMAGE_NAME:  HssDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe31b

FAILURE_BUCKET_ID:  X64_0xD1_HssDrv+188e

BUCKET_ID:  X64_0xD1_HssDrv+188e

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

Loading Dump File [D:\Kingston\BSODDmpFiles\lrm537\Windows_NT6_BSOD_jcgriff2\022812-17721-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`03257670
Debug session time: Tue Feb 28 11:17:42.604 2012 (UTC - 7:00)
System Uptime: 0 days 5:55:36.463
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e3144e0, fffff8800fbf57d8, 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+1597d8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e3144e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fbf57d8, 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+1597d8
fffff880`0fbf57d8 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`05f58358 fffff880`0486c000 : 00000000`00000116 fffffa80`0e3144e0 fffff880`0fbf57d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f58360 fffff880`0486bd0a : fffff880`0fbf57d8 fffffa80`0e3144e0 fffffa80`0b88cd50 fffffa80`0b877010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05f583a0 fffff880`04912f07 : fffffa80`0e3144e0 00000000`00000000 fffffa80`0b88cd50 fffffa80`0b877010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05f583d0 fffff880`04940d5a : fffffa80`ffffffff 00000000`0014de12 fffff880`05f58510 fffffa80`0b8a4350 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05f584b0 fffff880`0492cbf4 : 00000000`00000000 ffffffff`feced300 00000000`00000001 fffff880`0493ce65 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05f584f0 fffff880`0492bbc5 : fffffa80`0b8b5560 00000000`00000000 00000000`80000011 fffffa80`0b877010 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0xcc
fffff880`05f585c0 fffff880`04926827 : 00000000`ffffda01 00000000`00000003 fffffa80`0b894230 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x2a1
fffff880`05f58610 fffff880`04929375 : fffff8a0`00000000 fffff880`04924b71 00000000`00000000 fffff8a0`0cddfe01 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x4c3
fffff880`05f58760 fffff880`0492179d : 00000000`00000000 fffffa80`0e826000 00000000`0000000e fffffa80`073e2b90 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x14d
fffff880`05f587d0 fffff880`0493b65d : 00000000`00000000 fffff8a0`0aaf1df0 fffffa80`00000000 fffffa80`0e4aaf10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`05f589a0 fffff880`0493b398 : fffff800`04cd0080 fffff880`0493ad00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05f58b90 fffff880`0493ae96 : 00000000`00000000 fffffa80`0e438920 00000000`00000080 fffffa80`0b877010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05f58bc0 fffff800`03329fee : 00000000`0216c4f3 fffffa80`0b893210 fffffa80`06ca2990 fffffa80`0b893210 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05f58c00 fffff800`030805e6 : fffff800`03204e80 fffffa80`0b893210 fffff800`03212cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05f58c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1597d8
fffff880`0fbf57d8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+1597d8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d7376ce

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Caused by Hotspot shield: HssDrv.sys
Graphics card TDR error 0x116: see below.

Do the following steps to resolve your crashes:

If you are overclocking any hardware, please stop.
I suggest removing Hotspot shield.
H2SO4 said:

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

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.

The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.

lrm537 · 07 Mar 2012

writhziden said:

Just an FYI: With VIPRE installed, keep a close watch on your Event Viewer logs for Event ID: 1000 caused by SBAMSvc.exe due to faulting module SbWebFilter.dll or faulting module unknown. I am currently volunteering my time to help GFI debug this problem that I have now replicated on six different machines. It causes the system to become slow to respond with actions taking 5-10 minutes to be carried out, i.e. the time between clicking on the start menu and having the start menu show up can take 5-10 minutes. You are welcome to use VIPRE, but I thought you should be aware of this problem. For another security option, take a look at the Good and Free system security combination.

Antivirus Software:

Code:

sbamsvc.exe	c:\program files (x86)\gfi software\vipre\sbamsvc.exe	4020	8	200	1380	5/3/12 12:01 AM	5.0.5134.0	3.14 MB (3,289,032 bytes)	19/1/12 04:12 PM
sbamtray.exe	c:\program files (x86)\gfi software\vipre\sbamtray.exe	3228	8	200	1380	5/3/12 12:01 AM	5.0.5134.0	2.91 MB (3,050,352 bytes)	19/1/12 04:44 PM
sbpimsvc.exe	c:\program files (x86)\gfi software\vipre\sbpimsvc.exe	2500	8	200	1380	5/3/12 12:00 AM	5.0.5134.0	169.36 KB (173,424 bytes)	19/1/12 04:11 PM

Code:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\lrm537\Windows_NT6_BSOD_jcgriff2\030512-24538-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`0325f670
Debug session time: Sun Mar  4 15:33:29.620 2012 (UTC - 7:00)
System Uptime: 0 days 21:56:11.479
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff88001739c83}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001739c83, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c9100
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisReturnPackets+73
fffff880`01739c83 488b7910        mov     rdi,qword ptr [rcx+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800cfc0980 -- (.trap 0xfffff8800cfc0980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000098 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001739c83 rsp=fffff8800cfc0b10 rbp=0000000000000001
 r8=fffffa800ab5de30  r9=0000000000000001 r10=fffffa800ab5d020
r11=fffffa800ab5db30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!NdisReturnPackets+0x73:
fffff880`01739c83 488b7910        mov     rdi,qword ptr [rcx+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030961e9 to fffff80003096c40

STACK_TEXT:  
fffff880`0cfc0838 fffff800`030961e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0cfc0840 fffff800`03094e60 : fffffa80`0d239b00 00000000`00000000 fffffa80`0a29e1a0 fffffa80`07831240 : nt!KiBugCheckDispatch+0x69
fffff880`0cfc0980 fffff880`01739c83 : fffffa80`0ab5d000 fffff880`016859a4 fffffa80`0ab5dac0 fffffa80`0a27d1a0 : nt!KiPageFault+0x260
fffff880`0cfc0b10 fffff880`05f9088e : fffffa80`0d36f580 00000000`00000000 fffffa80`0ab5dac0 fffffa80`10668d10 : ndis!NdisReturnPackets+0x73
fffff880`0cfc0b60 fffffa80`0d36f580 : 00000000`00000000 fffffa80`0ab5dac0 fffffa80`10668d10 fffffa80`0ab5db30 : HssDrv+0x188e
fffff880`0cfc0b68 00000000`00000000 : fffffa80`0ab5dac0 fffffa80`10668d10 fffffa80`0ab5db30 fffff880`01742f1f : 0xfffffa80`0d36f580


STACK_COMMAND:  kb

FOLLOWUP_IP: 
HssDrv+188e
fffff880`05f9088e ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  HssDrv+188e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HssDrv

IMAGE_NAME:  HssDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe31b

FAILURE_BUCKET_ID:  X64_0xD1_HssDrv+188e

BUCKET_ID:  X64_0xD1_HssDrv+188e

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

Loading Dump File [D:\Kingston\BSODDmpFiles\lrm537\Windows_NT6_BSOD_jcgriff2\022812-17721-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`03257670
Debug session time: Tue Feb 28 11:17:42.604 2012 (UTC - 7:00)
System Uptime: 0 days 5:55:36.463
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e3144e0, fffff8800fbf57d8, 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+1597d8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e3144e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fbf57d8, 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+1597d8
fffff880`0fbf57d8 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`05f58358 fffff880`0486c000 : 00000000`00000116 fffffa80`0e3144e0 fffff880`0fbf57d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f58360 fffff880`0486bd0a : fffff880`0fbf57d8 fffffa80`0e3144e0 fffffa80`0b88cd50 fffffa80`0b877010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05f583a0 fffff880`04912f07 : fffffa80`0e3144e0 00000000`00000000 fffffa80`0b88cd50 fffffa80`0b877010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05f583d0 fffff880`04940d5a : fffffa80`ffffffff 00000000`0014de12 fffff880`05f58510 fffffa80`0b8a4350 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05f584b0 fffff880`0492cbf4 : 00000000`00000000 ffffffff`feced300 00000000`00000001 fffff880`0493ce65 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05f584f0 fffff880`0492bbc5 : fffffa80`0b8b5560 00000000`00000000 00000000`80000011 fffffa80`0b877010 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0xcc
fffff880`05f585c0 fffff880`04926827 : 00000000`ffffda01 00000000`00000003 fffffa80`0b894230 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x2a1
fffff880`05f58610 fffff880`04929375 : fffff8a0`00000000 fffff880`04924b71 00000000`00000000 fffff8a0`0cddfe01 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x4c3
fffff880`05f58760 fffff880`0492179d : 00000000`00000000 fffffa80`0e826000 00000000`0000000e fffffa80`073e2b90 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x14d
fffff880`05f587d0 fffff880`0493b65d : 00000000`00000000 fffff8a0`0aaf1df0 fffffa80`00000000 fffffa80`0e4aaf10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`05f589a0 fffff880`0493b398 : fffff800`04cd0080 fffff880`0493ad00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05f58b90 fffff880`0493ae96 : 00000000`00000000 fffffa80`0e438920 00000000`00000080 fffffa80`0b877010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05f58bc0 fffff800`03329fee : 00000000`0216c4f3 fffffa80`0b893210 fffffa80`06ca2990 fffffa80`0b893210 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05f58c00 fffff800`030805e6 : fffff800`03204e80 fffffa80`0b893210 fffff800`03212cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05f58c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1597d8
fffff880`0fbf57d8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+1597d8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d7376ce

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Caused by Hotspot shield: HssDrv.sys
Graphics card TDR error 0x116: see below.

Do the following steps to resolve your crashes:

If you are overclocking any hardware, please stop.
I suggest removing Hotspot shield.
H2SO4 said:

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

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.

The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.

Thanks for your help.

I don't have anything called hotspotshield installed. I think it may be something called Expatshield. I believe they are from the same developer and are probably the same thing in all but name. I will remove it as i only use it for college as certain things are restricted on the network there.

As for the second suggestion, i think i'll wait for it to happen again. At the time of that BSOD, i think i was messing with the settings on the NVIDIA control panel, and so it was more likely as a result of my curiosity more than a fault. I'll see what happens on that score.

Thanks again for your time
:)
And i just uninstalled Vipre in the end. I went back to MSE as I've never had a problem with it in the past. Will, in you'r opinion, Vipre actually be usable in the future? I only ask because i bought a lifetime license from them and it would be nice to get some use out of it. Good luck with the debugging of Vipre.

writhziden · 07 Mar 2012

I have an appointment Friday morning to help a VIPRE support representative track down the Web Filter and Active Protection active file scanning issues in the current version of VIPRE. The VIPRE representative who is working with me Friday expects the Web Filter and Active Protection features to be completely revamped prior to the release of version 6. Version 6 does not currently have an estimated release date, but beta testing will likely begin in August. Hopefully the next release will have less bugs and be usable.

Thanks for the good luck wishes. I hope we can resolve the problems for users like you who have lifetime subscriptions.