Hello first!

I have this AMD 1.3Ghz that, for as long as I can remember, got problem
starting "cold" in the morning (after being turned off for a couples of hours
at least)... it never got problem restarting nor coming back from stanby
mode. The problem is that I get a blue screen error message (and dumping
physical mem) and/or it just hang at different stage of the startup (and I
have to hit the reset button)... and it will restart by itself say two to
tree time to started correctly and completly without problem.

The message (blue screen) I get (the one that I actually been able to write
down!) is (if correctly wrote):

DRIVERE_IRQL_NOT_LESS_OR_EQUAL

Check to make sure any new hardware or software is properly installed...

STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)

Beginining dumping physical mem...

If the problem continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing...

I do have recently make a complete full clean installed and since only have
the VERY necessary programs installed (bare minimum)...

So, what's about it?!

I have'nt yet foundede any relevant info about this blue screen message on
the Microsoft search...

I tend to think that it's about hardware because it's only when the PC has
been off (shut down or hibernating) and not on restart or coming back from
stanby...

I hope I have included all the relevant info...?!

Thanks in advance for any help!

Paco 8-)

Have you worked your way through:
http://aumha.org/win5/kbestop.php#0x0a
--
Cari (MS-MVP)
Windows Technologies, Printing & Imaging
http://www.coribright.com/windows


"Paco" <Paco@discussions.microsoft.com> wrote in message
news:B4448F70-9587-4E07-BEB3-D106DE85C2C6@microsoft.com...
> Hello first!
>
> I have this AMD 1.3Ghz that, for as long as I can remember, got problem
> starting "cold" in the morning (after being turned off for a couples of
> hours
> at least)... it never got problem restarting nor coming back from stanby
> mode. The problem is that I get a blue screen error message (and dumping
> physical mem) and/or it just hang at different stage of the startup (and I
> have to hit the reset button)... and it will restart by itself say two to
> tree time to started correctly and completly without problem.
>
> The message (blue screen) I get (the one that I actually been able to
> write
> down!) is (if correctly wrote):
>
> DRIVERE_IRQL_NOT_LESS_OR_EQUAL
>
> Check to make sure any new hardware or software is properly installed...
>
> STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)
>
> Beginining dumping physical mem...
>
> If the problem continue, disable or remove any newly installed hardware or
> software. Disable BIOS memory options such as caching or shadowing...
>
> I do have recently make a complete full clean installed and since only
> have
> the VERY necessary programs installed (bare minimum)...
>
> So, what's about it?!
>
> I have'nt yet foundede any relevant info about this blue screen message on
> the Microsoft search...
>
> I tend to think that it's about hardware because it's only when the PC has
> been off (shut down or hibernating) and not on restart or coming back from
> stanby...
>
> I hope I have included all the relevant info...?!
>
> Thanks in advance for any help!
>
> Paco 8-)

Not much of any help so for from this link Cari, but I'll do some homework...
still, thanks!

Keep it coming...

Paco

"Cari (MS-MVP)" wrote:

> Have you worked your way through:
> http://aumha.org/win5/kbestop.php#0x0a
> --
> Cari (MS-MVP)
> Windows Technologies, Printing & Imaging
> http://www.coribright.com/windows
>
>
> "Paco" <Paco@discussions.microsoft.com> wrote in message
> news:B4448F70-9587-4E07-BEB3-D106DE85C2C6@microsoft.com...
> > Hello first!
> >
> > I have this AMD 1.3Ghz that, for as long as I can remember, got problem
> > starting "cold" in the morning (after being turned off for a couples of
> > hours
> > at least)... it never got problem restarting nor coming back from stanby
> > mode. The problem is that I get a blue screen error message (and dumping
> > physical mem) and/or it just hang at different stage of the startup (and I
> > have to hit the reset button)... and it will restart by itself say two to
> > tree time to started correctly and completly without problem.
> >
> > The message (blue screen) I get (the one that I actually been able to
> > write
> > down!) is (if correctly wrote):
> >
> > DRIVERE_IRQL_NOT_LESS_OR_EQUAL
> >
> > Check to make sure any new hardware or software is properly installed...
> >
> > STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)
> >
> > Beginining dumping physical mem...
> >
> > If the problem continue, disable or remove any newly installed hardware or
> > software. Disable BIOS memory options such as caching or shadowing...
> >
> > I do have recently make a complete full clean installed and since only
> > have
> > the VERY necessary programs installed (bare minimum)...
> >
> > So, what's about it?!
> >
> > I have'nt yet foundede any relevant info about this blue screen message on
> > the Microsoft search...
> >
> > I tend to think that it's about hardware because it's only when the PC has
> > been off (shut down or hibernating) and not on restart or coming back from
> > stanby...
> >
> > I hope I have included all the relevant info...?!
> >
> > Thanks in advance for any help!
> >
> > Paco 8-)
>
>
>

Paco wrote:

> Not much of any help so for from this link Cari, but I'll do some
> homework...
> still, thanks!
>
> Keep it coming...
>
> Paco
>
> "Cari (MS-MVP)" wrote:
>
>> Have you worked your way through:
>> http://aumha.org/win5/kbestop.php#0x0a
>> --
>> Cari (MS-MVP)
>> Windows Technologies, Printing & Imaging
>> http://www.coribright.com/windows
>>
>>
>> "Paco" <Paco@discussions.microsoft.com> wrote in message
>> news:B4448F70-9587-4E07-BEB3-D106DE85C2C6@microsoft.com...
>> > Hello first!
>> >
>> > I have this AMD 1.3Ghz that, for as long as I can remember, got
>> > problem starting "cold" in the morning (after being turned off for
>> > a couples of hours
>> > at least)... it never got problem restarting nor coming back from
>> > stanby
>> > mode. The problem is that I get a blue screen error message (and
>> > dumping physical mem) and/or it just hang at different stage of the
>> > startup (and I
>> > have to hit the reset button)... and it will restart by itself say
>> > two to tree time to started correctly and completly without
>> > problem.
>> >
>> > The message (blue screen) I get (the one that I actually been able
>> > to write
>> > down!) is (if correctly wrote):
>> >
>> > DRIVERE_IRQL_NOT_LESS_OR_EQUAL
>> >
>> > Check to make sure any new hardware or software is properly
>> > installed...
>> >
>> > STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)
>> >
>> > Beginining dumping physical mem...
>> >
>> > If the problem continue, disable or remove any newly installed
>> > hardware or
>> > software. Disable BIOS memory options such as caching or
>> > shadowing...
>> >
>> > I do have recently make a complete full clean installed and since
>> > only have
>> > the VERY necessary programs installed (bare minimum)...
>> >
>> > So, what's about it?!
>> >
>> > I have'nt yet foundede any relevant info about this blue screen
>> > message on the Microsoft search...
>> >
>> > I tend to think that it's about hardware because it's only when the
>> > PC has been off (shut down or hibernating) and not on restart or
>> > coming back from stanby...

I agree with you that it is probably hardware. However, first make sure
that you've installed all drivers for your hardware. Never get drivers
from Windows Update. Get them from:

1. The device mftr.'s website; OR
2. The motherboard mftr.'s website if hardware is onboard; OR
3. The OEM's website for your specific machine if you have an OEM
computer (HP, Dell, Sony, etc.).

Read the installation instructions on the website where you get the
drivers.

Once you've done that, I'd do some hardware troubleshooting starting
with the RAM and the power supply. Here are general hardware t-shooting
steps:

1) Open the computer and run it open, cleaning out all dust bunnies and
observing all fans (overheating will cause system freezing). Obviously
you can't do this with a laptop, but you can hear if the fan is running
and feel if the laptop is getting too hot.

2) Test the RAM - I like Memtest86+ from www.memtest.org. Obviously, you
have to get the program from a working machine. You will either
download the precompiled Windows binary to make a bootable floppy or
the .iso to make a bootable cd. If you want to use the latter, you'll
need to have third-party burning software on the machine where you
download the file - XP's built-in burning capability won't do the job.
In either case, boot with the media you made. The test will run
immediately. Let the test run for an hour or two - unless errors are
seen immediately. If you get any errors, replace the RAM.

3) Test the hard drive with a diagnostic utility from the mftr. Download
the file and make a bootable floppy or cd with it. Boot with the media
and do a thorough test. If the drive has physical errors, replace it.

4) The power supply may be going bad or be inadequate for the devices
you have in the system. The adequacy issue doesn't really apply to a
laptop, although of course the power supply can be faulty.

5) Test the motherboard with something like TuffTest from
www.tufftest.com. Sometimes this is useful, and sometimes it isn't.

Testing hardware failures often involves swapping out suspected parts
with known-good parts. If you can't do the testing yourself and/or are
uncomfortable opening your computer, take the machine to a professional
computer repair shop (not your local equivalent of BigStoreUSA).

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

This one is more likely
http://aumha.org/win5/kbestop.php#0xd1

Paco wrote:

> Not much of any help so for from this link Cari, but I'll do some homework...
> still, thanks!
>
> Keep it coming...
>
> Paco
>
> "Cari (MS-MVP)" wrote:
>
>
>>Have you worked your way through:
>>http://aumha.org/win5/kbestop.php#0x0a
>>--
>>Cari (MS-MVP)
>>Windows Technologies, Printing & Imaging
>>http://www.coribright.com/windows
>>
>>
>>"Paco" <Paco@discussions.microsoft.com> wrote in message
>>news:B4448F70-9587-4E07-BEB3-D106DE85C2C6@microsoft.com...
>>
>>>Hello first!
>>>
>>>I have this AMD 1.3Ghz that, for as long as I can remember, got problem
>>>starting "cold" in the morning (after being turned off for a couples of
>>>hours
>>>at least)... it never got problem restarting nor coming back from stanby
>>>mode. The problem is that I get a blue screen error message (and dumping
>>>physical mem) and/or it just hang at different stage of the startup (and I
>>>have to hit the reset button)... and it will restart by itself say two to
>>>tree time to started correctly and completly without problem.
>>>
>>>The message (blue screen) I get (the one that I actually been able to
>>>write
>>>down!) is (if correctly wrote):
>>>
>>>DRIVERE_IRQL_NOT_LESS_OR_EQUAL
>>>
>>>Check to make sure any new hardware or software is properly installed...
>>>
>>>STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)
>>>
>>>Beginining dumping physical mem...
>>>
>>>If the problem continue, disable or remove any newly installed hardware or
>>>software. Disable BIOS memory options such as caching or shadowing...
>>>
>>>I do have recently make a complete full clean installed and since only
>>>have
>>>the VERY necessary programs installed (bare minimum)...
>>>
>>>So, what's about it?!
>>>
>>>I have'nt yet foundede any relevant info about this blue screen message on
>>>the Microsoft search...
>>>
>>>I tend to think that it's about hardware because it's only when the PC has
>>>been off (shut down or hibernating) and not on restart or coming back from
>>>stanby...
>>>
>>>I hope I have included all the relevant info...?!
>>>
>>>Thanks in advance for any help!
>>>
>>>Paco 8-)
>>
>>
>>

Forgive my ignorance but...

I've seen in several newsgroups people saying "Don't get drivers from
Windows Update" - are the drivers on there that bad? or is it just that they
are the M$ generic ones?

"Malke" wrote:

> Paco wrote:
>
> > Not much of any help so for from this link Cari, but I'll do some
> > homework...
> > still, thanks!
> >
> > Keep it coming...
> >
> > Paco
> >
> > "Cari (MS-MVP)" wrote:
> >
> >> Have you worked your way through:
> >> http://aumha.org/win5/kbestop.php#0x0a
> >> --
> >> Cari (MS-MVP)
> >> Windows Technologies, Printing & Imaging
> >> http://www.coribright.com/windows
> >>
> >>
> >> "Paco" <Paco@discussions.microsoft.com> wrote in message
> >> news:B4448F70-9587-4E07-BEB3-D106DE85C2C6@microsoft.com...
> >> > Hello first!
> >> >
> >> > I have this AMD 1.3Ghz that, for as long as I can remember, got
> >> > problem starting "cold" in the morning (after being turned off for
> >> > a couples of hours
> >> > at least)... it never got problem restarting nor coming back from
> >> > stanby
> >> > mode. The problem is that I get a blue screen error message (and
> >> > dumping physical mem) and/or it just hang at different stage of the
> >> > startup (and I
> >> > have to hit the reset button)... and it will restart by itself say
> >> > two to tree time to started correctly and completly without
> >> > problem.
> >> >
> >> > The message (blue screen) I get (the one that I actually been able
> >> > to write
> >> > down!) is (if correctly wrote):
> >> >
> >> > DRIVERE_IRQL_NOT_LESS_OR_EQUAL
> >> >
> >> > Check to make sure any new hardware or software is properly
> >> > installed...
> >> >
> >> > STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)
> >> >
> >> > Beginining dumping physical mem...
> >> >
> >> > If the problem continue, disable or remove any newly installed
> >> > hardware or
> >> > software. Disable BIOS memory options such as caching or
> >> > shadowing...
> >> >
> >> > I do have recently make a complete full clean installed and since
> >> > only have
> >> > the VERY necessary programs installed (bare minimum)...
> >> >
> >> > So, what's about it?!
> >> >
> >> > I have'nt yet foundede any relevant info about this blue screen
> >> > message on the Microsoft search...
> >> >
> >> > I tend to think that it's about hardware because it's only when the
> >> > PC has been off (shut down or hibernating) and not on restart or
> >> > coming back from stanby...
>
> I agree with you that it is probably hardware. However, first make sure
> that you've installed all drivers for your hardware. Never get drivers
> from Windows Update. Get them from:
>
> 1. The device mftr.'s website; OR
> 2. The motherboard mftr.'s website if hardware is onboard; OR
> 3. The OEM's website for your specific machine if you have an OEM
> computer (HP, Dell, Sony, etc.).
>
> Read the installation instructions on the website where you get the
> drivers.
>
> Once you've done that, I'd do some hardware troubleshooting starting
> with the RAM and the power supply. Here are general hardware t-shooting
> steps:
>
> 1) Open the computer and run it open, cleaning out all dust bunnies and
> observing all fans (overheating will cause system freezing). Obviously
> you can't do this with a laptop, but you can hear if the fan is running
> and feel if the laptop is getting too hot.
>
> 2) Test the RAM - I like Memtest86+ from www.memtest.org. Obviously, you
> have to get the program from a working machine. You will either
> download the precompiled Windows binary to make a bootable floppy or
> the .iso to make a bootable cd. If you want to use the latter, you'll
> need to have third-party burning software on the machine where you
> download the file - XP's built-in burning capability won't do the job.
> In either case, boot with the media you made. The test will run
> immediately. Let the test run for an hour or two - unless errors are
> seen immediately. If you get any errors, replace the RAM.
>
> 3) Test the hard drive with a diagnostic utility from the mftr. Download
> the file and make a bootable floppy or cd with it. Boot with the media
> and do a thorough test. If the drive has physical errors, replace it.
>
> 4) The power supply may be going bad or be inadequate for the devices
> you have in the system. The adequacy issue doesn't really apply to a
> laptop, although of course the power supply can be faulty.
>
> 5) Test the motherboard with something like TuffTest from
> www.tufftest.com. Sometimes this is useful, and sometimes it isn't.
>
> Testing hardware failures often involves swapping out suspected parts
> with known-good parts. If you can't do the testing yourself and/or are
> uncomfortable opening your computer, take the machine to a professional
> computer repair shop (not your local equivalent of BigStoreUSA).
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>

On Thu, 22 Dec 2005 02:53:01 -0800, "Mort"
<Mort@discussions.microsoft.com> wrote:

>Forgive my ignorance but...
>
>I've seen in several newsgroups people saying "Don't get drivers from
>Windows Update" - are the drivers on there that bad? or is it just that they
>are the M$ generic ones?

They aren't necessarily bad, just not as good as the manufacturer's own
optimized and tested ones available through their own websites.
--
Michael Cecil
http://home.comcast.net/~macecil/
http://home.comcast.net/~safehex/

Hi

Agreed - download the drivers from the device's manufacturer's web site
instead of using Windows/Microsoft Update. No, they're not 'bad', but the
manufacturer will/should write drivers specifically for their own devices.

--


Will Denny
MS MVP Windows Shell/User
Please reply to the News Groups

"Mort" <Mort@discussions.microsoft.com> wrote in message
news:33047CCD-89E3-437E-A070-5C7160E7CE72@microsoft.com...
> Forgive my ignorance but...
>
> I've seen in several newsgroups people saying "Don't get drivers from
> Windows Update" - are the drivers on there that bad? or is it just that
> they
> are the M$ generic ones?
>
> "Malke" wrote:
>
>> Paco wrote:
>>
>> > Not much of any help so for from this link Cari, but I'll do some
>> > homework...
>> > still, thanks!
>> >
>> > Keep it coming...
>> >
>> > Paco
>> >
>> > "Cari (MS-MVP)" wrote:
>> >
>> >> Have you worked your way through:
>> >> http://aumha.org/win5/kbestop.php#0x0a
>> >> --
>> >> Cari (MS-MVP)
>> >> Windows Technologies, Printing & Imaging
>> >> http://www.coribright.com/windows
>> >>
>> >>
>> >> "Paco" <Paco@discussions.microsoft.com> wrote in message
>> >> news:B4448F70-9587-4E07-BEB3-D106DE85C2C6@microsoft.com...
>> >> > Hello first!
>> >> >
>> >> > I have this AMD 1.3Ghz that, for as long as I can remember, got
>> >> > problem starting "cold" in the morning (after being turned off for
>> >> > a couples of hours
>> >> > at least)... it never got problem restarting nor coming back from
>> >> > stanby
>> >> > mode. The problem is that I get a blue screen error message (and
>> >> > dumping physical mem) and/or it just hang at different stage of the
>> >> > startup (and I
>> >> > have to hit the reset button)... and it will restart by itself say
>> >> > two to tree time to started correctly and completly without
>> >> > problem.
>> >> >
>> >> > The message (blue screen) I get (the one that I actually been able
>> >> > to write
>> >> > down!) is (if correctly wrote):
>> >> >
>> >> > DRIVERE_IRQL_NOT_LESS_OR_EQUAL
>> >> >
>> >> > Check to make sure any new hardware or software is properly
>> >> > installed...
>> >> >
>> >> > STOP: 0X000000D1 (0X918B1AD9,0X000000FF,0X00000000,0X918B1AD9)
>> >> >
>> >> > Beginining dumping physical mem...
>> >> >
>> >> > If the problem continue, disable or remove any newly installed
>> >> > hardware or
>> >> > software. Disable BIOS memory options such as caching or
>> >> > shadowing...
>> >> >
>> >> > I do have recently make a complete full clean installed and since
>> >> > only have
>> >> > the VERY necessary programs installed (bare minimum)...
>> >> >
>> >> > So, what's about it?!
>> >> >
>> >> > I have'nt yet foundede any relevant info about this blue screen
>> >> > message on the Microsoft search...
>> >> >
>> >> > I tend to think that it's about hardware because it's only when the
>> >> > PC has been off (shut down or hibernating) and not on restart or
>> >> > coming back from stanby...
>>
>> I agree with you that it is probably hardware. However, first make sure
>> that you've installed all drivers for your hardware. Never get drivers
>> from Windows Update. Get them from:
>>
>> 1. The device mftr.'s website; OR
>> 2. The motherboard mftr.'s website if hardware is onboard; OR
>> 3. The OEM's website for your specific machine if you have an OEM
>> computer (HP, Dell, Sony, etc.).
>>
>> Read the installation instructions on the website where you get the
>> drivers.
>>
>> Once you've done that, I'd do some hardware troubleshooting starting
>> with the RAM and the power supply. Here are general hardware t-shooting
>> steps:
>>
>> 1) Open the computer and run it open, cleaning out all dust bunnies and
>> observing all fans (overheating will cause system freezing). Obviously
>> you can't do this with a laptop, but you can hear if the fan is running
>> and feel if the laptop is getting too hot.
>>
>> 2) Test the RAM - I like Memtest86+ from www.memtest.org. Obviously, you
>> have to get the program from a working machine. You will either
>> download the precompiled Windows binary to make a bootable floppy or
>> the .iso to make a bootable cd. If you want to use the latter, you'll
>> need to have third-party burning software on the machine where you
>> download the file - XP's built-in burning capability won't do the job.
>> In either case, boot with the media you made. The test will run
>> immediately. Let the test run for an hour or two - unless errors are
>> seen immediately. If you get any errors, replace the RAM.
>>
>> 3) Test the hard drive with a diagnostic utility from the mftr. Download
>> the file and make a bootable floppy or cd with it. Boot with the media
>> and do a thorough test. If the drive has physical errors, replace it.
>>
>> 4) The power supply may be going bad or be inadequate for the devices
>> you have in the system. The adequacy issue doesn't really apply to a
>> laptop, although of course the power supply can be faulty.
>>
>> 5) Test the motherboard with something like TuffTest from
>> www.tufftest.com. Sometimes this is useful, and sometimes it isn't.
>>
>> Testing hardware failures often involves swapping out suspected parts
>> with known-good parts. If you can't do the testing yourself and/or are
>> uncomfortable opening your computer, take the machine to a professional
>> computer repair shop (not your local equivalent of BigStoreUSA).
>>
>> Malke
>> --
>> Elephant Boy Computers
>> www.elephantboycomputers.com
>> "Don't Panic!"
>> MS-MVP Windows - Shell/User
>>

Mort wrote:

> Forgive my ignorance but...
>
> I've seen in several newsgroups people saying "Don't get drivers from
> Windows Update" - are the drivers on there that bad? or is it just
> that they are the M$ generic ones?
>

The "don't use drivers from WU" mantra is based on years of experience.
Here are some reasons:

1. WU doesn't always identify drivers correctly. Install those drivers
and your device will no longer work.
2. OEM's often have specialized hardware and drivers made just for them.
3. Hardware mftrs. write new drivers to enable their device to work with
new software and also to get the absolute best performance out of their
device. The most commonly updated drivers are for the video card (with
the sound card second) and really only hardcore gamers need to do this
regularly.
4.It isn't necessary to update drivers if nothing is broken. A home user
(who isn't playing the latest-greatest computer games) with everything
working properly should just leave his drivers alone.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Malke wrote:
> Mort wrote:
>
>
>>Forgive my ignorance but...
>>
>>I've seen in several newsgroups people saying "Don't get drivers from
>>Windows Update" - are the drivers on there that bad? or is it just
>>that they are the M$ generic ones?
>>
>
>
> The "don't use drivers from WU" mantra is based on years of experience.
> Here are some reasons:
>
> 1. WU doesn't always identify drivers correctly. Install those drivers
> and your device will no longer work.
> 2. OEM's often have specialized hardware and drivers made just for them.
> 3. Hardware mftrs. write new drivers to enable their device to work with
> new software and also to get the absolute best performance out of their
> device. The most commonly updated drivers are for the video card (with
> the sound card second) and really only hardcore gamers need to do this
> regularly.

Case in point: Yesterday I installed a USB 2.0 PCI card in my son's
older PC so he will get best performance when he opens his xmas gift :-)

XP detected the card, loaded drivers, said it was good to go. I checked
device manager, yup, Enhanced USB Hub - yet when I plugged in a thumb
drive, XP popped up the old USB 1.1 routine about the device being able
to perform better yadda yadda - then suggested I move the device to the
port I just connected it to.

There's no manufacturer's web site for this el-cheapo Chinese knockoff,
but installing the chipset manufacturer's latest drivers solved the issue.

Sunny

> 4.It isn't necessary to update drivers if nothing is broken. A home user
> (who isn't playing the latest-greatest computer games) with everything
> working properly should just leave his drivers alone.
>
> Malke