Announcement

Collapse
No announcement yet.

G400, K7M, gets frozen plaid screen in W98

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

  • G400, K7M, gets frozen plaid screen in W98

    I think I may have found a solution, but most likely have not. LOL. I struggled with the same or similar problem that’s in the posts below. http://forums.murc.ws/ubb/Forum5/HTML/006221.html

    http://forums.murc.ws/ubb/Forum5/HTML/006310.html

    http://www.amdzone.com/ubb/Forum8/HTML/000236.html


    I’ll go over my specs and describe my trouble for reference.
    ASUS K7M rev 1.04
    SuperMicro SC-750A w/ Sparkle 300W PS
    K7-500 (Eclipse mod)
    Alpha P3125 Heatsink
    3 x 64 Mb PC100 (it fits with a little mod)
    Matrox G400 MAX
    KDS VS-195
    Sound Blaster Live Value
    3Com 56K Voice Fax Modem ISA
    Hauppauge WinTV /FM
    Toshiba SD-M1212 DVD-CD
    Maxtor Diamond Max Plus 13.6 G
    Iomega Zip CD 650 CDRW
    Imation LS-120
    Panasonic 1.44 Floppy
    W98 SE
    NT4
    SuSE 6.2

    The drivers 5.41 would load fine and after a reboot would still be OK. But a complete shutdown and warm or cold start, and I would get the “Frozen Plaid Screen” in W98.
    I tried different combinations of loading the drivers and yes (mini port) with D7 or 6.1 with no success.
    I swapped out the G400 for my trusty G200, changed the AGP aperture from 32MB in increments to 256MB. There is no assign IRQ for VGA in this BIOS. I tried each driver 5.25, 5.30, 5.41.
    The case was open as I still had it on the bench, and it has two of the big Radio Shack 4 ¾” 120v 60qf/m blowing through it.
    I even tried letting it sit overnight and firing it up cold in hopes that it may be an overheat problem, nada.
    I scoured this BBS for hints and applied all that were possible (my 425W PS isn’t in yet) and I don’t know how to adjust the MGA Tweak yet, but hoped that it wouldn’t come to that. I love solving problems but was running out of things to try. Finally I thought of swapping out my 5BNC cable for the 15 D-Sub so the DDC Plug n Play could do its thing. It worked!
    So now I wonder if anyone else that is having this problem were using a 5BNC or a non-DDC Monitor Monitor?
    I’m happy I hope this helps someone else.


    PS (the next day) It didn't work, later that night after shutting down for 20mins and re-starting...It Plaid Locked up again. Arg...
    Oh well see my post below, I'm not giving up.







    ------------------
    "If all else fails, read the instructions"




    [This message has been edited by MXR4LIFE (edited 10 December 1999).]
    "If your still stock,... ya' best stay on the porch"

  • #2
    I'v had that problem but only if i up the bus speed. I don't like jumping the bus speed up with my promise fasttrak card so i only used 105Mhz bus, everthing worked fine for the whole night woke up in the morning turn'd on the computer and when windows loaded i was greated by that nice looking screen. and i am using the D-Sub any ideas?

    ------------------
    Did WHAT! WHEN! no you gotta have the wrong guy!
    K7-500 @ 533, Asus K7M Rev. 1.04, 128MB PC-100, G400Max @ (168/210), Diamond MX300, Promise FastTrak, Aopen ITU/2, Quntum KA+ 9.1, Quantum CX6.4, Quntum CX6.4, Acer 40X, Acer CD-RW, Aopen HX-08/425W Turbo-cool PS, 3 4" Sunson case fans

    Comment


    • #3
      Dang it, did you try lowering the VIO
      The only fix besides what I've listed is removing the driver with the utility, switching to VGA and re-install.
      "If your still stock,... ya' best stay on the porch"

      Comment


      • #4
        No i'v never try'd that. but removeing the card from safe mode worked just as well =]
        But i think i'll try getting the my system to play a game befor i start OC bring more problems to the mix.



        ------------------
        Did WHAT! WHEN! no you gotta have the wrong guy!
        K7-500 @ 533, Asus K7M Rev. 1.04, 128MB PC-100, G400Max @ (168/210), Diamond MX300, Promise FastTrak, Aopen ITU/2, Quntum KA+ 9.1, Quantum CX6.4, Quntum CX6.4, Acer 40X, Acer CD-RW, Aopen HX-08/425W Turbo-cool PS, 3 4" Sunson case fans

        Comment


        • #5
          Well, the DDC activation by dumping the BNC5 didn't help Sorry, I jumped the gun a little

          Anyway I got my PC Power&Cooling Turbo-Cool 425W in this morning...Yippy

          And it fired up with a good screen after sitting all night, and replacing the PS. God I pray this fixes it. But I doubt it.
          Seems to me that it's a problem with the A) MB BIOS B)Matrox drivers or card. Like the Video Card memory or MB BIOS gets cleared after sitting long enough loosing the settings? I don't know, just guessing. I will do some more testing, cuz this setup ROCKS...YEA BABY! If anyone knows or has any ideas please comment. Thanks This Forum has saved my sanity more than once

          ------------------
          "If all else fails, read the instructions"
          "If your still stock,... ya' best stay on the porch"

          Comment


          • #6
            Well, had some strange probs with my Athlon and G200 too...

            Seem like there is hard to get the Miniport AGP driver to work with the matrox drivers.

            When I installed my matrox drivers, I got a garbled screen when shuting down and turning on. I too had installed miniport driver. I found out that the drivers forced my G200 to 1x AGP, and strangly enough, when I forced it to 2x AGP, my machine booted normally.

            My current problem however is 3D games freeze my system, with need for reboot.

            Geez, these are troubled times...

            Comment


            • #7
              Well i hope that power supply help fix the problem cuz i sould be getting the same one on monday. As for the plaid screen i hadn't seen it till i overclocked my system after i turn'd it back to the defult clock everthing was fine. but last night i forced AGP*1 to see if i could play games without being dumped back to the desktop. wich it seam'd to fix. But when i turn'd on my system this morning i had the lovly screen again. I didn't have much time to play with it to see if AGP*1 was the problem but i'm sure it was as i havn't changed anything else. maybe i'll try forcing AGP*1 and see what happens.

              Comment


              • #8
                Well i hope that power supply help fix the problem cuz i sould be getting the same one on monday. As for the plaid screen i hadn't seen it till i overclocked my system after i turn'd it back to the defult clock everthing was fine. but last night i forced AGP*1 to see if i could play games without being dumped back to the desktop. wich it seam'd to fix. But when i turn'd on my system this morning i had the lovly screen again. I didn't have much time to play with it to see if AGP*1 was the problem but i'm sure it was as i havn't changed anything else. maybe i'll try forcing AGP*1 and see what happens.

                Comment


                • #9
                  So far the new PS has worked, but that's what I thought about DDC.LOL Time will tell...

                  5:24PM 12/10/99 Shut it down, and let it sit for 3 hours. Fired right up to the desktop, will play some Q3 and UT for fun. No problems in 3D yet, and 3D Mark 2K is like WoW

                  [This message has been edited by MXR4LIFE (edited 10 December 1999).]
                  "If your still stock,... ya' best stay on the porch"

                  Comment


                  • #10
                    It is starting to look like the Powersupply fixed this gremlin.

                    I've shut it down for a few hours, hot, warm and cold booted it all day, and no fsck'd screens
                    I even gave the Eclipse Mod a workout
                    Ran this K7 500
                    at:

                    700
                    1.7v
                    1/2 cache
                    ___________
                    750
                    1.75v
                    1/2 cache
                    ____________
                    800
                    1.75v
                    1/2 cache

                    And from a cold boot each time, no problems
                    Yahoo
                    "If your still stock,... ya' best stay on the porch"

                    Comment


                    • #11
                      Well that good to here i hope my PS get's here soon.

                      ------------------
                      Did WHAT! WHEN! no you gotta have the wrong guy!
                      K7-500 @ 533, Asus K7M Rev. 1.04, 128MB PC-100, G400Max @ (168/210), Diamond MX300, Promise FastTrak, Aopen ITU/2, Quntum KA+ 9.1, Quantum CX6.4, Quntum CX6.4, Acer 40X, Acer CD-RW, Aopen HX-08/425W Turbo-cool PS, 3 4" Sunson case fans

                      Comment


                      • #12
                        Still working great. Before I put in this new PS, it would get the "locked, Scottish plaid looking screen" at W98 desktop by the first or second cold start. Now it's been 24hrs and looking good.

                        For those that are confused by my definition "locked plaid screen", let me apologize for my poor literary skills. What I'm trying to describe is a pattern on the screen that looks simular to the scottish paid, vertical and horizontal multi colored lines that is locked with no response from the computer. The colors or patterns will vary depending on what resolution and color depth you had your desktop set at. Some will look almost white with a little color plaiding, others are very rich whith sharp dark stripes. A reset or three finger salute is the only way to bail, and when W98 desktop is due during the reboot, this situation returns and repeats forever. The only fix that I know of is; removal of Matrox drivers with the utility, replace with VGA driver, reboot (wich will look ok but not what we paid for ). Finally re-install the Matrox drivers. This will work and be ok if you just do Hot-reboots or resets while running. If the computer is shutdown, the first or second start will summon this demon.

                        I will be surprised if it turns out to be the powersupply. Because I would get it with just the CPU, RAM, keyboard and either the G400 or G200 card in using the 5.xx drivers.

                        But I'm sure that there will be another fix somewhere, the BIOS upgrade got rid of the poor coldstarting problem for me and others. ?

                        Any comments and suggestion are allways welcome.

                        ------------------
                        "If all else fails, read the instructions"


                        [This message has been edited by MXR4LIFE (edited 11 December 1999).]
                        "If your still stock,... ya' best stay on the porch"

                        Comment


                        • #13
                          Yep MXR4LIFE, it's very unlikely that it was your powersupply. I have a 500 MHz with and K7M and a 300 W powersupply (which should be more than enough), and I had the exact same plaid problem with the 5.41 drivers......

                          I changed to the "old" 5.30 drivers and it has been working perfectly ever since

                          That's all

                          Torben R.

                          G400 news, info, downloads and mailinglist : http://TRsDomain.homepage.dk

                          Comment


                          • #14
                            OK, this is still very preliminary testing, but I am also experiencing the cold bootup plaid death. The good news is that I found a workaround for 3 consecutive cold boots!

                            I turned on the Force AGP 2X registry setting and it fixed it. (as noted before, still very preliminary)

                            ASUS K7M rev 1.04
                            Enlight 7237 w/ VEXTREC 300W PS
                            K7-700
                            AAVID big honkin' dual fan heatsink
                            Matrox G400 dual head (not MAX)
                            2 * 128MB Corsair (Micron) PC133
                            Sound Blaster Live Value (liveware 3.0)
                            W. Digital 18GB 7200RPM HD
                            Hitachi GD2500 DVD
                            Iomega Zip 250
                            Teac 3.5" 1.44MB
                            Win98 (OEM, but not SE)

                            Using DirectX 7 and PD 5.41.

                            Let's just say that I'm not too happy of a camper over this problem. I usually keep my system on 24/7 because I run www.distributed.net client. However, yesterday my local braintrust of a power company glitched the power at my house while I was at work. When I came back, I turned it on and got the plaid death. I was due for a reinstall of W98, so I did the dirty deed. Then I read this thread. I was spooked. I did a shutdown. I waited 5 minutes, powered up, and plaid death. Booted to safe mode, Matrox uninstaller, reboot, std VGA, reboot, PD 5.41, reboot and I'm back to normal.

                            I shutdown again, but this time I wait only long enough for the fans & hard disk to spin down. Booted, and plaid death. (Ditto of above sequence.) Shutdown again, booted, and plaid death. Now I'm getting really pissed. I run PCIlist, and I notice that I am only running in AGP 1X. Now I'm even more pissed. It can't even work right in AGP 1X mode. Flames shoot out of my ears. So I have the bright idea of seeing what it does when I force AGP 2X mode.

                            Both PCIlist and registry hacks are available from the MURC downloads. Thank goodness! I installed the ForceAGP2X.reg, reboot, and it is running OK in AGP 2X mode. I shutdown. Power on, it boots, and NO PLAID DEATH! I repeat shutdown & boot 2 more times, only waiting long enough for the fans to spin down. It still works.

                            However, I have not yet done any 3D gaming to see how stable it is in AGP 2X mode. I'm about to start some Unreal Tournament to see what it can handle.

                            Maybe this helps. I am very interested in getting to the bottom of this issue.

                            Comment


                            • #15
                              Thanks for adding comments guys, hopefully there will be an official fix for this bug soon.
                              "If your still stock,... ya' best stay on the porch"

                              Comment

                              Working...
                              X