At first I thought this was Windowblinds or WindowFX to blame, but even after I had rebooted w/o them I saw this desktop. I currently have to run w/o the Matrox drivers...
Announcement
Collapse
No announcement yet.
Help?! Parhelia troubles :(
Collapse
X
-
this is not an AGP issue, it's memory corruption.
Iso, saw your post on Matrox's forums. If this happens consistantly they'll have you RMA it asap."Be who you are and say what you feel, because those who mind don't matter, and those who matter don't mind." -- Dr. Seuss
"Always do good. It will gratify some and astonish the rest." ~Mark Twain
Comment
-
Presumably as in the memory isn't be read or written to correctly. That would account for the corruption, especially since a similar phenomonen can be seen when you overclock the memory too far on a graphics card. This has happened to me with my G400 though and turning the Agp speed down to 2x resolved the issue.What do you want a signature for?
Comment
-
Not to be mean or anything , but you have no experience with Parhelia."Be who you are and say what you feel, because those who mind don't matter, and those who matter don't mind." -- Dr. Seuss
"Always do good. It will gratify some and astonish the rest." ~Mark Twain
Comment
-
LOL. Nice reply Greebe.
He's right though, other cards exhibit similar symptoms when the memory's being pressed to far. (GF4, hint, hint). Not that this necessarily means anything for the Parhelia, but it has been that way with practically every other card I've ever had (er, that I've bothered to try overclocking). This includes a TNT, a G400Max, a TNT2Ultra, a GF2GTS, and a GF3, prior to my current GF4. Notice, among that ton of nV cards that Matrox- it wasn't the exception."..so much for subtlety.."
System specs:
Gainward Ti4600
AMD Athlon XP2100+ (o.c. to 1845MHz)
Comment
Comment