[mistermatt]

Hi guys. This is my first post to Tech Support Guy. I have a thread running here on windows7forums.com, but I wanted to post somewhere else so I could collect some more ideas on what exactly is going wrong.

So far, mostly from the other forum that I posted at, is that I have some sort of driver conflict going on, because when I boot windows after installing the latest nvidea drivers, I get stuck on a black screen after the 'starting windows' message disappears. I wait a while, but nothing happens and I am not able to bring up the task manager or anything like that.

If I change the installed drivers to the Generic VGA drivers, the system boots just fine, and I can log into my desktop without any problems. Stuff doesn't work when I try to use nvidea drivers.

I have tried to use the drivers provided by HP for my specific laptop model, found here, but I have been getting a BSOD after 'starting windows', where the newer drivers simply hang after 'starting windows'.

I am not very experienced in dealing with drivers. My experience with them so far has usually just been getting them from windows update (I know, I know), and then they would install just fine. Right now, the nvidea driver from windows update causes a BSOD.

I used to be running vista, I ran it fine for probably two years and then I started getting those 'Display driver has stopped responding but it has successfully recovered' messages, and related BSODs. So I did a fresh install of windows 7, with a format, and I am still having problems.

If more information is needed please let me know. I will try to see if i can replicate the BSOD with the HP video drivers and post the minidump for you guys to look at. Any help would be greatly welcomed. Thank you.

EDIT: I have attached the minidump after installing the latest GeForce drivers from HP's product page for my laptop. I have to run those drivers in compatibility mode for windows vista, because HP doesn't have any drivers for Windows7.

[joeten]

Hi and welcome to TSG this is the output from the debug on your dump file it points at your driver if not that then the problem could be the card itself
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\joe\Desktop\063010-24507-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Wed Jun 30 19:19:58.523 2010 (GMT+1)
System Uptime: 0 days 0:00:45.552
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80077624e0, fffff88003c93750, 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+f750 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80077624e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c93750, 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+f750
fffff880`03c93750 803d01528b0000 cmp byte ptr [nvlddmkm+0x8c4958 (fffff880`04548958)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`061b59c8 fffff880`03b62ef8 : 00000000`00000116 fffffa80`077624e0 fffff880`03c93750 00000000`00000000 : nt!KeBugCheckEx
fffff880`061b59d0 fffff880`03b62c02 : fffff880`03c93750 fffffa80`077624e0 fffffa80`0752ac00 fffffa80`0752f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061b5a10 fffff880`03c0ff07 : fffffa80`077624e0 00000000`00000000 fffffa80`0752ac00 fffffa80`0752f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`061b5a40 fffff880`03c39b75 : 00000000`ffffffff 00000000`00000ac0 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`061b5b20 fffff880`03c382bb : 00000000`00000102 00000000`00000000 00000000`00000ac0 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`061b5b50 fffff880`03c0b2c6 : ffffffff`ff676980 fffffa80`0752f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`061b5bf0 fffff880`03c37e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0631ac68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`061b5d00 fffff800`02d2da86 : 00000000`045d514f fffffa80`0753a060 fffffa80`03ccf040 fffffa80`0753a060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`061b5d40 fffff800`02a66b06 : fffff880`009e9180 fffffa80`0753a060 fffff880`009f3f40 fffff880`0122c534 : nt!PspSystemThreadStartup+0x5a
fffff880`061b5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+f750
fffff880`03c93750 803d01528b0000 cmp byte ptr [nvlddmkm+0x8c4958 (fffff880`04548958)],0
SYMBOL_NAME: nvlddmkm+f750
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 493755c1
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------

[mistermatt]

Does anyone know of any fixes to the VIDEO_TDR_FAILURE problem? From what I looked at online it doesn't really seem to have a specific cause, and may in face, and unfortunately for me, be a hardware issue that I am not able to solve.

[joeten]

Hi try a older driver,what security are you using as that sometimes interfers with things