RE: XP locks up, how to troubleshoot?

I would recommend isolating the problem from the OS.
Run several hardware level tests such as memTest X86 for several hours to
verify there is no problem at that level.


"T.S." wrote:

> I am also leaning towards a hardware problem and not a driver problem as you
> stated. My recommendation is to strip the machine down to just the primary
> harddrive, basic memory, video card, keyboard and mouse. Power it back up and
> observe the systems behaivor with just the basic system. If everything runs
> fine and no freeze occurs, try adding additional cards and drives - one at a
> time to see which piece of hardware is giving you the problem.
>
> "Ook" wrote:
>
> > I continue to have lockup issues on XP home. This started after upgrading
> > from Win2000 to XP (no, I did a clean install, I just went from 2000 to XP).
> > I was getting disk errors in the event log, and the mskb said to replace ide
> > cables. I did, and I no longer get disk errors. I removed and reseated all
> > cables, memory, and video card, no change. After 3-4 days, everything just
> > freezes and I have to power cycle. Power supply is new, mobo, cpu, memory is
> > new, hard drives test with no problems. Video is nvidia vanta. nic/sound is
> > on the mobo, drivers are current. Memory is crucial or kingston ( I forget
> > which, but I bought name brand).
> >
> > I'm not convinced it's not a driver causing this, or some component of XP,
> > as I did not have these problems with Win2000. I've removed all
> > non-essential programs. I'm currently running:
> >
> > half-life 1 server
> > apache
> > mysql
> > Bulletproof ftp server.
> >
> > I have run these programs for years on Win2000 with no problems.
> >
> > What have you done that fixed a locking up problem?
> > Have you found Win2000 to be more stable the XP?
> > Is there any way to test drivers/services to ensure they are causing the
> > problem?
> >
> > I'm about to replace mobo/cpu/memory/power supply, as they are the most
> > likely culprits, but I'd like to make sure it's not a driver/XP issue first.
> >
> >
> >
.

Relevant Pages

  • Re: Help me, this sucks...
    ... It COULD be a memory issue, but since Windows manages mememory, it ... It COULD be a hardware issue, ... More likely it is a driver issue. ... Try to uninstall the sound card's ...
    (rec.audio.pro)
  • Re: Writing and reading from a physical address
    ... If you just return the pointer to the memory you got from ... driver to read or write some registers on the hardware. ... How can I do this through a driver. ... run my complete application in kernel mode. ...
    (microsoft.public.windowsce.app.development)
  • Re: Writing and reading from a physical address
    ... MmMapIoSpaceinto my application memory. ... driver to read or write some registers on the hardware. ... How can I do this through a driver. ... run my complete application in kernel mode. ...
    (microsoft.public.windowsce.app.development)
  • Re: BSOD 0x0000007E STOP Error
    ... In your case the 0xC0000005 parameter indicates a memory access violation. ... The 0x7E Stop error means it was in an area of memory owned by a driver. ... The hardware for the driver is bad. ... "Kerry Brown" wrote: ...
    (microsoft.public.windowsxp.general)
  • [opensuse] openSUSE 10.3 not detecting SATA HD
    ... the sata_sis driver. ... I've tried turning off ACPI in bios and acpi=off which ... openSUSE 10.2 and all my hardware is working fine. ... info.product = 'USB Raw Device Access' ...
    (SuSE)
Loading