PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Turak <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Wed, 14 Oct 1998 17:10:39 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
I have a new TMC AI5VP using the VIA VPX-B chipset with:
AMD K6/233.
Seagate 4.3gig IDE
Kingston Busmaster PCI KNE40-BT network card
Diamond Stealth 2000 pro video
32 meg edo ram.
Windows 95B.
Kingston does not ship drivers.  Their web page lists
the Win95B cd driver as current.
The latest and greatest Diamond driver is loaded.
The latest and greatest VIA busmaster driver is loaded.
This PC does not have a cdrom, but regardless, I have not
had trouble with the VIA ultra DMA driver on other identical
PC's.

It repeatedly locked up in win95.  I checked CMOS and
someone had adjusted many of the settings.  I set all the
CMOS settings to the ones TMC recommends, this board's
manual is pretty explicit.

Now the system locks up about every 48 hours.  Its on 24 / 7.
When I re-boot, the scandisk standard test insists that
scandisk cannot fix the errors unless a thorough scan is run.
However, a thorough test never finds any errors to report.  If I run
scandisk again it will finish the standard test without asking that
the thorough test be run.
The only software loaded is Microsoft Office 97 and Explorer.
Someone sits at this PC 8 hours a day and he never reports GPF's,
illegal operations, or any other software crashes.  The freezing tends
to happen when the system is idle, like at night or while he is on the
phone, but that is only following the laws of probability, since it's idle
90% of the time.
My diagnosis is to reformat and reload everything, since I can't recall
a hardware issue with such a long interval between failures, but I'm
wondering if anyone can tell me why scandisk is acting strangely
after a crash.
Any suggestions are more than welcome.
Tom Turak

                                  -----
                PCBUILD mailing list -  http://nospin.com
         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]

ATOM RSS1 RSS2