Announcement

Collapse
No announcement yet.

Problem with DX8 build140 and 3dmark2000 rev 1.1 on Win2k. Im stumped

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

  • Problem with DX8 build140 and 3dmark2000 rev 1.1 on Win2k. Im stumped

    Ok fellows gurus...oops did I refer to myself as a guru? damn too late I here the Matrox Gods rumbling at me. I am having a problem after installing the 140 build of dx8 and it seems that I cannot find anyone else experiencing similar. After I installed the dx8 beta 140 everything seemed fine. All my games worked, 2d for some reason was much faster than before (something I read about a flaw in in win2k directdraw calls is supposedly fixed by dx8) but then I tried to run 3dmark2000 rev 1.1 which had been working fine before the install of dx8. After a few seconds of running the helicopter demo (each run varied a little bit) i suddenly had memory core dump and the computer rebooted. I have tried switching drivers, switching resolutions, reinstalling 3dmark2000 rev 1.1, reinstalling the dx8 beta but the memory core dumps continued until dx8 was removed (gotta love the fact that MS put that niffy uninstaller in there for us beta testers LOL) so any ideas?

    ------------------
    Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends
    Celeron II 566@ 952 on a Abit BE6 Rev 1, 128 Pc100, Matrox G450 32 DH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends

  • #2
    so any ideas?"
    Yea...stop screwing with MS beta crap
    Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s

    Comment


    • #3
      hehe thx I hadn't thought of that one DOH! imjust wondering why im the only one who seems to have this particular problem. Its not like im the only one trying the dx8 beta.

      ------------------
      Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends
      Celeron II 566@ 952 on a Abit BE6 Rev 1, 128 Pc100, Matrox G450 32 DH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends

      Comment


      • #4
        I installed 3dmark2000 on one of my oc'd celery machines similar to yours just to test that theory, but it works fine at all resolutions. Must be your config.. or too much overclocking.
        I can bet anything that somewhere in DX8 code there is a function called "D3D_Luck". Now if only we could tweak that..

        ------------------
        P60-120Thz, 256Tb ram, 27.5Pb 225000 RPM HD, 142" .001 dot pitch monitor @ 30720x23040x64, Matrox G24000 w/512Gb, SB UltraLive2, DX120 beta, Win2124 SP4. Hey -- beta testers have their advantages...
        P60-120Thz, 256Tb ram, 27.5Pb 225000 RPM HD, 142" .001 dot pitch monitor @ 30720x23040x64, Matrox G24000 w/512Gb, SB UltraLive2, DX120 beta, Win2112 SP4. Hey -- beta testers have their advantages...

        Comment


        • #5
          Storm, shouldn't that be Win2112? LOL
          "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


          • #6
            well i dont see how its the overclocking because if it was then games etc would be affected as well but their not, just 3dmark2000 rev 1.1. Well I just got beta 145 build today I will try it out as well

            ------------------
            Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends
            Celeron II 566@ 952 on a Abit BE6 Rev 1, 128 Pc100, Matrox G450 32 DH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends

            Comment


            • #7
              I learned my lesson not to play with dx betas awhile back....LOL

              Paul
              "Never interfere with the enemy when he is in the process of destroying himself"

              Comment


              • #8
                I meant that as a joke, I have no clue what the problem could be. It's most likely a hardware conflict, given that you get a core dump and a system reset. Maybe DX8 doesn't like something about your system. With M$ products.. it's hard to tell. Good luck
                Greebe - Haha, it will now


                ------------------
                P60-120Thz, 256Tb ram, 27.5Pb 225000 RPM HD, 142" .001 dot pitch monitor @ 30720x23040x64, Matrox G24000 w/512Gb, SB UltraLive2, DX120 beta, Win2112 SP4. Hey -- beta testers have their advantages...
                P60-120Thz, 256Tb ram, 27.5Pb 225000 RPM HD, 142" .001 dot pitch monitor @ 30720x23040x64, Matrox G24000 w/512Gb, SB UltraLive2, DX120 beta, Win2112 SP4. Hey -- beta testers have their advantages...

                Comment


                • #9
                  Overclocking can effect one program it depends on how much the cpu is stressed. But in this case blame the beta
                  Chief Lemon Buyer no more Linux sucks but not as much
                  Weather nut and sad git.

                  My Weather Page

                  Comment


                  • #10
                    I fixed the problem by installing the new 146 build of DX8. all problems are gone

                    ------------------
                    Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends
                    Celeron II 566@ 952 on a Abit BE6 Rev 1, 128 Pc100, Matrox G450 32 DH, SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other odds and ends

                    Comment

                    Working...
                    X