Have you seen me?

[Brian R.]

I've had the exact same appearance on my screen. It only happens to me when I overclock my MAX too far.

[Rob M.]

hm... If I wanted to underclock the card in win2k and win98 with the 5.11/6.01 drivers, what would be the best way to do it?

[Daniel Fazekas]

I second that I have never ever seen anything like this before on a G400 and there are four of them around here (all 2x only).

(I also never ever overclock anything.)

In fact the only thing remotely similar was on my Millennium II with one specific driver release in NT4 (didn't happen with the previous release). That was also the only time I've ever written to Matrox tech support. I even received a reply in two weeks saying "Well then go back to the previous driver release."

[Rob M.]

Ok, I've got powerstrip, what is the g400 regular normally clocked at? I'm playing around in q3radiant with agp at 2x right now, core/mem at 123/165.

[Greebe]

Rob, the "Proximity Effect" may not be due to you! Anyone else around? (that's what we have experianced)

[Greebe]

That's it default for a G400 reg... now just drop it down from there (also may want to see if raising it makes the problem worse)

[Joel]

Have you tried attaching a fan to the G400's heatsink? I agree with most here when they say this looks like a heat related problem. Also more system stats please.

Joel

[Rob M.]

well at 113/150, cpu at 495 agp bus at 60, and the case open I'm still crashing in q3radiant (which is all that matters to me)

Interestinly enough, when I disable busmastering through the matrox util, q3radiant acts like the icd is toast (crashes on startup)

have yet to see the garbled screen at 2x, but it's early still..