Re: Boot problems
- From: RB <RB@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 7 Dec 2006 06:15:00 -0800
Chkdsk seemed to help, although the boot process still sems longer than it
used to be. I also don't quite understand chkdsk and hope you will be kind
enough to explain it. When I ran it from a command line window it found
numerous errors, mostly of the nature of "first allocation unit is not valid,
file will be truncated". Then I ran it with /f in order to cause it to run on
boot, which it did. But when I then again ran chkdsk from a command line
window it again found these numerous errors. Does the autochk that runs with
boot-up also repair errors or does it just report them? It is hard to see
what it does because it doesn't give you enough time to read the results but
immediately disappears. Then I ran autochk a second time and then running
chkdsk inside windows reported many fewer entries of first allocation unit
not valid, but the result still said "windows found problems with the file
system, run chkdsk with /f to repair". What is all this about and how can I
fix the errors now that we no longer have the option of a dos bootup for
tasks like this?
Many thanks.
P.S. Sorry if I have been a bit long winded but I spent quite abit of time
trying to sort this out and would like to try and understand what is
happening.
"Gerry Cornell" wrote:
RB.
Have you tried to run chkdsk?
http://support.microsoft.com/kb/315265
As you are having problems involving your C drive you will need to reboot,
which may or may not cause problems. The tool runs before booting to
the Desktop. I did wonder whether improper shutdowns were causing
this tool to automatically run. Running chkdsk can take some time but
I think you might have noticed it if it was running.
Please let me know how you get on.
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"RB" <RB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0181DC3D-7ED2-433B-AAE4-3B6EA8534119@xxxxxxxxxxxxxxxx
No, that is not what I am saying. The problem is in normal mode. Entering
safe mode and then restarting permits successful booting into normal mode.
But when it gets stuck in the initial boot into normal mode (when I first
switch on) no events are created presumably because the system gets stuck
at
a stage before any event can be logged. In fact now I realize that the
problem only occurs when I power up the computer after complete shut-down.
Performing restart afterI am logged in works fine with no problem.
I checked the device manager and startup programs and did not see anything
out of the ordinary.
Thanks.
"Gerry Cornell" wrote:
RB
Are you saying that the problematic is in Safe Mode rather than Normal
Mode?
Can you post a copy of the Report listing the drivers?
Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties. Hardware,
Device Manager. If yes what is the Device Error code?
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"RB" <RB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:091F5026-4218-4750-B494-4295F18AFBD4@xxxxxxxxxxxxxxxx
The startup process does not seem to have proceeded sufficiently to
generate
an event.
Here is what I have in the system log, none of the other logs appear to
have
anything relevant:
Type of Event: Information
Origin of Event: EventLog
?????????? ?????: None
Ev ent ID: 6009
DaTE: 06/12/2006
Time: 08:39:04
User: N/A
Computer: BARUCH-1
???????:
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor
Free.??
For further information see the help and support center:
http://go.microsoft.com/fwlink/events.asp.
Succeeding entries relate to services that ouldn't start in safe mode.
Thanks.
"Gerry Cornell" wrote:
For a single problematic boot please check Event Viewer for Warning /
Error Reports in the System and Application logs and post copies.
You can access Event Viewer by selecting Start, Administrative Tools,
and
Event Viewer. When researching the meaning of the error, information
regarding Event ID, Source and Description are important.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&sd=tech
A tip for posting copies of Error Reports! Run Event Viewer and double
click
on the error you want to copy. In the window, which appears is a
button
resembling two pages. Double click the button and close Event Viewer.
Now
start your message (email) and do a paste into the body of the
message.
This
will paste the info from the Event Viewer Error Report complete with
links
into the message. Make sure this is the first paste after exiting from
Event
Viewer.
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"RB" <RB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:69E37143-F28F-46C3-B4D0-42F87C35E59A@xxxxxxxxxxxxxxxx
My system is XP-SP2-Home. Security programs running include Windows
Defender,
AVG-Free AV, AVG-Free Antispyware, Comodo firewall, Mailwasher free,
Winpatrol and Spyware Guard.,
Lately I have been having a problem with booting that after the XP
logo
the
screen goes blank and nothing happens necessitating a hard reset.
Then
I
get
the startup menu. Selecting "last good configuration" sometimes
helps
but
usually not. If I enter safe mode, log on to my account and then
perform
restart I then get into the entry screen normally. However this
whole
process takes too much time and clearly something is wrong. I
performed
routine maintenance o cleaning up temp files and cleaning the
registry
(CCleaner), but hat didn't improve matters.
I would appreciate any suggestions.
- Follow-Ups:
- Re: Boot problems
- From: Gerry Cornell
- Re: Boot problems
- References:
- Re: Boot problems
- From: Gerry Cornell
- Re: Boot problems
- From: RB
- Re: Boot problems
- From: Gerry Cornell
- Re: Boot problems
- From: RB
- Re: Boot problems
- From: Gerry Cornell
- Re: Boot problems
- Prev by Date: Re: virtual mem
- Next by Date: Repeated USB mouse failures
- Previous by thread: Re: Boot problems
- Next by thread: Re: Boot problems
- Index(es):