xp pro blue screen

[Jim]

--
My xp pro dsl computer was running extremely slow so I when tothe hard
drive, right clicked chose properties/tools/ and then checked the boxes to
fix files/errors on start up -rebooted....and it went thru the process of
checking the 5 steps....however, after it did that - it just stayed there -
so I rebooted - now - it continues to go to the check screen - and I
canceled the disk checking - however, that just hangs - if I press the
reboot button (soft or hard) nothing happens - it won't do anything- I've
pressed escape ect..nothing happens - so I have to manually pull the
plug...yikes! Then next time I turn it on it gives me the screen with error
" STOP and the error # is 0x00000071 (0x00000000 000000000 0x00000000
0x00000000)

then I have to reboot and then I'm back at the checking file system screen
again ... I've tried to reboot from cd - but it seems to bypass that ...I've
also gotten the screen about windows not shutting down properly and to
choose which way I want to reboot - safe mode ect...however, the up and down
keys on my computer don't do anything to change the process and so it starts
windows normally - I've also tried hitting the f8 key to boot in safe mode -
but it doesn't do anything either.

any helpwould GREATLY be appreciated - I've been working on it for 5 hours
now ... andhave no clue where to go from here. I'm working from my husband's
computer right now.

thanks!

Pam

 

[Ron Martell]

My xp pro dsl computer was running extremely slow so I when tothe hard
drive, right clicked chose properties/tools/ and then checked the boxes to
fix files/errors on start up -rebooted....and it went thru the process of
checking the 5 steps....however, after it did that - it just stayed there -
so I rebooted - now - it continues to go to the check screen - and I
canceled the disk checking - however, that just hangs - if I press the
reboot button (soft or hard) nothing happens - it won't do anything- I've
pressed escape ect..nothing happens - so I have to manually pull the
plug...yikes! Then next time I turn it on it gives me the screen with error
" STOP and the error # is 0x00000071 (0x00000000 000000000 0x00000000
0x00000000)

then I have to reboot and then I'm back at the checking file system screen
again ... I've tried to reboot from cd - but it seems to bypass that ...I've
also gotten the screen about windows not shutting down properly and to
choose which way I want to reboot - safe mode ect...however, the up and down
keys on my computer don't do anything to change the process and so it starts
windows normally - I've also tried hitting the f8 key to boot in safe mode -
but it doesn't do anything either.

any helpwould GREATLY be appreciated - I've been working on it for 5 hours
now ... andhave no clue where to go from here. I'm working from my husband's
computer right now.

thanks!

Pam

The name of your error is SESSION5_INITIALIZATION_FAILED and it is
rather a rare beastie.

The documentation available from Microsoft for this error just
includes the name and the following comment:

"The SESSION5_INITIALIZATION_FAILED bug check has a value of
0x00000071. This indicates that the Windows initialization failed."

And that is it. No mention of possible causes or of how to recover
from it.

Can you boot the computer into Safe Mode? To start the computer in
Safe Mode turn it on and start tapping the F8 key rapidly just as soon
as the first information of any kind shows on the screen. Keep
tapping rapidly until the Windows XP Startup Menu appears and choose
Safe Mode from the menu.

If it will start up in Safe Mode use System Restore (in Accessories -
System Tools) and choose the most recent restore point that is prior
to your hard drive cleanup attempt.

Good luck


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

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

 

[Pam]

Interesting solution -

I was going to send the pc out the window tonight .. .or to the pcgod in the
am if it lasted that long ... as when I would get this screen - I could not
get out - everytime it rebooted it would go back to this screen.....and the
keyboard didn't seem to do anything (its a remote keyboard) so on a WHIM I
plugged in my husband's keyboard to my tower and rebooted - held breath and
my keyboard WORKED!!! I was able to choose SAFE MODE and then booted into
that - then rebooted normally - and wow I'm now busy backing up stuff - it's
working normally.

All this began when I have been trying to fix my fp2003 program - it all of
the sudden would not allow me to publish/use the 'localhost' - I had
uninstalled and reinstalled numerous times my IIS, fp2003 ect ect... nothing
worked - and nothing is working on that end yet - I can open fp2003 and use
my documents/mywebs - but not the localhost feature - I've got a thread a
mile long on the frontpageclient newsgroup - all to no avail at this point.

but wanted to pass my info on on the bluescreen - I'm sure I'm not out of
the woods yet - and it will probably pop up again - but at least I'll have
backed up stuff

if you have any clues ideas ect - please let me know - I'd also like to know
how to clean up my registry - maybe that has too many deleted program files
floating around -

thanks
Pam

 

[Ron Martell]

if you have any clues ideas ect - please let me know - I'd also like to know
how to clean up my registry - maybe that has too many deleted program files
floating around -

Don't fret about the registry status. It is just a text based
database and Windows XP does a pretty good job of housekeeping with
it.

If you have uninstalled these programs using the uninstall function
that came with that program or by using Control Panel - Add/Remve
Programs then there is rarely anything substantive left behind in the
registry, although a few orphan entries may still remain. But almost
certainly nothing that is going to interfere with the normal operation
of the computer or trigger error conditions such as the one you
reported here earlier.

Good luck

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

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

 

[Pam]

thank you Ron - will breathe a bit easier and not buy another 'help' program
.... just wish I could figure out why all the sudden my pc is running so
slow when opening anything - mostly IE though I guess.... and of course this
stupid fp IIS problem I have

thanks again!

Pam

 

[Ron Martell]

thank you Ron - will breathe a bit easier and not buy another 'help' program
.... just wish I could figure out why all the sudden my pc is running so
slow when opening anything - mostly IE though I guess.... and of course this
stupid fp IIS problem I have

thanks again!

Two main reasons for slow performance:

1. Background "tools and toys" that are using up CPU cycles, leaving
less time for processing of the current task. Press Ctrl+Alt+Delete
to bring up the Windows Task Manager. Go to the Processes tab and
click twice on the CPU column header to sort the list into descending
order based on CPU usage. The "System idle process" (= time when the
computer has nothing to do) should be at the top of the list and
normally would account for 95 to 98 percent of the CPU time. If the
system idle is less than 95% make note of the 4 or 5 other top items
on the list and post that information back here.

2. Insufficient RAM. Windows XP performance is very sensitive to
the amount of RAM, and performance seems to suffer quite badly if and
when Windows XP gets into any significant amount of actual usage of
the paging (=swap) file. Note that the PFUsage figure reported by
Windows Task Manager is basically useless for this type of assessment
as it almost always includes a substantial amount of "phantom" usage.
For example, my own system at this moment is reporting PFUsage as 453
mb. However the actual paging file (pagefile.sys) is only 80 mb in
size, so there is something else that Task Manager is also counting as
PFUsage (and quite legitimately so, based on the definition of PFUsage
that Microsoft uses). But for the purposes of checking on the
adequacy of the current installed amount of RAM what is needed is a
measure of the amount of active memory content that is currently
residing in the pagefile because Windows needed that RAM for other,
currently more important tasks. Again on my system, that value at
the moment is 39 mb. The utility that I use to find out this
information was written by MVP Bill James and can be downloaded from
http://www.dougknox.com/xp/utils/xp_pagefilemon.htm

If that utility reports actual Pagefile usage (as I have desribed it
above) as more than 50 mb on a regular basis then it is quite likely
that your computer's performance would benefit from having additional
RAM.

Good luck

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

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

 

[Pam]

thank you so much for trying to help with this problem!

your #1 ... clicked twice on CPU and boy it changes so fast - the first one
is System Idle Process and changes quickly from 98 to 94 to 92 to 96 back to
98 .... the next things are explorer - 02; zlcient ; cidaemon.exe;
svchost.exe; and a point 32.exe keeps popping up to #2 spot as well as
msimm.exe - something keeps popping up to #2 spot with a 31 to 48 but I
can't catch it it goes so fast...not sure what it is ... did try the link
you gave below but keep getting a page not displayed - will see if I can
find it though

thanks
Pam

 

[Ron Martell]

thank you so much for trying to help with this problem!

your #1 ... clicked twice on CPU and boy it changes so fast - the first one
is System Idle Process and changes quickly from 98 to 94 to 92 to 96 back to
98 .... the next things are explorer - 02; zlcient ; cidaemon.exe;
svchost.exe; and a point 32.exe keeps popping up to #2 spot as well as
msimm.exe - something keeps popping up to #2 spot with a 31 to 48 but I
can't catch it it goes so fast...not sure what it is ... did try the link
you gave below but keep getting a page not displayed - will see if I can
find it though

With the System Idle process in the high nineties it is not likely to
be background software that is bogging down your system.

I just tried the link to the Page File Monitor web site and it works
okay for me.

Good luck

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

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

 

[Pam]

I ran the page utility thing and it says:

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 30 MB
Session Peak Usage: 31 MB
Current Pagefile Size: 768 MB


what do you think?

Pam

 

[Pam]

just had anohter blue screen death - was listening to live video via
webcast - no problems ... a nd all of the sudden crash - error was:

0x0000008E (ox80000004, ox8056a13c, oxf8925c8c, ox00000000)

have been googling to find out what it could be - but no luck so far - any
help?

Pam

 

[Ron Martell]

I ran the page utility thing and it says:

Pagefile Physical Location: C:\pagefile.sys
Current Pagefile Usage: 30 MB
Session Peak Usage: 31 MB
Current Pagefile Size: 768 MB


what do you think?

There is only 31 mb of active memory content in the pagefile. That is
not enough to indicate that you would likely get a subtantial
performance boost by adding more RAM. But check it periodically,
especially when you have a normal "full set" of applications open. If
it gets up to 100 mb or even close to it then you might want to
consider more RAM.

Good luck

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

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

 

[Ron Martell]

just had anohter blue screen death - was listening to live video via
webcast - no problems ... a nd all of the sudden crash - error was:

0x0000008E (ox80000004, ox8056a13c, oxf8925c8c, ox00000000)

have been googling to find out what it could be - but no luck so far - any
help?

You posted this same error message under another subject. See my
reply there.

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

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

 

[Pam]

I did? I've looked - I can't find the answer - was it in this thread? I've
looked ... pls tell me where or copy/paste your answer to this thread if you
have time - thanks

Pam

 

[Ron Martell]

I did? I've looked - I can't find the answer - was it in this thread? I've
looked ... pls tell me where or copy/paste your answer to this thread if you
have time - thanks

****
Here it is.

I've had 2 blue screen deaths - the first I don't remember what I was
doing - and I got this error:

STOP ox0000008E, ox80000004, 0x8056A13C, oxF2452c82, ox00000000

and the other one was when I had nothing running except ZA and AVG in the
background - and I tried to run the Norton online virus scanner

then it said

STOP ox0000008E, ox80000004, 0x8056A13C, oxf4015c8c, ox00000000

can someone help me with this please?

Pam

Your error code is named KERNEL_MODE_EXCEPTION_NOT_HANDLED. Parameter
1 indicates that the specific exception code involved was
STATUS_SINGLE_STEP and Parameter 2 says that the error originated at
memory address 0x8056A13C.

This type of error is most often caused by a defective device driver
or by incompatible hardware. Have you made any recent changes to the
computer that involved either updating drivers for existing hardware
and/or installing new hardware?

There is a method by which the driver or component using the error
address can be identified but it is a bit cumbersome. If the answer
to the above question does not provide a clue then we will proceed
with identifying the item from the memory address.

Good luck

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

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

 

[Pam]

thank you so much Ron! no I couldn't find that email/reply - thank you - no
I have not installed any new hardware whatsoever - however I did go to
Microsoft's page and installed the recommended updates....

thanks

Pam

 

[Ron Martell]

thank you so much Ron! no I couldn't find that email/reply - thank you - no
I have not installed any new hardware whatsoever - however I did go to
Microsoft's page and installed the recommended updates....

thanks

There seems to be a bit of a rash of these STOP 0x0000008E errors
recently, but I can't find any common factors so it may just be a
coincidence.

We need to find out what item (Windows component, driver, etc) is
using address 0x8056a13c

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
last 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.

Note: If you do not have Microsoft Excel available then you can email
the PSTAT2.TXT file to me as an attachment and I will check it out.

Good luck






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

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