Archived from groups: comp.sys.laptops (More info?)
Having constant BSODs with a few Toughbooks (CF-50a) running XP Sp1.
Pretty well up to date with patches, downloaded the newest drivers
from the vendor. Still BSOD just about every day.
BSODs suggest drivers - but updated and the problems are still
happening.
Archived from groups: comp.sys.laptops (More info?)
RR wrote:
> Having constant BSODs with a few Toughbooks (CF-50a) running XP Sp1.
> Pretty well up to date with patches, downloaded the newest drivers
> from the vendor. Still BSOD just about every day.
>
> BSODs suggest drivers - but updated and the problems are still
> happening.
>
> Anyone have the same problems?
>
> Working ok for anyone else? Any suggestions?
Sounds like memory issues. Download memtest86 and try to leave it
overnight. If it doesnt show any issues, I'd reinstall and go straight
for SP2. If it does, check if your memory is seated correctly, or if you
have more than one chips remove them one at a time to find the one
responsible.
Archived from groups: comp.sys.laptops (More info?)
Thanks. I'll try the memtest. This is happening with the four systems
I have on XP so I'm doubting it is hardware.
Can't go to SP2 as there are about 120 of these systems and haven't
tested SP2 enough to move on it. Later, but not yet.
Stavros Christoforou <stgreek@remove_mehotmail.com> wrote in message news:<b6254$42664b7e$82a1c9eb$4747@news1.tudelft.nl>...
> RR wrote:
> > Having constant BSODs with a few Toughbooks (CF-50a) running XP Sp1.
> > Pretty well up to date with patches, downloaded the newest drivers
> > from the vendor. Still BSOD just about every day.
> >
> > BSODs suggest drivers - but updated and the problems are still
> > happening.
> >
> > Anyone have the same problems?
> >
> > Working ok for anyone else? Any suggestions?
>
> Sounds like memory issues. Download memtest86 and try to leave it
> overnight. If it doesnt show any issues, I'd reinstall and go straight
> for SP2. If it does, check if your memory is seated correctly, or if you
> have more than one chips remove them one at a time to find the one
> responsible.
>
> Stavros
Archived from groups: comp.sys.laptops (More info?)
RR wrote:
> Thanks. I'll try the memtest. This is happening with the four systems
> I have on XP so I'm doubting it is hardware.
Actually, since it IS happening on all four systems, then it most likely
has to do w/the hardware. More specifically, software/driver
incompatibility w/one of the components in that model laptop. I'm
afraid it might be one of the MS patches or vendor drivers you have
installed, and that might take a really friggin long time to find out
which one is causing the problem.
Recently my new laptop was BSODing like crazy after I reinstalled all my
software, and I was lucky to quickly find out it was my RealSecure
firewall program.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.