Shut down / log off in XP

I posted some months ago about a problem I had with Windows 2K not shutting down properly. Whenever I attampted to shut down, when the PC would normally power off, it would jump to a blue screen, give an ntoskernel error message and do a physical dump of memory.

A reformat solved the problem, temporarily, and I lived with it from that day forward - logging of as a user and manually switching the pc off. In fact, when I logged off as a user, the second I pressed the power button (had to be helf for 3 - 4 secs to actually power off), the above blue screen/error would appear. Led me to believe this was a hardware, not a software problem.

Today I updated to XP Pro - during the upgrade process, the pc 'rebooted' itself several times, as it does, without any errors. Now that the installation is complete, and I am using it as normal again, whenever I choose 'log off' (not switch user) or 'turn off the computer' - it jumps to a blue screen saying it could be hardware or driver error as detailed in the 'STOP' message!! ??Also, it performs a dump of physical memory to disk.......

Here's the message.....

STOP: 0x0000008E (0x00000005, 0xC0000005, 0x8060E31B, 0xF794DA54, 0x00000000)

It still does the same thing if I choose swith user, then when I press the power button on the pc, it goes to this message and does the phtsical dump of memory

Does this mean anything to anyone - I really am stumped.

Win XP Pro
AMD Athlon XP 2000+
1Gb RAM
Asus A7S333 mb
nVidia (MSI) 4200ti 128Mb
C Media onboard 5.1 sound
DVD ROM
DVD +/- RW
USB 1.1
USB 2.0
Firewire card (generic)
Vivanco "SMART OFFICE KEYBOARD" EZ8000 - USB
****(incidentally, sometimes - when the pc is turned on - it stops with an error saying keyboard not present/found - a 'reset' sorts the problem)****
Microsoft Intellimose Explorer Optical (ps2)
Canon mp360 - USB

Just about covers everything......

stupid question coming ....... does anyone need to see the 'dump' .txt file ??

Thanks in advance

Seany

 

Sounds like you bought over your Win2k problem when you upgraded to WinXP or was it a clean install of WinXP? Cuz if it was it amost sounds like it could be a hardware error not a software error if fresh install.

 

A STOP: 0x0000008E looks to be a RAM error, so I would start by removing one stick (assuming you have 2 sticks?) and rebooting and observe. Will probably need to do the same with the other stick, and observe.

 

I would do as Paul says- experiment with the memory. I think you do have a hardware issue, too, because you carried the stop error over to the new install. Tony T's advice to try a PS2 kb is a smart idea, too. Also, check your temperatures, either from the BIOS or MotherboardMonitor

Post back and let us know what you find out.

Johanna

 

Check the BIOS

seany202,

Check your BIOS Setup looking at all power off settings, making sure they're what you want. I can't find you mobo manual online; please post a url if you know one ( looked on asus usa). You should also check your BIOS date and version and make sure you have the latest.

 

http://www.asus.com.tw/support/download/item.aspx?ModelName=A7S333&Type=All&SLanguage=en-us

URL for my mobo handbook

My bios is latest - 1006

 

oh, another thing.........

My spybot S&D wasnt working

I uninstalled it - rebooted - and then downloaded it again and installed!

Still not working!

Starts up and immediately shuts down - within a second!!

 

Spybot will do that disappearing act if you change the default Windows Focus settings with TweakUI or some other program or registry hack, to eliminate the click when moving the mouse to bring the window into focus. I don't think it's a consistent problem, but I have seen it on a few computers.

Johanna

 

These make too many points to post. Take a look.

seany202,

Thanks for the reference; I'm still studying it.

Google found a lot of related pages, for example:
“STOP†ERROR MESSAGES AT SHUTDOWN
"Stop 0x9F and Stop 0x8E are two of the most common of these at shutdown, and generally point to a bad driver."

This kb article also provides suggestions for troubleshooting STOP messages and states that "STOP messages literally mean Windows has stopped! These appear only in the NT-based operating systems: Win NT, Win 2000, and Win XP. Most are hardware issues. "

 

I used to get that same blue screen at random times when I had Zone Alarm for my firewall. The true vector engine, or service, that ZA uses was fubared. I got rid of ZA and not only did fix the one problem but other's too. Might check into this if you use ZA and still have the problem.

One other thing. The next time this happen's, if it still is, check the event viewer and see what errors ar listed in the applications and system files.

 

In order to figure out the cause of this, you need to crack the bugcheck code.

STOP: 0x0000008E (0x00000005, 0xC0000005, 0x8060E31B, 0xF794DA54, 0x00000000)

(looking at this, there is a typo, the first DWORD is invalid, i think you meant for it to look like this:

STOP: 0x0000008E (0xC0000005, 0x8060E31B, 0xF794DA54, 0x00000000)

This lines up. Using the debuggers.chm from the debugger package, there is an easy lookup table.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved


So, you got a kernel mode access violation from the instruction at 8060e31b. In the dump that was generated, you will find the trap frame for further analysis at f794da54. So basically, this is a dr watson in kernel.

The unfortunate part is that 8060e31b is in NTOSKRNL, which means that it was a victim of another driver passing in bad data. I would expect that you will find this to be a bad 3rd party driver, not a hardware issue. Especially if it reproduces with the same error code.

If you are feeling saucy, you can load the dump under the debugger and !analyze -v it, to see which driver is on the stack (almost certainly an OEM driver) and then whack that. If thats too scary, just give microsoft tech support a call and they can help you read it.