I need help with a major problem with check disk.

[Guest]

Every time I run Error-checking, it restarts my computer runs then my
computer fails to start after the scan. I allow startup repair to scan and
it says there are corrupt system files and i allow it to run then my system
starts correct. Then i've tried scanning again same number of errors in
Error-checking then it fixes, failed boot, same cause for failed boot.

Please help.

 

[David Dickinson]

Every time I run Error-checking, it restarts my computer runs then my
computer fails to start after the scan. I allow startup repair to scan
and
it says there are corrupt system files and i allow it to run then my
system
starts correct. Then i've tried scanning again same number of errors in
Error-checking then it fixes, failed boot, same cause for failed boot.

Please help.

You can see the details of what chkdsk found and fixed in Administrative
Tools\Event Viewer. Look under Windows Logs\Application for an entry from
source Winlogon.

But it sounds like a bad hard drive. Call the dealer.

 

[Guest]

You can see the details of what chkdsk found and fixed in Administrative
Tools\Event Viewer. Look under Windows Logs\Application for an entry from
source Winlogon.

But it sounds like a bad hard drive. Call the dealer.

Thanks David

Here is part of the log can anyone tell me what i could do to fix the problem.

Source: VSS
Level: Error

Description:
Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005. This is often caused by
incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Thanks.

 

[David Dickinson]

Here is part of the log can anyone tell me what i could do to fix the
problem.

Source: VSS
Level: Error

Description:
Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005. This is often caused by
incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

There doesn't seem to be /any/ documentation on that error. It seems to me
that I read another post about that error in this forum, but that there was
no resolution. Have you changed any security settings on your machine that
you weren't quite sure about? I'm also wondering about the configuration of
your machine: could it possibly be a dual boot machine with XP? Also, this
problem may be related in some way to your chkdsk errors, e.g., if some of
the files that were corrupted were part of .NET Framework.

Is that the /only/ error in the log? The one's that most I'm interested in
are from source Winlogon at the time that you do the disk check -- and
they're not errors but "Information" entries in the log. (You can copy and
paste entire log messages in your posts. We won't mind at all!)

 

[Guest]

There doesn't seem to be /any/ documentation on that error. It seems to me
that I read another post about that error in this forum, but that there was
no resolution. Have you changed any security settings on your machine that
you weren't quite sure about? I'm also wondering about the configuration of
your machine: could it possibly be a dual boot machine with XP? Also, this
problem may be related in some way to your chkdsk errors, e.g., if some of
the files that were corrupted were part of .NET Framework.

Is that the /only/ error in the log? The one's that most I'm interested in
are from source Winlogon at the time that you do the disk check -- and
they're not errors but "Information" entries in the log. (You can copy and
paste entire log messages in your posts. We won't mind at all!)

I disabled UAC -various programs i use do not cooperate at any level with
UAC on
Windows Vista Home Premium - my only os
The only error that appears is that one and the log for that is there
repetitively for my system for every startup repair after a error-check

Log Name: Application
Source: VSS
Date: 11/06/2007 2:00:06 AM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Brandon-PC
Description:
Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005. This is often caused by
incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {038f28b6-4f1d-4ead-9268-fde5a46c696f}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-06-11T08:00:06.000Z" />
<EventRecordID>1672</EventRecordID>
<Channel>Application</Channel>
<Computer>Brandon-PC</Computer>
<Security />
</System>
<EventData>
<Data>0x80070005</Data>
<Data>

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {038f28b6-4f1d-4ead-9268-fde5a46c696f}</Data>

<Binary>2D20436F64653A20575254575254494330303030303935382D2043616C6C3A20575254575254494330303030303932382D205049443A202030303030313337362D205449443A202030303030313331362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E5420415554484F524954595C4E4554574F524B2053455256494345202020202D205369643A2020532D312D352D3230</Binary>
</EventData>
</Event>

Thanks for your help so far

 

[David Dickinson]

I disabled UAC -various programs i use do not cooperate at any level with
UAC on
Windows Vista Home Premium - my only os
The only error that appears is that one and the log for that is there
repetitively for my system for every startup repair after a error-check

Log Name: Application
Source: VSS
Date: 11/06/2007 2:00:06 AM
Event ID: 8194

Hmmm... I just don't think this is the cause of the problem that you
initially described. In fact, this error /may/ be a result of that problem
(although maybe not).

And I regret that I made a mistake before: the results of the disk check
will be stored in an "information" event 1001 from source Wininit. It is
/not/ an "error" message.

Without seeing the results of the disk check, I still think it's a bad hard
drive.

 

[Jill Zoeller [MSFT]]

I concur that the VSS error is not the cause of the chkdsk problem. Is this
a brand new computer by chance?

 

[Guest]

I concur that the VSS error is not the cause of the chkdsk problem. Is this
a brand new computer by chance?

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows file and storage technologies? Visit our
team blog at http://blogs.technet.com/filecab/default.aspx.

It is a new computer
And i'm not at it so i'll send the results later.

Could it maybe a problem with check disk since it is alone and also part of
startup repair?

 

[David Dickinson]

It is a new computer
And i'm not at it so i'll send the results later.

Could it maybe a problem with check disk since it is alone and also part
of
startup repair?

chkdsk will tell you if there are problems with your hard drive. Trust it.
I've never known it to actually /cause/ a problem, only to reveal (and often
fix) problems that already existed. (It is true that it sometimes will
appear to make a problem worse than it was, but its not really chkdsk's
fault.)

Safest bet: I think you need a technician to look at your system.

 

[Guest]

chkdsk will tell you if there are problems with your hard drive. Trust it.
I've never known it to actually /cause/ a problem, only to reveal (and often
fix) problems that already existed. (It is true that it sometimes will
appear to make a problem worse than it was, but its not really chkdsk's
fault.)

Safest bet: I think you need a technician to look at your system.

I'll be able to send the results in 0.5-2hrs
I ran one of the disk checks so it would scan for/repair bad sectors but it
found none that's why I think it is not the hard drive btw.

 

[Guest]

Way to go microsoft
It turns out some of my system files got corrupted by the registration fixer
program microsoft recommended. Lucky that i had one system restore point
that could work to fix the problem.
Everything is fine now.

Thanks for everyone's help.

 

[David Dickinson]

Way to go microsoft
It turns out some of my system files got corrupted by the registration
fixer
program microsoft recommended. Lucky that i had one system restore point
that could work to fix the problem.
Everything is fine now.

Thanks for everyone's help.

Well, good! I guess that I didn't understand your first post. But I'm glad
you got it worked out.