First boot - no windows - 2nd boot - there it is

[ltromans]

Very consistant - first time I boot up this PC (cold) it goes through the post and gets to where you would login for windows (2K) except there is nothing but a blue screen - you can't see the login at all or sometimes you only see the blue bars, but no id or password box. Reboot and everything loads normally. If I turn it off and let it sit awhile, it happens again.

It is almost like something is heating up and expanding to make a connection, but what??? I have reseated the mem chip and the video card and checked all cables.

Is this a motherboard problem or is there a cheap fix? It's a P-450 so I am not going to put a lot of $$ in it.

I have reinstalled op sys twice (originally had Win NT and problem appeared there - which prompted the Win 2K install.)

Thanks for your input.

 

[wolluf]

As you say - sounds like something heating up and expanding to 'make the connection'. You could check over everything even more carefully (or try removing/disconnecting items of hardware to see if it changes the situation).

Or, given age of machine, could just live with it!

 

[franklin97355]

Try turning the computer on for a few seconds then off for a few and then on againg if this works you may have a sticky hard drive that isn't getting up to speed fast enough for the OS. You may want to replace the drive before it quits all together.

 

[SYAR2003]

Hi there !

I think this also could sound like the dns issue .
Is the pc networked .
If so run the same tests with the NIC disconnected .

 

[ltromans]

OK - I have swapped and then removed the nic - problem still occurs. I have replaced the HD from another machine - problem still occurs. I have run memtest and (you guessed it) the problem still occurs.

So.. I think I have spent enough time on this, given that it is a 450, but I gave it my best shot. Thanks for your input.

Leslie

 

[TekTippy4U]

Sounds like TSR driver loading into mem, gets hung up, and then upon a warm restart it works cause the mem doesn't get flushed and tested at POST, as it would on a cold boot....
Also could be Not having the 6 second standard HDD delay set in the BIOS.... check this.

And look for Network Boot and Onboard LAN settings options in BIOS to see if interference there...Set Boot Order CDROM, Floppy, HDD, NOT boot from Network Drive if present..

Could start up in Safe Mode (see if it's a Protected Mode driver or not)

Could Start up to Start Menu and choose Step-by-Step confirmation (98 method) and Bootlog.txt for clues..(not sure how Win2K does this)

TT4U

Notification:
These are just "my" thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[BadBigBen]

Yep, but could also be a failing PSU... especially one with a cold solder point... or the mobo for that matter...

Ben

 

[ltromans]

Checked the bios - the HDD delay is 6 sec and the boot order is CD Floppy HDD.

Started in safe mode - it booted normally, so I think you are on to something tektippy. I will try the step by step.

Thanks
Leslie

 

[TekTippy4U]

Ok...Safe Mode is basically Disabling Config.sys and autoexec.bat...So Start > Run SYSEDIT

Copy and paste only the Config.sys and Autoexec.bat info into a new notepad file so you can quickly review in future and post them here and we'll review.. Do NOT alter the text in the orig. files for now.

First thing...Check the BIOS for "QuickBoot", "Fast Boot", "QuickStart" usually found in the Power Mngmt section....and Disable them so you get to see the Memory test and Device Detection (HDD, mouse, keyboard) during POST..

Don't use below techniques in conjunction with Step by Step Confirmation.... or in combination with any other Startup menu selection such as Safe Mode, Command Prompt Only, etc....

Another way to be sure that it's one of the entries in these files is to
Start > Run MSCONFIG
On the General Tab .."uncheck" the boxes
Process Config.sys
Process Autoexec.bat

and shutdown ...and power up obviously, as a restart is in essence a warm boot... Do you have a RESET button as this "should" be the same as a cold boot. (If you do have a Reset button and Have NOT been using it, Don't Start now, midstream while T-shooting).

Waddling through a Bootlog.txt file can be more Painful than reviewing someone's HijackThis log..
Here's a little guideline I found quickly pertaining to Step by Step Confirmation through google advanced search

http://www.adobe.com/support/techdocs/10d8a.htm

(Keywords = "Using Step by Step Confirmation&quot


TT4U

Notification:
These are just "my" thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[VulcanJedi]

seriously i had this friggan annoying problem when I built my newest pc. Had two drives, but I swear had the problem even when just one. did this problem just occur to an existing machine or new/modified one?
Check the EIDE cables/jumpers. EIDE cables look the same but are not. Try cable select.

Tranpkp

 

[ltromans]

OK - I disabled the quick boot. Also checked (and rechecked cables and jumpers). Autoexec and config.sys are both empty and there is no msconfig - running win2k on NTFS.

I am giving up. I have scavenged the HD, the ram, the video card and the nic - the rest is heading to the recycle center. The pieces are marked - if I put them into other systems I can watch for errors. It was only a P2-450 - not worth any more effort.

Thanks all for your input.
Leslie

 

[TekTippy4U]

Oh well , thanks for posting back with update....hope you lost the issue in the trash heap
Keep us posted though, in case

TT4U

Notification:
These are just "my" thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[yada]

I seem to be getting this a lot with via chipsets lately. Especially with 64gbyte nvida video cards. I'n thing AGP problems. It don't hurt anything but just pi**es me off.

 

[rockerfellerz]

Had a very similar problem myself awhile back; comp would only start on second boot if it was " cold " but would restart fine after that. I installed a newer version of directx and that cleared the problem.

If you're going through Hell...keep going... (Winston Churchill)
RocKeRFelLerZ