Computing.Net > Forums > Windows 2000 > Cannot boot

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Cannot boot

Reply to Message Icon

Name: Shawn
Date: July 9, 2003 at 11:08:02 Pacific
OS: win2k
CPU/Ram: 1.4ghz/128mb
Comment:

Hello, I am running (or aleast trying to)
a Soyo mobo with an Athlon 1600+ processor
and 128 mb of ram, before 2 weeks ago I have always left my system running, then I was going on vacation and decided I will shut down the computer while I am gone, system shut down normally. I come back from vacation
and try to start up the computer to find the
file NTOSKRNL.exe is missing or corrupt, so O.K. I have seen this before. I try to get into safe mode- no luck. try from boot floppies- after the F6 to load drivers goes away i get "LINE 216 OF THE INF FILE IS INVALID SETUP CANNOT CONTINUE, PRESS ANY KEY"
pressing any key just repeats the process with same resluts. So I thought floppies were bad and created a new set, but same resluts. I then tried from the CD and have the same message come up, And this is a recent (ok maybe 7-8 mo. ago)installation
and did not get the chance to install the recovery console. Nothing was recently installed or changed and system was as normal as can be before I shut it down.
Any suggestions on how to get my system booted to make repairs, I have searched to my wits end for the error message I am getting but to no avail, and I am reluctant
to just format the drive just yet as there are some things I need from the drive if it still intact.(Yes, I think my hard drive crashed bad but am hoping some will tell me other wise.)
Thanks,
Shawn



Sponsored Link
Ads by Google

Response Number 1
Name: jollyman
Date: July 9, 2003 at 12:10:57 Pacific
Reply:

If you have a spare hard drive with an OS loaded, you can get on there and get your data off the old hard drive. The hard drive itself probably did not go bad, but it looks like your windows install did. You may want to try and repair it from the w2k CD if you have it.


0

Response Number 2
Name: voxtek
Date: July 9, 2003 at 12:18:57 Pacific
Reply:

You should use a software like NortonGhost. On my system i have 3 OS (2000, 2003, Linux), and i have done an image for my 3 OS.
It's very useful?



0

Response Number 3
Name: shawn
Date: July 9, 2003 at 12:30:34 Pacific
Reply:

I was thinking of the old hard drive route,
and it may have to be done. I do have the w2k cd, when I try and boot it, it will start up at the blue screen and as soon as the "press F6 to install 3rd party drivers"
goes away the message " LINE 216 OF THE INF FILE IS INVALID, SETUP CANNOT CONTINUE, PERSS ANY KEY TO EXIT" after pressing a key it goes back to the black screen with "setup is checking..."then to the blue screen again. A constant loop. I have tried booting from CD, floppies, floppies created on another machine, everything. A win 98 startup disk and fdisk show the volume is NTFS and is showing correct capacity so I do belive the hard drive is in working order,
I just cannot find any means to get the system booted to recover it.


0

Response Number 4
Name: trvlr
Date: July 9, 2003 at 13:21:55 Pacific
Reply:

The "inf" error message 'could' be due to a failing RAM stick or two/three.

If possible, try a fresh/known reliable stick and see how things go.

If you still cannot boot normally etc. then try the Setup\repair routine; even perhaps the Upgrade of current installation approach - via CD boot or the floppies. This may then allow you back in OK - providing installed RAM is OK.

Incidentally that ntoskrnl error is 'usually' associated with a corrupt or incorrect boot.ini entry for the OS itself. (i.e. the ARC path) The line for the ntoskrnl.exe is not pointing to the correct location. Since you were away and changed nothing (knowingly) yet the error/problem appeared when you booted up on your return, it does tend to point to something else - and this could be RAM...?

A virus problem might also be present - but I put that low on the list on this occasion...

Also verify that RAM is securely installed (pressed home) in its slot(s).

What file format is the drive at present? If fat32 then you should be able access the boot.ini (via a'98 boot-disk) and post details here?

Also how is the drive configured (partitions etc.)?


0

Response Number 5
Name: Shawn
Date: July 9, 2003 at 13:48:04 Pacific
Reply:

RAM.. Hmmm... About 2-3 months ago I got some BOSD's related to RAM. Reseated the DIMM's and all was good, I will try that again.
The current drive format is NTFS on a single
partition on a 8GB drive so booting a '98
startup disk doesn't get me far.
Virus files updated about 2weeks before all
of this and never really gave it a second thought that a virus may be causing havok, if is it's a darn good one.

I cannot get to the repair/setup routine on this system, the CD will boot but stops before I can choose to repair or reinstall.
Floppies are the same way. (floppies created from the cd and tried ones from bootdisk.com
all the same result)

I will try reseating the RAM
and also I'll get out that old hard drive and
see if I can get w2k loaded on that.
Thanks for all the input please keep it coming,It gives my brain a little break.I will post my results and findings.


0

Related Posts

See More



Response Number 6
Name: buster65
Date: July 9, 2003 at 17:06:42 Pacific
Reply:

Look at this site to see if this will help:

http://www.ntfaq.com/Articles/Index.cfm?ArticleID=14722


0

Response Number 7
Name: trvlr
Date: July 10, 2003 at 09:29:18 Pacific
Reply:

Sounds more and more like a RAM issue. possibly reseating will resolve it - but I'm inclined to say: borrow/beg/steal a known good stick and try it in place of current stick?

FWIW - NT sufferd the same problems re RAM and problems copying files, or loading "inf" etc... Frequently the sytem would cough up an error message saying it couldn't copy a file (or files); suggested the CD was duff -even the CDROM... All the while it was less than NT (W2K in your case) friendly RAM... that RAM being less than perfect. Chips do fail - albeit not as frequently as perhaps once - but they do go down...; cheaper brands will possibly be more prone to it thatn higher brands (but I've no hard evidence of this).


0

Response Number 8
Name: Shawn
Date: July 12, 2003 at 22:19:38 Pacific
Reply:

Yes, it was a RAM issue. I didn't have a good one to test with but using HIMEM.SYS I found that some of the memory areas were bad and was causing all my problems. Well today I was able to make over to my local computer shop and picked up 256MB PC333 for $20, I was damn happy, doubled my RAM and saved a bunch of cash. Pluged it in as soon as I got it home started the computer up, booted right into w2k no problem. been running for several hours now rebooted a number of time and all seems fine. Thanks all for the input, it sure helps.

Shawn



0

Response Number 9
Name: trvlr
Date: July 13, 2003 at 06:40:32 Pacific
Reply:

Good to hear all is now OK.

Tanx for posting back; it happens so rarely. Usually folks is left in the dark as to what the solution for each problem posted here.



0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: Cannot boot

Cannot boot up www.computing.net/answers/windows-2000/cannot-boot-up/36829.html

Win 2k Cannot boot up! www.computing.net/answers/windows-2000/win-2k-cannot-boot-up/2793.html

Cannot boot Windows 2K Pro www.computing.net/answers/windows-2000/cannot-boot-windows-2k-pro/56607.html