Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RE: ATIKMDAG.SYS

25 views
Skip to first unread message

Laacagoia

unread,
May 4, 2007, 10:22:00 AM5/4/07
to

Hi,
I have the same problem as you with Catalyst 7.4, and I use Windows Vista
Home Premium 32b with Peak Radeon X1950GT 512 MB GDD3.
How have You resolved the problem?
Thanks if you'll can help me.
Best Regards
snoopy


"tomhyde2" wrote:

> Problem with ATIKMDAG.SYS
> ATI Radeon Kernel mode driver
> Vista Beta 2, build 5384, Asus P5WD2-Prem, ATI-X1900XTX
> Anyone have a solution?

Lilo Lentz

unread,
May 5, 2007, 3:16:18 AM5/5/07
to

Lilo Lentz

unread,
May 5, 2007, 3:16:18 AM5/5/07
to

Laacagoia

unread,
May 5, 2007, 10:04:00 AM5/5/07
to
Thanks,
I saw that there are many user with the same problem with atikmdag. Almost I
can't config the thermal control of my video card, the Catalyst 7.4 on my
system haven't the option VPU recover, ATI Overclock. I have probed to
install ATITools and tried to configure some option but after the system
crashed. I removed the ATITools.
My system go well without ATi driver!!!! Wonderful but without 3d
acceleration, aero, and glass effect. You know if one patch is still in
progress to resolve these problem with ATi card?
Thanks
Best Regards.
laacagoia

astronautbaby

unread,
Aug 29, 2007, 11:02:54 PM8/29/07
to

Ive recently built a new computer with vista 64Bit and Msi's new 2600
diamond plus card thinking wow this is gonna be a decent mid range
computer. ive had this thing for a week now and after countlessly
bouncing my head off the wall and locking myself in my computer room to
trouble shoot this atikmdag file stuff and after trying everything from
drivers to ati tools to rivatuner (btw area pain in the rear to get
working in vista even if you get it to) to control the fan speed because
that seems to be the issue here. when the fan needs to kick in my
favorite error pops up to tell me that another attempt has failed after
tirelessly trying everything i could think of i decided to take matters
in my own hands. what i did is not ment to be done in any way shape or
form by someone without the know how here it is im not gonna say 100%
its gonna work for you but if your up to it and you have the nads this
is what i did its really rather simple i took a old case fan with the 4
pin connector on it and cut the wire off the fan NOT THE PLUG you will
need the plug later
next i unplugged the fan from the graphics card notice i said
UNPLUGGED. then i took the fan wires and cleaned off some insulation on
the ends and stuck those ends into the fan power (MATCH THE COLORS UP
BLACK to BLACK and RED to REDdont worry about that yellow wire on
there).connector(make sure you use some electrical tape so the wires
dont come out after that i plugged the 4 pin connector into any old plug
comming off the power supply returned the card to its rightfull place
double checked my work and powered the computer up (which was kinda
nerve recking) but waala fan was powered up to 100% and i was gamming
again with no crashes ive been throwing every game i can at it to see if
i can crash it and i cant. the reason i did it this was was 1 the cards
fan can allways be put back to normal whenever ati or microsoft whoever
feels its time to fix this issue 2. i dont like giant box fans sitting
next t my pretty new computer it looks tacky and there obnoxious 3 its
just fun for me to do stuff like this well any how this solved my
problem try it if you dare otherwise you may be like the nvidia guys
sitting around 6 months or whatever waiting on driver support good luck
if you attempt this its at your own risk peace:smile:


--
astronautbaby

BadMouth

unread,
Apr 8, 2008, 6:25:11 PM4/8/08
to

::How to prevent ā€œ-Driver failed to respond ā€œAtikmdag.sys, but has
recovered-ā€ message.::
::First my systems specs:::
::--------------------------------------------------------------------------------------::
::DELL DualCore Intel Core 2 Duo E4500, 2200 MHz::
::MB: Intel G33::
::Ram: DDR2 SDRAM Dual Channel 2 sticks at 1 gig each.::
::PSU: 300 watts::
::1 DVD drive::
::1 Floppy::
::2 SATA drives 500 – 200 gigs respectively::
::GPU: ATI HD 2600 XT, 512mb::
::Monitor: Dell E228WFP LCD Digital + Analog signals 22inch.::
::System: Vista Premium 32bit::
::----------------------------------------------------------------------------------::
::AMD Athlon 64 3200+ custom made.::
::MB: Abit KN8::
::Ram: DDR3 DIM 1 stick at 2 gigs.::
::PSU: 450 watts::
::1 DVD drive::
::1 Floppy::
::1 SATA drive 200 gigs::
::1 IDE drive 100 gigs::
::GPU: Nvidia BFG 8600 GT, 512mb::
::Monitor: Gateway FPD1810 LCD Digital + Analog signals 19inch.::
::System: XP Professional 32bit::
::----------------------------------------------------------------------------------::
::After a couple of weeks battling this error type, from viewing over
55 or so forums, and over 1000s posts and trying out some of the
following promising leads to fix this error:::
::1. Downloading and installing ONLY the ATI driver software.::
::2. Editing the registry.::
::3. Removing a stick of ram.::
::4. Trying a more powerful PSU.::
::5. Removing and replacing devices one at a time such as hard drive,
etc…::
::6. Buying extra cooling fans.::
::7. Throw the dam ATI card into the trash bin.::
::Did all of the above, except the seventh one, was not ready to give
up that easy!::
::Most posts that I have read from the ATI (RED TEAM) that it was not
there drivers causing this issue. In addition, Nvidia (GREEN TEAM) for
some Nvidia users has posted similar responses. Their remedy to fix this
problem was to remove one stick of ram, buy a new PSU, Buy a new
motherboard, or ā€˜what the heck buy a completely new PC’ LOL!::
::My Instructions are too long to post within this thread, therefore I
created a link to my instructions for those who are having crashes after
crashes and message pop ups, and cannot wait for ATI team members to
come out of their holes and fix this issue.::
::For those who are curious as to what my instructions did for me here
are the before and after results:::
::Before:::
::On my average day of computer time, I would receive about 20 blue
screens, 67 crashes, 111 ATIKMDAG.SYS message pop ups, all totaling up
to 198 reboots. ::
::NOTE: Not including (Catalyts Control Center) software package.::
::After:::
::After doing my steps, I went from 20 blue screens down to zero, 67
crashes down to zero, 111 \"ATIKMDAG.SYS\" message pop ups down to zero,
with a total of zero reboots.::
::NOTE: Including (Catalyts Control Center) software package.::
::I say ā€œWHAT A DAM DIFFERENCEā€. ::
::Your results will vary depending on your system, card, and driver
versions you pick and use within my instructions.::
::The instructions are found here: 'RapidShare: 1-Click Webhosting'
(http://rapidshare.com/files/105950403/ATI_Problem_Solved.pdf)::
::Note: I am keeping them up only for a week or two, therefore if you
are curious whether you will benefit from my instructions I suggest you
grab it before it is too late. You will also need Adobe Reader to view
them, which you can download and install on your own.::
::Assumption to the problem:::
::The ATI kernel driver is crashing because one or more of its relative
components are sending a false value sent by the video card, or by
DirectX 9/10 interface, thereby causing the kernel to crash.::
::This false value or data is sent after the signal of the LCD monitor
has changed, or when initializing DirectX 9/10 interface components and
or vice versa.::
::It is not a Vista problem, or an XP problem, nor a hardware
problem.::
::Is it the drivers?::
::You betcha it is!::

::Conclusion to the problem:::
::To the (ATI (RED TEAM)) and (Nvidia (GREEN TEAM )) I hope you will
STOP cramming so much crap into these drivers just so you can save space
and a little time and money. As you can see what I had to go through
just to make these dam drivers work with my card. Instead of cramming
all drivers for all the cards into one package, you should have special
driver packages for a particular or similar card models. This also will
save time in debugging hard problems such as this type, because you will
not need to test every dam driver and or card model. A package such as
this is not destined to fit all, PERIOD.::
::I suggest both teams should look into this problem very deeply,
instead of guiding customers to false theory such as buying a new
powerful PSU. As you can see, my DELL has a 300-watt PSU throwing 22
amps at a +12 volt rating enough to run all my devices and more. This
annoying error and crashes also occurred in an XP system using a 450
PSU, BAH!::

::B.M::


--
BadMouth

BadMouth

unread,
Apr 10, 2008, 7:48:49 PM4/10/08
to

::Since my previous post, I have been helping coworkers, and neighbors
in modifying their drivers.::
::For those who have downloaded my instructions, and are still having
trouble making them work, try the following modification combination:::
::1.:: ::Download the 8.3 standalone driver package, and the full
package 7.6 from the ATI site.::
::2.:: ::When you have extracted both packages as in my instructions,
instead of coping two files from the 7.6 package, we are going to copy
all files EXCEPT the following:::

::atikmdag.sy_::

::3.:: ::Paste all files into the 8.3 directory.::
::4.:: ::Now install the drivers as you would normally.::
::Note: you can install the 7.6 (Catalyts Control Center) software
package if the modification works for you.::
::I have also tried this on my DELL and I am currently using it now,
the difference with this modification is that both the games that I had
previous mention had some minor issues, work fine now, however the game
Crysis although runs normal, does not run as smooth as it did with the
previous driver modification. But then again we cannot have it all.::
::For those who have laptops, I did a few of them using the following
packages:::
::8.3 standalone driver package, and the old 7.4 package. Within the
old, package 7.4 copy ONLY the following files into the 8.3 directory:::
::atiumdag.dl_::
::atiumdva.dl_::
::This seems to work fine for the laptops I did.::
::This is my last post; I hope some of you got those drivers to work,
such as I did!::
::I am going to take a vacation now, and give my computer a rest since
it has been on for 3 weeks straight.::
::I encourage anyone NOT to give up; you will find a modification that
will work for you as I did, until ATI Team members get off their lazy
F#&*!@ A%$#& and do something about it.::
::Until then may the wind blow behind you always!::
::B.M::


--
BadMouth

doctorWHO

unread,
Apr 13, 2008, 12:52:51 PM4/13/08
to

Hello,
Running Windows Vista 64:asus m3a32mvp, 2x2gGskill, 750quad
silencer(pcPower&Cooling), visiontek 3870(w/arctic cooling),
coolermaster 690case8-120mm fans/1-80mmfan, amd 5000+X2(w/arctic
cooling) Temps: cpu29/40, gpu32/48-62

I tried what your pdf described, but for me i used 7.11's atimkdag.sy,
and the other two files from 7.12 the first drivers to support my card,
and still got the error playing bioshock.....for me bioshock gives me
the most errors of any other game i play. i can't get hl2 based games
to freeze, Prey is rock solid maxed. Unreal Tournament 3 also freezes
constantly, not nearly as bad as Bioshock but at least UT3 doesn't
require rebooting the game. Bioshock completely locks and u lose your
progress. Funny thing is UT3 and Bioshock are both Unreal Engine.
Audiosurf also freezes only when u plop Antialiasing on 8x. At this
point it is my mission to get stability in Bioshock, once that is
complete i think my prob will be fixed. Wow this is an annoying
problem....Still haven't tried what was suggested in your last post, any
other tips hints or tricks would be greatly appreciated......


--
doctorWHO
Posted via http://www.vistaheads.com

BadMouth

unread,
Apr 14, 2008, 2:13:22 AM4/14/08
to

::No ATIKMDAG.SYS message pop up driver packages:::
::Ok folks I know I said this previously that it will be my last post,
but there was something bothering me as to why some modifications of the
drivers worked and others did not.::
::After analyzing the driver packages, I came to the conclusion that
the start of the ATI driver bug begins with the 7.6 drivers. Doing
further study, I also realize that the old driver versions such as 7.3,
7.4 and 7.5 are the only drivers that are ATIKMDAG.SYS message free. I
used one of my old ATI cards with the above packages and no crashes,
blue screens and message pop ups occurred. However, I could not run some
of my games because the card was too old.::
::From this, I decided to convert a mixture of the 7.4, and 7.5 drivers
into recognizing my card ATI HD 2600 XT PCI-EX and newer cards that the
8.3 driver package recognizes.::
::The following are the results of these driver packages:::
::7.4 driver package:::
::1. Vista performance test pass.::
::2. No crashes, blue screens and ATIKMDAG.SYS message pop ups.::
::3. All games that I have previously mentioned in my instructions run
good, except the BIA still crashes occasionally on to the desktop with a
(General Protection Fault) message box.::
::4. When un-installing the drivers as soon as the driver is removed,
you will get a black screen, you then need to shutdown, or restart your
computer.::
::::
::7.5 driver package:::
:: 1. Vista performance test pass.::
::2. No crashes, blue screens and ATIKMDAG.SYS message pop ups.::
::3. All games that I have previously mentioned in my instructions run
good, except the game Crysis slow as crap. However, this can change by
setting medium and low graphic options.::
::4. When un-installing the driver removes normally.::
::::
::Now for the driver package 7.4 mixed with 7.5 files:::
::1. Vista performance test pass.::
::2. No crashes, blue screens and ATIKMDAG.SYS message pop ups.::
::3. All games that I have previously mentioned in my instructions run
good, except Crysis still very slow in the introduction and main menu. I
would need to repeatedly press the [ESC] key and left mouse button to
pass the introduction and load my save game. Nevertheless, as soon as
the game loads whoosh fast as hell.::
::4. When un-installing the driver removes normally.::
::Now I am not going to say that the driver packages are going to work
with every card especially the newer cards. However, they do work with
mine and with some old and newer cards. Also, note that these drivers
are ONLY for Radeon type cards and no other type.::
::I would like to also point out that since these are old driver
versions, don’t expect to utilize the full graphics potential of your
card, since they do not support special graphic operations that your
card model may include.::
::I cannot stress this enough, if you are not going to follow the
directions in removing the current drivers you are using, DO NOT even
bother to install these older driver packages. I got a call last night
from a neighbor asking me as to why the 7.4 driver package crash her
system. I said did you remove the driver’s accordingly to my
instructions. She said, ā€œYes I used the Program and Features to remove
them!ā€ I said did you go into safe mode and used the driver cleaner to
remove left over components? She said, ā€œO, I forgot!ā€ This is why you
must remove them as stated in my instructions, because the setup program
is not going to overwrite newer driver components already in your
system. If you don’t you will have a mixture of the old and new driver
components, which can crash your system or worse.::
::For Vista 64-bit users I am sorry, I did not create such a package,
since I am not using or ever going to use a 64-bit system again. I had
my fills with these 64-bit systems and I feel the extra 16-bit
processing power is not worth the headaches.::
::For those who are new and have not downloaded my instructions they
can be found here:::
::http://rapidshare.com/files/105950403/ATI_Problem_Solved.pdf::
::All must do the following steps as in my instructions before and
after installing the driver packages:::
::1.:: ::Do steps 1 – 9 to remove the drivers.::
::2.:: ::Install the drivers.::
::3.:: ::Then do steps 16 – 19.::
::Note: I am not going to reply to any comments whether positive or
negative, I did what I had to do in making my system run smooth until
the ATI team members fix these issues in their new release.::
::The driver packages, which are in WinRAR format, are located here:::
'::_http://rapidshare.com/files/107305840/7-4_vista32_dd_ccc_enu_44985.rar_::'
(http://rapidshare.com/files/107305840/7-4_vista32_dd_ccc_enu_44985.rar)
'::_http://rapidshare.com/files/107309981/7-5_vista32_dd_ccc_enu_46757.rar_::'
(http://rapidshare.com/files/107309981/7-5_vista32_dd_ccc_enu_46757.rar)
'_::http://rapidshare.com/files/107319789/7-4_Mixed_with_7-5_vista32_dd_ccc_enu_44985.rar::_'
(http://rapidshare.com/files/107319789/7-4_Mixed_with_7-5_vista32_dd_ccc_enu_44985.rar)
::Realize that these old driver packages are only here for 15 days, and
will be deleted after that, so get them while you can. Also, note you
can install the (Catalyst Control Center) software package version 7.6
which you can download from here:::
::'Previous Catalystā„¢ Display Drivers for Windows Vista (32 bit)'
(http://ati.amd.com/support/drivers/vista32/commonprevious-vista32.html)::
::I have not tested the control center with driver package 7.4, so I do
not know if it will work.::
::Now I can rest!::
::B.M::


--
BadMouth

BadMouth

unread,
Apr 14, 2008, 9:34:37 PM4/14/08
to

No ATIKMDAG.SYS message pops up, Update:

Ok folks I have just deleted the driver packages and my instructions on
how to prevent the ATIKMDAG.SYS message pop ups.
A new breaking solution has just dawn on me after reading the previous
posts of these two members:
CATALYSTCATCHER, and SilverDev a fellow programmer.

As I stated in my first post and I will stick with it, is that I feel
that the problem is related to the monitor signal and the card and
drivers. I consider myself as an outcast compared to most of the posters
in this thread, which posted similar symptoms.
For me, my system would randomly and constantly crash along with the
ATIKMDAG.SYS message. I could not and I repeat could not do anything
with my system without crashing using the driver versions: 7.6 all the
way up to the 8.3 drivers.
If anyone is going to solve this problem, it is going to happen with a
system as mine. Why? Because as a programmer when a program crashes just
once in a while, it is hard to pinpoint the cause unless we actually
stumble into the problem.
If a program crashes sometimes, and then sometimes, constantly crashes,
then we have a program that can be easily debugged to pinpoint the
cause.
Now you guessed it, my system!

Here is the WONDERFUL BREAKING NEWS of my analysis:
I am currently using the FULL package of the Catalyst 8.3 driver
versions, that is right the FULL package mahahahahaha! Why am I
laughing? Because I am so overjoyed with excitement!
It has been now over 6hrs with no crashes, message pops ups, and guess
what? I am able to play with all the following games with no crashes
mamahahahahaa!
First my major crashing game Unreal Tournament followed by Brothers and
Arms and BIO Shock both also Unreal Engine game types, followed by
Crysis, O yeah!, Medal of Honor Airborne, Medieval Total Wars, Need for
Speed Blacklist, Need for speed Carbon, Call of Duty 4 and finally Tom
Clancys Rainbow Six Los Vegas.
I say, ā€œHit me Momma and wake me up!ā€

Now I bet you are wondering what I did to get this result? Here is what
I did, now mind you it is still in the testing mode, however since I
managed to bring my system to actually use these drivers without having
a dam crash, or pop up message, I believe it is a good clue into solving
this annoying problem.

1. Removed the drivers correctly accordingly to my previous post.
2. Shutdown the Monitor and System.
3. Disconnected the digital line from my Monitor and ATI card, leaving
the Analog connected.
4. Turn on the system, and booted into the BIOS, from within the BIOS I
disabled the Multithreading
feature.
5. Booted into Vista, then within my LCD Monitor display OSD menu, I
selected the DDC/CI option and selected the option Disabled. For those
that do not know what DDC/CI is let us say that it allows or prevents
any programs from changing the frequency signal of the monitor.
6. Installed the drivers 8.3 full with control center.
7. Rebooted my system.

OH DAMMIT! BAH! I know it is going to crash, just seen the dam random
dots on my desktop!
Oh well must follow my debugging instructions; Let me run the Vista
Performance test.
CRASH! Well I knew this was going to happen, Ok reboot system!

Back to the desktop, I go still random flashing dots!
Ok now it is time to do something else!

8. Double click the Catalyst control icon located at bottom right task
bar.
9. Selected (Advance) settings.
10. In the control center (Monitor Properties), (Attribute) section I
unchecked the (Use Extended Display Identification Data) box.

Now the following step is where I notice some changes:
11. In the Monitor (Adjustments) section I decided to place a check
mark in the (Composite synic) box.

As soon as I did that, my LCD display changed and was out of whack. Now
I did this because I know that if anything is going to happen it either
is going to be the same, better, or worse. I had nothing to lose.

After that I rebooted my system to make the changes take affect.
WELL WHAT DO YOU KNOW?
NO random dots appearing on my desktop? HMMM Seems as if I am getting
somewhere.
Ok time to adjust the monitor to reflect the change!
Within my LCD Monitor I selected the AUTO ADJUST
option. After a bit the monitor WALLA! Adjusted my display perfectly.

Now hmmmm, this seems familiar, reminds me of the good old days using
an Analog monitor!

Ok! Now it is time for a reboot!
Well folks after that reboot I have not seen one freaking little dot,
dark line, and the Vista performance test pass like a grass over my A@#.
There you go folks the start of a good chance of finding this no good,
disgusting aggravating nuisance of a crappy bug!

I will be posting later on when I make more changes, like setting the
Multitasking On.
I am not going to do anything now, because I am too happy to do
anything, and besides I want to enjoy my games.
B.M


--
BadMouth

BadMouth

unread,
Apr 15, 2008, 6:01:35 PM4/15/08
to

Just for the record folks: This DELL system is the first prebuilt system
I ever bought in my life, and if god willingness will be my last. I
always build my own systems, because I like to know what I have, but
since I am in a budget I had to either pick from buying a prebuilt
system, or build one from scratch. Since building a system would cost me
way over what I would pay for this crappy system, I decided to buy this
S@#%.
The first thing that went when I unpacked it was the operating system,
and the partitions. I like to install my own system; not having any crap
that I am not going to use is a waste.

As for the advice from ā€˜axmt’, about power management that is the first
place I go when I first install my systems. Yes, I have all set properly
for a desktop system.

Now for some results:
1. After my last post, my son and I ran the computer a total of 15hrs
straight,
from running programs to running the games. Result AOK.

2. Before I went to work, I enabled the multithreading feature, and ran
the
random image-creating program that I had made way back. This program
will
take 5 pictures that I have taken and will combine them into one then
save
the result into a file. I set the randomization to a total of 50, which
means it will create 50 images from several pictures before actually
saving
the image. Now this program is a total CPU pig, if anything is going to
happen
it is going to be with this program. Results FAILED.

3. After step 2, rebooted my system, ran Crysis. Results CRASH!

From the above results, we can say it is related to the following:
1. RAM
2. Monitor signal
3. Drivers

I am not upset with the results considering I am actually using the
drivers and the Control Center, with no constant crashes like I used to
get. I am very pleased with the results :).

I am leaving the multithreading enabled and I am going to make more
changes, and will post the results later.

B.M


--
BadMouth

BadMouth

unread,
Apr 15, 2008, 8:51:38 PM4/15/08
to

IMPORTANT:
Listen I am sorry that I have not
mentioned this before, but since I got carried away in trying to figure
out the problem of these dam drivers, I forgot to mention it
previously.
ANYONE who has installed the ā€œCatalyst
Control Centerā€ package whether you made changes or not using the
Control Center be sure to select the (Preferences) menu tab, and reset
your adapter to ā€œFactory Defaultsā€ before un-installing the Control
Center or the drivers.
This is very important to do,
especially if you are doing some testing with your system.
If you do not, you will get the same
results when installing another driver whether old or newer.
So if you are experiencing the same
results, after un-installing the drivers and the Control Center, be sure
to install the Control Center, and reset your adapter to default even if
you did not make any changes. THIS IS VERY IMPORTANT!
Ok now that my conscience is cleared, I
am still trying out some new changes, and will report later.
B.M


--
BadMouth

BadMouth

unread,
Apr 17, 2008, 12:31:33 AM4/17/08
to

Well folks after numerous testing with the ATI HD 2600 XT PCE the
results are:

1. With multithreading enabled the system crashed extensively.
2. With multithreading disabled the system occasionally crashed.

1. With DEP disabled and multithreading on, the system crashed
extensively.
2. With DEP disabled and multithreading disabled, the system crashed
occasionally.

1. With DEP and DDC/CI enabled and multithreading enabled system
crashed extensively.
2. With DEP and DDC/CI disabled and multithreading disabled system
crashed occasionally.

1. With DEP and DDC/CI enabled, and background services set to full
performance, system crashed
extensively.
2. With DEP and DDC/CI enabled, and foreground services set to full
performance, system crashed
occasionally.

Now the above tests were done with the 8.3 drivers and the control
center installed. These test range from
Printing, Gaming, Movies to productive programs such as CAD, Paintshop
Pro, Visual studio 2005, Visual
studio 6.0, Delphi 7.0, Burning studio, Databases, Word etc...

Now from all the tests, that I have done so far for the past month and
up to now is that the ATI drivers
are not completely the blame. What I mean is that they are partially to
blame for this bug. It is not the
whole driver package causing this mess, and I have no reason to believe
that the Catalyst Control Center
is the culprit. In fact, back a few weeks ago I ran the standalone
driver and still got the same results
as if I had the control center installed.

Now I decided to go on ahead to Circuit City and talk to one of my
friends, got a good deal on a GeForce
8600 GT, now mind you that this card is similar to the ATI HD 2600 XT
card.
Ran all the tests the same way, no special tweaks or settings, and
guess what? ALL PASSED!

So my solution to this problem folks is this:

1. Removed ATI favorites from my internet explorer, and in with Nvidia.
2. Deleted all my packages that I have created to run the 2600 XT,
freed up 1.g
3. Deleted all references of ATI from my registry.
4. Deleted all email documents from ATI Techs.

For those who are curious as to what I did with the ATI HD 2600 XT:
WHOOOSH--- BING---BANG---CLING---CLANG---CLAMP

And in with the good!
B.M'[image: http://www.driverheaven.net/images/smilies/smilie.gif]'
(http://www.driverheaven.net/images/smilies/smilie.gif)


--
BadMouth

AuroraDr

unread,
Jun 3, 2008, 5:17:37 AM6/3/08
to

I solved all of my crashes by simply upgrading the monitor driver from
my monitor manufacturers website. I have been running crash and error
free now for three days now when I used to bluescreen five to six times
a day.

System:
Two 2.8GHz Quad-Core Intel Xeon ā€œHarpertownā€ processors
10 GB memory
1.32 TB storage
ATI Radeon HD 2600 XT
ATI TV Wonder HD 650 Dual Tuner
Windows Vista 64 Bit with all MS updates

I am not a MAC person but Apple had the most powerful and reliable
system on the market when I bought this system. It runs Vista better
than any other computer that I have encountered.

Not sure if this will help anybody else but it fixed my problems with
ATIKMDAG.SYS

Rick
:)


--
AuroraDr
Posted via http://www.vistaheads.com

chuckbam

unread,
Jul 25, 2008, 11:33:28 AM7/25/08
to

'atikmdag error message/computer freeze. - Page 2 - Vista Forums'
(http://www.vistax64.com/showthread.php?p=786055#post786055)

What about the problem on like 1 out of 5 boots?''
(http://www.vistax64.com/showthread.php?p=786055#post786055)


--
chuckbam

*q6600 slacr quad cpu at 3.36 ghz/ fsb 1680 mhz ~ asus p5b deluxe ~
mushkin em2-6400, 8gb at 840 mhz, 5-5-5-15 ~ maxline pro 500, raid 0,
931gb ~ hd 3850 512mb/ hd 2600 pro 512mb ~ dual tv tuners: ati 650 pro/
550 pci ~ silverstone op650 ps ~ 3 lcd multiple display w/ full custom
aero ~ ... vista ultimate 64-bit ... windows experience index 5.9 ...
system runs 24/7 *

mehuh

unread,
Aug 13, 2008, 4:35:48 AM8/13/08
to

I wanted to post an update.

I am still experiencing problems with this error on my computer. I
looked through the logs and also discovered that apparently my video
card memory was insufficient (I have a 256mb card). So, I decided to
upgrade the card. When I went in to upgrade the card, I discovered that
the card was seated very close to the area where the memory is stored.
My memory produces a lot of heat (FB DIMM on a Mac Pro Early 2008
model). So, I used HWMonitor from 'CPUID'
(http://www.cpuid.com/hwmonitor.php) to check the temperature of the
video card CPU core. I found that it was the hottest component in my
computer running at about 80-85 degrees celsius (not farenheit). So,
when I installed the new card, I moved the video card to the next
available slot. Now my card is running less than 60 degrees celsius.

So, it is quite possible that the heat was causing this problem for me.
I would recommend that everyone check the temperature to ensure that
their video card is not overheating. Of course, I don't know whether
this will resolve my issue, but it seems very possible. I'll re-post if
the problem persists.


--
mehuh

mehuh

unread,
Aug 20, 2008, 4:47:41 AM8/20/08
to

It appears that the temperature of my video card was NOT the issue since
my computer is still BSODing while the temperature of the card is around
55-60 degrees Celsius. So, I am still being plagued by this problem
:mad:

mike-cow

unread,
Aug 21, 2008, 9:31:32 AM8/21/08
to

Catalyst 8.8 is out, try it. :)


--
mike-cow

mehuh

unread,
Aug 21, 2008, 1:31:44 PM8/21/08
to

Will do! Thanks for the info.

mike-cow;816031 Wrote:
> Catalyst 8.8 is out, try it. :)


--
mehuh

mehuh

unread,
Aug 22, 2008, 5:50:49 AM8/22/08
to

8.8 display drivers didn't help :(

8.8 drivers + catalyst software actually caused some significant slow
shutdowns.

mike-cow;816031 Wrote:
> Catalyst 8.8 is out, try it. :)


--
mehuh

Backtothefuture

unread,
Aug 25, 2008, 11:20:15 PM8/25/08
to

Hi,

Thought I would post an update. Since my last post, I have still not
had a BSOD. Guess the BIOS update worked. System is running stable.


--
Backtothefuture

mehuh

unread,
Aug 26, 2008, 12:00:20 AM8/26/08
to

Glad to hear you have gained some stability! Hopefully your system will
remain stable.

As for me, I just disabled TMM in Vista to see if this will help the
situation. I haven't had a BSOD yet myself in a few days, but it
sometimes doesn't occur for up 5 weeks, so I'll have to wait and see.


--
mehuh

mehuh

unread,
Aug 29, 2008, 3:06:11 AM8/29/08
to

*sigh*... disabling TMM didn't help either


--
mehuh

mehuh

unread,
Sep 1, 2008, 9:45:43 PM9/1/08
to

So I decided to finally give in and call MS since I wasn't getting
anywhere with this. Unfortunately, they too were unable to determine
the cause of the problem. Since this problem only occurs randomly on my
computer, they informed me that they were unable to do anything else.

However, they pointed something out that I found interesting.
Basically, since I use a high resolution LCD monitor (1680x1050), the
computer needs to be aware of what monitor it is talking to because the
computer and the monitor share information to correctly display the
screen. Unfortunately, Dell has decided not to post drives for my Dell
2005FPW, so all my computer shows for the monitor is "Generic PnP
Monitor". So, although this may not be the issue, getting a new monitor
that does correctly show up in Vista -may- help. So, I may consider
this.

Just FYI.


--
mehuh

Lum

unread,
Sep 13, 2008, 6:06:50 AM9/13/08
to

I have been having these same kind of troubles for a long time. Tried
all kinds of things to solve it and spent hours and hours searching for
a sollution.
With XP installed there is no problem at all but with Vista it keeps
getting unstable at random moments and sometimes crashes to a BSOD.

The _sollution_ for me: disable the second monitor i was using. Don't
just keep it turned off, disable it in your Catalyst Control Center.

This worked for me and i after i did it i havent had a single
atikmdag.sys error anymore (over 2 months)

(I have a Syncmaster 970P and had an old crt 19" Philips as 2nd one)

Hopefully this helps, good luck all and post here if it worked for you
or not please.


--
Lum

mehuh

unread,
Sep 13, 2008, 3:44:39 PM9/13/08
to

@Lum:

Hey! Unfortunately, the second monitor is a necessity for some of the
work I do (I actually need a third monitor). So, removing the second
monitor would not work for me. Although I have read on other forums
that this workaround has resolved this problem also. So, it's a good
solution if you don't absolutely need the second monitor.

Just curious, when you had both monitors connected, did they both show
up with their names in the Display Control Panel? Or, did one just show
up as a "Generic PnP monitor"? I am wonderingwhether the fact that it
is not identified by Windows Vista has anything to do with the problem.


--
mehuh

Lum

unread,
Sep 14, 2008, 3:52:33 PM9/14/08
to

I read something about installing drivers for the monitor helped for
some too. So i did try to install the old CRT monitor drivers and it
showed up with the actual type. But this didn't fix it for me.
Maybe its just crashing because its an LCD and CRT working next to each
other, but i can't test 2 LCD out myself at moment.

Good luck trying to fix the error, hopefully there will be a patch or
something for this soon :)


--
Lum

mehuh

unread,
Sep 14, 2008, 7:30:22 PM9/14/08
to

@Lum: So, it sounds like if I did get a new monitor that was
successfully recognized by Windows, that it probably won't help. Thanks
for clarifying that.


--
mehuh

Rich.

unread,
Sep 15, 2008, 8:45:33 AM9/15/08
to
Have you read this thread on the ATI forum?
http://forums.amd.com/game/messageview.cfm?catid=260&threadid=92659&highlight_key=y&keyword1=atikmdag


"mehuh" <gu...@unknown-email.com> wrote in message
news:c2979f4b1b456b32...@nntp-gateway.com...

mehuh

unread,
Sep 15, 2008, 1:31:03 PM9/15/08
to

Rich.;836498 Wrote:
> Have you read this thread on the ATI forum?
> 'AMD Game Forums - ATI ATIKMDAG Error'
> (http://forums.amd.com/game/messageview.cfm?catid=260&threadid=92659&highlight_key=y&keyword1=atikmdag)
>
>
> "mehuh" <gu...@xxxxxx-email.com> wrote in message
> news:c2979f4b1b456b32...@xxxxxx-gateway.com...> > >
> > >
> > > @Lum: So, it sounds like if I did get a new monitor that was
> > > successfully recognized by Windows, that it probably won't help.
> > Thanks
> > > for clarifying that.
> > >
> > >
> > > --
> > > mehuh > >
I have, but that hasn't helped. Also, the thread does not offer a
resolution that works for everyone.


--
mehuh

jamesr4199

unread,
Sep 23, 2008, 3:26:13 PM9/23/08
to

Same Problem tried ATI Web Site they tell me to start taking my computer
apart. Checking memory cooling of my cpu ETC. I think they have a
problem!!

Jimmi


--
jamesr4199

chuckbam

unread,
Sep 23, 2008, 4:52:54 PM9/23/08
to

I only have the stop problem on like one in 5 boots. After a boot, if I
am going to have one, it does not take long. I re-boot and then have
very long up-time free of the problem.

On a different computer, I loaded the drivers only. That fixed it.

I think the problem is with the c control center.

mehuh

unread,
Sep 23, 2008, 5:05:31 PM9/23/08
to

chuckbam;843596 Wrote:
> > jamesr4199;843519 Wrote:
> > Same Problem tried ATI Web Site they tell me to start taking my computer
> > apart. Checking memory cooling of my cpu ETC. I think they have a
> > problem!!
> >
> > Jimmi> >
>
> I only have the stop problem on like one in 5 boots. After a boot, if
> I am going to have one, it does not take long. I re-boot and then have
> very long up-time free of the problem.
>
> On a different computer, I loaded the drivers only. That fixed it.
>
> I think the problem is with the c control center.

For me, installing only the drivers didn't help. So, while it may work
for some people, it is unfortunately not a universal solution.

I am currently testing a new theory. I have heard that people have had
luck disabling Aero. However, I use Aero for the live previews while
alt tabbing, etc. So disabling Aero is not a feasible solution for me.
Instead, I have disabled transparency, which offers no functional
advantage to me. I'll post if I get positive results with this.


--
mehuh

chuckbam

unread,
Sep 23, 2008, 9:16:34 PM9/23/08
to

you may also want to try the Intel drivers. They don't load on their own
in Vista. You need to find the extracted files or use the zip and load
them in safe mode by hand. It greatly reduce the problem for me.

mehuh

unread,
Sep 23, 2008, 10:58:07 PM9/23/08
to

chuckbam;843793 Wrote:
> you may also want to try the Intel drivers. They don't load on their own
> in Vista. You need to find the extracted files or use the zip and load
> them in safe mode by hand. It greatly reduce the problem for me.

I assume you are referring to the Intel Chipset drivers? If so, I
installed that a while back, but it unfortunately didn't resolve the
problem for me.


--
mehuh

chuckbam

unread,
Sep 23, 2008, 11:08:26 PM9/23/08
to

I even have used the Run command, and they did not load.

*:\Program Files\Intel\INFINST -OVERWRITE -S

http://chuckbam.com/Posts/readme.txt

chuckbam

unread,
Sep 23, 2008, 11:03:36 PM9/23/08
to

Did you check the device manager to see if they loaded? You need to do
it by hand. They do not install with the setup in Vista. I know this for
a fact. You prob. have MS 2006 drivers loaded.

Lum

unread,
Sep 24, 2008, 10:13:46 AM9/24/08
to

To come back to what worked for me.....

Do you guys all have a 2nd monitor atached?
And if so....does the error stop for you too when you disable the 2nd
monitor in the control center?

Just so we can pinpoint the problem this would be usefull info for many
i think.

Greets,

Lum


--
Lum

chuckbam

unread,
Sep 24, 2008, 10:17:23 AM9/24/08
to

I have 3 and can disable any no problem

mehuh

unread,
Sep 29, 2008, 1:42:45 PM9/29/08
to

It appears that I do have the older Intel chipset drivers despite my
installing the news ones because we have to do a manual upgrade:
"In order to install an updated version of the utility, you will need
to use the have-disk installation method. Otherwise, you can use the
setup program to install the utility"
'IntelĀ® Chipset Software Installation Utility - Have-disk installation
instructions'
(http://www.intel.com/support/chipsets/inf/sb/CS-009272.htm?iid=chipsets+infmain&)

However, I was unable to successfully upgrade my chipset drivers using
this approach because for some reason I don't have a "Processor to I/O
Controller" option in the device manager. I tried upgrading other
processor related system devices with no luck. So, I will need to look
further into this (I have a Apple Mac Pro Early 2008 which complicates
matters).

In any case, Catalyst 8.9 came out on 9/17 so I will be trying them out
this week.

Also, disabling transparency hasn't helped. While my system hasn't
BSOD'd yet, I have seen the "ATIKMDAG has stopped responding but was
successfully recovered" which means that a BSOD will occur at some point
in the future.

Someone also mentioned that resetting the Catalyst software to defaults
and then installing the new version may help, but this has not resolved
my problem.

I'll post if 8.9 helps.


--
mehuh

chuckbam

unread,
Sep 30, 2008, 7:40:12 AM9/30/08
to

I needed to do it in *safe mode*. I updated every thing in the system
devices that said Intel and one other device would update. I wish I
remembered the one. I did the same with the USB.

By the way, I am not 100% driver stopped responding free. But, it is
better. Maybe one in five boots. It will happen shortly, so I re-boot
and usually don't have the problem. I think it also helps if you don't
use the CCC

mehuh

unread,
Sep 30, 2008, 1:17:10 PM9/30/08
to

chuckbam;848979 Wrote:
>
>
> I needed to do it in *safe mode*. I updated every thing in the system
> devices that said Intel and one other device would update. I wish I
> remembered the one. I did the same with the USB.
>
> By the way, I am not 100% driver stopped responding free. But, it is
> better. Maybe one in five boots. It will happen shortly, so I re-boot
> and usually don't have the problem. I think it also helps if you don't
> use the CCC

Good point! I'll have to try that in Safe Mode. Did you use the
Processor to IO selection in the device manager to update the chipset
drivers? If not, which device did you use to update the chipset driver?

Thanks.


--
mehuh

chuckbam

unread,
Oct 2, 2008, 12:41:13 PM10/2/08
to
I did one at a time. Get rid of the CCC too. It is a problem too.


> I needed to do it in *safe mode*. I updated every thing in the system
> devices that said Intel and one other device would update. I wish I
> remembered the one. I did the same with the USB.
>

mehuh

unread,
Oct 2, 2008, 8:57:46 PM10/2/08
to

Ok, thanks. I'll do this once the computer crashes again (I am hoping
that v8.9 has resolved the issue... but I am not feeling lucky).


--
mehuh

chuckbam

unread,
Oct 2, 2008, 9:02:22 PM10/2/08
to

I removed the CCC and it is filially gone 100%. I held off one my #1
system because I wanted Avio,

mehuh

unread,
Oct 2, 2008, 9:25:36 PM10/2/08
to

I initially didn't install CCC. But, when I started getting BSODs, as a
test I did install it to see if it would resolve the BSODs.
Unfortunately for my computer, having CCC installed or not installed
doesn't affect the BSODs.


--
mehuh

chuckbam

unread,
Oct 2, 2008, 9:32:24 PM10/2/08
to

I would not think having the drivers loaded only would cause BSOD. I
would look in the event viewer. JMHO

mehuh

unread,
Oct 2, 2008, 9:53:43 PM10/2/08
to

I wasn't able to locate anything in the event viewer that would explain
this around the times the BSODs occur. I also analyzed the crash dump
and it keeps pointing to atikmdag.sys (one of my crash dump bugcheck
analysis is at
http://www.vistax64.com/vista-hardware-devices/3707-atikmdag-sys-post765915.html#post765915
in case you want to see it). Also, the BSOD does not consistently occur
during any specific program - it happens randomly. Sometimes it occurs
2-3 times in a day and sometimes I'll go for 2-3 weeks without any
problems. The problem also sometimes occurs if I rebooted recently, or
also if I rebooted 1 week before. It's this randomness that makes it so
frustrating because I can't seem to pinpoint the issue.

When I contacted MS, they also kept blaming the ATI drivers. But, when
I contacted ATI, they denied responsibility.

I'll try updating the chipset drivers from the BIOS to see if that
works any better after the BSOD recurs since I isntalled 8.9.

I appreciate all of your help.


--
mehuh

chuckbam

unread,
Oct 2, 2008, 10:13:51 PM10/2/08
to

mehuh;851354 Wrote:
> What do you mean by fully clean up? I always uninstall, reboot and then
> install the new ATI driver-only package. Do you do something else after
> uninstalling the ATI software?

That is how I do too. I just don't understand how the CCC would stop a
blue screen, I find it a buggy TSR

mehuh

unread,
Oct 2, 2008, 10:06:28 PM10/2/08
to

What do you mean by fully clean up? I always uninstall, reboot and then
install the new ATI driver-only package. Do you do something else after
uninstalling the ATI software?


--
mehuh

chuckbam

unread,
Oct 2, 2008, 10:01:37 PM10/2/08
to

Mehue,
One last thing, try to clean up ad fully un-install the CCC installer
before updating.
good luck

mehuh

unread,
Oct 5, 2008, 7:55:46 PM10/5/08
to

So I downloaded the latest Intel Chipset software and extracted its
contents. While digging through the folders, I found the INF file that
correspond to my computer. When I opened them, I discovered that the
release dates listed in the INF files correspond with the versions on my
computer indicating that I already have the latest version dated January
30, 2008.

So, it appears that although the entire Intel Chipset software is
updated every few months, not all of the INF files for all of the
computers are updated.

Also, it appears that 8.9 has not resolved my problem. While the
computer hasn't BSOD'd yet, I have gotten the "ATIKMDAG has stopped
responding but was successfully recovered" message which means that the
computer will BSOD at some point.

It looks like my only option now is to use the Apple Bootcamp installer
to install a bunch of Apple software on my computer (I own a Apple Mac
Pro). I wanted to avoid this because Apple bundles a lot of
non-essential programs that I would rather avoid to keep my system
clean. But it appears that it may be my last resort to get this problem
resolved.


--
mehuh

chuckbam

unread,
Oct 5, 2008, 11:31:41 PM10/5/08
to

Something wrong, if you can't find the root cause of the BSOD, you may
need a clean OS install. I don't think it is a simple driver problem
when you can't run without the CCC.

mehuh

unread,
Oct 6, 2008, 12:01:43 AM10/6/08
to

chuckbam;853583 Wrote:
> > mehuh;853457 Wrote:
> > So I downloaded the latest Intel Chipset software and extracted its
> > contents. While digging through the folders, I found the INF file that
> > correspond to my computer. When I opened them, I discovered that the
> > release dates listed in the INF files correspond with the versions on my
> > computer indicating that I already have the latest version dated January
> > 30, 2008.
> >
> > So, it appears that although the entire Intel Chipset software is
> > updated every few months, not all of the INF files for all of the
> > computers are updated.
> >
> > Also, it appears that 8.9 has not resolved my problem. While the
> > computer hasn't BSOD'd yet, I have gotten the "ATIKMDAG has stopped
> > responding but was successfully recovered" message which means that the
> > computer will BSOD at some point.
> >
> > It looks like my only option now is to use the Apple Bootcamp installer
> > to install a bunch of Apple software on my computer (I own a Apple Mac
> > Pro). I wanted to avoid this because Apple bundles a lot of
> > non-essential programs that I would rather avoid to keep my system
> > clean. But it appears that it may be my last resort to get this problem
> > resolved.> >
>
> Something wrong, if you can't find the root cause of the BSOD, you
> may need a clean OS install. I don't think it is a simple driver
> problem when you can't run without the CCC.

Well, I can run, it's just that in the course of 1-4 weeks, I can
expect at least 1 BSOD at random times.

In any case, I just installed the Boot Camp software on my computer
along with an update that was released recently. Hopefully the update
contained a fix for my problem (Apple unfortunately doesn't document
what is contained within the update). We'll see if this resolves the
problem, and if not, a clean install may be required...*sigh*... my
installation is only about 4 months old :(


--
mehuh

mehuh

unread,
Oct 31, 2008, 5:17:40 AM10/31/08
to

I wanted to post an update:

1. I'm trying hard not to reformat, so I am exhausting all other
options first.
2. I tried the latest ATI Catalyst v8.10 (driver only), and still
experienced the same problem.
3. I installed the video driver provided by MS Update and it appears to
be working much better. I will see how this turns out. With my older
ATI 2600 card, the MS drivers didn't help, but with the newer ATI 3870,
I appear to be more stable. I will see how long I remain stable.

I found some other resources that have some potential solutions that
appears to have helped many people:
'Display Driver atikmdag and nvlddmkm Stopped Responding'
(http://www.repairyourpcnow.com/resources/atikmdag-has-stopped-responding.php)
'ATI Radeon graphics cards and the blue screen of death ( BOSD ).'
(http://www.aade.com/ati.htm)

So, I will try these approaches if the MS video driver doesn't work.
But, I wanted to post these links in case others are at a dead end.


--
mehuh

chuckbam

unread,
Nov 1, 2008, 6:41:07 PM11/1/08
to

I have fixed the problem about 95% by taking off all the ATI utilities.
I even disable a service ATI Eternal Event Service. I need to turn it
back on when reprogramming my two ATI Theater Pro cards. If I am going
to get it, the problem happens in less than an hour after a re-boot.

AliK_82

unread,
Jul 14, 2009, 8:35:33 AM7/14/09
to

Hi Guys, fix here for atikmdag error.


I had this chronic problem on my new ASUS M51se laptop (32 bit vista &
ATI HD 3470) and was able to solve the problem by uninstalling ATI
Catalyst Control Center which removes the atikmdag command all together.

Details of the problem are on the attached link.


To uninstall I used windows add/remove programs, you just uninstall the
ATI 'install manager' program and follow the prompts that say 'uninstall
all ATI software'. This will not affect the driver. More details are on
the ATI website about removing the software.


I had been getting major system freeze ups and this atikmdag error was
appearing all the time, even had a blue screen crash! Uninstalling ATI
CCC has totally fixed my problem and has not changed the quality of my
graphics (note I don't do gaming but heaps of duel screen video
editing).


I also want to point out that I tried removing windows updates and
messed around with other fixes & drivers but without result. This is the
only thing that has rid my system of this severe instability.


--
AliK_82
Posted via http://www.vistaheads.com

0 new messages