atikmdag.sys

[Frostmourne]

hm... if you don't mind sure, i'm guessing seven just doesn't like the driver

I'm running Catalyst 9.12 on a 1GB GGDR5 4890 stock from Sapphire - everything works fine.

 

[Hemulen]

Run a disk diagnostic such as Seagate Seatools, then schedule a check disk run. Then run Memtest86+.

I doupt thats the problem, as I'm running the same RAM stick, and the same harddrive for XP.

 

[ThePizzaMan]

hm.......... does your device manager show any conflicts with the card?

 

[smarteyeball]

Have you made sure that your motherboard chipset drivers are installed?

No unknown devices that appear in device manager?

Have you tried installing the latest Directx 9.0c redistributable?
Download details: DirectX Redist (August 2009)

Lastly, just because an overclock is stable in XP, does not mean it is stable in Seven. Seven is a little less tolerant of instable overclocks

 

[Hemulen]

Have you made sure that your motherboard chipset drivers are installed?

No unknown devices that appear in device manager?

Have you tried installing the latest Directx 9.0c redistributable?
Download details: DirectX Redist (August 2009)

Lastly, just because an overclock is stable in XP, does not mean it is stable in Seven. Seven is a little less tolerant of instable overclocks

hm.......... does your device manager show any conflicts with the card?

No conflicts, no unknows drivers in device manager 8except a bluetooth thingy), and chipset drivers installed (latest).

 

[smarteyeball]

Have you checked the Event Viewer Logs to see if there is a faulting module that may be crashing the display driver?

(type 'Event' in the taskbars search and select 'View Event Logs' > Custom Views > Administrative Events)

Look for the driver crash error and see if it points to a particular file in the Faulting Module Path:

 

[Hemulen]

Have you checked the Event Viewer Logs to see if there is a faulting module that may be crashing the display driver?

(type 'Event' in the taskbars search and select 'View Event Logs' > Custom Views > Administrative Events)

Look for the driver crash error and see if it points to a particular file in the Faulting Module Path:

View attachment 42596

No particular file in the Faulting Module Path.. Just "atikmdag.sys has crashed, and has successfully recovered".