Blue Screen On Shutdown

[Guest]

I just started getting this blue screen on shutdown that says something about
a corrupted driver or software. It says to check newly installed hardware or
software. I installed a new monitor, a usb wireless adapter and a wireless
logitech keyboard mouse in the past few days. They all work grerat and I
looked under device manager for improperly working devices/drivers and seen
nothing. It also says I may need a Windows Update. I do not let my pc do
automatic updates since the worm years ago. I have WinXP Home. My pc runs
smoothly except for the screen on shutdown. At the bottom of the screen it
says something about physical memory dump with some kind of a timer that the
numbers are getting larger instead of smaller. Thanks.

 

[Brian A.]

If it shutdown properly without issue before adding the new hardware:
Boot to Safe Mode > Device Manager.
Uninstall any/all devices listed under the Device types you recently installed.

Close out of DM and open either Explorer or MyComputer.
Navigate to and delete the contents of:
C:\Documents and Settings\Your user name folder\Local Settings\Temp
C:\Windows\Temp
C:\Windows\Prefetch

I just started getting this blue screen on shutdown that says something about
a corrupted driver or software. It says to check newly installed hardware or
software. I installed a new monitor, a usb wireless adapter and a wireless
logitech keyboard mouse in the past few days. They all work grerat and I
looked under device manager for improperly working devices/drivers and seen
nothing. It also says I may need a Windows Update. I do not let my pc do
automatic updates since the worm years ago. I have WinXP Home. My pc runs
smoothly except for the screen on shutdown. At the bottom of the screen it
says something about physical memory dump with some kind of a timer that the
numbers are getting larger instead of smaller. Thanks.

Shutdown and remove the devices except for the monitor.
Boot up, if everything runs smoothly shutdown and see if the problem exists.
If it does exist uninstall it in DM, shutdown and remove the device.
If it doesn't exist, shutdown and add another device.
Boot up, if everything runs smoothly shutdown and add another device.
See above for If/If not.

If no joy, post back with the exact error verbatim you get when shutting down.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Guest]

Also, near the bottom of the screen I get this Technical Info.:
***STOP: 0x000000C5 (0X589B2061, 0x00000002, 0x00000000, 0x8054B88F)

 

[Ron Martell]

Also, near the bottom of the screen I get this Technical Info.:
***STOP: 0x000000C5 (0X589B2061, 0x00000002, 0x00000000, 0x8054B88F)

The name of your error code is DRIVER_CORRUPTED_EXPOOL and Microsoft
defines it as "This indicates that the system attempted to access
invalid memory at a process IRQL that was too high."

The error originated with the device driver or other component that is
using memory address 0x8054B88F. There is a method of tracing this
but it is a bit cumbersome and requires the use of Excel or other
spreadsheet software.

Try getting the latest driver updates for your new hardware from the
manufacturer's web sites and see if that resolves the issue. If the
problem persists and you want to trace if further post a reply back
here and I will send the instructions.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Hi Ron. Thanks for the post. I tried the updated drivers and still get the
same thing. I have noticed that I get a different set of #'s/letters on
shutdowns. It's the same blue screen, literature, and style of code, etc, but
different #'s or letters time to time. I guess it's a different location or
something. I guess I need to try the method you were speaking of. I will be
greatful if you post the instructions. Thanks.

Raymond

 

[Ron Martell]

Hi Ron. Thanks for the post. I tried the updated drivers and still get the
same thing. I have noticed that I get a different set of #'s/letters on
shutdowns. It's the same blue screen, literature, and style of code, etc, but
different #'s or letters time to time. I guess it's a different location or
something. I guess I need to try the method you were speaking of. I will be
greatful if you post the instructions. Thanks.

Raymond

Hi Raymond.

As a general guide if the error code and/or parameters are different
with each error message then that indicates that a hardware related
cause is the more likely suspect. Software related errors, including
those caused by device drivers, generally tend to be more consistent -
the STOP code and all 4 parameters will be the same each time.

This is not a hard and fast rule, but rather a general guide as to
which aspect to check first when these errors occur.

Here are the instructions for tracing an error caused by a device
driver:

Identifying the cause of STOP errors using PSTAT & Excel

Many times when a STOP error occurs the information provided does not
specifically identify the application, device driver, or other
component file where the error occurred. However the 4 parameters
associated with the STOP (bugcheck) code will very often include one
that is the address where the error occurred. You first need to look
up the detailed information about the specific STOP code in order to
determine if the address is included and if so which of the 4
parameters has the address.

You can identify the meaning of each of the parameters for your
specific STOP code at:
http://msdn2.microsoft.com/en-us/library/ms789516.aspx

The second step in the procedure is to identify the addresses that
each active process is being loaded at. The PSTAT utility will
provide this information. On some systems the PSTAT utility may
already be present. Check this by opening a Command Prompt window
(Start - Run - CMD) and entering the following command:

PSTAT /?

If PSTAT is not on your computer you can download it free from
Microsoft. The download is called "Windows XP Service Pack 2 Support
Tools" and it is available from
http://www.microsoft.com/downloads/...76-9BB9-4126-9761-BA8011FABF38&displaylang=en
With PSTAT installed on your computer the next step is to open a
Command Prompt window again (Start - Run - CMD) and generate a report
with PSTAT. Because you need to copy part of the information from
this report (and only part) it is best to create the report as a text
file. In the Command Prompt window enter the following command:

PSTAT > C:\JUNK\PSTAT.TXT

You may change C:\JUNK\ to whatever drive and folder that you want to
save the report into.

Now open the saved file in Notepad. Start - Run - NOTEPAD
C:\JUNK\PSTAT.TXT

Scroll down the file, about 80% of the way to the end of the file and
you will find a head line:

ModuleName Load Addr Code Data Paged LinkDate

It is the information from this line to the end of the file that we
want to copy from this file and save as a separate file. Select the
block of text and copy it to the clipboard. Open a new notepad window
and paste the clipboard contents into it. Save this file under a
different name. I use PSTAT2.TXT and put it into the same C:\JUNK
folder.

Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT
file into Excel. Excel will automatically parse the file into
columns. Once this is done use DATA - SORT to sort the entire
spreadsheet based on the value in Column B (Load Addr).

It is now a simple task to read down the addresses until you find the
highest value that is less than the address where the error occurred.
That module (name in column A) is the prime suspect for the cause of
your error.


Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."