Graphics card causing boot problem

[mckillwashere]

Let me clarify cause I really didn't understand
Plugged into the on-board graphics = no problem
Plugged into graphics card = problems

Is that correct??

 

[EzioAuditore]

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 1 Year
- What is the age of OS installation (have you re-installed the OS?) Hmmm,,, Couple of weeks

Thanks,,, here're the requested files ( I think i should post them here instead of opening other thread no? ):

 

[mckillwashere]

- What is the age of OS installation (have you re-installed the OS?) Hmmm,,, Couple of weeks

You said this problem has been going on for a few weeks correct?? Could it be related to the reinstall?

 

[EzioAuditore]

Let me clarify cause I really didn't understand
Plugged into the on-board graphics = no problem
Plugged into graphics card = problems

Is that correct??

Yes!

 

[mckillwashere]

Let me clarify cause I really didn't understand
Plugged into the on-board graphics = no problem
Plugged into graphics card = problems

Is that correct??

Yes!

It is either a card or driver issue have you ensured all drivers are up to date??
and I agree with liquid snake anything can go bad within days or even hours of installing it.

 

[EzioAuditore]

- What is the age of OS installation (have you re-installed the OS?) Hmmm,,, Couple of weeks

You said this problem has been going on for a few weeks correct?? Could it be related to the reinstall?

Nah... I don't think so. It doesn't happen when its hooked to the onboard one, only when its hooked to the card. So, OS couldn't be the problem. :huh:

 

[EzioAuditore]

Let me clarify cause I really didn't understand
Plugged into the on-board graphics = no problem
Plugged into graphics card = problems

Is that correct??

Yes!

It is either a card or driver issue have you ensured all drivers are up to date??
and I agree with liquid snake anything can go bad within days or even hours of installing it.

Im currently using Catalyst 10.9, will upgade to 10.10 today but i dont think that's gonna do any good...

 

[mckillwashere]

- What is the age of OS installation (have you re-installed the OS?) Hmmm,,, Couple of weeks

You said this problem has been going on for a few weeks correct?? Could it be related to the reinstall?

Nah... I don't think so. It doesn't happen when its hooked to the onboard one, only when its hooked to the card. So, OS couldn't be the problem. :huh:

I just put the two together... Reinstall about the same time as the problems started... Maybe you have two drivers that dont play nice?

 

[EzioAuditore]

In device manager, i see nothing related to the on-board card... Btw, Im downloading the 10.10 driver now. Can u give me exact steps on uninstalling previous ATI drivers and reinstalling new drivers as i see that whenever i install or uninstall it, windows installs its own drivers and i doesn't get the CCC installed. I kinda have to install the ATI drivers again "on top of" the windows's drivers.. That's only way i can get CCC installed.. may be if that could be the reason... :O

 

[LiquidSnak]

This will aid in the removal of old drivers

Guru3D - Driver Sweeper (Setup) download from Guru3D.com

 

[mckillwashere]

In device manager, i see nothing related to the on-board card... Btw, Im downloading the 10.10 driver now. Can u give me exact steps on uninstalling previous ATI drivers and reinstalling new drivers as i see that whenever i install or uninstall it, windows installs its own drivers and i doesn't get the CCC installed. I kinda have to install the ATI drivers again "on top of" the windows's drivers.. That's only way i can get CCC installed.. may be if that could be the reason... :O

I just always install over the previous drivers and I never have had problems with it... I even have installed over windows drivers. I did have some issues with CCC not installing at one point but that was with Vista.

 

[EzioAuditore]

This will aid in the removal of old drivers

Guru3D - Driver Sweeper (Setup) download from Guru3D.com

Thanks LiquidSnak. Let me try it,, will let u know.

 

[EzioAuditore]

Guys, tried that but nope,,, the problem's still there...

 

[CarlTR6]

Thanks for uploading all of the requested files. The dumps confirm what you already know; it is a video error. Both dumps are nearly identical.

Error code 117, VIDEO_TDR_TIMEOUT_DETECTED. Usual causes: Video driver/sub-system

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Sun Oct 24 09:27:58.142 2010 (GMT-4)
System Uptime: 0 days 0:00:38.937
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8004ac4010, fffff88003c42f5c, 0, 0}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+6f5c )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
[B]The display driver failed to respond in timely fashion.[/B]
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8004ac4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c42f5c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+6f5c
fffff880`03c42f5c ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02e313c0 fffff880`03e794ef : fffffa80`04ac4010 102906c9`a00038bf 00000000`00000000 fffffa80`046bd901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`02e318e0 fffff880`03e79f6d : fffff8a0`0215cffc fffff8a0`01eb6ab0 fffff8a0`02004d69 00000000`00158293 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`02e31930 fffff880`03e7abda : fffffa80`04ac4010 fffffa80`04ac4010 fffffa80`047c3d50 fffffa80`046bd010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`02e319d0 fffff880`03f21f07 : fffffa80`04ac4010 00000000`00000000 fffffa80`047c3d50 fffffa80`046bd010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`02e31a00 fffff880`03f4bb75 : 00000000`ffffffff 00000000`000005b4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02e31ae0 fffff880`03f4a2bb : 00000000`00000102 00000000`00000000 00000000`000005b4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02e31b10 fffff880`03f1d2c6 : ffffffff`ff676980 fffffa80`046bd010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02e31bb0 fffff880`03f49e7a : 00000000`00000000 fffffa80`047c3d50 00000000`00000080 fffffa80`046bd010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02e31cc0 fffff800`02d31c06 : 00000000`0451994e fffffa80`046bea10 fffffa80`024cf040 fffffa80`046bea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02e31d00 fffff800`02a6bc26 : fffff800`02c07e80 fffffa80`046bea10 fffff800`02c15c40 fffff880`01257534 : nt!PspSystemThreadStartup+0x5a
fffff880`02e31d40 00000000`00000000 : fffff880`02e32000 fffff880`02e2c000 fffff880`02e30ea0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6f5c
fffff880`03c42f5c ??              ???

SYMBOL_NAME:  atikmpag+6f5c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c75c178

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

For troubleshooting purposes, I suggest that you uninstall Eset NOD32 using this uninstall tool: Tool. Eset is known to cause conflicts and crashes on some Win 7 systems. After you get your system stable, you can reinstall it; but I do not recommend doing so. Download and install Microsoft Security Essentials and make sure Windows Firewall is turned on. The idea in troubleshooting is to eliminate all possible causes of BSOD's.

Please completely uninstall Zone Alarm using this removal tool:http://download.zonealarm.com/bin/free/support/cpes_clean.exe. ZA is a well known cause of crashes with Win 7 systems. Do not reinstall ZA.

I find the following out of date drivers loaded on your system. Older drivers can and do cause conflicts and BSOD's. The drivers dated 2007 and 2008 are really obsolete. Update the following drivers.

ntdisk.sys Thu Nov 15 06:40:11 2007 - This is XP software and is not going to work with Win 7. NT Disk Manager Startup Driver belongs to the software Logical Disk Manager for Windows NT or dmload by Microsoft Corp., Veritas Software. You can try to update this driver through Microsoft or Veratis software. If you can't you need to uninstall the software. Before uninstalling, please create a system restore point.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - [FONT=&quot]Rt64win7.sys - [/FONT][FONT=&quot]Latest PCIe GBE (GigaBit Ethernet) drivers here: [/FONT][FONT=&quot]Realtek[/FONT]

safnt.sys Thu Aug 14 10:37:35 2008 - Saming OneKey recovery software driver. This software is obsolete. You can try to update it from the Lenovo website. If there is no update, uninstall the software. It is not designed for Win 7.

sammon.sys Thu Sep 27 02:18:30 2007 - PCGUARD DRIVER FOR Win2000/XP/2003. I cannot find the manufacturer. This is XP software; uninstall it.

How to find drivers -

- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
- - To remove any left over driver remnants, especially from graphics cards, use driver sweeper Guru3D - Driver Sweeper

Uninstall Eset and ZA. Update the above drivers or uninstall the associated software. Reboot and let's see how your system does. If you get another BSOD, please upload it and we will go from there. If you need help with the drivers, please post and ask.

 

[EzioAuditore]

Thanks Carl for analyzing the dumps.

So, i am now going to un-install ZA and ESET and this:

safnt.sys    Thu Aug 14 10:37:35 2008 -  Saming OneKey recovery  software driver. This software is obsolete. You can try to update it  from the Lenovo website. If there is no update, uninstall the software.  It is not designed for Win 7.
 
sammon.sys   Thu Sep 27 02:18:30 2007 - PCGUARD DRIVER FOR Win2000/XP/2003. I cannot find the manufacturer.  This is XP software; uninstall it.

Actually the above drivers relate to a software names "HCL EC2 Technology" which is basically a imaging software providing B2R (Boot to restore) facility to restore to earlier date even in worst cases when the pc cant boot even.. Just thought to let you know..

Will keep you informed with the results.

Btw, after removal of Eset and ZA, i'll be open to attacks.I don't like MSE much. Can i install KIS or that too would cause conflicts?

 

[mckillwashere]

May I ask what is your issue with MSE? Many of us recromend it.

 

[EzioAuditore]

May I ask what is your issue with MSE? Many of us recromend it.

Nothing much.. Only that it takes too long to update and its not much customizable..
I don't have any blazing fast net..

PS: I meant no offense to anyone's thoughts/recommendations.

 

[mckillwashere]

Teh updates are normally very very small. I mean less than a MB

 

[CarlTR6]

We recommend MSE because it does not conflict with Win 7 as most third party antivirus programs have the potential to do. Avast is one that rarely causes a problem. It is designed to work with Win 7. After you get your system stable, give it a try. I am currently using it.

Let us know how your system does with the changes.

 

[EzioAuditore]

Less than a MB?? When i used it once, it took hours to complete.. If its so, i may give it a second try..