Announcement

Collapse
No announcement yet.

Why G400 freezes with CS read!

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

  • Why G400 freezes with CS read!

    I mentioned this probably a couple of months back but didn't get an answer so I'll tr again.

    If u are using a Via chipset board (eg KT133 chipset) then u will have freezes when playing 3D games with u're AGP graphics card like the G400.

    The reason for this is that the Driving force value (a timing setting used to communicate with u're card during operation). Intel have excellent support from manufacturers so have been able to include good auto detection of the Driving Force value. Via have not hence the cop out by allowing users to enter their own Driving Force value through the BIOS.

    The catch is this: Graphics card manufacturers very rarely will provide these technical values to end users.

    Do not patronise me with 'update u're drivers.' I have researched this problem non stop for 5 months instead of fork out 100 pounds for a new m/b (I'm not that rich). This question is aimed at the Tech support people. PLEASE PLEASE PLEASE PLEASE compile a list of driving force values either through u're own research of opening up a poll for users of this board to reply to.

    What we need are Driving force values that work for specific Board and Card combo's. Mine being

    Card: Matrox Millenium G400 Dualhead
    Board: Gigabyte GA 7ZX KT133 chipset

    Driving Force: ????

    For more info on this goto: www.viahardware.com and check out their article on the AGP4x timing issues. Also if u're Via chipset board is an early model u may have to use a program to edit the Driving Force values (later boards have this option in the Bios).

    So I have issued the challenge Matrix tech peops. Will u take it up? I doubt it....but I can only hope.

    Sith

    p.s. Do not insult me by telling me to update: bios, via 4 in one driver set, or set my AGP to 1. I have tried it all extensivly.

    Stop misleading other posters to this board by letting them think that re-installing windows and then immediatly installing Via 4-in-1 drivers will stop the system freezes. IT WONT.

  • #2
    What is your main malfunction?

    Most every one of the problems on these boards and Matrox's board is due to improper chipset/videocard driver installation or a combination of the two. I would say nearly 70 percent of the problems are just that. Then about 25 percent are some configuration quirk such as the one you mention.

    Go read the survival guide. Don't come here to tell us that we are guiding people wrong. We are guiding people based on our own hardware experiences, and the chances are that we have the same hardware as these other people.

    Rags

    Comment


    • #3

      <blockquote>
      If u are using a Via chipset board (eg KT133 chipset) then u will have freezes when
      playing 3D games with u're AGP graphics card like the G400.
      </blockquote>

      Nope, not here. Sorry, it must be you. But I won't "insult" you by helping you.



      ------------------
      Epox 8KTA3 w/ Duron 850@7.5*133 with Alpha 6035, 256MB Crucial 7E, G400MAX,SBLive!-MP3,Pioneer 10x DVD, Plextor 12/10/32A, IBM 45GB 75gxp, and a Sony 420GS. Running RH7.0 (2.4.0-final), and Win98 (when I have to).
      Gigabyte P35-DS3L with a Q6600, 2GB Kingston HyperX (after *3* bad pairs of Crucial Ballistix 1066), Galaxy 8800GT 512MB, SB X-Fi, some drives, and a Dell 2005fpw. Running WinXP.

      Comment


      • #4
        As far as I recall the only reason you would change the driving force is when you are trying to O/C ( sorry - that's OverClock ) or force AGP x4 when running FSB ( sorry - Front Side Bus ) above 140 Mhz or so.
        But then again, I have NEVER OverClocked my GFX card nor my CPU so I don't know what I'm talking about.
        And I have never owned a G400 GFX and a VIA MB at the same time and used them without any problems.
        And of course this forum has never helped anyone with any of their problems at all !
        Insult you ... how could I, you already know everything there is to know and then some.

        And BTW some MB's doesn't allow you to change the Driving Force from BIOS, you need to use something like WPCREDIT and WPCRSET to change it on these boards.
        But then again I could be wrong because I don't know anything.

        Most often, updating drivers or re-installing windoze solves 98 pct of all problems so instead of using several months to track down a specific problem why not try the easy way first and save yourself a couple of months and if that does not help then look elsewhere/ask again.

        So don't patronize users for asking questions they don't know the answer to.

        [This message has been edited by Kosh Naranek (edited 27 June 2001).]
        Fear, Makes Wise Men Foolish !
        incentivize transparent paradigms

        Comment


        • #5
          Previous posters: Sorry if I upset you.

          For those of you who are reading this post and agree with me I'll buy a PCI card and manually go through the Driving Force values myself. The reason for the PCI card is because the G400 will not work when certain Driving values are assigned to it. Therefore the PCI card can take over.

          I'll write a support site as I can't find another like it, though many sites I've visited have voiced their support for a list of values for various m/b card combo's for the Via chipset AGP problem.

          The first entry will be my own value for my combination. I'll post the url for readers and u can e-mail me u're combo. Hopefully we can help some people.

          This was clearly the wrong place to come.

          <font face="Verdana, Arial" size="2">users will have to try out different values to see which one works best when in 4x mode in order to prevent 3d crashes.

          Cheers

          ------------------
          Haig
          Matrox Graphics
          Technical Support Manager

          </font>
          Just thought that quote might show how childish the above posters were when replying to my experience in this field.

          Sith

          Comment


          • #6
            It's not your knowledge (or lack there of) but your attitude (or overabundance there of) that gives you a cold reception here. The truth is, there are plenty of people whos personal knowledge would hang you out to dry, but we don't want to do that. Go to an nVidia or ATi forum if that's what you're looking for.

            >This was clearly the wrong place to come.

            It's a great place to come, but a poor choice of place to act holier-than-thou.

            >Just thought that quote might show how childish the above posters were when replying to my experience in this field.

            Are you kidding? We were nice to an ****ole. And I don't give any credit to your supposed "experience".

            Mature, or don't let the door hit you in the ass on your way out.

            Gigabyte P35-DS3L with a Q6600, 2GB Kingston HyperX (after *3* bad pairs of Crucial Ballistix 1066), Galaxy 8800GT 512MB, SB X-Fi, some drives, and a Dell 2005fpw. Running WinXP.

            Comment


            • #7
              And please stop blaming a MB (that's Mother Board) problem on a GFX card (that's short for Graphics) manufacturer.
              "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


              • #8
                <font face="Verdana, Arial" size="2">This was clearly the wrong place to come.</font>
                Sure, this was the wrong place to come here and say:

                "Do not patronise me with 'update u're drivers.'....p.s. Do not insult me by telling me to update: bios, via 4 in one driver set, or set my AGP to 1. I have tried it all extensivly....Stop misleading other posters to this board by letting them think that re-installing windows and then immediatly installing Via 4-in-1 drivers will stop the system freezes. IT WONT. "

                Because you are foolish if you don't ask someone if they have installed their drivers properly first. Here's the order: OS/Drivers/IRQ/Software/BIOS.

                Also you are incorrect by assuming (note the ASS in assume) that this is Matrox's tech support page. We are end users at this forum, so don't come in here with your ****ing attitude. And don't come in here bad mouthing Matrox Tech Support either, because you have NO reason to bash them.

                Rags

                Comment

                Working...
                X