|
Silly question, but same problem at normal clock rates?
Videoprt is where video hardware discovery and management occurs. If it's throwing 0xD1s then the drawing portion of the driver and the pass off to the hardware is breaking down. Either:
The code is buggy
Update driver. Uninstall old drivers first, clearing all settings, try again.
The hardware isn't responding as expected
Race conditions, failed hardware, pushed too hard, fan failing, etc.
You can see where this is going.
Video systems are complex animals. Different features tax different areas of the system. You might draw triangles all day without problem then see a failure with heavy texture processing because some part of the GPU or memory interface couldn't handle the load. This is where one application can show a problem that doesn't appear elsewhere, simply due to its sequence of operations and how hard it pushes a feature.
Selectively reduce or disable advanced features. AA, etc. Monitor temperatures, improve cooling and watch for effects. Disable BIOS video "features". (shadowing, etc.) Any difference? YOu know the drill. Good luck.
__________________
There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195
|