G400 problem

Hello.
I've got a Matrox G400 single head. I've long had this problem with it:
the loading of many 'bitmaps' on screen (such as in a browser, the skins
of MSN Messenger, Asusprobe, the icons in Corel Draw, Windows Media
Player etc) can prevoke a strange "out of resources" problem, where the
screen goes weird white & eventually the program crashes. This happens
in both Win95 & WinME, with all display driver revisions. It happens on
this Asus A7V133-VM, & I think it happened on my last motherboard too.
It does not happen in Linux, only Windows, and does not affect other
video cards in this system. I got this video card straight as it first
came out - were early ones faulty? It'd like to have a solution to this
problem rather than being forced to use the onboard video which can't be
set faster than 75Hz because of moronic Windows.

path <why.RemoveThis@must.I.enter.this> wrote:
| Hello.
| I've got a Matrox G400 single head. I've long had this problem with
| it: the loading of many 'bitmaps' on screen (such as in a browser,
| the skins of MSN Messenger, Asusprobe, the icons in Corel Draw,
| Windows Media Player etc) can prevoke a strange "out of resources"
| problem, where the screen goes weird white & eventually the program
| crashes. This happens in both Win95 & WinME, with all display driver
| revisions. It happens on this Asus A7V133-VM, & I think it happened
| on my last motherboard too. It does not happen in Linux, only
| Windows, and does not affect other video cards in this system. I got
| this video card straight as it first came out - were early ones
| faulty? It'd like to have a solution to this problem rather than
| being forced to use the onboard video which can't be set faster than
| 75Hz because of moronic Windows.

Hi 'path',
I use a few G400 cards - two single-heads and a few dual-heads & have never
seen this problem.
Given that it is okay in Linux then I think you can rule out a hardware
problem with the card and would suggest that it is one of three things:
1) Bad windoze driver - are you using an 'early' driver ? I'd suggest you
download the latest certified driver from the Matrox site.
2) Meagre system resources - if your system has only a small amount of
memory then it is very cheap to upgrade. I tend to use two or three pieces
of 256 Mb in all my systems (depending on no of m/board memory slots) which
some might consider overkill but so what. Editing large graphics files can
really eat up memory. Also check your virtual memory (paging file) is
sensibly managed.
3) Something else on your system might be using up resources - maybe some
bad software has a 'memory leak'. Try stopping things you can live without
from running and see if the situation improves.
Post back with some info on your system and the apps you are running if the
above does not help.
Kevin.