BSOD caused by Video Scheduler?

[zerowalker]

Okay i have been gettings BSOD randomly for sometime, i thought i solved it before when updating the drivers for my GPU, but it seems to be back, so maybe it wasn´t solved?.


i found a dump file, but not sure if it´s correct but it probably is, maybe you can find out something?

Q6600 CPU
5670 ATI GPU
Maximus Formula Asus MB

if you need more information just tell me

 

[FredeGail]

Hello Zerowalker and welcome to Sevenforums.

To be able to help you, we'd need you to attach a full report. This includes, sys$info, nfo etc. To get these files, use our thread below.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

BSOD Analyse

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80054eb4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002e55768, 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.

Suspecting your ATI Driver or at least video related. Please do a clean install of the driver by doing this-

i) Make your way to ATI Drivers - Downloads and download the latest driver for your card, save it to your desktop for instance
ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
iii) Download Driver Sweeper
iv) Get to safe mode (without network) and search for Driver Sweeper in your rb:
v) Select all the ATI components and analyse them
vi) Clean them, head into Windows without internet and install the driver you've downloaded previously

When we have a full report, we can get a bigger perspective.

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80054eb4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002e55768, 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.
[COLOR="Orange"]
Debugging Details:
------------------
FAULTING_IP: 
atikmpag+8768
fffff880`02e55768 ??              ???
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
BUGCHECK_STR:  0x117
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`042df630 fffff880`07cd85f7 : fffffa80`054eb4e0 fffff800`02e8e590 00000000`00000010 00000000`00010202 : watchdog!WdDbgReportRecreate+0xa3
fffff880`042dfb50 fffff880`07cd92bc : fffff8a0`0ccd1110 fffff8a0`0ccd1110 00000000`00000080 fffffa80`054eb4e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`042dfba0 fffff880`07cad6b3 : 00000000`00000001 fffffa80`0890b000 00000000`00000000 00000000`00000033 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`042dfbd0 fffff880`07cd9e0f : fffffa80`04630a58 ffffffff`fffe7960 fffffa80`054eb4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`042dfc80 fffff880`07da8ec1 : fffffa80`084e4290 00000000`00000080 00000000`00000000 fffffa80`04630410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`042dfd00 fffff800`0312c6fa : 00000000`04cc0e2f fffffa80`081c3060 fffffa80`039eb740 fffffa80`081c3060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`042dfd40 fffff800`02e6ab46 : fffff880`03164180 fffffa80`081c3060 fffff880`0316efc0 79797979`79797979 : nt!PspSystemThreadStartup+0x5a
fffff880`042dfd80 00000000`00000000 : fffff880`042e0000 fffff880`042da000 fffff880`042ddd40 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+8768
fffff880`02e55768 ??              ???
SYMBOL_NAME:  atikmpag+8768
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4f7e4294
FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
Followup: MachineOwner[/COLOR]

Best Regards,
Frederik.

 

[zerowalker]

Okay, but i Think i may have solved that problem, but not it just feezes randomly, once per day or something, and i don´t know why?


I am thinking of doing a reformating of the system, then i will get back to you if i am continuing having problems

(i think the BSOD was thanks to daemon tools)

 

[FredeGail]

If you suspect Daemon Tools, make sure to uninstall it with this tool.

Best Regards,
Frederik.

 

[zerowalker]

I think i did, it was someone else having BSOD here, and someone linked to some uninstalling tool

 

[FredeGail]

Have you done a clean installation of your Graphics Driver yet? Even though you may just have uninstalled it and reinstalled it, it's a requirement to flush away the old one completely.

(see post #2)

Best Regards,
Frederik

 

[zerowalker]

I am pretty sure i have done this in the past, cause i thought it was the Graphic Card that was the culprit.

Though i don´t remember exactly how i did it, but i think i used driver sweeper and such in safe mode, then downloaded the latest Catalyst.

 

[FredeGail]

Great!

Report if you're having any incoming BSODs.

Best Regards,
Frederik.

 

[zerowalker]

Will do that, hopefully it won´t be necessary, but i it still isn´t solved, my "skills" are not enough;D

 

[FredeGail]

Don't worry, we're here to help!

Best Regards,
Frederik.

 

[zerowalker]

Well, i am still having the problem it seems.
Know it´s been a year, but i recently wanted to do a total cleanup on the system.

OC a bit, stress test (only cpu is OCed) and do a clean install on everything.

Everything works fine, i stress tested very very much in all kinds of tests.

But still i do get the BSOD Video Scheduler randomly, it´s always that one.
And it´s coming even on stock, so it isn´t a CPU crash, atleast not from the OC.

But often i noticed that the screen would turn of and on.

You know when you get "Driver stopped responding", that kind of reset on the display.
But i don´t get the message, though i do sometimes.

And i think that it´s either, reset display, "driver stopped responding" or a BSOD.

Though i can´t replicate it. I have tried with stress testing the CPU and GPU.

It´s driving me nuts, i can´t put my hands on it, never had this much trouble, starting to really think something is damaged;S

EDIT:

Also, weird enough.

When i was going to install windows 8, i heard this constant beep.
And i could only boot up to bios if i used "clear cmos" and went with default.

The culprit was AHCI. For some reason, if i activate it, it beeps when it´s trying to identify the HDD.
I can´t grasp why, as it has been activated for years;S
But when i change to IDE Enhanced, problems goes away and i can boot.