Announcement

Collapse
No announcement yet.

Mystique G200 produces Screen-Errors

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Up
    God damn the server ate my username

    Comment


    • #17
      Allright now,
      I´m happy now. I did exactly what M Ragsdale mentioned: deleted the Matrox drivers, reinstalled the new Via 4 in 1 driver, updated the G200 bios (used the unified bios) and reinstalled the latest G200 drivers. I also changed AGP Aperture in mobo-bios to 128 (got 128MB RAM).
      Thank You, thank You, thank You...
      That really helped me at the moment.
      When I switch to 16bit colors it´s not better, but at 24bit I have no problems so far.

      regards
      MaS

      ------------------
      -------------------------
      Y2K is soon, don´t trust your Comp.

      Comment


      • #18
        You don't really want to use 24 bit though... What's 32bit like?

        Also, does it start off OK, but progressivley get worse over a couple of hours of normal 2d use?

        ------------------
        Cheers,
        Steve

        My PC houses one of these things which seems to affect some people's lives far too much...

        Comment


        • #19
          Here it's problems in all resolutions now...
          And usually when I start up my PC first in the morning/afternoon. I have to let it sit idle for 30 minutes, then reboot and sometimes reboot one other time to clear the problems. Could it be that my mobo/G200 needs a certain operating temperature??

          If so, why haven't I had these problems with other drivers as well??

          I'm at a loss, and getting very annoyed to having to reboot/refresh every time.

          Jorden.

          P.S: I'm back at 85Hz V, have reinstalled DX6.0 enduser and DX6.1, and that seemed to help for one day.
          Jordâ„¢

          Comment


          • #20
            OK, just to see what you're getting, can any of you post screen shots?

            Here's a few examples of what I see:

            <A HREF="http://gtech.matroxusers.com/bad.jpg" target="_blank">screwed up IE</A>

            <A HREF="http://gtech.matroxusers.com/bad2.jpg" target="_blank">dodgy properties</A>

            <A HREF="http://gtech.matroxusers.com/setibad.jpg" target="_blank">screwed up SETI</A>

            <A HREF="http://gtech.matroxusers.com/outlook.jpg" target="_blank">screwed up Outlook</A>

            All these completely out of the blue.
            Are your errors anything similar?

            ------------------
            Cheers,
            Steve

            My PC houses one of these things which seems to affect some people's lives far too much...

            Comment


            • #21
              Hi Steve

              I had similar problems some time ago, and when I remember correctly I had the volume control open too. Sometimes I had a locked MSGSRV32.EXE. I think this was related to the volume control too.

              Now it works just fine , but dunno why

              Helmchen

              Comment


              • #22
                yes - the volume control does get screwed all the time too.... weird!

                ------------------
                Cheers,
                Steve

                My PC houses one of these things which seems to affect some people's lives far too much...

                Comment


                • #23
                  I've been having similar problems. In one instance, I scrolled the window in IE and a ghost image of the screen scrolled, but I could see the original right thru.

                  My heatsink was burning hot to the touch also. I've since rigged a fan to blow on the G200 until I can get an old 486 fan & sink or even a Lasange to replace the stock heatsink.

                  No problems since then. I immediately ran 3D Mark in a loop for about an hour with no probs either.

                  I am using 5.13. Don't remember if I've updated my sig yet.


                  ------------------
                  K6-2 350@400,FIC-503+ 1.1a,Mill G200 AGP 16 meg SDRAM, bios 2.3, driver 4.51 (or 4.33c),64 meg RAM


                  K6-III 400 @ 5x100, FIC VA-503+ rev 1.1a, Mill G200 16 meg SDRAM, 3 rowdy children, 5 hrs of sleep last night.

                  Comment


                  • #24
                    I've been having similar problems. In one instance, I scrolled the window in IE and a ghost image of the screen scrolled, but I could see the original right thru.

                    My heatsink was burning hot to the touch also. I've since rigged a fan to blow on the G200 until I can get an old 486 fan & sink or even a Lasange to replace the stock heatsink.

                    No problems since then. I immediately ran 3D Mark in a loop for about an hour with no probs either.

                    I am using 5.13. Don't remember if I've updated my sig yet.


                    ------------------
                    K6-2 350@400,FIC-503+ 1.1a,Mill G200 AGP 16 meg SDRAM, bios 2.3, driver 4.51 (or 4.33c),64 meg RAM


                    K6-III 400 @ 5x100, FIC VA-503+ rev 1.1a, Mill G200 16 meg SDRAM, 3 rowdy children, 5 hrs of sleep last night.

                    Comment


                    • #25
                      I've been having similar problems. In one instance, I scrolled the window in IE and a ghost image of the screen scrolled, but I could see the original right thru.

                      My heatsink was burning hot to the touch also. I've since rigged a fan to blow on the G200 until I can get an old 486 fan & sink or even a Lasange to replace the stock heatsink.

                      No problems since then. I immediately ran 3D Mark in a loop for about an hour with no probs either.

                      I am using 5.13. Don't remember if I've updated my sig yet.


                      ------------------
                      K6-2 350@400,FIC-503+ 1.1a,Mill G200 AGP 16 meg SDRAM, bios 2.3, driver 4.51 (or 4.33c),64 meg RAM


                      K6-III 400 @ 5x100, FIC VA-503+ rev 1.1a, Mill G200 16 meg SDRAM, 3 rowdy children, 5 hrs of sleep last night.

                      Comment


                      • #26
                        I still haven't been able to get the PD 5.13 drivers to work on my 503+ and from the posts it seems many BX boards are also having problems. The 4.51 drivers are working, but I still get random spontaneous changing back to 16 colors.

                        The most likely explanation is that the 5.13's are just not ready for prime time yet. Did the Beta Boys all have G400's when they tested them or did they also try G200's?

                        Other possible explanations:
                        1) the VIA 4-in-1 drivers are really a step backward.
                        2) Windows 98 Second Edition is screwing things up badly
                        3) The newest FIC 503 bios 1536 is not helping either.

                        However 1) and 3) don't explain the BX board problems, so I'm guessing its either the 5.13's or Win98SE.

                        Jorden, do the old 4.51's still work? If so, I guess we will just have to wait for the 5.2x's to be released. Also, are you using Win98 old version or SE?
                        AMD K6III-450; Epox EP-MVP3G5; G400DH32; Maxtor 10gig UDMA66; 128meg PC100; Aureal SQ2500 sound; PCI Modem Blaster; Linksys 10/100 NIC; Mag 800V 19"; AL ACS54 4 speaker sound; Logitech wireless mouse; Logitech Wingman Extreme (great for lefties)

                        Comment


                        • #27
                          I still haven't been able to get the PD 5.13 drivers to work on my 503+ and from the posts it seems many BX boards are also having problems. The 4.51 drivers are working, but I still get random spontaneous changing back to 16 colors.

                          The most likely explanation is that the 5.13's are just not ready for prime time yet. Did the Beta Boys all have G400's when they tested them or did they also try G200's?

                          Other possible explanations:
                          1) the VIA 4-in-1 drivers are really a step backward.
                          2) Windows 98 Second Edition is screwing things up badly
                          3) The newest FIC 503 bios 1536 is not helping either.

                          However 1) and 3) don't explain the BX board problems, so I'm guessing its either the 5.13's or Win98SE.

                          Jorden, do the old 4.51's still work? If so, I guess we will just have to wait for the 5.2x's to be released. Also, are you using Win98 old version or SE?
                          AMD K6III-450; Epox EP-MVP3G5; G400DH32; Maxtor 10gig UDMA66; 128meg PC100; Aureal SQ2500 sound; PCI Modem Blaster; Linksys 10/100 NIC; Mag 800V 19"; AL ACS54 4 speaker sound; Logitech wireless mouse; Logitech Wingman Extreme (great for lefties)

                          Comment


                          • #28
                            RAB - I hope that wasn't a dig at us, and just a question? I can only say for myself, but I did have the G400 in my machine, but I for one, also has a PC with a G200 in too (infact two, if you count my work PC). Also, there are internal testing procedures too which the drivers go through on whatever hardware the drivers will run on.

                            But, you could be right with the heating thing - I've assumed here that the compaq I use has adequate cooling. But it can take, like today, 3 hours of constant use (all 2d stuff) before any problems show up. Maybe the 5.xx drivers push the chip a little harder? Who knows?

                            ------------------
                            Cheers,
                            Steve

                            My PC houses one of these things which seems to affect some people's lives far too much...

                            Comment


                            • #29
                              RAB: I haven't tried... With the old 4.51 I cannot play SiN in OGL mode, so I am not going back either.

                              BTW: In SiN I also have texture problems, and some of the expelled bullet-cartridges hang suspended in the air (still spinning), then gradually one by one they disappear...

                              Could this be a bug in SiN or is it due to the drivers as well??

                              Temperature MoBo: 32C
                              Temperature CPU G200: touchable.

                              No heat problems here!!

                              Jorden
                              Jordâ„¢

                              Comment


                              • #30
                                Steve, it was just a question. I really appreciate all the time and effort you put into the forum and into testing for very little pay. Giving you a G400 is the far less than you deserve for all your help. I still suspect Win98SE is a problem. Did you have it when you tested?

                                ------------------
                                FIC503+1.2a,bios115je36;AMD K6-2/350;128MB PC100;Myst G200,bios2.3,drivers4.51;Win98SE;YamahaS-YXG50 sound;no OC

                                AMD K6III-450; Epox EP-MVP3G5; G400DH32; Maxtor 10gig UDMA66; 128meg PC100; Aureal SQ2500 sound; PCI Modem Blaster; Linksys 10/100 NIC; Mag 800V 19"; AL ACS54 4 speaker sound; Logitech wireless mouse; Logitech Wingman Extreme (great for lefties)

                                Comment

                                Working...
                                X