• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The dreaded ATI nvlddmkm error ?

kmufc77

kmufc77

kmufc77

Soldato
Joined
15 Jul 2007
Posts
4,953
Location
South West
EDIT: title should say:

atikmdag error

hi i havent had this error since my 8800 GTX, ive done a search on here and google and cant find any solid fixes to correct this.
i have found 4 files nvlddmkm files in my windows /system32 folder these will not delete for some reason and are named as nvdia files? i only have ever had a ATI card installed? so why have i got these files name as nvida files.

i recenlty overclocked my CPU last night for the first time didnt have the problem at stock could this be the problem?

would very much like ppl experiences or how this can be fixed for ATI cards please.
 
Last edited:
You say that you once had an 8800GTX. Did you do a format before installing the ATI card? I used to have the same BSOD with my 8800GTX before moving to my 4870x2. But all I did was use Driver Cleaner to clear out the appropriate nVidia files. A format really is the best way of clearing out old driver files to be honest but so far I have managed to get away with it.
 
-BA- said:
You say that you once had an 8800GTX. Did you do a format before installing the ATI card? I used to have the same BSOD with my 8800GTX before moving to my 4870x2. But all I did was use Driver Cleaner to clear out the appropriate nVidia files. A format really is the best way of clearing out old driver files to be honest but so far I have managed to get away with it.
Click to expand...
i had my gtx 12 months ago i have installed vista many times since:) This is a clean install only with a ATI card i have not owned a nvdia card for 12 months
 
Last edited:
In that case I wish I could help but with nothing from nVidia installed or recently uninstalled, I am at a loss. Will be most peeved if I come across this error with my ATI card, as it dogged me for 12 months with my 8800GTX.
 
i had this problem when i first upgraded to crossfire

what i managed to find as a fix to my problem was to.

1)boot into safe mode
2)use driver sweeper to eat the ATI drivers
3)reboot then uninstall the reminantes of the ati drivers normaly from the control pannel
4)reboot, install ATI drivers again, DO NOT reboot at end of install
5)click on start menu and type services into search box, press return.
6)On the list of services there should be one called ATI external event utility DISABLE IT!
7)Reboot, cross fingers and hope.

I hope this works for you this is the only way i can get my card drivers to work with out some blue screen fun.

-sdavlaws-
 
i recenlty overclocked my CPU last night for the first time didnt have the problem at stock could this be the problem?
Click to expand...

This, needs some more voltage to the north bridge or vcore, also make sure that your pci-e is not overclocking with the fsb.

From my own experience I can replicate this error with an overclock that is not stable on either the cpu or the gpu's.

Seems that the nvidia files would have probably come with physx API.
 
sdavlaws said:
i had this problem when i first upgraded to crossfire

what i managed to find as a fix to my problem was to.

1)boot into safe mode
2)use driver sweeper to eat the ATI drivers
3)reboot then uninstall the reminantes of the ati drivers normaly from the control pannel
4)reboot, install ATI drivers again, DO NOT reboot at end of install
5)click on start menu and type services into search box, press return.
6)On the list of services there should be one called ATI external event utility DISABLE IT!
7)Reboot, cross fingers and hope.

I hope this works for you this is the only way i can get my card drivers to work with out some blue screen fun.

-sdavlaws-
Click to expand...
Hi thanks for the tips i will try these can i ask what the ati external event utility does?
 
VinceB1 said:


This, needs some more voltage to the north bridge or vcore, also make sure that your pci-e is not overclocking with the fsb.

From my own experience I can replicate this error with an overclock that is not stable on either the cpu or the gpu's.

Seems that the nvidia files would have probably come with physx API.
Click to expand...
hi at the moment my NB is running at 1.24V is this enough? my pcie is set at 101 my vcore is set on auto i think what should this be set at is this CPU related?
 
I have no idea what the utility dose but i have no negative impact in anyway,

All games run loverly
3dmark06 around 17500 so nuthing important
 
kmufc77 said:
hi at the moment my NB is running at 1.24V is this enough? my pcie is set at 101 my vcore is set on auto i think what should this be set at is this CPU related?
Click to expand...

I'm not overly familiar with overclocking 45nm quads. Is the system stable under intel burn or prime? also does memtest show any errors with memory after the overclock?

running the above should give you an idea of what component is causing the upset, from that you should be able to narrow down what component is failing and therefore which one needs voltages tweaking.

Like I say if it was stable at stock and has only been happening since overclocking then this is where the problem lies. :)
 
Last edited:
VinceB1 said:
what hIm not overly familiar with overclocking 45nm quads? Is the system stable under intel burn or prime? also does memtest show any errors with memory after the overclock?

running the above should give you an idea of what component is causing the upset, from that you should be able to narrow down what component is failing and therefore which one needs voltages tweaking.
Click to expand...
well i ran prime last night for a couple hours and all was fine, i have just took my memory down to 1050mhz as it was running a little higher.
i will try memtest later my problems are almost certainly related to my OC on my cpu as since ive had it which was xmas time had no problems untill OC last night
 
sdavlaws said:
I just had a quick google and i seems to have something to do with detecting the resolutions of monitors pulled into the card
Click to expand...
not sure what this mean?
ive been reading on the net for hours and lots of ppl have conclusions what causes this problem on both the ATI side and NVDIA neither company has said what the problem is caused by and i doubt we will ever find out im sure its only vista related too
 
sdavlaws said:
just try going back to total stock setting to see if it is the overclock
Click to expand...
yes i will give that a shot later ive made a few adjustments in the last hour or so. will wait and see what happens.

also im getting this error more on normal desktop rather than gaming which is odd as its usually vice versa
 
This is a bit of a pointless post by me as i don't have a solution to the problem :(

I had a fresh install of Vista 32 bit and had this problem with the 8.9 to 8.12 drivers and also seemed to have more trouble at desktop and surfing the net than in games.

In the end i moved back to XP 64 bit and haven't had a problem since so i'm sticking with XP until Windows 7.
 
You must log in or register to reply here.
Back
Top Bottom