Announcement

Collapse
No announcement yet.

Display hell...

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

  • Display hell...

    I have been trying to push the envelope of fsb on my computer (see below in sig). The current hang-up is a completely unintelligible display after a few minutes of running in Win2K (from the IBM ATA66 drive), usually while running IE 5.0 and SETI (background) simultaneously. Another symptom is I am unable to run UT at 992 MHz (124 Mhz fsb). UT gives me a general protection fault during load-up.

    I have just installed the latest BIOS for both MB and HPT366. I am one BIOS revision behind in my MAX.

    The BIOS update to the BE-6 and HPT366 improved my stability, but I'm looking to get past this video hurdle. Any possibilities anyone? I'm going to update the MAX BIOS, but I don't hold much hope for that. Running at AGP 1x has no effect. Also, the processor seems to be running quite cool to the touch.

    ------------------
    800e PIII @ 992 MHz (1.75 V) w/Tennmax P3 TF heatsink, ABIT BE6 (ACPI), 256 MB Mushkin PC133 (Mosel REV2 PC133 222) + G400 MAX, CL SB Live with Sennheiser HD-600 headphones, Sennheiser DSP360 Dolby processor, and Shure FP22 headphone amplifier, IBM Deskstar 13 GB ATA66 HD, Adaptec AHA2940 w/uw SCSI, IBM Ultrastar 9ZX 9.1GB 10K UW SCSI HD, WD Enterprise 4360 4.3GB 7.2k UW SCSI HD, Pioneer 303s SCSI DVD, Plexwriter 8/4/32A, Win2K, in a modified Supermicro SC750A case, and a partridge in a pear tree.

    [This message has been edited by Brian R. (edited 28 June 2000).]

  • #2
    Have you tried bumping the CPU core voltage up to 1.8v ????? I've been running my P3-700 there for several months with no problems at 124MHz FSB.

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

    Comment


    • #3
      Not recently. I used to run it at 1.80 when I first installed it. As soon as it would boot at 1.75, I lowered the voltage. When I ran 1.80 V, it was not stable either (sort of like now). I guess it's worth a try. It runs so well and cool now (except for this periodic lock-up) that I think the processor is not the problem.

      Comment


      • #4
        try switching to udma33 slot instead of udma66 and see if that helps
        jim

        ------------------
        Abit BE6-2 with P3 700(cb0) @ 7*143=1002 using an MC-1000!
        15.3 gb Maxtor ata66 and Twinmos 128mb pc-133 ram
        G400 vanilla 32mb @ 168/210 @ 2x
        Sblive with Altec Lansing speaker combo
        384k DSL and Realtek nic
        Windows 98se with DX7a
        Worn out reset button :O)


        PIII-500mhz @ 620 ! with an Abit BE6 mobo
        128mb pc-100 cas 2
        Mill G400 (vanilla!!!) 32mb @ 167/208 with MGATweak-417mhz, (2.5, 2, 2.5), PD 5.5010 & bios 1.5-22
        Maxtor 14.3 gb Uata66 hdd
        SB Live!
        Winblows 98se & DX7
        and 384k DSL!

        Comment


        • #5
          What changes (other than the cable) do I need to make? Any idea?

          Comment


          • #6
            Check in your bios on the setting for your ide channels, but the motherboard is probably smart enough to see for it self and detect DMA33, BUT you don't need to change cable if you change in your settings in the bios! Just set to mode 2 instead of 4
            But why would you even want to go to DMA33 when you have DMA66, The system speed isn't all about CPU-frequency. Your computer will probably be slower (overall) if you get it stable with DMA33.

            ------------------
            My system:
            • Athlon 700 MHz
            • 192 Mb Ram
            • Asus K7V mb
            • Matrox G400 (oc @ 150/200)
            • wester 10.2Gb and seagate 6.5Gb (removable) hdd
            • Soundcrapster PCI64 (soon Aureal A3d )
            • Logitech Force Feedback wheel (cool)
            • 300W atx case

            My system:
            | Athlon XP2600+ 2,4GHz@200FSB| Water Cooled Processor | Samsung 2x256MB PC3200 Ram (400MHz) | Epox 8RDA mb | Hercules FDX Radeon 8500 LE 128MB | Abit Hot Rod DMA/100 RAID controller | 2*20GB IBM and Western 10.2GB @RAID controller | Soundblaster 5.1 Audigy Player | Actima 6x/32x DVD-ROM, Samsung 12x/8x/32x CDRW | Logitech Force Feedback wheel | Microsoft Sidewinder Force Feedback 2 Joystick | 550W water-cooled Q-TEC PSU | 278/278 kbit DSL internet connection | Windows 2000 Pro | My Homepage
            homemade watercooling in use,Pics on the homepage...

            no more VIA, no more!

            Comment


            • #7
              Try lowering your Memory settings.. I should say raise you memeory timings.. 3-2-2, often times Even good ram won't work well when there is more than one stick... besides it takes a few seconds to test...

              I'm running a 650E@910 without a prob... are you running the PCI bus at 31 or 41?? some mobo's have a choice between the PCI clock divider...


              Craig
              1.3 Taulatin @1600 - Watercooled, DangerDen waterblock, Enhiem 1046 pump, 8x6x2 HeaterCore Radiator - Asus TUSL2C - 256 MB Corsair PC150 - G400 DH 32b SGR - IBM 20Gb 75GXP HDD - InWin A500

              Comment


              • #8
                Some people have found the HPT66 controller to be the weak point in their systems as far as overclocking goes. I need to try the ATA33 controller to see if it offers greater stability at 124 or 133 MHz fsb.

                Anyway, I have found only a little difference in HD speed between ATA33 and ATA66.

                Actually, I'm beginning to think IE 5.0 is the problem. It only crashes while running this program. (Won't start UT). The computer ran all night with SETI at 992 MHz without crashing. Seems to be fine without IE running.

                Stringy - I have tried the various possble memory timing settings and have found no difference. Maybe I should try only one stick of memory...

                My PCI bus is at 41 MHz. I lowered it to 31 MHz without seeing a difference. Still unstable.

                [This message has been edited by Brian R. (edited 29 June 2000).]

                Comment

                Working...