Windows 7: BSOD graphic card related?

pandasaurus · 23 Feb 2011

My boyfriend has had troubles with his PC ever since he received it. When he first starts his PC for the day, he will have to restart multiple times for a proper display to show up. Sometimes when we're playing a game, the screen will flicker, go black for a second and then part of the screen will be cut off.

Attached are the multiple dump files that were in his minidump folder. Can someone please tell us what is causing this problem? Thanks!

pandasaurus · 23 Feb 2011

Anyone?

Maguscreed · 23 Feb 2011

I'm seeing signs of memory issues here.

Code:

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa800699a480, the pool entry being checked.
Arg3: 0000000f3386b361, the read back flink freelist value (should be the same as 2).
Arg4: 0000000f3386a361, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033f7d6f to fffff800032c4740

STACK_TEXT:  
fffff880`021b65d8 fffff800`033f7d6f : 00000000`00000019 00000000`00000003 fffffa80`0699a480 0000000f`3386b361 : nt!KeBugCheckEx
fffff880`021b65e0 fffff880`03f49ed7 : fffff8a0`00000001 00000000`00000002 fffffa80`ffffffa1 fffffa80`00000000 : nt!ExDeferredFreePool+0xa56
fffff880`021b66d0 fffff880`03f298c1 : fffff8a0`00fd61d0 fffff880`021b6790 fffff8a0`01d699d8 00000000`000007ff : dxgkrnl!DMMVIDPN::Serialize+0x207
fffff880`021b6770 fffff880`03f2561e : fffffa80`08eb3880 fffff880`021b6898 00000000`00000000 00000000`00000000 : dxgkrnl!VIDPN_MGR::COMMITVIDPNREQUEST::SerializeCommitVidPnRequests+0x1f5
fffff880`021b6840 fffff880`03f2710b : fffff880`03ea4560 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VIDPN_MGR::AcquireDiagSummary+0x4a2
fffff880`021b6aa0 fffff880`03f32df7 : 00000000`00000000 fffff8a0`0248937c 00000000`00002000 00000000`00000000 : dxgkrnl!VIDPN_MGR::AcquireDiagInfo+0x66f
fffff880`021b6b60 fffff880`03ee7103 : fffffa80`08e91000 fffffa80`08e91000 00000000`00000080 fffff8a0`0248937c : dxgkrnl!DmmCollectTdrDiagInfo+0x143
fffff880`021b6ba0 fffff880`03ebb6b3 : 00000000`00000001 fffffa80`08e91000 00000000`00000000 fffff880`00000025 : dxgkrnl!TdrCollectDbgInfoStage2+0x67
fffff880`021b6bd0 fffff880`03ee7e0f : fffffa80`09283340 ffffffff`fffe7960 fffffa80`09d624e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`021b6c80 fffff880`0514dec1 : fffffa80`09b57d50 00000000`00000080 00000000`00000000 fffffa80`08e79010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`021b6d00 fffff800`035677c6 : 00000000`fffffc32 fffffa80`08e7a4d0 fffffa80`06a28040 fffffa80`08e7a4d0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`021b6d40 fffff800`032a2c26 : fffff800`0343ee80 fffffa80`08e7a4d0 fffff800`0344cc40 fffff880`01260534 : nt!PspSystemThreadStartup+0x5a
fffff880`021b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a56
fffff800`033f7d6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a56

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56

Followup: Pool_corruption
---------

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009c5e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1d3bc, 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: 
atikmpag+73bc
fffff880`03e1d3bc 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0217a9c8 fffff880`03ec1000 : 00000000`00000116 fffffa80`09c5e010 fffff880`03e1d3bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`0217a9d0 fffff880`03ec0d0a : fffff880`03e1d3bc fffffa80`09c5e010 fffffa80`0914dd50 fffffa80`090d7010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0217aa10 fffff880`0480ff07 : fffffa80`09c5e010 00000000`00000000 fffffa80`0914dd50 fffffa80`090d7010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0217aa40 fffff880`04839b75 : 00000000`ffffffff 00000000`00000541 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0217ab20 fffff880`048382bb : 00000000`00000102 00000000`00000000 00000000`00000541 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0217ab50 fffff880`0480b2c6 : ffffffff`ff676980 fffffa80`090d7010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0217abf0 fffff880`04837e7a : 00000000`00000000 fffffa80`0914dd50 00000000`00000080 fffffa80`090d7010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0217ad00 fffff800`035657c6 : 00000000`029fff86 fffffa80`090d8360 fffffa80`06a29040 fffffa80`090d8360 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0217ad40 fffff800`032a0c26 : fffff880`009e8180 fffffa80`090d8360 fffff880`009f2fc0 fffff880`01260534 : nt!PspSystemThreadStartup+0x5a
fffff880`0217ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`03e1d3bc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

It jumps back and forth between those two primary errors.
If had to guess you have something overclocked.

pandasaurus · 23 Feb 2011

He said he troubleshooted the screen flickering error himself and someone said something about overclocking the card just keep the minimum speed at a certain level, so that's what he did but it did not fix the issue. This issue was happening before he OC'd it.

We also ran Memtest86+ on his comp a while back and it didn't come up with any errors.

Maguscreed · 23 Feb 2011

I'm sorry I didn't even notice that this wasn't the system in your specs. Could you give the system details please?

pandasaurus · 23 Feb 2011

Quote: Originally Posted by Maguscreed

I'm sorry I didn't even notice that this wasn't the system in your specs. Could you give the system details please?

I apologize!
Windows 64bit Home Prem
GIGABYTE 840A-UD3 mobo
ATI Radeon HD6850
AMD Phenom 2x 4 925 processor

He has read that there is alot of screen flickering issues with Radeon cards too.

Maguscreed · 23 Feb 2011

okay, I've looked at some more of the dumps and that pool header seems to not have been as common as I thought at first.
Let's completely wipe the ati drivers off the system then reinstall them.
This tool is good for getting hte drivers off.
Guru3D - Driver Sweeper (Setup) download from Guru3D.com

pandasaurus · 24 Feb 2011

Quote: Originally Posted by Maguscreed

okay, I've looked at some more of the dumps and that pool header seems to not have been as common as I thought at first.
Let's completely wipe the ati drivers off the system then reinstall them.
This tool is good for getting hte drivers off.
Guru3D - Driver Sweeper (Setup) download from Guru3D.com

He has done this and the problem is still occurring.

Maguscreed · 24 Feb 2011

Question - has any of the hardware recently changed?

Barring that answer, I would have him remove any anti-virus or firewall software currently on the machine.

Is this crash simply occurring no matter what he's doing or is he playing a game or running the web browser or doing anything specific when it occurs?

DeanP · 24 Feb 2011

Sounds like a faulty RAM or GPU - could be both.
STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Windows 7: BSOD graphic card related?

BSOD graphic card related? problems?