GPU,MOBO or PSU problem????

darkheretic

Junior Member
Nov 19, 2012
6
0
0
Hey i'm new here.My problem is this.After seven mothns of usin' my upgrated PC suddenly in a middle of a game igot a BSOD(B=Black).I reset my system with no success,in POST my screen getting black with horizontal collored lines.Thinkin' tha the GPU was the problem.I did those...
Bios update
CMOS reset
reinstall ram
put my gpu to another pc>>>>all fine(runnin" 3dmarks all night)
try another gpu in my system>>>>all fine
my "damaged" gpu to the 2nd PCI-E slot(x4 not x16)>>>seems good untill in a middle of my windows experience index got a BSOD(B=Blue)
my system
CPU>>>i5 2500k
GPU>>>saphire radeon 7770 ghz edition
MOBO>>>asrock z75 pro3
RAM>>>corsair xms3 8gb 1600 ghz
PSU>>>TT litepower 700w
OS>>>windows 7 ultimate x64
THANKS and sorry for my english,is not my nattive language
:colbert::colbert::colbert::colbert::colbert:
 

Tweak155

Lifer
Sep 23, 2003
11,449
264
126
Are you saying putting another video card in your computer makes it work without issue?

What is the swapped out card? Maybe your PSU is losing its power output consistency. 700w is plenty, but that doesn't mean it is working properly.
 

darkheretic

Junior Member
Nov 19, 2012
6
0
0
Sorry,the second gpu(asus en9600gt)was the card that i try in order to check if my mobo or psu is damaged
 
Last edited:

darkheretic

Junior Member
Nov 19, 2012
6
0
0
But the 9600gt has a 6pin power adapter as 7770.If the psu is the problem why the 9600 workin' just fine??The voltages r the same is n't it????
 
Last edited:

Fallengod

Diamond Member
Jul 2, 2001
5,908
19
81
Highly unlikely to be the PSU...just fyi. PSU's generally either work or dont work. They dont cause "lines" etc. There are exceptions of course. What is a TT litepower? Is that thermaltake? First and foremost dont buy shit brand PSU's and you dont have to worry about it.

Trying to interpret this..

My guess is video card or drivers. Maybe motherboard or stability settings/bios issue.
 

darkheretic

Junior Member
Nov 19, 2012
6
0
0
During WEI i got this as error(BSOD)
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e44f010, fffff8800577edb8, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\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+8db8 )

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: fffffa800e44f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800577edb8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+8db8
fffff880`0577edb8 4055 push rbp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`075ff928 fffff880`054ea000 : 00000000`00000116 fffffa80`0e44f010 fffff880`0577edb8 00000000`00000000 : nt!KeBugCheckEx
fffff880`075ff930 fffff880`054e9d87 : fffff880`0577edb8 fffffa80`0e44f010 fffffa80`0e3c8b90 fffffa80`0b6c9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`075ff970 fffff880`05590f07 : fffffa80`0e44f010 00000000`00000000 fffffa80`0e3c8b90 fffffa80`0b6c9010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`075ff9a0 fffff880`055bab75 : fffff8a0`ffffffff 00000000`0009b233 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`075ffa80 fffff880`0558c2d5 : fffffa80`0b6c9010 fffffa80`00000005 00000000`0009b233 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`075ffab0 fffff880`055b8e7a : 00000000`00000000 fffffa80`0a28e9a0 00000000`00000080 fffffa80`0b6c9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`075ffbc0 fffff800`0392de5a : 00000000`fffffc32 fffffa80`0b84d060 fffffa80`069c74a0 fffffa80`0b84d060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`075ffc00 fffff800`03687d26 : fffff800`03809e80 fffffa80`0b84d060 fffff800`03817cc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`075ffc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8db8
fffff880`0577edb8 4055 push rbp

SYMBOL_NAME: atikmpag+8db8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5064f994

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

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: fffffa800e44f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800577edb8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+8db8
fffff880`0577edb8 4055 push rbp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`075ff928 fffff880`054ea000 : 00000000`00000116 fffffa80`0e44f010 fffff880`0577edb8 00000000`00000000 : nt!KeBugCheckEx
fffff880`075ff930 fffff880`054e9d87 : fffff880`0577edb8 fffffa80`0e44f010 fffffa80`0e3c8b90 fffffa80`0b6c9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`075ff970 fffff880`05590f07 : fffffa80`0e44f010 00000000`00000000 fffffa80`0e3c8b90 fffffa80`0b6c9010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`075ff9a0 fffff880`055bab75 : fffff8a0`ffffffff 00000000`0009b233 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`075ffa80 fffff880`0558c2d5 : fffffa80`0b6c9010 fffffa80`00000005 00000000`0009b233 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`075ffab0 fffff880`055b8e7a : 00000000`00000000 fffffa80`0a28e9a0 00000000`00000080 fffffa80`0b6c9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`075ffbc0 fffff800`0392de5a : 00000000`fffffc32 fffffa80`0b84d060 fffffa80`069c74a0 fffffa80`0b84d060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`075ffc00 fffff800`03687d26 : fffff800`03809e80 fffffa80`0b84d060 fffff800`03817cc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`075ffc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8db8
fffff880`0577edb8 4055 push rbp

SYMBOL_NAME: atikmpag+8db8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5064f994

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------
 
Last edited: