blue screen error - registry cleaner can help?

On Fri, 30 Oct 2009 21:39:37 -0400
Paul <nospam@needed.com> wrote:

> AG wrote:
> > my laptop keeps on giving me a blue screen saying that "dump of
> > physical memory begins"... the strange thing about it is that it
> > depends whether my wireless is on or off. when it is on, i usually
> > get the blue screen right after windows starts up or a bit later
> > (when i m working on something). also it does not occur at all
> > wireless hot spots. somehow this error is not really consistent...
> > i searched the internet about this error and found that some posts
> > about registry cleaners -
> > http://www.goarticles.com/cgi-bin/showa.cgi?C=2110416 - talk about
> > the "blue screen of death" and that a registry cleaner can actually
> > fix it. i tried various fixes and seems like nothing really rids my
> > laptop of the blue screen error. maybe i should buy a new laptop or
> > reinstall windows.
>
> "registry cleaner... buy new laptop... reinstall windows"
>
> These are all rather extreme reactions to a computer problem.
>
> A registry cleaner doesn't really have a purpose, except to
> create extra problems you didn't have before. Any web site
> saying positive things about a registry cleaner, is trying
> to sell you one.
>
> First, start by collecting as much info as possible from
> the original error message. It helps if the driver name
> is stated in the error. If the same driver name appears
> in every error, then that is a strong indication that
> driver has a problem. If the driver names are randomly
> distributed, it could be a problem with the computer
> memory.
>
> Disable automatic restarts, so the blue screen stays put
> long enough for you to copy the information. To disable
> automatic restarts, requires removing the tick from
> the box shown here. This is deep in the System control panel.
>
> http://students.washington.edu/rtlib...ndRecovery.png
>
> ( http://students.washington.edu/rtlibby/bluescreen/ )
>
> If you got a minidump, it can be read with a tool from this download.
> The tool "dumpchk.exe" can read the files in C:\WINDOWS\Minidump .
> I have some minidmp files here, but I don't find the info given
> by the "dumpchk.exe" utility to be very useful. It doesn't seem to
> indicate the faulting module. The "BugCheckCode" field is probably
> the same value as the "Stop" error, so that might be of use to you.
> But the five numbers shown in the Stop error in the blue screen,
> are the same thing.
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> You can look up Stop errors here.
>
> http://aumha.org/a/stop.htm
>
> If it is related to the Wifi, then there might be a later driver
> for the Wifi available. Or it could be that there is a problem
> with the computer memory. You can test computer memory with this.
> This test runs forever, and you want to run it long enough to
> make two complete passes. Test5 used to provide the most
> thorough testing - some of the others seem to be easier to
> pass.
>
> http://www.memtest.org/
>
> To get help, you really need to present the contents of the
> error message.
>
> This is an example of an error message.
>
> Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)
> IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename
>
> The driver name may be printed somewhere in that message. The
> four parameters in brackets, don't always have a useful
> information content (except to someone with additional debugging
> tools), and only occasionally would perhaps the first field
> distinguish between several subtypes of the same error. But
> by presenting all possible information, you may get an
> answer faster.
>
> You could also mention the make and exact model number of the
> laptop. At least then, we could look for a driver for it.
>
> Paul
>
>


There are some wireless adapters that cause the blue screen of death.
SMC is the last one that locked up my wife's system. I'd suggest
before the OP try anything else, buy a linksys brand USB wireless
adapter. -Dave
--
Dave C. <noway@nohow.never>

my laptop keeps on giving me a blue screen saying that "dump of
physical memory begins"... the strange thing about it is that it
depends whether my wireless is on or off. when it is on, i usually get
the blue screen right after windows starts up or a bit later (when i m
working on something). also it does not occur at all wireless hot
spots. somehow this error is not really consistent... i searched the
internet about this error and found that some posts about registry
cleaners - http://www.goarticles.com/cgi-bin/showa.cgi?C=2110416 -
talk about the "blue screen of death" and that a registry cleaner can
actually fix it. i tried various fixes and seems like nothing really
rids my laptop of the blue screen error. maybe i should buy a new
laptop or reinstall windows.

AG wrote:
> my laptop keeps on giving me a blue screen saying that "dump of
> physical memory begins"... the strange thing about it is that it
> depends whether my wireless is on or off. when it is on, i usually get
> the blue screen right after windows starts up or a bit later (when i m
> working on something). also it does not occur at all wireless hot
> spots. somehow this error is not really consistent... i searched the
> internet about this error and found that some posts about registry
> cleaners - http://www.goarticles.com/cgi-bin/showa.cgi?C=2110416 -
> talk about the "blue screen of death" and that a registry cleaner can
> actually fix it. i tried various fixes and seems like nothing really
> rids my laptop of the blue screen error. maybe i should buy a new
> laptop or reinstall windows.

"registry cleaner... buy new laptop... reinstall windows"

These are all rather extreme reactions to a computer problem.

A registry cleaner doesn't really have a purpose, except to
create extra problems you didn't have before. Any web site
saying positive things about a registry cleaner, is trying
to sell you one.

First, start by collecting as much info as possible from
the original error message. It helps if the driver name
is stated in the error. If the same driver name appears
in every error, then that is a strong indication that
driver has a problem. If the driver names are randomly
distributed, it could be a problem with the computer
memory.

Disable automatic restarts, so the blue screen stays put
long enough for you to copy the information. To disable
automatic restarts, requires removing the tick from
the box shown here. This is deep in the System control panel.

http://students.washington.edu/rtlib...ndRecovery.png

( http://students.washington.edu/rtlibby/bluescreen/ )

If you got a minidump, it can be read with a tool from this download.
The tool "dumpchk.exe" can read the files in C:\WINDOWS\Minidump .
I have some minidmp files here, but I don't find the info given
by the "dumpchk.exe" utility to be very useful. It doesn't seem to indicate
the faulting module. The "BugCheckCode" field is probably the same value
as the "Stop" error, so that might be of use to you. But the
five numbers shown in the Stop error in the blue screen,
are the same thing.

http://www.microsoft.com/downloads/d...displaylang=en

You can look up Stop errors here.

http://aumha.org/a/stop.htm

If it is related to the Wifi, then there might be a later driver
for the Wifi available. Or it could be that there is a problem
with the computer memory. You can test computer memory with this.
This test runs forever, and you want to run it long enough to
make two complete passes. Test5 used to provide the most
thorough testing - some of the others seem to be easier to
pass.

http://www.memtest.org/

To get help, you really need to present the contents of the
error message.

This is an example of an error message.

Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)
IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename

The driver name may be printed somewhere in that message. The
four parameters in brackets, don't always have a useful
information content (except to someone with additional debugging
tools), and only occasionally would perhaps the first field
distinguish between several subtypes of the same error. But
by presenting all possible information, you may get an
answer faster.

You could also mention the make and exact model number of the
laptop. At least then, we could look for a driver for it.

Paul

On Sat, 31 Oct 2009 09:27:02 GMT
"SteveH" <steve.houghREMOVE@THISblueyonder.co.uk> wrote:

> Dave C. wrote:
>
> >
> > There are some wireless adapters that cause the blue screen of
> > death. SMC is the last one that locked up my wife's system. I'd
> > suggest before the OP try anything else, buy a linksys brand USB
> > wireless adapter. -Dave
>
> Indeed there are. I fixed a lappy a couple of days ago that was blue
> screening due to its DLink wireless PCMCIA card needing a new driver.
> --
> SteveH
>

I believe that. But I've seen it happen with wireless adapters even
though they had the most recent manufacturer supplied drivers
installed. -Dave

Dave C. wrote:

>
> There are some wireless adapters that cause the blue screen of death.
> SMC is the last one that locked up my wife's system. I'd suggest
> before the OP try anything else, buy a linksys brand USB wireless
> adapter. -Dave

Indeed there are. I fixed a lappy a couple of days ago that was blue
screening due to its DLink wireless PCMCIA card needing a new driver.
--
SteveH