Member Avatar for iamtheone188

Hello,
I'm running on Windows XP SP2 and have been getting BSODs quite frequently lately.
The problem seems to occur randomly, sometimes even right after i get into windows, but I've noticed that it seems to occur the most when I'm running more than one type of program at once.
Here are the two errors:
The first one doesn't have any description but has the following:
0x000000F4 (0x00000003, 0x87071020, 0x87071194, 0x805D11F8)

The second one has KERNEL_STACK_INPAGE_ERROR written:
0x00000077 (0xC0000185, 0xC0000185, 0x00000000, 0x025A4000)

I've tried using system restore however, it does not resolve the problem.
I've run Spybot and AVG antivirus but both turned up with nothing.
I've run hard drive diagnostics and memtest for RAM with nothing.
The only reason I can come up with is that I recently installed a PCI network adapter in the computer and BSODs started getting more frequent after that.
I will reformat in a few days but I am afraid that the issue is not software related but hardware related.
Any help on this matter would be greatly appreciated
Thank you.

P.S. I remember running a registry cleaner maybe 4 to 5 months ago but I doubt that would be of any importance.

TechExpress Link:

  • 2 Contributors
  • 2 Replies
  • 103 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by zandiago

Dani AI

Generated

— the STOP types you named point more to the storage/driver/kernel layer than to a routine registry cleaner problem. CRITICAL_OBJECT_TERMINATION is raised when a critical system process unexpectedly ends; KERNEL_STACK_INPAGE_ERROR means the kernel could not page needed data from disk (commonly an I/O device/controller issue). Microsoft’s debugger notes for those checks are useful background: CRITICAL_OBJECT_TERMINATION and KERNEL_STACK_INPAGE_ERROR. As suggested, hardware faults can cause BSODs, but these particular stops tend to narrow the fault toward the storage stack or a bad kernel driver.

Prioritized checklist to run before reformatting:

  • Physically isolate the recent change: remove the PCI network adapter and run Windows for a while. If stability returns, test the card in another slot and reinstall only the vendor-supplied XP driver.
  • Check cabling and ports: reseat/swap the drive data and power cables and try a different controller port. Loose or failing cables often cause in‑page errors.
  • Run chkdsk /r at boot and the HDD maker’s extended diagnostics to rule out remnant sector/controller problems (software checks can miss intermittent hardware faults).
  • Inspect the System log in Event Viewer (eventvwr.msc) for disk/NTFS/atapi errors that match BSOD timestamps — those entries usually show the first I/O failure.
  • Collect minidumps and analyze with a tool like BlueScreenView or WinDbg. If a driver looks suspicious, use Driver Verifier (with recovery media ready) to force and identify faulty drivers: Driver Verifier.
  • If crashes persist with the NIC removed and cables swapped, test with a known-good drive or boot a Linux live USB. Repro under another OS strongly indicates PSU/motherboard or controller hardware.

Back up important data before any destructive steps. Reformatting will not fix failing hardware; follow the checklist in order to avoid unnecessary reinstalls.

Recommended Answers

All 2 Replies

Member Avatar for zandiago

The blue screen has to mainly do with hard-ware conflicts....in more severe cases, i think it can also it's a case of a faulty mother board. Additionally, the blue screen can be caused by; faulty memory, a corrupt Registry, or incompatible DLLs. There are softwares out there that can be used to diagnose the prob mentioned above it it's the registry.
Regards.

Member Avatar for zandiago

The blue screen has to mainly do with hard-ware conflicts....in more severe cases, i think it can also it's a case of a faulty mother board. Additionally, the blue screen can be caused by; faulty memory, a corrupt Registry, or incompatible DLLs. There are softwares out there that can be used to diagnose the prob mentioned above it it's the registry.
Regards.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.