BSOD

LosT SpiriT said:

Hi everyone

I built my own pc before 1 year but it seems there is something wrong

i reinstalled windowss 7 two times because BSOD

and again the last two weeks it appeared twice

Iam now thinking that the proplem maybe a hardware

OS windows 7
asus deluxe
zotac nividia 275 gtx
ram 4gb DDr3
power supply 550 w

The one thing missing from that file is the DMP file which we need most. It is usually located in C:\windows\minidump (if your computer is configured correctly) and is called *.DMP. Please check there and if it isnt there please search for *.dmp.

When you find it please zip and upload to us.

Ken

here is the file

sorry

plz anyone can help me?

LosT SpiriT said:

plz anyone can help me?

This crash was caused by your video driver. You need to remove all traces of the current driver before re-installing a new copy. Nvidia makes an un-install tool.

Then download and install a new copy

Let us know if you need help


Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\071810-19858-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Sun Jul 18 16:29:59.759 2010 (GMT-4)
System Uptime: 1 days 14:19:06.297
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005fdc010, fffff8800ff71d50, 0, 2}

Unable to load image 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+11bd50 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005fdc010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800ff71d50, 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+11bd50
fffff880`0ff71d50 803d815cb70000  cmp     byte ptr [nvlddmkm+0xc919d8 (fffff880`10ae79d8)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05fd79c8 fffff880`042eccbc : 00000000`00000116 fffffa80`05fdc010 fffff880`0ff71d50 00000000`00000000 : nt!KeBugCheckEx
fffff880`05fd79d0 fffff880`042ec9c6 : fffff880`0ff71d50 fffffa80`05fdc010 fffffa80`061a4b10 fffffa80`06170010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05fd7a10 fffff880`04393f07 : fffffa80`05fdc010 00000000`00000000 fffffa80`061a4b10 fffffa80`06170010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05fd7a40 fffff880`043bdb75 : 00000000`ffffffff 00000000`0086ecd8 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05fd7b20 fffff880`043bc2bb : 00000000`00000102 00000000`00000000 00000000`0086ecd8 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05fd7b50 fffff880`0438f2c6 : ffffffff`ff676980 fffffa80`06170010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05fd7bf0 fffff880`043bbe7a : 00000000`00000000 fffffa80`062589d0 00000000`00000080 fffffa80`06170010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05fd7d00 fffff800`02d76166 : 00000000`fffffc32 fffffa80`061624d0 fffffa80`03cd1040 fffffa80`061624d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05fd7d40 fffff800`02ab1486 : fffff800`02c4be80 fffffa80`061624d0 fffff800`02c59c40 fffff880`0123d534 : nt!PspSystemThreadStartup+0x5a
fffff880`05fd7d80 00000000`00000000 : fffff880`05fd8000 fffff880`05fd2000 fffff880`05fd6690 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+11bd50
fffff880`0ff71d50 803d815cb70000  cmp     byte ptr [nvlddmkm+0xc919d8 (fffff880`10ae79d8)],0

SYMBOL_NAME:  nvlddmkm+11bd50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb7d7fd

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

thank you very much

I reinstalled the video driver in a proper way

I hope this will solve the problem

thanks again