Announcement

Collapse
No announcement yet.

Weird Abit BH6 Problems (?)

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

  • Weird Abit BH6 Problems (?)

    I just upgraded my work system to a Abit BH6 v1.1 and a P3 450 (128MB ram). All of the other components came from my old system, which was running on an Abit LX6/P2 300. The problem is that both my Creative/Ensoniq sound card and Diamond Fireport 20 SCSI card don't seem to like their new home. The sound card will start spitting out static instead of normal sound. The CD-rom attached to SCSI card (only had a CD-rom attached to it) would keep polling (for lack of a better word) the SCSI card and Windows 2000 kept giving me errors about it. It seemed to happen about once a day on the SCSI card, which I finally ended up pulling out because it was driving me nuts. The sound card has been pretty ok for a couple of weeks, but today it started outputting static again. Rebooting the machine brings it back to normal, but that sucks.

    Like I said, both of these cards were working beautifully in my old machine, so my main suspect is the BH6. The only other thing new to the system is the ATI Rage II AGP video card I was forced to buy. Anyone have any thoughts or suggestions?

    System:
    Windows 2000 RC2
    Abit BH6 v1.1
    PIII 450 Retail
    128MB generic PC100 RAM
    IBM 14.4GB Deskstar HD
    ATI Rage II AGP video (I know, I know, but it's a work machine...)
    Creative/Ensoniq PCI Sound
    Diamond Fireport 20 SCSI card
    Toshiba 40x SCSI CD-Rom
    Internal IDE Zip Drive
    Linksys LNE100TX NIC

    No IRQ's being shared.
    P4 2.53GHz, Intel D845PEBT2, 1GB Ram, G400 Max, Adaptec 19160 running, 2 Maxtor 18GB 10KRPM HD, Toshiba 40/10 SCSI DVD-Rom, Plextor 32/12/10 SCSI CD-RW, Seagate 80GB Barracuda IV, Turtle Beach Santa Cruz, Viewsonic G790 19" Monitor

  • #2
    Very strange.
    Did you reinstall windows after you swapped motherboards?
    Win9x makes it a very unpleasant experience switching mobo's while you have an OS installed, and i'd imagine Win2k only compounds the problem.
    If you haven't, I'd venture that there is some crud leftover from the previous motherboard, and you can only clear it up with a reformat and reinstall.
    Seeing as I haven't worked with Win2000 much yet, this should be a last resort, but if your office has a spare harddrive lying around, you could just swap it out with your current one and do a fresh, minimum install on that and test the theory out. That's what I usually do when i'm not sure if its hardware or software causing the prob.

    ------------------
    P3-450@558mhz@2.1v, ABit BE6, 128megs 7.3125ns PC133 SDRAM, SB Live! Value, G400 32meg Dualhead (@120%), Acer ALN-201 PCI 10bT NIC, 6.5gig Seagate Medalist Pro 7200rpm, 13gig Quantum Fireball CR, Yamaha 4416e Burner, Pioneer 10x DVD-ROM, Panasonic e70 17" Monitor, Antec KS-188 24" Tower, 6 year old Honeywell-SUH 101key Keyboard, Logitech Trackman Marble+

    P3-450@558mhz@2.1v, ABit BE6, 128megs 7.3125ns PC133 SDRAM, SB Live! Value, G400 32meg Dualhead (@120%), Acer ALN-201 PCI 10bT NIC, 6.5gig Seagate Medalist Pro 7200rpm, 13gig Quantum Fireball CR, Yamaha 4416e Burner, Pioneer 10x DVD-ROM, Panasonic e70 17" Monitor, Antec KS-188 24" Tower, 6 year old Honeywell-SUH 101key Keyboard, Logitech Trackman Marble+

    Comment


    • #3
      Yes, it was a fresh install of W2K
      P4 2.53GHz, Intel D845PEBT2, 1GB Ram, G400 Max, Adaptec 19160 running, 2 Maxtor 18GB 10KRPM HD, Toshiba 40/10 SCSI DVD-Rom, Plextor 32/12/10 SCSI CD-RW, Seagate 80GB Barracuda IV, Turtle Beach Santa Cruz, Viewsonic G790 19" Monitor

      Comment

      Working...
      X