SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?


To: Dave Hanson who wrote (2521)9/15/1998 4:14:00 PM
From: Spots  Read Replies (1) | Respond to of 14778
 
>> stability problems with NT.

First, I'm not likely to be able to help much, but FWIW ...

Not too surprising you can't get a dump after disk problems,
SCSI or IDE. THe dump goes to the disk, after all. Many
of my instabilities have occurred because of NT disk mapping,
ESPECIALLY when a drive path fails.

I don't have a solution, but that's a possible source of one
problem.

As to SCSI chains, yes, you're right that both ends should
be terminated. I can think of two possibilities (well,
three if you count the fact that you're only guessing about
the termination on the CDROM, but I'd guess like you that
unjumpered is terminated from your description). First,
possibly the card itself is terminated, which, if true,
would put a terminator in the middle of the chain. Lends
a somewhat different meaning to the word "terminator".
Most reasonably current cards are self-terminating,
but that was a pretty cheap card if I recall your price
list. Second, I remember from somewhere deep down in
Anand's page (I think Anand's) that there is some problem
with the ABIT BH6 and Adaptec SCSI cards. Some incompatibility. Unfortunately, many el-cheapo SCSI cards pretend to be
Adaptecs of some stripe or other to get a free ride on
the drivers.

When you say "problem happens whether SCSI drive installed
or not" are you including the adapter or just CD-ROM? That
is, is there a problem if you yank the sucker, by which I mean
the SCSI adapter, out altogether? Not that I see where to
go either way, but it's at least narrowing the scope a bit.

I'm really sorry to hear about your trouble. I wish I had
better suggestions. Hope you get it solved before I build
my next system <g>.

Spots



To: Dave Hanson who wrote (2521)9/15/1998 9:27:00 PM
From: Dan Spangenberg  Read Replies (1) | Respond to of 14778
 
I believe it is your ram. About a week or two ago I had my OC'ed Celeron 266 (oc to 400)on a BX chipset running NT 4.0 real stable. I had 128 meg of ram, the good ones, 100 mhz 10 nanos or less. Everything was rock solid. No BSODs at all. I decided to add a couple more 64 meg ram modules (heck if 128 meg is good then 256 is even better! :~) NT does love ram)
I borrowed a couple of 64 meggers I had laying around, not even thinking if they were 100 mhz. Well it now wasn't as stable. I didn't notice it right off. Sometimes it would BSOD on the blue screen loading the NT kernel, other times it would BSOD randomly while working. I put up with it for a couple of days. The errors were virtually identical to both of yours. I researched it in the knowledge base but nothing seemed to work or make sense. I've done NT for a long time now, it can't be this hard I said. It then dawned on me RAM PROBLEM. I promptly removed it and walla! NT was rock stable again.
I would remove and swap or replace the ram. I would bet that it is the problem. Sure was for me. I am sad now that I only have 128 meg.:~(

On the SCSI, if one device is external and the other is internal, then yes both devices should be terminated. You may or may not also have a software termination setting for the scsi card itself in the scsi BIOS setup. This should be disabled if you are using both busses

Let me know what you find out.
Good Luck
Dan