• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

atikmpag.sys BSOD

E

Epitaph64

Limp Gawd
Joined
Nov 17, 2009
Messages
156
Been getting a BSOD recently on my ATI 4890. The screen corrupts over and it's always the same artifacting pattern, and them mouse becomes a corrupted box sprite, then the computer BSODs and restarts. I tried completely uninstalling drivers, going into safe mode and running driver sweeper, and then reinstalling the latest 10.6 drivers afterwards, and the issue still happens. It happens during games and happened on the desktop once while using FL Studio. If anyone could help me to fix this it would be much appreciated.
 
The last release that never had this problem was 10.4, but since I play BC2 very often and the last two updates have greatly increased load times and performance, I am hesitant to go back. I just clocked my CPU back to stock speeds and I'm going to see if the issue is observed at all anymore. Also, I ran windows memory test and it had no errors (I ran memtest when I first bought the PC with no errors as well.)
 
Oh, as far as flash playback goes, you can disable hardware acceleration in Flash to temporarily alleviate that, but I actually read while researching this BSOD that a certain BIOS flash can resolve hardware accelerated video BSODs. Right now I'm calling off the search for more information until the problem happens again (after I went back to stock speeds) and if it doesn't show up for a week or so, then I'll look into getting some help with overclocking it since I may have just done something wrong.
 
have you checked inside ur case and card for dust bunnies? i'm not sure if this is a solution but artifacting for the most part does involve a bit more heat than hardware is comfortable with. maybe a dusting might help?

also the new flash 10.1 + ccc 10.6 is supposed to be optimized for low resource usage (i think) so while i may be completely wrong about this, i'd try the cleaning and then 10.1+10.6

$0.02
 
I have cleaned my case less than a month ago and temps are fine. Still no recurrence of it since reverting to the stock clock speeds so I think perhaps either the RAM or CPU were giving bad data to the card causing it to crash. I might have to read some more guides on how to overclock since the mark I had hit (3.33 ghz) isn't much for an i7 920 D0 to pull.
 
Been quite awhile and no issues. Guess it was the overclock! Everything I've been doing is running just fine on stock speeds so I suppose I'll save the electricity and use stock for now until I have the need to overclock.
 
Well, speak of the devil, it's back. Opened up a game and it happened, but this time there was no BSOD. Just went to a black screen for about 10 seconds and then restarted. It had the same graphical corruption all over the screen (pink with black boxes and the mouse is an artifacted sprite.) Not sure what to do next to fix it. I really don't want to roll back drivers since the latest make the load times in BC2 so much better than the older ones.

EDIT: Did some more research and found out there's a driver verifier tool. I ran it, and a BSOD occured with a glitched screen (though unlike the one I normally get in aesthetics) and it said the my audigy 2 drivers were to blame. I wonder if it was Creative's faulty drivers all along that have been doing me in! Anyways, I'm uninstalled the drivers and used driver cleaner on it, and am using my Realtek integrated sound now. I think I may need to buy a new sound card for my music production because creative can't make drivers to save their lives.
 
Last edited:
Do you have one for x64?

EDIT: Nevermind, I just googled for it, and found it (not sure why I didn't think of that sooner.) I applied it, so I'll see if it happens again now.
 
Last edited:
Hmm, this issue went away for awhile after 10.7 and has now returned. Does anyone else have any other ideas?
 
I have seen that same error with OC'd RAM. Set you RAM back to stock SPD profile if OC'd or try some different RAM.
 
My RAM right now is running at less than stock speed by a few Mhz. Also, this issue happened with it set to stock speed. I've done memtest a few times without any errors as well.
 
I've been having these lately- started with 10.7, so I uninstalled and went back to 10.6. Just had another one last night during C.O.P. benchmark.

I guess I will go back to 10.5, which seemed pretty stable to me. (I went through a LONG troubleshooting an F4 BSOD. Now that it's resolved -bad SATA I/O -, I can be more confident when it's the drivers.)

Also, I have uninstalled iTRACKER2. It is giving me a constant error in Windows logs..."atidgllk has been blocked due to incompatibility with the system...". I can't seem to get an answer as to WHAT this is, or how big of an issue it is, but I am going to go back to AB, and live with stock voltages for now, and see how my stability is from there...Worth a shot, I guess.
 
I just rolled back to 10.4 since that was the last time I had a stable computer. I had had about 3 of the BSODs all in the same memory address in the course of about 30 minutes, so I just said fuck it. :p Anyways, I really hope this isn't a hardware issue because I swear I have never bought a GPU without having to RMA the first one that I get...

EDIT: Instantly got the exact same BSOD with the old drivers that used to work. I think the card may just be failing like EVERY other GPU I've purchased online. I guess it's time to get in contact with Sapphire and see what I have to do for an RMA.
 
Last edited:
Yeah, but for some reason the drivers no longer change it whenever I do that. It used to work but doesn't anymore.
 
Blackforge said:
Have you tried switching to manual fan controls and turning up the fan speed?
Click to expand...

That was actually my limiting factor in OC'ing my cards... The auto setting didn't appear to be spooling up fast enough to compensate for the heat. Once I set to manual at 80%, all was well.

(and for those interested...I also ran some tests on my 2 GPUs individually so I could find my "weakest link"- turns while one hits 1009 at stock voltage, the other only goes to 940, which is where I am now in X-fire.)
 
try uninstalling your drivers than run a little program called "drivercleaner" then reinstall the latest drivers
 
You must log in or register to reply here.
Back
Top