Windows 2000 Problem?

chipshot

Full Access Member
Joined
Feb 6, 2002
Posts
33,519
Reaction score
0
Points
36
Age
50
Location
Boise
Website
Visit site
Any idea what coud cause it to freaze up at the screen that has the white bars across the bottom that says "Starting Windows"?

It eventually starts after sevarl attempts but it is scary as hell since we have alot of data on the box.
 
A number of things, usually though, it's a corrupt or clogged registry. It could also be something mechanical/electrical.

Remember though, you have data on your hard drive, not on the computer. Most people don't seem to get this or udnerstand its significance. If you have important data, back it up on another drive or burn a CD with the important data files.
 
I thought the o/s was loading device drivers at that point. Can you boot into Safe Mode okay? Safe mode with networking okay?
 
That's usually a hardware problem. Last time I couldn't figure it out, I reset the BIOS to defaults and never had any more trouble.
 
HardHarry said:
A number of things, usually though, it's a corrupt or clogged registry. It could also be something mechanical/electrical.

Remember though, you have data on your hard drive, not on the computer. Most people don't seem to get this or udnerstand its significance. If you have important data, back it up on another drive or burn a CD with the important data files.


I understand but when you cannot get to it and you need it "yesterday" it can cause problems when people need to access the database.
 
Ahh, that's one of the reasons they developed redundancy (aka RAID). I have two HD's in my box. Neither one cost me more than $50, but I have over 200 GBs storage space, in a RAID array. And that's just so I don't lose mp3's and a buncha word docs.
 
I'm not concerned with losing the data, I need to have the database accessible. If it doesn't start it is not accessable until the problem can be solved. Business decisions cannot wait for the computer to be fixed in 99/100 cases.
 
If it's that important to the business, have the business buy some real hardware to run it on. Windows is likely choking because of a hardware failure (almost guaranteed since it works after a number of power cycles - the software isn't changing from reboot to reboot...). There are some bootup logs you can review to find out where it chokes, but the reality is it sounds like you're running a "desktop" OS and a desktop piece of hardware for a business critical function, and I'd spend the time and energy on resolving that bigger issue rather than tackling the symptom...
 

Members online

Latest posts

Trending content

Forum statistics

Threads
158,340
Posts
2,824,038
Members
11,199
Latest member
garyfrank231
Back
Top