chkdsk /p errors detected repeatedly

Hello,

I recently built a new machine and I'm having errors that seem odd. WinXP
Pro SP2 disk. Install to new SATA2 HD. Immediately upgrade to SP3. Install
Recovery Console. Boot to Recovery Console. Run chkdsk /p. It finds errors.
Then run chkdsk /r. It takes an hour or two. Run chkdsk /p again. No errors.
Boot to WinXP. Immediately reboot to Recovery Console. Run chkdsk /p again
and find errors. There are no codes at this point, just standard chkdsk
"Found errors" dialog.

Looks like a hardware failure, but... I'm on a second motherboard, third HD,
second set of RAM (second set is from a working pull) and now second CPU.
I've run the MS RAM checker on all the RAM (approximately 12 hours per
stick). It checks out fine. Hard Drive diagnostics check out fine. The
cleanest install uses Microsoft video drivers. The only thing constant is the
errors.

Original new computer:
ASUS 5Pk Mobo (BIOS flashed to latest)
Intel Q9450 CPU
2 x 2 gig Crucial RAM (I've tried them together and seperately)
Western Digital SATA2 250 gig HD
2 x Matrox G450 PCI video cards
Power Supply Antec 650

Lots of BSOD with a range of codes. This is on a clean install with nothing
going on. BIOS was flashed to handle the new chip.

Computer now:
New ASUS P5K (BIOS flashed to latest)
Intel E6400
2 x 1 gig Kingston RAM
Different model Western Digital SATA2 250 gig
2 x Matrox G450 PCI video cards
Power Supply Antec 650
This setup is stable (3 days so far), but still getting chkdsk errors.

This setup does not generate BSODs. Both setups generate chkdsk errors. So,
I'm starting to think chkdsk is always going to find some errors. If that's
the case, fine, I'll live with it. Or, do I have more problem solving ahead?

I think the first computer problem was the CPU. It wouldn't stay running
with any configuration. But, the constant errors under both setups is curious.

Ideas? (sorry to be so long winded)

Thanks,
Mark

HD manufacturers diagnostics?
www.memtest.org memory test?
Maybe problomatic psu

"tstew" wrote in message
...
Hello,

I recently built a new machine and I'm having errors that seem odd. WinXP
Pro SP2 disk. Install to new SATA2 HD. Immediately upgrade to SP3. Install
Recovery Console. Boot to Recovery Console. Run chkdsk /p. It finds
errors.
Then run chkdsk /r. It takes an hour or two. Run chkdsk /p again. No
errors.
Boot to WinXP. Immediately reboot to Recovery Console. Run chkdsk /p again
and find errors. There are no codes at this point, just standard chkdsk
"Found errors" dialog.

Looks like a hardware failure, but... I'm on a second motherboard, third
HD,
second set of RAM (second set is from a working pull) and now second CPU.
I've run the MS RAM checker on all the RAM (approximately 12 hours per
stick). It checks out fine. Hard Drive diagnostics check out fine. The
cleanest install uses Microsoft video drivers. The only thing constant is
the
errors.

Original new computer:
ASUS 5Pk Mobo (BIOS flashed to latest)
Intel Q9450 CPU
2 x 2 gig Crucial RAM (I've tried them together and seperately)
Western Digital SATA2 250 gig HD
2 x Matrox G450 PCI video cards
Power Supply Antec 650

Lots of BSOD with a range of codes. This is on a clean install with
nothing
going on. BIOS was flashed to handle the new chip.

Computer now:
New ASUS P5K (BIOS flashed to latest)
Intel E6400
2 x 1 gig Kingston RAM
Different model Western Digital SATA2 250 gig
2 x Matrox G450 PCI video cards
Power Supply Antec 650
This setup is stable (3 days so far), but still getting chkdsk errors.

This setup does not generate BSODs. Both setups generate chkdsk errors.
So,
I'm starting to think chkdsk is always going to find some errors. If
that's
the case, fine, I'll live with it. Or, do I have more problem solving
ahead?

I think the first computer problem was the CPU. It wouldn't stay running
with any configuration. But, the constant errors under both setups is
curious.

Ideas? (sorry to be so long winded)

Thanks,
Mark

Hi DL,

Yes, HD manufacturers diagnostics.

I tried Memtest86, but can't get machine to boot to an ISO file. Just beyond
my knowledge. Ideas? I didn't see the DOS files before. I'll try that.

PSU? You think? Looking at PC Wizard 2008, the 3.3v is putting out 3.23, 5V
is 4.94 and 12V is 11.40. I love Antec PSUs and have never had a problem with
them. But, then again, who knows at this point. It does seem strange that
dual core is stable (but still chkdsk errors) and quad core was a disaster.

What should I look for?

Thanks,
Mark

"DL" wrote:

HD manufacturers diagnostics?
www.memtest.org memory test?
Maybe problomatic psu

"tstew" wrote in message
...
Hello,

I recently built a new machine and I'm having errors that seem odd. WinXP
Pro SP2 disk. Install to new SATA2 HD. Immediately upgrade to SP3. Install
Recovery Console. Boot to Recovery Console. Run chkdsk /p. It finds
errors.
Then run chkdsk /r. It takes an hour or two. Run chkdsk /p again. No
errors.
Boot to WinXP. Immediately reboot to Recovery Console. Run chkdsk /p again
and find errors. There are no codes at this point, just standard chkdsk
"Found errors" dialog.

Looks like a hardware failure, but... I'm on a second motherboard, third
HD,
second set of RAM (second set is from a working pull) and now second CPU.
I've run the MS RAM checker on all the RAM (approximately 12 hours per
stick). It checks out fine. Hard Drive diagnostics check out fine. The
cleanest install uses Microsoft video drivers. The only thing constant is
the
errors.

Original new computer:
ASUS 5Pk Mobo (BIOS flashed to latest)
Intel Q9450 CPU
2 x 2 gig Crucial RAM (I've tried them together and seperately)
Western Digital SATA2 250 gig HD
2 x Matrox G450 PCI video cards
Power Supply Antec 650

Lots of BSOD with a range of codes. This is on a clean install with
nothing
going on. BIOS was flashed to handle the new chip.

Computer now:
New ASUS P5K (BIOS flashed to latest)
Intel E6400
2 x 1 gig Kingston RAM
Different model Western Digital SATA2 250 gig
2 x Matrox G450 PCI video cards
Power Supply Antec 650
This setup is stable (3 days so far), but still getting chkdsk errors.

This setup does not generate BSODs. Both setups generate chkdsk errors.
So,
I'm starting to think chkdsk is always going to find some errors. If
that's
the case, fine, I'll live with it. Or, do I have more problem solving
ahead?

I think the first computer problem was the CPU. It wouldn't stay running
with any configuration. But, the constant errors under both setups is
curious.

Ideas? (sorry to be so long winded)

Thanks,
Mark

Hello,

I recently built a new machine and I'm having errors that seem odd.
WinXP
Pro SP2 disk. Install to new SATA2 HD. Immediately upgrade to SP3.
Install Recovery Console. Boot to Recovery Console. Run chkdsk /p. It
finds errors. Then run chkdsk /r. It takes an hour or two. Run chkdsk
/p again. No errors. Boot to WinXP. Immediately reboot to Recovery
Console. Run chkdsk /p again and find errors. There are no codes at
this point, just standard chkdsk "Found errors" dialog.

Looks like a hardware failure, but... I'm on a second motherboard,
third HD, second set of RAM (second set is from a working pull) and
now second CPU. I've run the MS RAM checker on all the RAM
(approximately 12 hours per stick). It checks out fine. Hard Drive
diagnostics check out fine. The cleanest install uses Microsoft video
drivers. The only thing constant is the errors.

Original new computer:
ASUS 5Pk Mobo (BIOS flashed to latest)
Intel Q9450 CPU
2 x 2 gig Crucial RAM (I've tried them together and seperately)
Western Digital SATA2 250 gig HD
2 x Matrox G450 PCI video cards
Power Supply Antec 650

Lots of BSOD with a range of codes. This is on a clean install with
nothing going on. BIOS was flashed to handle the new chip.

Computer now:
New ASUS P5K (BIOS flashed to latest)
Intel E6400
2 x 1 gig Kingston RAM
Different model Western Digital SATA2 250 gig
2 x Matrox G450 PCI video cards
Power Supply Antec 650
This setup is stable (3 days so far), but still getting chkdsk errors.

This setup does not generate BSODs. Both setups generate chkdsk
errors. So, I'm starting to think chkdsk is always going to find some
errors. If that's the case, fine, I'll live with it. Or, do I have
more problem solving ahead?

I think the first computer problem was the CPU. It wouldn't stay
running
with any configuration. But, the constant errors under both setups is
curious.

Ideas? (sorry to be so long winded)

Thanks,
Mark

Chkdsk /p?? What's that? It's not listed under chkdsk /? listing.
Perhaps that's part of the problem?G

I think the first thing you should do is uninstall SP3, or do another
rebuild and use SP2 instead, whichever is most reliable for you. SP3
has caused some strange, verified and unverified but consistantly
reported problems. On a new sys, I'd start with SP2 and forget SP3
until later after it's all been qualified.

Have you been watching Event Viewer? Clear the logs and start fresh so
you have a known starting point and aren't confused by previous errors.
Build a new set, sort of.

Got a firewall running? You shouldn't, at this point, but if so there
might be some surprise entries in it.

Since you've been running chkdsk /r, switch to chkdsk /f for the rest of
the time; makes it run faster. The /r also checks unused space, which
you've already tested and gain nothing by repeatedly testing unused
space for bad sectors. Just worry about what actually contains data.

BIOS: Was it actually necessary to update it to the latest? Are you
CERTAIN the latest is a good rev for YOUR machine? It may not be.

Based on your description:
IMO you've created too many possibilities for errors to happen all at
once and that's really tough to track things down in. It can become a
real mess.

I think you need to go back to the beginning, start over by tossing
in the XP CD, booting from it, deleting recreating the partition, JUST
ONE, and install XP. Do not install ANYTHING else! Get everything
working. THEN start to update, add SP3, whatever. But do not go any
further until you are error free, including your event Viewer logs.

The XP CD *IS* a *retail* version, right? If it's an OEM, it MIGHT
*not* be capable of handling the hardware you have. Yes, some
manufacturers do butcher the OS that badly and will support only the one
set of hardware the machine was sold on when it's an OEM operating
system.

I'd be interested in hearing back how you make out if you follow any of
this advice. I suspect that if you don't, you'll be a long, long time
getting anywhere. You've got to knock it down into smaller blocks to
work on.

HTH

Twayne

Hi Twayne,

Thanks for the response.

All the stuff I put in this post was (is) actually over two months of
fighting to get this thing right. I did do the various steps you mentioned
sequentially. Painstakingly!

I am running a retail disk.

I did have to flash the bios to utilize the Intel Q9450 chip. My confidence
in this ver is fairly low. The chip is so new that it could easily be a
sloppy revision just to get it out for this chip. However, ASUS tech support
L2 says they are not getting the kinds of errors I'm getting from other
similar setups.

I am not running a software firewall. Only running a hardware firewall.
Actually (FYI) I love my router. It's a dual WAN 1 gig Netgear. Solid as a
rock. Yea. Not cheap, though.

The chkdsk /p and /r switches are utilized in the Recovery Console, as far
as I can tell. I agree, I didn't see them with the chkdsk /? command. MS
support got me on that track.

I do keep up with the Event Viewer, since I've been spending stupid amounts
of time hunting down the errors. Thx.

I like the idea of just using SP2. I wanted the speed enhancements of SP3,
but at this point, having a working computer would be enhancement enough.
BTW, the older slower chip has been stable for 4 days now. (that is how long
it's been since I pulled the new chip out, so hope is running high). That's
two more than the newer chip, so I'm calling Intel tomorrow for an RMA and
I'll try a new chip.

Thanks,
Mark



Chkdsk /p?? What's that? It's not listed under chkdsk /? listing.
Perhaps that's part of the problem?G

I think the first thing you should do is uninstall SP3, or do another
rebuild and use SP2 instead, whichever is most reliable for you. SP3
has caused some strange, verified and unverified but consistantly
reported problems. On a new sys, I'd start with SP2 and forget SP3
until later after it's all been qualified.

Have you been watching Event Viewer? Clear the logs and start fresh so
you have a known starting point and aren't confused by previous errors.
Build a new set, sort of.

Got a firewall running? You shouldn't, at this point, but if so there
might be some surprise entries in it.

Since you've been running chkdsk /r, switch to chkdsk /f for the rest of
the time; makes it run faster. The /r also checks unused space, which
you've already tested and gain nothing by repeatedly testing unused
space for bad sectors. Just worry about what actually contains data.

BIOS: Was it actually necessary to update it to the latest? Are you
CERTAIN the latest is a good rev for YOUR machine? It may not be.

Based on your description:
IMO you've created too many possibilities for errors to happen all at
once and that's really tough to track things down in. It can become a
real mess.

I think you need to go back to the beginning, start over by tossing
in the XP CD, booting from it, deleting recreating the partition, JUST
ONE, and install XP. Do not install ANYTHING else! Get everything
working. THEN start to update, add SP3, whatever. But do not go any
further until you are error free, including your event Viewer logs.

The XP CD *IS* a *retail* version, right? If it's an OEM, it MIGHT
*not* be capable of handling the hardware you have. Yes, some
manufacturers do butcher the OS that badly and will support only the one
set of hardware the machine was sold on when it's an OEM operating
system.

I'd be interested in hearing back how you make out if you follow any of
this advice. I suspect that if you don't, you'll be a long, long time
getting anywhere. You've got to knock it down into smaller blocks to
work on.

HTH

Twayne

Hi Twayne,

Thanks for the response.

All the stuff I put in this post was (is) actually over two months of
fighting to get this thing right. I did do the various steps you
mentioned sequentially. Painstakingly!

I am running a retail disk.

I did have to flash the bios to utilize the Intel Q9450 chip. My
confidence in this ver is fairly low. The chip is so new that it
....

I like the idea of just using SP2. I wanted the speed enhancements of
SP3, but at this point, having a working computer would be
enhancement enough. BTW, the older slower chip has been stable for 4
days now. (that is how long it's been since I pulled the new chip
out, so hope is running high). That's two more than the newer chip,
so I'm calling Intel tomorrow for an RMA and I'll try a new chip.

Thanks,
Mark

Best of luck.
One more thing: I have never heard that SP3 will give you any speed
advantages and seriously doubt it will. All SP3 is, is SP2 with all the
hotfixes and updates that followed SP2 implemented in it, plus a couple
of pretty much negligible features that aren't likely to be of any use
to anyone with a current machine.
So, SP3 = SP2 with following updates. Plus SP2 didn't have the kinds
of problems being reported for SP3.
So an SP2 machine with the updates is just as good reliabilty and
security wise as SP3 was supposed to be. Unfortunately some unexpected
glitches arose in SP3 that I don't quite understand so I'm recommending
people hold off until a few hotfixes AFTER SP3 came out, to take care of
the problems it has. Excuse me; uhh, that should have been "features"
not problemsg.

Sometimes it can be a long haul, I know. G'Luck!

Twayne




Chkdsk /p?? What's that? It's not listed under chkdsk /? listing.
Perhaps that's part of the problem?G

I think the first thing you should do is uninstall SP3, or do another
rebuild and use SP2 instead, whichever is most reliable for you. SP3
has caused some strange, verified and unverified but consistantly
reported problems. On a new sys, I'd start with SP2 and forget SP3
until later after it's all been qualified.

Have you been watching Event Viewer? Clear the logs and start fresh
so you have a known starting point and aren't confused by previous
errors. Build a new set, sort of.

Got a firewall running? You shouldn't, at this point, but if so
there might be some surprise entries in it.

Since you've been running chkdsk /r, switch to chkdsk /f for the
rest of the time; makes it run faster. The /r also checks unused
space, which you've already tested and gain nothing by repeatedly
testing unused space for bad sectors. Just worry about what
actually contains data.

BIOS: Was it actually necessary to update it to the latest? Are you
CERTAIN the latest is a good rev for YOUR machine? It may not be.

Based on your description:
IMO you've created too many possibilities for errors to happen all at
once and that's really tough to track things down in. It can become a
real mess.

I think you need to go back to the beginning, start over by
tossing in the XP CD, booting from it, deleting recreating the
partition, JUST ONE, and install XP. Do not install ANYTHING else!
Get everything working. THEN start to update, add SP3, whatever.
But do not go any further until you are error free, including your
event Viewer logs.

The XP CD *IS* a *retail* version, right? If it's an OEM, it MIGHT
*not* be capable of handling the hardware you have. Yes, some
manufacturers do butcher the OS that badly and will support only the
one set of hardware the machine was sold on when it's an OEM
operating system.

I'd be interested in hearing back how you make out if you follow any
of this advice. I suspect that if you don't, you'll be a long, long
time getting anywhere. You've got to knock it down into smaller
blocks to work on.

HTH

Twayne