"Y: not accessible due to inpage error" -- Why is this happening?

Today, this starting happening. This morning it was working fine. This
drive is a brand new partition on a new Western Digital 640 GB USB 2.0
drive. The partition is my backups drive and it would help if I could
get it working again.

I am running Windows XP Pro SP3. The change appears to have happened
while I was running a backup to the drive. About then, Windows BSODed
for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive, Windows
has been reporting that it had to replace registry files with backups.
I don't know if that is related or not; just that it has been happening
since the drive was installed.

The partition was created with my GParted LiveCD. I used it because
all other partitioners I could have used were giving up during the
format. That was due to the old partition getting corrupted due to
events outside Windows.

Since I created the partition, I have place on it a 30 GB file that is a
backup of my boot partition. That took all day to write out there and I
don't want to lose it.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related.
Could be - if the new drive came with a virus/trojan/something. Could be
just coincidence and your machine was dying all along. Could be that's why
you got the drive - to backup befor complete death of the machine. Unsure -
you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted
LiveCD. I used it because all other partitioners I could have used were
giving up during the format. That was due to the old partition getting
corrupted due to events outside Windows." -- you want to explain that?
Sounds like you could have dmaged the *new* drive.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related.
Could be - if the new drive came with a virus/trojan/something. Could be
just coincidence and your machine was dying all along. Could be that's why
you got the drive - to backup befor complete death of the machine. Unsure -
you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted
LiveCD. I used it because all other partitioners I could have used were
giving up during the format. That was due to the old partition getting
corrupted due to events outside Windows." -- you want to explain that?
Sounds like you could have dmaged the *new* drive.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Well, we got the external drive due to problems on my Dad's computer. I
had an older one that was working, but he needed more disk space. We
found the WD for $69 with free shipping and no tax. So I decided to use
it and put the other external on Dad's computer.

As for why I do backups to an external drive; well, my system was built
in 2003, so I am concerned. But the reason why I started doing backups
to an hard drive was I could gobble up even Blue-Ray disks -- and I
don't have a Blue-Ray drive and just 250 GB on the internal drive.

I do need backups as the internal drive is relatively new and I have had
to send it back to Seagate several times already. Each time usually at
least means reinstalling Windows. (Hence, I started backing up the boot
partition.)

I don't know much about the BSODs. All where hardware related. At
least one was Page Fault in Non-paged Area. I would update my drivers,
but most are considered legacy now and rarely updated. (Notably my ATI
9700.)

What corrupted the old Backups partition was G4L. I don't know all the
options and accidentally told it to copy the boot partition on top of
the backup partition rather than as a file. (The new image is a file,
not a partition. I got that down.) At the time, I was getting grief
from an old version of G4L that appears to have had a bit overflow on
the amount of disk space available at the destination.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related.
Could be - if the new drive came with a virus/trojan/something. Could be
just coincidence and your machine was dying all along. Could be that's why
you got the drive - to backup befor complete death of the machine. Unsure -
you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted
LiveCD. I used it because all other partitioners I could have used were
giving up during the format. That was due to the old partition getting
corrupted due to events outside Windows." -- you want to explain that?
Sounds like you could have dmaged the *new* drive.

Well, we got the external drive due to problems on my Dad's computer. I
had an older one that was working, but he needed more disk space. We
found the WD for $69 with free shipping and no tax. So I decided to use
it and put the other external on Dad's computer.

As for why I do backups to an external drive; well, my system was built
in 2003, so I am concerned. But the reason why I started doing backups
to an hard drive was I could gobble up even Blue-Ray disks -- and I
don't have a Blue-Ray drive and just 250 GB on the internal drive.

I do need backups as the internal drive is relatively new and I have had
to send it back to Seagate several times already. Each time usually at
least means reinstalling Windows. (Hence, I started backing up the boot
partition.)

I don't know much about the BSODs. All where hardware related. At
least one was Page Fault in Non-paged Area. I would update my drivers,
but most are considered legacy now and rarely updated. (Notably my ATI
9700.)

What corrupted the old Backups partition was G4L. I don't know all the
options and accidentally told it to copy the boot partition on top of
the backup partition rather than as a file. (The new image is a file,
not a partition. I got that down.) At the time, I was getting grief
from an old version of G4L that appears to have had a bit overflow on
the amount of disk space available at the destination.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related.
Could be - if the new drive came with a virus/trojan/something. Could be
just coincidence and your machine was dying all along. Could be that's why
you got the drive - to backup befor complete death of the machine. Unsure -
you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted
LiveCD. I used it because all other partitioners I could have used were
giving up during the format. That was due to the old partition getting
corrupted due to events outside Windows." -- you want to explain that?
Sounds like you could have dmaged the *new* drive.

I also think it is unlikely that I got a virus or trojan via the
external drive. I deleted the original partition (FAT32!!!!) and Norton
360 is up to date.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related.
Could be - if the new drive came with a virus/trojan/something. Could be
just coincidence and your machine was dying all along. Could be that's why
you got the drive - to backup befor complete death of the machine. Unsure -
you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted
LiveCD. I used it because all other partitioners I could have used were
giving up during the format. That was due to the old partition getting
corrupted due to events outside Windows." -- you want to explain that?
Sounds like you could have dmaged the *new* drive.

I also think it is unlikely that I got a virus or trojan via the
external drive. I deleted the original partition (FAT32!!!!) and Norton
360 is up to date.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related.
Could be - if the new drive came with a virus/trojan/something. Could be
just coincidence and your machine was dying all along. Could be that's why
you got the drive - to backup befor complete death of the machine. Unsure -
you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted
LiveCD. I used it because all other partitioners I could have used were
giving up during the format. That was due to the old partition getting
corrupted due to events outside Windows." -- you want to explain that?
Sounds like you could have dmaged the *new* drive.

See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!) and
Norton 360 is up to date.

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the drive -
to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!) and
Norton 360 is up to date.

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.

Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the drive -
to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

WD's tool errored out while testing the external. HD Tools isn't done
yet, but it is showing back sectors.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Bill Blanton wrote:
See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!) and
Norton 360 is up to date.

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the drive -
to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

WD's tool errored out while testing the external. HD Tools isn't done
yet, but it is showing back sectors.
------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Bill Blanton wrote:
See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!) and
Norton 360 is up to date.

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the drive -
to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD said, what
registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

I assume you mean that you are running HDTools on your internal
system drive?

You need to confirm the memory before relying on anything software.
If memory is corrupt you may get unreliable results from the disk
scanning tools.

MemTest86 and DocMemory are two software testers that you might
have a look at. As an alternative, if you have more than one module
installed, you could do a remove/swap/remove/swap physical test of
the modules.



"Will Pittenger" wrote in message ...
WD's tool errored out while testing the external. HD Tools isn't done yet, but it is showing back sectors.

Bill Blanton wrote:
See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!)
and Norton 360 is up to date.

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the
drive - to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD
said, what registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

I assume you mean that you are running HDTools on your internal
system drive?

You need to confirm the memory before relying on anything software.
If memory is corrupt you may get unreliable results from the disk
scanning tools.

MemTest86 and DocMemory are two software testers that you might
have a look at. As an alternative, if you have more than one module
installed, you could do a remove/swap/remove/swap physical test of
the modules.



"Will Pittenger" wrote in message ...
WD's tool errored out while testing the external. HD Tools isn't done yet, but it is showing back sectors.

Bill Blanton wrote:
See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!)
and Norton 360 is up to date.

Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the
drive - to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD
said, what registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

Well, I ran RAM Probe, but had to burn a CD. Windows won't acknowlege
anything in my floppy drive (a LS-120 attached via PATA). Strangely
enough, I can boot from the drive. (I just tried it.) As for RAM
Probe's results, I am not sure what it did. After a minute or two of
scanning, it would hang and no longer respond to input. Below is a link
to a screen shot.

http://img38.imageshack.us/my.php?im...ts20090521.jpg


Since my earlier posts with attachments appear to have been rejected by
the server, I am reposting those for reference, this time from Image Shack.

http://img33.imageshack.us/my.php?im...fo20090520.png
http://img132.imageshack.us/my.php?i...th20090520.png
http://img195.imageshack.us/my.php?i...an20090520.png
http://img40.imageshack.us/my.php?im...rk20090520.png
http://img132.imageshack.us/my.php?i...eerrorscan.png
http://img207.imageshack.us/my.php?i...ebenchmark.png
http://img291.imageshack.us/my.php?i...250620aqy6.png

------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Bill Blanton wrote:
I assume you mean that you are running HDTools on your internal
system drive?

You need to confirm the memory before relying on anything software.
If memory is corrupt you may get unreliable results from the disk
scanning tools.

MemTest86 and DocMemory are two software testers that you might
have a look at. As an alternative, if you have more than one module
installed, you could do a remove/swap/remove/swap physical test of
the modules.



"Will Pittenger" wrote in message ...
WD's tool errored out while testing the external. HD Tools isn't done yet, but it is showing back sectors.

Bill Blanton wrote:
See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!)
and Norton 360 is up to date.
Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the
drive - to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD
said, what registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.

Well, I ran RAM Probe, but had to burn a CD. Windows won't acknowlege
anything in my floppy drive (a LS-120 attached via PATA). Strangely
enough, I can boot from the drive. (I just tried it.) As for RAM
Probe's results, I am not sure what it did. After a minute or two of
scanning, it would hang and no longer respond to input. Below is a link
to a screen shot.

http://img38.imageshack.us/my.php?im...ts20090521.jpg


Since my earlier posts with attachments appear to have been rejected by
the server, I am reposting those for reference, this time from Image Shack.

http://img33.imageshack.us/my.php?im...fo20090520.png
http://img132.imageshack.us/my.php?i...th20090520.png
http://img195.imageshack.us/my.php?i...an20090520.png
http://img40.imageshack.us/my.php?im...rk20090520.png
http://img132.imageshack.us/my.php?i...eerrorscan.png
http://img207.imageshack.us/my.php?i...ebenchmark.png
http://img291.imageshack.us/my.php?i...250620aqy6.png

------
Will Pittenger
[will 68 at mtco dot com]
[will dot pittenger 1 at gmail dot com]

Bill Blanton wrote:
I assume you mean that you are running HDTools on your internal
system drive?

You need to confirm the memory before relying on anything software.
If memory is corrupt you may get unreliable results from the disk
scanning tools.

MemTest86 and DocMemory are two software testers that you might
have a look at. As an alternative, if you have more than one module
installed, you could do a remove/swap/remove/swap physical test of
the modules.



"Will Pittenger" wrote in message ...
WD's tool errored out while testing the external. HD Tools isn't done yet, but it is showing back sectors.

Bill Blanton wrote:
See
Common Cause of "Error Performing Inpage Operation" Explained
http://support.microsoft.com/kb/141117

Given the BSODs, the registry corruption, the failure of tools to complete
a format of the drive, (and the above error),, you might want to do a
thorough memory diagnostic. It might also be a good idea to check
the drive that contains the paging file, using the drive manufacturer's
software.




"Will Pittenger" wrote in message ...
I also think it is unlikely that I got a virus or trojan via the external drive. I deleted the original partition (FAT32!!!!)
and Norton 360 is up to date.
Shenan Stanley wrote:
Will Pittenger wrote:
Today, this starting happening. This morning it was working fine.
This drive is a brand new partition on a new Western Digital 640 GB
USB 2.0 drive. The partition is my backups drive and it would help
if I could get it working again.

I am running Windows XP Pro SP3. The change appears to have
happened while I was running a backup to the drive. About then,
Windows BSODed for possibly unrelated reasons.

I should also noted that since I first hooked up the new drive,
Windows has been reporting that it had to replace registry files
with backups. I don't know if that is related or not; just that it
has been happening since the drive was installed.

The partition was created with my GParted LiveCD. I used it
because all other partitioners I could have used were giving up
during the format. That was due to the old partition getting
corrupted due to events outside Windows.

Since I created the partition, I have place on it a 30 GB file that
is a backup of my boot partition. That took all day to write out
there and I don't want to lose it.
Two things - no idea if the BSOD/registry settings requests is related. Could be - if the new drive came with a
virus/trojan/something. Could be just coincidence and your machine was dying all along. Could be that's why you got the
drive - to backup befor complete death of the machine. Unsure - you left out some vital information there (like what the BSOD
said, what registry settings were trying to be replaced, etc.)

In any case - since you said "The partition was created with my GParted LiveCD. I used it because all other partitioners I
could have used were giving up during the format. That was due to the old partition getting corrupted due to events outside
Windows." -- you want to explain that? Sounds like you could have dmaged the *new* drive.