Hi. I first performed a search for this topic but didnt find an appropriate solution. So i am making this thread. Here lies the problem:

As soon as i power on my system, my monitor remains blank for close to 5 minutes (The monitor is on and the CPU and SMPS fan are working during this period). After waiting that long, finally i hear a beep and the system begins to boot (showing the 'verifying dma pool data' screen).

Now just before the desktop screen is about to show up, the system restarts and i get a 'Safe Mode' prompt. I choose safe mode and then after getting to the desktop successfully, i restart my system again to run in normal mode.

Now my concerns are:

1. Why does it take close to 5 mins for the system to start booting (This is the case every time i shut down my system and start it again after some time)

2. Why does my system always restarts the first time after booting and asks for safe mode? (Even this happens every time i start my system)

I have Windows 98SE installed and my comp specs are:

Intel Pentium Celeron
750 MHz 128MB RAM

Anyone having any suggestions/ideas?

Thanks and Regards,
Nisar.

PS: Just to see how my system reacts, i once shut down my system after successfully reaching the desktop. Then after 4-5 seconds, i again started my system and this time, it didnt take more than 1-2 seconds to boot up. (It seems like if i keep my system turned off for more than 2-3 hours, it takes close to 5 mins to boot up the next time i power it on). Does this mean this is probably a hardware issue rather than a software one?

First, has the machine been working fine, and this behaviour just started?

Is the "Fast Boot Option" enabled in the machines bios? (This bypasses extended checking of memory etc.)

"The monitor is on ..."

The monitor "power lite" changes from Orange or Red to Green (signifying signal to the monitor)?

"my monitor remains blank for close to 5 minutes"

Is this to say there is absolutely nothing displayed? (Bios version/data, Memory count, etc.)

Are you using onboard video or a add-in card? (PCI/AGP)

"and the ... SMPS fan are working during this period..."

SMPS? * * Power Supply? Please define.

"Verifying DMA pool data" is a command or machine level check of your IRQ settings and your DMA channels. You may have a device conflict. The machine may be "working things out/reassigning device elements" on this "first boot".

A device conflict occurs when two different hardware components or cards try to use the same interrupt (IRQ) or the same channel (DMA). If you have installed any new devices on your machine, that device would be suspect as to causing the problem.
Check Device Manager and look for any yellow exclamation marks or red Xs (open all the device directories so you can see individual items). These indicate a device that is not working properly.

"Just to see how my system reacts, i once shut down my system after successfully reaching the desktop. Then after 4-5 seconds, i again started my system and this time, it didnt take more than 1-2 seconds to boot up. (It seems like if i keep my system turned off for more than 2-3 hours, it takes close to 5 mins to boot up the next time i power it on). Does this mean this is probably a hardware issue rather than a software one?"

RAM takes about thirty or so seconds to "bleed off". It may be that system settings are retained within this time period.

Originally Posted by Dan Penny

First, has the machine been working fine, and this behaviour just started?

Is the "Fast Boot Option" enabled in the machines bios? (This bypasses extended checking of memory etc.)

Yeh this problem has started recently. Until a month ago, it was working normally. The fast boot option is not disabled.

"The monitor is on ..."

The monitor "power lite" changes from Orange or Red to Green (signifying signal to the monitor)?

Its an old system so theres only the green color which always remains lit.

"my monitor remains blank for close to 5 minutes"

Is this to say there is absolutely nothing displayed? (Bios version/data, Memory count, etc.)

Yep. Nothing is displayed. Not even any bois information, memory count etc

Are you using onboard video or a add-in card? (PCI/AGP)

Its an onboard chip (Intel 82810 Graphics Controller)

"and the ... SMPS fan are working during this period..."

SMPS? * * Power Supply? Please define.

Yeh the unit which gives power to the system. The fan inside that unit is working. This is what i am refering to:

"Verifying DMA pool data" is a command or machine level check of your IRQ settings and your DMA channels. You may have a device conflict. The machine may be "working things out/reassigning device elements" on this "first boot".

A device conflict occurs when two different hardware components or cards try to use the same interrupt (IRQ) or the same channel (DMA). If you have installed any new devices on your machine, that device would be suspect as to causing the problem.
Check Device Manager and look for any yellow exclamation marks or red Xs (open all the device directories so you can see individual items). These indicate a device that is not working properly.

Sorry i forgot to mention it. I installed an ethernet card. I checked the device manager and i have a red X on my sound device....but it is due to the fact that i disabled it.

"Just to see how my system reacts, i once shut down my system after successfully reaching the desktop. Then after 4-5 seconds, i again started my system and this time, it didnt take more than 1-2 seconds to boot up. (It seems like if i keep my system turned off for more than 2-3 hours, it takes close to 5 mins to boot up the next time i power it on). Does this mean this is probably a hardware issue rather than a software one?"

RAM takes about thirty or so seconds to "bleed off". It may be that system settings are retained within this time period.

I was wondering that that my system is waiting for some part of the motherboard to heat up. As soon as it heats up, the system boots. This may explain the reason why my system starts immediately when i turn it off without any delay. Maybe because that part is already heated up by the time i shut down my computer.

" As soon as it heats up, the system boots. This may explain the reason why my system starts immediately when i turn it off without any delay. Maybe because that part is already heated up by the time i shut down my computer."

Are the machines Time and Date "holding settings" between starts? If not, the CMOS battery may be on it's way out. (If the battery is dead or dying, the machine will resort to factory defaults, thereby taking time to scan for floppy drives, hard disk parameters, add-in cards in motherboard slots, etc and set things so the machine will boot unless there is a serious hardware error.)

Again, the RAM takes about thirty or so seconds to "bleed off". (Loosing any pre-determined settings held in the bios via the cmos battery.) It may be that system settings are retained within this time period. (Again leads to possible CMOS battery failure.)

If the above doesn't apply.......

"As soon as it heats up..." can be the machine "sorting things out", (as above,) and not heat related.

If it is "heat related", this could be a connection problem. Ensure all connectors are fully seated to the motherboard and all ancillary components. It sometimes pays to remove/reseat all connectors a couple of times to remove oxidation on pins etc.

As well, it could be a cracked track on the motherboard, (main power (or other) connector/memory module pushed too hard flexing the motherboard) or, the motherboard is not securely tightened to the stand-offs securing it to the enclosure. (A grounding problem could exist even though grounds are provided through the power connectors.)

Further speculation; This appears to be an ~older~ machine;

Intel Pentium Celeron
750 MHz 128MB RAM
Windows 98SE

Are the sound/ethernet components onboard devices, or, add-in cards?

If cards, are they "Plug N' Play"? If not, there may be jumpers on the cards to set IRQ and DMA settings. (Even some older cards with jumpers had jumper positions for "Plug N' Play".)

If jumpers are not set according to what is available on the machine, conflicts can arise. Thus extended boot time and certain components will be disabled.

Originally Posted by Dan Penny

Are the machines Time and Date "holding settings" between starts? If not, the CMOS battery may be on it's way out. (If the battery is dead or dying, the machine will resort to factory defaults, thereby taking time to scan for floppy drives, hard disk parameters, add-in cards in motherboard slots, etc and set things so the machine will boot unless there is a serious hardware error.)

Again, the RAM takes about thirty or so seconds to "bleed off". (Loosing any pre-determined settings held in the bios via the cmos battery.) It may be that system settings are retained within this time period. (Again leads to possible CMOS battery failure.)

The time and date changes only when the machine is running...so i replaced the battery with a new one but still the problem persists.

If it is "heat related", this could be a connection problem. Ensure all connectors are fully seated to the motherboard and all ancillary components. It sometimes pays to remove/reseat all connectors a couple of times to remove oxidation on pins etc.

I tried this as well but invain.

As well, it could be a cracked track on the motherboard, (main power (or other) connector/memory module pushed too hard flexing the motherboard) or, the motherboard is not securely tightened to the stand-offs securing it to the enclosure. (A grounding problem could exist even though grounds are provided through the power connectors.)

I think this probably might be the reason behind the unusual behaviour of my system.

Are the sound/ethernet components onboard devices, or, add-in cards?

If cards, are they "Plug N' Play"? If not, there may be jumpers on the cards to set IRQ and DMA settings. (Even some older cards with jumpers had jumper positions for "Plug N' Play".)

If jumpers are not set according to what is available on the machine, conflicts can arise. Thus extended boot time and certain components will be disabled.

Both the sound and ethernet cards are add-cards. They were there before and my machine ran normally during those times. I didnt even change any of its settings on the motherboard (jumpers etc). And i see no 'Yellow' exclamation mark on any of the devices listed under Device Manager. So the question of conflicts doesnt arise.

Quote:
As well, it could be a cracked track on the motherboard, (main power (or other) connector/memory module pushed too hard flexing the motherboard) or, the motherboard is not securely tightened to the stand-offs securing it to the enclosure. (A grounding problem could exist even though grounds are provided through the power connectors.)

I think this probably might be the reason behind the unusual behaviour of my system.

Do you recall something on this order happening in the past? (Board "overflexed"?)

The more I re-read your topic, the more it seems to be hardware related......

Generally only hardware conflicts/component damage bring something like this forth.

(Not related really but,) I've seen old (dinosaur) HP machines refuse to boot because a modem card was in a certain slot. Move it over one slot and the machine would boot fine. (It's) just that certain hardware in certain machines can/will cause anomalies.

Originally Posted by Dan Penny

Do you recall something on this order happening in the past? (Board "overflexed"?)

The more I re-read your topic, the more it seems to be hardware related......

Generally only hardware conflicts/component damage bring something like this forth.

Actually i do experiment a lot with my system and in the process have removed all the parts and re-assembled them many times. Damage to the motherboard may have occurred during those times.

(Not related really but,) I've seen old (dinosaur) HP machines refuse to boot because a modem card was in a certain slot. Move it over one slot and the machine would boot fine. (It's) just that certain hardware in certain machines can/will cause anomalies.

I tried this before; changing positions of the sound and ethernet card. But that didnt help.

Anyways, thanks for replying. I think its a hardware problem. You can close this thread if you want.