B
Brian
Thank you Sharon for the information on the blue screen of
death. Out of the many responses to my situation, yours is
valuable.
I'm running Windows XP, and my hard drive was using a 40-
pin cable, so I switched it to a 80-pin. I thought that
the difference bewteen the two was that the 80-pin sends
data faster and had little to do with my problem.
* How do I check to see if my hard drive is UDMA, and
why could a 40-pin cable cause the problems I have?
I still want to keep my hard drive at 3GB for the
operating system. Since that leaves me with about 11GB to
play with on the other partition, I'll move the swapfile
there.
In new to this whole swapfile thing, and I need some
things clarified, please.
1. What is a swapfile and what does it do?
2. Where is it located?
3. How do I move it to the other partition (if I can't cut
and paste)?
4. How do I "divide it up between partitions?"
Thank you so much for your help.
Subject: Re: HELP! two blue screens of death!
From: "Sharon F" <[email protected]> Sent:
10/15/2003 12:34:01 PM
In my opinion, 3GB is cutting it short for an XP
partition. Although the
operating system folder, even on a mature system, will
only weigh in at
about 2GB that doesn't leave a lot of elbow room. For
example, add
your swapfile in and you're done. There's nothing left if
a few more MB
of virtual memory are suddenly needed. Slam the operating
system and
programs up against a wall repeatedly and the resulting
and recurring
errors could eventually cause file damage and, if forced
shutdowns are
involved, possibly hardware damage.
Have you considered moving the swapfile to a partition
with more room? Or
dividing it up between the partitions? While it's
advisable to move the
swapfile to another drive (if you're going to move it at
all), other partitions
would be acceptable if the operating system partition
remains at 3 GB.
The first stop error (c0000218) is related to a corrupt
registry. The
second stop error is an input/output error usually related
to the disk
drive.
If the hard drive is UDMA, are you using an 80 wire cable?
If it is and
you're using 40 wire, that could be part of the problem.
There is an update from February 10, 2002 that helps on
some systems
getting the Stop 0x000000ED message. Details about the
problem and the
update can be found here:
Stop 0x000000ED Error Message When Volume on IDE Drive
with Caching Enabled Is Mounted
http://support.microsoft.com/?kbid=315403
If you need and use the 80 wire cable, apply the update,
rearrange your
swapfile a bit and still continue to have problems, it may
be time to
increase the size of the Windows partition and/or get a
larger hard drive.
There's always a possibility that the drive is starting to
show its age but
you could run diagnostics on it to confirm or rule this
out. These tools
are available at most hard drive manufacturer's websites.
While problematic RAM can cause repeated registry
corruption, it may not be
a factor in your case considering the other details you've
given us.
Safe Mode is a useful troubleshooting environment if the
errors are due to
a recent change in the system. Use it to disable software
or drivers that
were just installed. Or use it to test in general since
safe mode load only
minimal drivers and no startup applications. In your case,
I agree with you
that it wouldn't be very helpful.
death. Out of the many responses to my situation, yours is
valuable.
I'm running Windows XP, and my hard drive was using a 40-
pin cable, so I switched it to a 80-pin. I thought that
the difference bewteen the two was that the 80-pin sends
data faster and had little to do with my problem.
* How do I check to see if my hard drive is UDMA, and
why could a 40-pin cable cause the problems I have?
I still want to keep my hard drive at 3GB for the
operating system. Since that leaves me with about 11GB to
play with on the other partition, I'll move the swapfile
there.
In new to this whole swapfile thing, and I need some
things clarified, please.
1. What is a swapfile and what does it do?
2. Where is it located?
3. How do I move it to the other partition (if I can't cut
and paste)?
4. How do I "divide it up between partitions?"
Thank you so much for your help.
Subject: Re: HELP! two blue screens of death!
From: "Sharon F" <[email protected]> Sent:
10/15/2003 12:34:01 PM
In my opinion, 3GB is cutting it short for an XP
partition. Although the
operating system folder, even on a mature system, will
only weigh in at
about 2GB that doesn't leave a lot of elbow room. For
example, add
your swapfile in and you're done. There's nothing left if
a few more MB
of virtual memory are suddenly needed. Slam the operating
system and
programs up against a wall repeatedly and the resulting
and recurring
errors could eventually cause file damage and, if forced
shutdowns are
involved, possibly hardware damage.
Have you considered moving the swapfile to a partition
with more room? Or
dividing it up between the partitions? While it's
advisable to move the
swapfile to another drive (if you're going to move it at
all), other partitions
would be acceptable if the operating system partition
remains at 3 GB.
The first stop error (c0000218) is related to a corrupt
registry. The
second stop error is an input/output error usually related
to the disk
drive.
If the hard drive is UDMA, are you using an 80 wire cable?
If it is and
you're using 40 wire, that could be part of the problem.
There is an update from February 10, 2002 that helps on
some systems
getting the Stop 0x000000ED message. Details about the
problem and the
update can be found here:
Stop 0x000000ED Error Message When Volume on IDE Drive
with Caching Enabled Is Mounted
http://support.microsoft.com/?kbid=315403
If you need and use the 80 wire cable, apply the update,
rearrange your
swapfile a bit and still continue to have problems, it may
be time to
increase the size of the Windows partition and/or get a
larger hard drive.
There's always a possibility that the drive is starting to
show its age but
you could run diagnostics on it to confirm or rule this
out. These tools
are available at most hard drive manufacturer's websites.
While problematic RAM can cause repeated registry
corruption, it may not be
a factor in your case considering the other details you've
given us.
Safe Mode is a useful troubleshooting environment if the
errors are due to
a recent change in the system. Use it to disable software
or drivers that
were just installed. Or use it to test in general since
safe mode load only
minimal drivers and no startup applications. In your case,
I agree with you
that it wouldn't be very helpful.