Weird XP Start-Up Problem - Please help!

[Debi]

Hi Guys,

I've been working on this weird and wonderful problem for a few weeks now
but I've come to an absolute dead end. I hope you can help me!

First of all, here's my system:

XP Pro (SP2) - Retail/Fully Updated
Asus P5N32-SLI Deluxe Motherboard
DualCore Intel Pentium D 950, 3400 MHz (17 x 200)
Thermaltake 430W TR2 Quiet PSU
nVIDIA GeForce 6200 TurboCache Graphics
2GB Ram (2x 1GB Corsair Sticks)
2 x 250GB SATA Hard Drives

BIOS Updated - Different Configurations attempted (currently at default)
No Overclocking
All Drivers updated and all Software removed except for XP
Event Logs showing no errors

Basically, when I power on for the first time in the day, after the initial
post 'beep' it goes forward to the Windows Splash Screen (Blue Scrolling
Line) then the system suddenly restarts and this time the operating system
loads up as normal.

I can restart and/or power off numerous times throughout the day, even if
left for a few hours, but the problem will not be repeated until the next
day!

Indeed, once booted the system runs fine without any problem and today I
loaded Nero and re-coded a large AVI file to make a DVD whilst working on a
PowerPoint presentation with music running (Media Player). Absolutely no
problem whatsoever...runs like a dream with absolutely no errors! However, I
know when I switch on tomorrow I'll have this "double boot" scenario again!

I've since done FIXBOOT (Recovery Console) & CHKDSK /R but I still get the
problem once a day.

As a final resort I amended the BOOT.INI file to include /SOS as I wanted to
see what was actually happening - I did that last thing yesterday evening in
preparation of today's boot!

I duly fired my PC up this evening and it did exactly the same routine. Now
then, instead of the splash screen, I quickly noted down this message on the
screen before the auto reboot:

CHECKING FILE SYSTEM ON D:
THE VOLUME IS CLEAR
CHECKING FILE SYSTEM ON C:
THE VOLUME IS CLEAR
WINDOWS HAS FINISHED CHECKING THE DISK

It then rebooted into XP as normal.

Oh yes, one more thing, sometimes (but not always) on the second reboot I
get the standard "Sorry for the inconvenience" screen to which I select
"Last Good Configuration" or "Start Windows Normally" and it does. Like I
said, I can power off completely off and I can restart anytime in the day
without any issues until the next day.... it's as if something is happening
overnight! Spooky!

I really can't think of what to try next!

Any pointers will be appreciated.

Kindest regards,

Debi

 

[R. McCarty]

It seems like one or both of your drives are being marked "Dirty".
You might want to use a command prompt just before shutdown
and type >FsUtil Dirty Query C:
This will tell you if the volume is marked Dirty and will AutoCheck
on the next boot/Power-up.
Also, in BIOS Setup if your PC supports it add a 1-2 Second IDE
delay for your drives to spin up before XP starts.

 

[Debi]

Thanks.... I will try that now and report back tomorrow.

I still thinks it's weird why it only happens the once because if I power
off now and restart it will be fine but not so tomorrow evening!

Thanks again - You've given me some hope of solving this before Xmas!

Kindest regards,


Mike

 

[Debi]

Just tried it:

C:\>FsUtil Dirty Query C:
Volume - C: is NOT Dirty

I'll now try the BIOS tip!

Cheers!

Debi

 

[Pop`]

It seems like one or both of your drives are being marked "Dirty".
You might want to use a command prompt just before shutdown
and type >FsUtil Dirty Query C:
This will tell you if the volume is marked Dirty and will AutoCheck
on the next boot/Power-up.
Also, in BIOS Setup if your PC supports it add a 1-2 Second IDE
delay for your drives to spin up before XP starts.

No help to offer, but thought you might like to know about the collateral
non-damage you did. Fsutil is new to me, and I appreciate discovering it.

Pop`

 

[Pop`]

Thanks.... I will try that now and report back tomorrow.

I still thinks it's weird why it only happens the once because if I
power off now and restart it will be fine but not so tomorrow evening!

Thanks again - You've given me some hope of solving this before Xmas!

Kindest regards,


Mike

I haven't been following this thread, but the problem sounds like it might
be date/time stamp related? Or possibly something in Scheduled TAsks?

Scheduled Tasks you can just look at and turn things on/off IFF you're using
it. If not, then it's not the issue.

For the timestamp, you could try, while you're running well and know it'll
reboot OK, setting the computer clock ahead by 24 hours and try a reboot.
If it makes the problem happen, it's definitely date/time related. If
not, then it's another issue but it could still have to do with the
date/time settings; that;s why Scheduler occurred to me.

Do NOT forget to reset the date when you're done! <g>

HTH
Pop`

 

[Debi]

No luck I'm afraid.... situation still stands.

Nothing in Scheduled tasks!

Thanks for trying anyway - I'll get to the bottom of it eventually!

Regards,

Debi

 

[SBS 2003 User]

Hi Debi,
Just a quick thought here. I noticed you say the BIOS was updated so I am
assuming you flashed the BIOS with the latest release from the manufacturer?
Did you have this problem before you flashed the BIOS? I ask this because
sometimes with POST starting issues it does involved the BIOS which makes
sense because the only thing running during post are the BIOS and system
setup checks. May I suggest that if you did not have this issue before you
flashed the BIOS to return to the previous version and if this isn't the
case insure you do have the latest update.

 

[Debi]

Hi,

Yes, the only reason why I flashed the BIOS to the latest version was to
hopefully rectify this 'fault' otherwise I would have left well alone.

Thanks anyway... nice of you to write!

Regards,

Debi

 

[Paul Mckenna]

This is probably not your problem...

but a while ago we built a number of PCs with gigabyte motherboards and I
can't remember what memory but after XP was installed the following day a
number of these PCs didn't boot, they blue screened but after that each PC
started perfectly ran every test we could think of and nothing. so we
shipped a PC of to gigabyte to examine it and they found that there was a
problem with the memory starting up correctly. Their solution was to use
different memory or when powering up to hold the power button a little
longer!! Seems crazy and even telling the customer (prior to us getting new
memory in) to hold the power button for a second longer when switching on
they looked at me crazy but it worked.. It may be worth a try no matter how
insane it sounds

Regards
Paul

 

[SBS 2003 User]

Kind of sounds like it wants to go and do the chkdsk /r again. Have you
tried repairing to MBR? Can you get a hold of a Windows 98 startup disk that
has the fdisk command on it. If you can you can try to repair the MBR with
the fdisk /MBR command. I know this sounds redundant but trust me I have
done this before on a system that could boot but always got hung on the
spalsh screen. someone suggested this to me and lo and behold it worked.

 

[Debi]

Hi!

Is there not a MBR Command in the XP Recovery console? I was going to try
that in addition to FIXBOOT but got a strong warning not to proceed!

Regards,

Debi

 

[Debi]

Cheers Paul, I'll try that tomorrow!

I'll try anything!

Regards,

Debi

 

[Paul Mckenna]

There's a FIXMBR command, never had a problem running either but if your
getting a warning you may want to look up or tell us the warning first.

 

[SBS 2003 User]

Yes I do believe there is but from what I was told the W98 version works
best for the fdisk /mbr. Why I don't know and did not question it.