Windows 2000 Slooow Boot
After trying a new copuple of 512 MB DIMM memory module, Windows 2000 boots very slowly (over 3 minutes before login mask).
I think my stupid fingers moved something on hardware, but what? Everything elese seem to work fine.
There are no errors in Windows 2000 event viewer.
Tried almost everything:
* restored original 2 x 128 DIMM RAM PC133 Ram;
* reinstalled Windows 2000;
* Mbrfix from Windows2000 recovery console;
* checked all connections on motherboard;
* boot with video card & hd only (no other periphals).
It's always slooow boot!!
Help please!
My system:
P3V4X
P3-600EB
Matrox G400
2x128 MB DIMM RAM PC133
Enrico
I think my stupid fingers moved something on hardware, but what? Everything elese seem to work fine.
There are no errors in Windows 2000 event viewer.
Tried almost everything:
* restored original 2 x 128 DIMM RAM PC133 Ram;
* reinstalled Windows 2000;
* Mbrfix from Windows2000 recovery console;
* checked all connections on motherboard;
* boot with video card & hd only (no other periphals).
It's always slooow boot!!
Help please!
My system:
P3V4X
P3-600EB
Matrox G400
2x128 MB DIMM RAM PC133
Enrico
Once it boots up, how does it perform? Slow bootup with Win2000 is often a case of networking software incorrectly configured. Could be coincidence with the memory upgrade.
Let us know if there were any other changes along with the memory upgrade. Since you put the old RAM back in, it probably isn't the RAM causing the problem. Please verify that it is seeing the 256 MB you have in it.
Did you reset the BIOS to factory default?
Did you reset the BIOS to factory default?
ASKER
tanjnt > Check your BIOS settings. When you put in the new RAM, did you change anything?
No.
tanjnt > If you don't see anything obvious, reset to default.
Yes, it actually is what I did (I forgot to mention in my question). But it did not help!
tanjnt > maybe go to
http://www.belarc.com/ and do a system report and print it.
Done. It doesn't show anything abnornal.
magarity > Once it boots up, how does it perform?
Normally, I believe.
magarity > Slow bootup with Win2000 is often a case of networking software incorrectly configured. Could be coincidence with the memory upgrade.
Mmmh... I haven't changed my network configuration. Anyway, I also tried to boot with no network cards.
tanjnt > Let us know if there were any other changes along with the memory upgrade.
No, not deliberately! What I fear is I have "broken" or disconnected something, at hardware level, when inserting and removing RAM modules. But I can't figure out what.
tanjnt > Since you put the old RAM back in, it probably isn't the RAM causing the problem
That's right. It's the same changing the RAM modules.
tanjnt > Please verify that it is seeing the 256 MB you have in it.
Yes, 256, here they are.
tanjnt > Did you reset the BIOS to factory default?
I tried this as a fix. But it didn't work.
Some more information about my sloooow boot.
After the Boot.ini menu, it takes...
- about 1 minute to complete the Windows 2000 logo bar;
- then, a dozen of seconds preparing startup;
- another dozen seconds preparing network connections;
- a quick second for protection stuff;
- about 100 seconds for a dumb empty desktop before the logon mask (first I can hear the hard disk going, then it stops for a long while).
My box has 2 multipartitioned hard disks, multiboot Win2000 / Win 98 SE.
Enrico
No.
tanjnt > If you don't see anything obvious, reset to default.
Yes, it actually is what I did (I forgot to mention in my question). But it did not help!
tanjnt > maybe go to
http://www.belarc.com/ and do a system report and print it.
Done. It doesn't show anything abnornal.
magarity > Once it boots up, how does it perform?
Normally, I believe.
magarity > Slow bootup with Win2000 is often a case of networking software incorrectly configured. Could be coincidence with the memory upgrade.
Mmmh... I haven't changed my network configuration. Anyway, I also tried to boot with no network cards.
tanjnt > Let us know if there were any other changes along with the memory upgrade.
No, not deliberately! What I fear is I have "broken" or disconnected something, at hardware level, when inserting and removing RAM modules. But I can't figure out what.
tanjnt > Since you put the old RAM back in, it probably isn't the RAM causing the problem
That's right. It's the same changing the RAM modules.
tanjnt > Please verify that it is seeing the 256 MB you have in it.
Yes, 256, here they are.
tanjnt > Did you reset the BIOS to factory default?
I tried this as a fix. But it didn't work.
Some more information about my sloooow boot.
After the Boot.ini menu, it takes...
- about 1 minute to complete the Windows 2000 logo bar;
- then, a dozen of seconds preparing startup;
- another dozen seconds preparing network connections;
- a quick second for protection stuff;
- about 100 seconds for a dumb empty desktop before the logon mask (first I can hear the hard disk going, then it stops for a long while).
My box has 2 multipartitioned hard disks, multiboot Win2000 / Win 98 SE.
Enrico
Since it is dual boot, does it boot normally or slowly to Win98? If normally, the problem isn't BIOS or hardware (like something inside that you bumped or connected wrong).
If slowly, the problem isn't software unless it is something like a virus that infected boot sector or both partitions. Is your antivirus current?
If slowly, the problem isn't software unless it is something like a virus that infected boot sector or both partitions. Is your antivirus current?
ASKER
> Since it is dual boot, does it boot normally or slowly to Win98?
Normally.
> If normally, the problem isn't BIOS or hardware (like something inside that you bumped or connected wrong).
But it could be some hardware problem that shows only with Win2000?
> Is your antivirus current?
Yes. Anyway, I did a fixmbr and a fixboot.
Enrico
Normally.
> If normally, the problem isn't BIOS or hardware (like something inside that you bumped or connected wrong).
But it could be some hardware problem that shows only with Win2000?
> Is your antivirus current?
Yes. Anyway, I did a fixmbr and a fixboot.
Enrico
There could easily be device driver or incompatibility issues causing a slow boot, but I can't think of any defective hardware that would cause problems with one OS and not the other. Since you tried booting with only video card and hard drive, those should be the only drivers other than core OS modules.
Take a look at this article on advanced restart options:
http://support.microsoft.com/default.aspx?scid=kb;en-us;317995
Might you have modified any boot parameters? Had you done anything else, such as install other software or devices around the time this problem occurred?
Have you applied all service packs? There were some performance issues resolved.
Take a look at this article on advanced restart options:
http://support.microsoft.com/default.aspx?scid=kb;en-us;317995
Might you have modified any boot parameters? Had you done anything else, such as install other software or devices around the time this problem occurred?
Have you applied all service packs? There were some performance issues resolved.
ASKER
> Had you done anything else, such as install other software or devices around the time this problem occurred?
No. The strange thing is that the problem occurs even after a Win2000 reinstall.
> Have you applied all service packs?
Yes. Sp3 and last Hotfixes.
Is there any tool to debug the Win2000 boot-startup process?
No. The strange thing is that the problem occurs even after a Win2000 reinstall.
> Have you applied all service packs?
Yes. Sp3 and last Hotfixes.
Is there any tool to debug the Win2000 boot-startup process?
ASKER
> Is there any tool to debug the Win2000 boot-startup process?
I tried with Xp's Msconfig, the diagnostic startup, but it's always 3 minutes long.
I tried with Xp's Msconfig, the diagnostic startup, but it's always 3 minutes long.
ASKER
Today is a bright day.
Today my Windows 2000 box boots in less than 1 minute (it was 3 minutes long!) :-)))
How did I fix it?
This morning (european time) I deleted some linux partitions on the second disk, I didn't any give importance. (reasons why I didin't give importance:
1. the Linux boot was just from floppy, not an Os selector installed on hd;
2. those partitions were there in the past (before the Ram moving and the Win2000 boot delays), and there were no problems in the past.
I am a new user on Experts-Exchange, so I don't know exactly what I should do now. Even if nobody guessed the perfect answer, maybe I didn't give all the necessary information , and anyway I appreciated the support I received. So, can I accept a comment as answer and give the points anyway?
Today my Windows 2000 box boots in less than 1 minute (it was 3 minutes long!) :-)))
How did I fix it?
This morning (european time) I deleted some linux partitions on the second disk, I didn't any give importance. (reasons why I didin't give importance:
1. the Linux boot was just from floppy, not an Os selector installed on hd;
2. those partitions were there in the past (before the Ram moving and the Win2000 boot delays), and there were no problems in the past.
I am a new user on Experts-Exchange, so I don't know exactly what I should do now. Even if nobody guessed the perfect answer, maybe I didn't give all the necessary information , and anyway I appreciated the support I received. So, can I accept a comment as answer and give the points anyway?
ASKER
I asked Community_Support/New_to_E
and following suggestions in
https://www.experts-exchange.com/questions/20408231/Can-I-accept-a-comment-as-answer.html
I'll ask to PAQ my question and open a new question to reward tanjnt's follow-ups.
and following suggestions in
https://www.experts-exchange.com/questions/20408231/Can-I-accept-a-comment-as-answer.html
I'll ask to PAQ my question and open a new question to reward tanjnt's follow-ups.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's an interesting situation. The OS must have been having trouble reading the drive because of the partition, but what triggered it at this particular time is a mystery. I'm surprised you didn't get some sort of error message. What file system was the partition using?
ASKER
> That's an interesting situation
Yes... "interesting" for the doctor, but not so pleasant for the patient :-)
> The OS must have been having trouble reading the drive because of the partition
Yes, but this showed up only during startup, as I did not access the linux partitions from Win2000 (they didn't even have a drive letter in Win2000).
> but what triggered it at this particular time is a mystery
Computer science, about misteries and paranormal! :-)
> What file system was the partition using?
They were the default partitions created by a Linux Mandrake 9.0 installation. something like Ext3 (if I remember it right) and Swap. Never had such problems before.
Yes... "interesting" for the doctor, but not so pleasant for the patient :-)
> The OS must have been having trouble reading the drive because of the partition
Yes, but this showed up only during startup, as I did not access the linux partitions from Win2000 (they didn't even have a drive letter in Win2000).
> but what triggered it at this particular time is a mystery
Computer science, about misteries and paranormal! :-)
> What file system was the partition using?
They were the default partitions created by a Linux Mandrake 9.0 installation. something like Ext3 (if I remember it right) and Swap. Never had such problems before.
tanjnt,
Putifarre has left points for you at https://www.experts-exchange.com/questions/20409418/Question-for-tanjnt.html
Please comment there so the question can be closed.
Netminder
EE Admin
Putifarre has left points for you at https://www.experts-exchange.com/questions/20409418/Question-for-tanjnt.html
Please comment there so the question can be closed.
Netminder
EE Admin
http://www.belarc.com/ and do a system report and print it.