SATA saga - resolved

  • Thread starter Thread starter Bobby
  • Start date Start date
B

Bobby

I bought a new motherboard and memory yesterday to resolve my on-going SATA
problem with my Asus motherboard.

Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus)
motherboard - and guess what? The fecking thing worked.

So it looks like my problem was dodgy memory. It certainly felt like that -
but I had two memory sticks (512Mb and 256Mb) and I used them independently
and still got BSODs. So it was logical to assume that it wasn't RAM.

But this new RAM module seems to have cured the problem. So it must have
been. But how could flashing a BIOS screw-up *two* DIMMs?

Computers never fail to surprise me.

Thanks to everyone who helped.

I still say that some mobos, SATA and XP don't mix very well.

Bobby
 
Glad to hear you got it resolved.
Curious as to why flashing the BIOS would damage mem chips. I, for one,
resist the temptation to flash the BIOS until I absolutely need some
advanced functionality. If it ain't broke, don't fix it is my motto.
 
I'm pleased you've fixed it too. Interesting that the fault happened only
after you were installing the SATA drive in your machine and not before -
perhaps ESD do you think? You'd think that running the machine in a minimal
configuration while attempting to install windows (as I suggested earlier in
one of the threads) would have surely picked up a dodgy DIMM if you'd tried
them one at a time. The only possible explanation is that whatever happened
affected both DIMMs. Memory modules are extremely sensitive to electrical
damage so it wouldn't take much (e.g. just touching them without using a
properly grounded wrist strap could do it). This is also another reason why
its best to flash motherboards in a minimal configuration too - everything
unnecessary unplugged/removed (including only having one DIMM installed if
the mobo will run like this). Having said that I doubt the actual flashing
process caused this problem - probably something else around the same time.
It would be worth testing out the memory modules in another board before
deciding they're faulty - they may have just developed an "incompatibility"
with that mobo. I've had that happen to me when I installed unapproved (but
correct spec) Micron memory in my Tyan S2460 - eventually I started getting
memory errors which Samsung memory showed no sign of producing yet the
Micron modules tested fine in another board. 3 years on the Samsung modules
are still going perfectly.

Its true that some configurations are less compatible than others but as
you've proven with your replacement memory module, it wasn't the combination
of mobo, SATA and XP that caused your problem. As long as people choose
their components after some research looking at "manufacturer recommended
lists" for compatibility, it shouldn't be a problem.

Paul

So now that you've ascertained it was the memory all along are you
 
I bought a new motherboard and memory yesterday to resolve my on-going SATA
problem with my Asus motherboard.

Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus)
motherboard - and guess what? The fecking thing worked.

So it looks like my problem was dodgy memory. It certainly felt like that -
but I had two memory sticks (512Mb and 256Mb) and I used them independently
and still got BSODs. So it was logical to assume that it wasn't RAM.

But this new RAM module seems to have cured the problem. So it must have
been. But how could flashing a BIOS screw-up *two* DIMMs?

Computers never fail to surprise me.

Thanks to everyone who helped.

I still say that some mobos, SATA and XP don't mix very well.

Bobby
Click to expand...
It could very well be that you inadvertantly damaged the new memory
through ESD. It could also have been that the memory timings set in
the bios were the problem and needed to be adjusted after the BIOS
flash/reset. In either event, if you had ran Memtest86 like we
recommended, you could have found this out without wasting the money
on a new motherboard.

I am glad it is all working for you though. I bypassed SATA driver
load issues by including the SATA controller drivers from various
manufacturers in my XP cd so that they will load without having to use
the floppy
 
I'm pleased you've fixed it too. Interesting that the fault happened only
after you were installing the SATA drive in your machine and not before -
perhaps ESD do you think? You'd think that running the machine in a minimal
configuration while attempting to install windows (as I suggested earlier in
one of the threads) would have surely picked up a dodgy DIMM if you'd tried
them one at a time. The only possible explanation is that whatever happened
affected both DIMMs. Memory modules are extremely sensitive to electrical
damage so it wouldn't take much (e.g. just touching them without using a
properly grounded wrist strap could do it). This is also another reason why
its best to flash motherboards in a minimal configuration too - everything
unnecessary unplugged/removed (including only having one DIMM installed if
the mobo will run like this). Having said that I doubt the actual flashing
process caused this problem - probably something else around the same time.
It would be worth testing out the memory modules in another board before
deciding they're faulty - they may have just developed an "incompatibility"
with that mobo. I've had that happen to me when I installed unapproved (but
correct spec) Micron memory in my Tyan S2460 - eventually I started getting
memory errors which Samsung memory showed no sign of producing yet the
Micron modules tested fine in another board. 3 years on the Samsung modules
are still going perfectly.

Its true that some configurations are less compatible than others but as
you've proven with your replacement memory module, it wasn't the combination
of mobo, SATA and XP that caused your problem. As long as people choose
their components after some research looking at "manufacturer recommended
lists" for compatibility, it shouldn't be a problem.

Paul

So now that you've ascertained it was the memory all along are you
Click to expand...

Memory timings could have easily gotten changed in a BIOS flash and
what worked in one config didn't work in another.
 
NoneOfBusiness said:
It could very well be that you inadvertantly damaged the new memory
through ESD. It could also have been that the memory timings set in
the bios were the problem and needed to be adjusted after the BIOS
flash/reset. In either event, if you had ran Memtest86 like we
recommended, you could have found this out without wasting the money
on a new motherboard.

I am glad it is all working for you though. I bypassed SATA driver
load issues by including the SATA controller drivers from various
manufacturers in my XP cd so that they will load without having to use
the floppy
Click to expand...

I know how to create a slipstreamed SP2 inclusive XP CD but where did you
put the drivers - or was it a case that you still had to point the
installation program to their location on the CD when it asked for the
floppy disk to be inserted into A:?

Paul
 
Believe, I would not now flash the BIOS if I needed a BIOS upgrade to find
next week's lottery numbers.
 
I know how to create a slipstreamed SP2 inclusive XP CD but where did you
put the drivers - or was it a case that you still had to point the
installation program to their location on the CD when it asked for the
floppy disk to be inserted into A:?

Paul
Click to expand...

Take a look at http://unattended.msfn.org/

All sorts of neat stuff here. I did a full unattended install of xp
sp2 with office, av, many little apps, reg tweaks, etc. Of course i
about filled a DVD up in the process but it beats loading software
manually.. The directions for including SATA/RAID drivers are there.
 
NoneOfBusiness said:
Take a look at http://unattended.msfn.org/

All sorts of neat stuff here. I did a full unattended install of xp
sp2 with office, av, many little apps, reg tweaks, etc. Of course i
about filled a DVD up in the process but it beats loading software
manually.. The directions for including SATA/RAID drivers are there.
Click to expand...
Thanks for that link (and Sunny), I've bookmarked it. It sure looks
interesting although allot of work! I suspect it would be easier for me to
just keep using a floppy disk at the required moment and save an image of my
final setup to a restore DVD. If I wanted a master CD (or DVD) that I could
use to perform a "common" install on a wide variety of hardware that'd be
ideal though. It sure would have been helpful to know when I used to work as
a computer tech!

Paul
 
Thanks for that link (and Sunny), I've bookmarked it. It sure looks
interesting although allot of work! I suspect it would be easier for me to
just keep using a floppy disk at the required moment and save an image of my
final setup to a restore DVD. If I wanted a master CD (or DVD) that I could
use to perform a "common" install on a wide variety of hardware that'd be
ideal though. It sure would have been helpful to know when I used to work as
a computer tech!

Paul
Click to expand...
Once you have it built, its worth it, plus you can add all your
updates, patches, whatnot to it for next time so that you don't have
to update your image. I tell you its worth it. I use images too, but
i also keep this updated
 
NoneOfBusiness said:
It could very well be that you inadvertantly damaged the new memory
through ESD. It could also have been that the memory timings set in
the bios were the problem and needed to be adjusted after the BIOS
flash/reset. In either event, if you had ran Memtest86 like we
recommended, you could have found this out without wasting the money
on a new motherboard.

I am glad it is all working for you though. I bypassed SATA driver
load issues by including the SATA controller drivers from various
manufacturers in my XP cd so that they will load without having to use
the floppy
Click to expand...
How did you do that with the drivers?
 
NoneOfBusiness wrote:
<snip and HTML turned off for newsgroup>
How did you do that with the drivers?

See NoneofBusiness's reply to that same question earlier in this thread.

Paul
PS in case your newserver doesn't have that post the link you need is
http://unattended.msfn.org/
 
If you read the OP's posts carefully, you'll realize
all his troubles started with his using the wrong
pair of SATA connections on his mobo. There are 2
sets, somewhat confusingly labeled and it takes
careful reading of the manual to sort this out.
 
If you read the OP's posts carefully, you'll realize
all his troubles started with his using the wrong
pair of SATA connections on his mobo. There are 2
sets, somewhat confusingly labeled and it takes
careful reading of the manual to sort this out.
Click to expand...
true but either of the sets would have worked had he used the correct
drivers and not had memory problems. But then again if he would have
used memtest like we suggested, he would have discovered it much
quicker.
 
Steve Sweet said:
Hi There



You didn't ignore it, you responded to it.
Click to expand...
He's referring to the fact that only plain text should be used for newsgroup
posts - and is even the default for Outlook Express! Bottom posting however
is not OEs default, surely that means that as an OE user you realise the
importance of adopting accepted practices?

Paul
 
He's referring to the fact that only plain text should be used for newsgroup
posts - and is even the default for Outlook Express! Bottom posting however
is not OEs default, surely that means that as an OE user you realise the
importance of adopting accepted practices?

Paul
Click to expand...


Steve's just trying to be anal. Anyone can see that the
HTML itself was what was being referred to as "ignored" not
the header indicating it was HTML that followed as the
message body.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Windows 10 One of my previous builds is experiencing random, multiple BSODs 9
My Autistic son (UK, Wales) needs advice please 6
SATA saga 26
SATA drive seen as removeable device? Help please 3
Missing RAM 7
ASUS Sabertooth z87 unstable 32
Loading WinXP to Sata HHD with Sata DVD/RW dirve all connected to on board MOBO Sata Controllers 13
Maximum memory allowed 5

Back
Top