# Please help me diagnose this Windows XP problem.

**URL:** <https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612>\
**Category:** Factual Questions\
**Created:** [December 4, 2008, 2:07am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612 "2008-12-04T02:07:39Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\
**Post date:** [December 4, 2008, 2:07am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/1 "2008-12-04T02:07:39Z")

</div>

For the last few weeks, I’ve gotten occasional “Windows Delayed Write Failed” error messages on my data drive, and at the same time the system would slow down significantly. It would seem as if it was locked up, but if you moved the mouse and waited about 30 seconds, the cursor would move a little, then freeze, and do the same thing about 30 seconds later. When I hard booted, everything was usually back to normal with no problems. Then it would happen again a few days later.

I assumed the hard drive was about to fail, even though no errors turned up on a CHKDSK, and Belarc Advisor reported its condition as healthy. So I bought a new drive today, set it up, and started copying data from the old drive to the new one.

But it did the same slow freeze. I tried several times, and it kept doing it. It also happened in Safe Mode.

I figured the old HD was just dying, so I resigned myself to having to do a restore from my last backup. (Yes, I do regular backups. No matter what happens, I will not lose any data.) So I removed the old, presumably failing, drive from the system, and started a restore. A few minutes in, the system got into the same slow freeze.

I had been assuming that a failing hard drive was causing the slowdown, but now it seems that something else is causing it, and the HD may be fine.

Any ideas on what could be causing it, or how best to troubleshoot the problem? I’m reasonably sure it’s not a virus. I have Norton Internet Security, up to date, with regular scans and no reported problems ever. (Please spare me the anti-Norton rants. It’s always worked just fine for me.)

I thought I would first try to let Windows repair itself, but I’d love your ideas and suggestions, especially if it will help me avoid having to completely reinstall Windows, which I just did about six months ago and would prefer not to have to do again.

Thanks.

---

<div class="post-metadata">

**Author:** ![Harmonious\_Discord](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@Harmonious\_Discord](https://boards.straightdope.com/u/Harmonious_Discord)\
**Post date:** [December 4, 2008, 2:12am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/2 "2008-12-04T02:12:29Z")

</div>

Try plugging a different power plug into the drive. The one you have currently on the drive may have intermittent contact problems. You may also have a cable loose at the mother board or hard drive. I’ll leave it at those easy suggestions.

---

<div class="post-metadata">

**Author:** ![Qwisp](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/qwisp/32/397_2.png) [@Qwisp](https://boards.straightdope.com/u/Qwisp)\
**Post date:** [December 4, 2008, 3:46am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/3 "2008-12-04T03:46:02Z")

</div>

Could be something wrong with your RAM

---

<div class="post-metadata">

**Author:** ![rainwalker78](https://avatars.discourse-cdn.com/v4/letter/r/eb9ed0/32.png) [@rainwalker78](https://boards.straightdope.com/u/rainwalker78)\
**Post date:** [December 4, 2008, 5:09am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/4 "2008-12-04T05:09:52Z")

</div>

[8 common causes for ‘delayed write failed’ errors](http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1041334,00.html)

[Microsoft Knowledge Base article](http://support.microsoft.com/kb/330174)

[QUOTE=commasense]  
the system would slow down significantly. It would seem as if it was locked up, but if you moved the mouse and waited about 30 seconds, the cursor would move a little, then freeze, and do the same thing about 30 seconds later. When I hard booted, everything was usually back to normal with no problems. Then it would happen again a few days later.  
[/QUOTE]

The slowdowns sound like memory issues to me. Two issues from the 1st article are memory related.

> [@](#):
>
> # 7. Memory parity issues. If the problem appears after installing new memory, the memory in question may be faulty or not of the correct type for the motherboard in question. (This may go hand-in-hand with other problems such as random lockups, too.)
> 
> # 8. The LargeSystemCache Registry tweak and ATI video adapters. One peculiar set of circumstances that has been observed on multiple machines with ATI video adapters and more than 512MB of memory involves the LargeSystemCache Registry setting, a DWORD entry found in HKEY\_LOCAL\_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management. This setting governs the amount of memory set aside by the system for certain kernel processes. If it’s set to 1 (which allegedly improves performance on systems with more than 512MB of memory), it can cause data corruption on some systems, and produce the “Delayed Write Failed” error. Try resetting it to 0 if it’s been set

If it is neither of those issues, it still sounds memory related to me - at least the slowdown part. Check how much memory your system is using when the slowdown occurs.

---

<div class="post-metadata">

**Author:** ![drachillix](https://avatars.discourse-cdn.com/v4/letter/d/48db29/32.png) [@drachillix](https://boards.straightdope.com/u/drachillix)\
**Post date:** [December 4, 2008, 6:48am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/5 "2008-12-04T06:48:05Z")

</div>

> [@commasense](#):
>
> But it did the same slow freeze. I tried several times, and it kept doing it. It also happened in Safe Mode.

The simple fact that things happen in safe mode make a hardware problem a more likely culprit. I would be very curious to see what tasks are pulling the most CPU time and ram when those slowdowns occur.

How much ram do you have and in what configuration. (ie 2x1GB sticks, 1x256MB, whatever)

---

<div class="post-metadata">

**Author:** ![Quartz](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/quartz/32/267_2.png) [@Quartz](https://boards.straightdope.com/u/Quartz)\
**Post date:** [December 4, 2008, 9:31am UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/6 "2008-12-04T09:31:46Z")

</div>

You mentioned a data drive: do you have a separate OS drive? Have you tried checking that? Can you post the full data from the event viewer entry?

---

<div class="post-metadata">

**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\
**Post date:** [December 4, 2008, 4:07pm UTC](https://boards.straightdope.com/t/please-help-me-diagnose-this-windows-xp-problem/475612/7 "2008-12-04T16:07:36Z")

</div>

Thanks for all the suggestions, and for helping my clarify my thinking. I agree that the problem is (or was) probably in the hardware, not the OS.

After leaving the system off all night, I checked and reseated the connectors for all the drives, and removed and reseated all the memory boards. One of the drive connectors was slightly loose, but that might have happened yesterday when I pulled the cage with the four hard drives out to look at them. (But even if it didn’t cause the original problem, it could have been responsible for the apparent worsening of the situation at that time.)

So everything seems to be up and running okay at the moment, but that’s what has happened every time this problem has shown up in the past. I had previously applied one of the fixes recommended on the Microsoft site: switching off System Cache. But at least now I have a couple more options to try if the problem recurs.

So thanks again, all. I was worried that I would have to spend most of the day today trying to fix this. I’ve got better things to do.

(But I’m also planning to buy a replacement machine in the next few months, too.)
