Announcement

Collapse
No announcement yet.

Crashes -- Is this a G400 problem?

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

  • Crashes -- Is this a G400 problem?

    I'm making this post to both the MATROXUSERS group and the AMDZONE group in hopes that someone has an answer.

    I have a 700Mhz Athlon overclocked to 1Ghz by SDTom (a reputable overclocker from the AMDZONE group) installed in a K7V motherboard, using a Matrox G400 Max video card. The G400 Max does have a serial number that indicates that it was tested for AGP 4X. To the best of my knowledge, all of the recent drivers, BIOS flashes, etc have been done.

    The case is an INWIN case with a 300W power supply. For cooling, the processor has an Alpha heatsink, and the case is open with external fans blowing across the heatsink. The G400 has no additional cooling other than a little bit of circulation from the external fans blowing on the main processor.

    The problem is that the system is unstable. By dropping the bus speed of the K7V to 95Mhz, I get a reasonably stable system, only occasionally crashing during game play. At 100 Mhz, the system usually freezes somewhere between the time when the screen first turns light blue, and when windows asks for my password. This freeze is typically just a total halt, but occsaionally, I get "plaid" marks across the screen, indicating a possible video card problem.

    Other random bits of information: This problem occurs no matter what the voltage of the processor is set at, all the way up to 2.05V (the max setting for the K7V). I'm not using the dual-head features of the MAX. I've re-greased the Alpha heatsink for the Athlon.

    It may be possible that there are problems with both the procesor AND the video card-- I haven't ruled that out yet. In fact, I haven't been able to rule ANYTHING out because I have no idea what methods I can use to determine where the problem lies.

    So my although my question is basically "What do I do next?" the important part of the question is: "How do I determine where my failure is?" Any help is appreciated, and I can give any information anyone needs to help solve the problems.

  • #2
    What is your L2 set for? Run the cpu at 1.9Vcccore, this is the sweet spot. What are your ICQ's (post complete list).
    "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


    • #3
      Also, what speed is your agp running at?
      jim

      ------------------
      P3-700e @ 1052! Check it here!
      Abit BE6-2
      TwinMos 128mb pc-133
      G400 32mb DH
      Maxtor 15.3gb 7,200rpm
      SB Live!
      Winblows 98se & DX7
      and 384k DSL!
      System 1:
      AMD 1.4 AYJHA-Y factory unlocked @ 1656 with Thermalright SK6 and 7k Delta fan
      Epox 8K7A
      2x256mb Micron pc-2100 DDR
      an AGP port all warmed up and ready to be stuffed full of Parhelia II+
      SBLIVE 5.1
      Maxtor 40g 7,200 @ ATA-100
      IBM 40GB 7,200 @ ATA-100
      Pinnacle DV Plus firewire
      3Com Hardware Modem
      Teac 20/10/40 burner
      Antec 350w power supply in a Colorcase 303usb Stainless

      New system: Under development

      Comment


      • #4
        Greebe,
        A list of ICQs? Don't people usualy have just 1?
        He means IRQs of course.
        chuck

        PS unless you realy do mean ICQs.
        Chuck
        秋音的爸爸

        Comment


        • #5
          To answer everyone:

          * I assume I'm running at AGP 4x, since both the motherboard and video card support it. (I assume win98 SE supports it as well)

          * The L2 cache is also set to whatever the default is. I assume it is on.

          Both of the above I'd check in more detail if someone could tell me where to find the information.

          IRQ List (reported by win98 SE):

          00 System Timer
          01 Keyboard
          02 PIC
          03 COM2
          04 COM1
          05 D-Link DFE-530TX Ethernet Adapter
          05 IRQ Holding
          06 Floppy Disk
          07 Printer Port
          08 Clock
          09 SCI IRQ used by API bus
          10 VIA PCI Audio
          11 Matrox G400 Max
          11 IRQ Holder
          12 PS/2 mouse port
          13 Numeric Data Processor
          14 VIA Bus Master
          14 Primary IDE
          15 VIA Bus Master
          15 Secondary IDE

          Comment


          • #6
            This sounds somewhat similar to the "plaid death" that many of us got with an Asus K7M mobo + G400. The work around for that rig was to use the registry hack to force agp2x. (Do PD6 registry hacks exist yet?)

            My other hunch is that perhaps that CPU is being overclocked just a bit more than it can handle with stability.

            FYI, Plaid death = on cold bootups, it would almost finish loading win98, but then freeze completely locking up your system with an interesting plaid pattern on the screen. You would either have to use the agp2x registry hack, or you had to uninstall the G400 drivers, install standard vga drivers, then reinstall G400 drivers and never power off your system again. Plaid death had nothing to do with crashes during 3d gaming.

            I have not heard of anybody with an Asus K7V mobo having the plaid death, though.

            (I am so glad that I have gotten rid of that K7M mobo. It caused me sooo many headaches, especially with the beta bios of the week for 4 months before Asus finally released an official bios update! Now I'm on an Abit KT7, and it is absolutely perfect! I am one extremely happy camper with the KT7.)

            Comment


            • #7
              Oops! LOL (I was tired, so cut me some slack!
              "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
                Someone else had an Athlon going silly when they overclocked it and this was down to the cache divider. I think setting it at 2/5 solved the problem for them. Of course Sdtom should have done this and checked the pc properly before shipping it.
                Chief Lemon Buyer no more Linux sucks but not as much
                Weather nut and sad git.

                My Weather Page

                Comment


                • #9
                  When you have stability problems, you should always run everything in specs before even trying to find a solution. If you assume your Athlon 700@1000 is fine, most probably that's the cause of problem.

                  KJ Liew

                  Comment

                  Working...
                  X