DSL update and another issue

To refresh those who helped me fix my protocol problem...,
When we tried installing the DSL modem, there were no protocols to bind the
adaptor to. Through several attempts Mike told me that I had a bunch of
missing .inf files. Now, all .inf files from those .cab files that also
were copied from the ME disk are on this machine and the Windstream guy is
coming to try again tomorrow sometime between 1-5 pm.

I'm now having a start-up issue that's driving me insane. The boot process
gets all the way up just before the desktop, then a BSOD appears saying that
the computer needs to be re-started. So, I do and the start-up menu comes
and I'm able to boot to safe mode. I let it scandisk and then reboot and by
some miracle it boots into regular mode.

I've uninstalled Spybot because I've heard that it could cause this problem
but that didn't work, I reduced the size of SR because that can cause this,
but that didn't work, and I've uninstalled some unofficial patches from
MDx's site and that didn't work. A modem driver file that I've disabled
from start in msconfig hasn't gone away. Is it possible that I've got a
driver issue?

... then a BSOD appears saying that
the computer needs to be re-started.

Is that all it says - no error code?

.. A modem driver file that I've disabled
from start in msconfig hasn't gone away.
Is it possible that I've got a
driver issue?

Quite possible. (But not necessarily the modem)

You could try Starting in Safe Mode (F8 key) and select option 4 -
Step-by-step Confirmation - from the menu.
Answer Yes (y) to each request, being sure to create a startup log (2nd
request)
Note whether the 'disabled' modem driver is included - and for the time
being, answer 'yes'. Try again later and answer 'no' - Any difference?

Take a look at the BOOTLOG.TXT file - located in the root folder (C:\) using
Notepad. Any clues there? (look towards the end of the file)

Mart



"SSJ04 Mewtwo" wrote in message
...
To refresh those who helped me fix my protocol problem...,
When we tried installing the DSL modem, there were no protocols to bind
the
adaptor to. Through several attempts Mike told me that I had a bunch of
missing .inf files. Now, all .inf files from those .cab files that also
were copied from the ME disk are on this machine and the Windstream guy is
coming to try again tomorrow sometime between 1-5 pm.

I'm now having a start-up issue that's driving me insane. The boot
process
gets all the way up just before the desktop, then a BSOD appears saying
that
the computer needs to be re-started. So, I do and the start-up menu comes
and I'm able to boot to safe mode. I let it scandisk and then reboot and
by
some miracle it boots into regular mode.

I've uninstalled Spybot because I've heard that it could cause this
problem
but that didn't work, I reduced the size of SR because that can cause
this,
but that didn't work, and I've uninstalled some unofficial patches from
MDx's site and that didn't work. A modem driver file that I've disabled
from start in msconfig hasn't gone away. Is it possible that I've got a
driver issue?

Mart wrote:

Is that all it says - no error code?

Correct. I removed the modem driver and let Windows find it again, but this
morning it did it again. I'll do what you suggested and report back later.

--
So says the cat

Just did it Mart, but it didn't create that bootlog file you said it would.

I checked msconfig again and found two disabled entries of load power
profile. I enabled the one nearest the bottom and had to go into the
registry to get rid of the other. After getting rid of the invalid reg
entry it booted fine. That's the other thing about this problem, it'll do
it up to three to four times, but on some restarts it will boot normally.
It seems to be at its worse when the machine is first turned on in the
mornings.

Hmm... Firstly, it's very odd that it doesn't give an detailed error
report/code (other than tell you to restart your computer) at your BSOD. I
just wonder if it really is a BSOD or more likely the 'completion
report/command' following a (bad?) driver installation utility.

Secondly, you say that it didn't create the bootlog.txt file.

Assuming you tried the step-by-step confirmation AND you opted to create the
startup log, I am at a loss as to where it can be (or why it's not there!)
It *should* be in the C:\ folder (along with autoexec.bat and config.sys,
etc.). I don't have an answer to that issue. NB - There may also be a copy
of bootlog.prv (the previous copy of bootlog.txt) in the C:\ folder but
you'll have to rename it with a .txt suffix to read it in Notepad.

Under the circumstances, check Device Manager in SAFE MODE and look for
duplicate (modem?) drivers and/or yellow exclamation/question marks. If any,
'Remove' any/all items shown and reboot and re-install (fresh copies) of any
drivers requested.

Sounds like you *may* just have a bad/corrupted driver installation.

BTW - I don't think you need to mess with the two power profile entries.
IIIRC they are there by design.

Mart



"SSJ04 Mewtwo" wrote in message
...
Just did it Mart, but it didn't create that bootlog file you said it
would.

I checked msconfig again and found two disabled entries of load power
profile. I enabled the one nearest the bottom and had to go into the
registry to get rid of the other. After getting rid of the invalid reg
entry it booted fine. That's the other thing about this problem, it'll do
it up to three to four times, but on some restarts it will boot normally.
It seems to be at its worse when the machine is first turned on in the
mornings.

... on some restarts it will boot normally.
It seems to be at its worse when the machine
is first turned on in the mornings.

Hmm ... FWIW - Something else I've witnessed but never managed to
technically *prove*.

Cold (first boot of the day) starts on *some* 'older' HDD's appear to be
sluggish - like the bearings are cold. Second and subsequent bootings have
'warmed-up' the bearings and the drive runs at the correct speed. My
personal method of 'proof' has been substitution of the HDD.

Mart

Mart wrote:
Under the circumstances, check Device Manager in SAFE MODE and look for
duplicate (modem?) drivers and/or yellow exclamation/question marks. If any,
'Remove' any/all items shown and reboot and re-install (fresh copies) of any
drivers requested.

Would that also include removing the modem from WDM Modem Enumerator as well
as "Modem" in device manager?

Ah! .. From here, it sounds like you've got (at least) a couple of drivers
'installed' for the same modem. So yes, 'Remove' any/all modem drivers in
Dev Man in Safe Mode.

Off out - won't be able to continue till late tonight.

Mart


"SSJ04 Mewtwo" wrote in message
...
Mart wrote:
Under the circumstances, check Device Manager in SAFE MODE and look for
duplicate (modem?) drivers and/or yellow exclamation/question marks. If
any,
'Remove' any/all items shown and reboot and re-install (fresh copies) of
any
drivers requested.

Would that also include removing the modem from WDM Modem Enumerator as
well
as "Modem" in device manager?

Mart wrote:
... on some restarts it will boot normally.
It seems to be at its worse when the machine
is first turned on in the mornings.

Hmm ... FWIW - Something else I've witnessed but never managed to
technically *prove*.

Cold (first boot of the day) starts on *some* 'older' HDD's appear to
be sluggish - like the bearings are cold. Second and subsequent
bootings have 'warmed-up' the bearings and the drive runs at the
correct speed. My personal method of 'proof' has been substitution of
the HDD.


Had that with a chipset fan for quite a while - made a dreadful racket 1st
boot of a chilly morn. In those days I'd regularly remove the fan, invert
it, peel back the label that covered the center and give a quick blast of
WD40 at the bearing race. However I would think once an HDD is doing that it
would be a good idea to replace it asap.

Archie

Some ISPs have stopped trying to install DSL on old OSs. Their current
software is incompatible. You might need an old router and software.
--
Corday


"SSJ04 Mewtwo" wrote:

To refresh those who helped me fix my protocol problem...,
When we tried installing the DSL modem, there were no protocols to bind the
adaptor to. Through several attempts Mike told me that I had a bunch of
missing .inf files. Now, all .inf files from those .cab files that also
were copied from the ME disk are on this machine and the Windstream guy is
coming to try again tomorrow sometime between 1-5 pm.

I'm now having a start-up issue that's driving me insane. The boot process
gets all the way up just before the desktop, then a BSOD appears saying that
the computer needs to be re-started. So, I do and the start-up menu comes
and I'm able to boot to safe mode. I let it scandisk and then reboot and by
some miracle it boots into regular mode.

I've uninstalled Spybot because I've heard that it could cause this problem
but that didn't work, I reduced the size of SR because that can cause this,
but that didn't work, and I've uninstalled some unofficial patches from
MDx's site and that didn't work. A modem driver file that I've disabled
from start in msconfig hasn't gone away. Is it possible that I've got a
driver issue?