Windows 7 BSOD on Dual monitors

Kalyan

New Member
Hi,
From last 1 week, my computer is driving me crazy with random blue screen of deaths when ever I use it in a dual screen mode. This happens only if I use my 22 inch and 19 inch monitors. If I use my 22 in and the laptop screen, i haven't noticed this problem.

Attached are the dump files from the crashes this week.

Can anyone help me with my problem?

Thanks in advance

Kalyan
 

Attachments

  • BSOD.zip
    216.5 KB · Views: 420
Is this on a laptop? Maybe the video can't drive two monitors, and I am assuming you have 2 external video outputs, which I have not seen on a laptop.
 
Yes, this is Dell D630 laptop. I use one DV output for the Dell 2208 monitor and the anolog output from the laptop to the other Dell 19 in monitor. This is the standard setup in my company and I have been using this setup for last 1 years. Only in last 2 weeks have I seen the blue screen crashes

PS: The dual monitors might not be a problem, this is just my guess. I am seeing lot of Windows 7 users are having similar issues with blue screen crashes
 
The dump shows your graphics driver (nvlddmkm.sys) at fault. Update the driver from the manufacturer's website: NVIDIA Driver Downloads - Automatically Detect NVIDIA Products

Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

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

FAULTING_IP: 
nvlddmkm+c700
8f030700 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 
Last edited:
Thank You. I will give it a try

The dump shows your graphics driver (nvlddmkm.sys) at fault. Update the driver from the manufacturer's website: NVIDIA Driver Downloads - Automatically Detect NVIDIA Products

Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 87d4f008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8f030700, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
 
Debugging Details:
------------------
 
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
 
FAULTING_IP: 
nvlddmkm+c700
8f030700 55              push    ebp
 
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 
With 0x116 tdr timeout errors, version of the video driver never matters and is not the cause. We must look for other reasons for the crash, such as other poor drivers or heat.

I will analyze and respond soon.
 
Please uninstall MagicDisc because of this old driver. You may use PowerIso as a great emulation replacement.

Code:
 mcdbus   mcdbus.sys   Tue Feb 24 05:42:13 2009
Your VPN client must be updated or uninstalled due to this old driver which has high chances of causing problems:

Code:
dne2000  dne2000.sys  Mon Nov 10 19:59:21 2008
This iTunes driver is known to cause crashes. Please update it or uninstall:

Code:
GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:16:53 2009
Please visit your laptop manufacturer's site to obtain and install the latest networking drivers (wireless and wired) because these are simply too old:

Code:
netw5v32 netw5v32.sys Thu Mar 26 12:10:37 2009 
b57nd60x b57nd60x.sys Sun Apr 26 07:15:34 2009
Please update your Sigmatel Audio driver. Again, way too old for Win 7.

Code:
stwrt    stwrt.sys    Thu Sep 13 11:29:43 2007
After completing these things, please post a new crash dump if necessary and/or tell us how it seems to be going. Good luck.
 
Problem with mother board

My problem is with hardware failure, IT replaced the motherboard and no issues so far.

Thanks everyone for your support
 
Back
Top