Blue Screen of Death

  • Thread starter Thread starter Alberto & Silvia
  • Start date Start date
A

Alberto & Silvia

Hello,I am getting the BSOD every few days,and I am wondering if anybody
here could give me some pointers.
This is the message I am getting:

Address: win32K.sys BF80AA51 base at BF800000, date stamp 43446a58

Stop: 0X0000008E(0XC0000005, 0Xbf 80AA51, 0XED7B9824, 0X00000000)

Thanks for any information

Alberto
 
Read this MS article KB834450 which in part says:

To resolve this problem, obtain the latest service pack for Microsoft
Windows XP. For additional information, click the following article number
to view the article in the Microsoft Knowledge Base: 322389 How to obtain
the latest Windows XP service pack
rgds
Roberto
 
Hi Alberto,

When? Is there any pattern as to timing, software in use, etc?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Alberto said:
Hello,I am getting the BSOD every few days,and I am wondering if anybody
here could give me some pointers.
This is the message I am getting:

Address: win32K.sys BF80AA51 base at BF800000, date stamp 43446a58

Stop: 0X0000008E(0XC0000005, 0Xbf 80AA51, 0XED7B9824, 0X00000000)

Thanks for any information

Alberto
Click to expand...

http://aumha.org/win5/kbestop.htm
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
 
Thanks everyone for the responses.

Rick,the problem has happened at least a couple of time when using MSN
Messenger and Skype.

I am in the process of getting the Service Pack 2 and have read the valuable
information mentioned by some of you.
Thanks again
Regards

Alberto
 
It is a RAM error. Follow step one below, review the logs and see if there are any outstanding error messages.

General Troubleshooting of STOP Messages:

If you can’t find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.

1. Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.

2. If you’ve recently added new hardware, remove it and retest.

3. Run hardware diagnostics supplied by the manufacturer.

4. Make sure device drivers and system BIOS are up-to-date.

5. However, if you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.

6. Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.

7. Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn’t, then pay particular attention to the non-HCL hardware in your troubleshooting.

8. Check for viruses.

9. Investigate recently added software.

10. Examine (and try disabling) BIOS memory options such as caching or shadowing.
 
Back
Top