BSOD stop:0x0000005

I keep getting these stop errors. I've had 4 now in the past month or so. At first I did a restore system, and ran a registry clean. Then about a month later I got a stop:0x0000008e. I did a restore again, ran a registry cleaner, it found like 1300 error. The system ran good for about 10 days, then another stop error of 0x0000008e. I did nothing. Just rebooted, and it was good for another month. The first stop error report looks like this.

Stop:0x00000050(0xf1007c2f, 0x00000000,oxbf82ed79,0x00000000)

win32k. sys address bf82ed79 base at bf800000, date stamp 4de797d3

Next
Stop:0x0000008e(0xc0000005,0xbf9552ca,0xb4603c00,0x00000000)
same win32 sys as last error

Next
Stop:0x0000008e(0xc0000005,0xbf955332,0xac3d7c00,0x00000000)
win32k.sys address bf955332 base atbf800000 date stamp 4e661e29

Next
0x0000005(0xe2a7f01c,0x00000000,0xbf82ee1f,0x00000001)
win 32k.sys address bf82ee1f base at bf800000, date stamp 4e661e29

My Who Crashed, program shows


--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: D3JVRMF1
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T5270 @ 1.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145353728 total
VM: 2147352576, free: 2042953728



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 10/27/2011 2:39:22 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102711-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2EE1F)
Bugcheck code: 0x10000050 (0xFFFFFFFFE2A7F01C, 0x0, 0xFFFFFFFFBF82EE1F, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 10/23/2011 5:00:28 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102311-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x155332)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF955332, 0xFFFFFFFFAC3D7C00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Need some help on this problem. Hope I can keep rebooting out of this BSOD, or get this resolved.

Thanks ahead,
RGN

 

net framework 2

I get an error message that I can not continue because this version of .NetFrameWork is incompatible with a previously installed one.

 

Data dump

The down load says it for Windows 7. I have XP, is there a difference between the downloads?

 

Data dump

I get to the installation, there isn't a download named "'debugwiz.zip at the bottom of the page like the the instruction say.

 

When these types of problems occur, it is best to seek help from a place like here. Reg. cleanups can cause more harm than good. I have done them several times with no ill effects. Have done it before and also had to do a CLEAN INSTALL. You can remove all the .NetFramwork updates and then start them over. I have seen where just installing 4 will work without installing the others and seen where it didn't without install the others with the first to the last.

 

It's there at the bottom of the post. Here's a direct link: http://WindowsBBS.com/debugwiz.zip

 

Data dump

Thanks for in heads up, but they should say in the instructions that it's on the Thread. I was so focused on following the word by word, that I over looked it.

 

dump data

Opened log file 'c:debuglog.txt'

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Program Files\Debugging Tools for Windows (x86)\cdb.exe]
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
ModLoad: 01000000 01060000 C:\Program Files\Debugging Tools for Windows (x86)\cdb.exe
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=01042345 esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na po nc
cs=0000 ss=0000 ds=0000 es=0000 fs=0000 gs=0000 efl=00000000
cdb!mainCRTStartup:
01042345 e8e0060000 call cdb!__security_init_cookie (01042a2a)
0:000> !analyze -v;r;kv;lmtn;.logclose;q
.lastevent
Last event: f0f0f0f0.1: Load module C:\Program Files\Debugging Tools for Windows (x86)\cdb.exe at 01000000
debugger time: Fri Oct 28 10:49:52.937 2011 (UTC - 7:00)
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=01042345 esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na po nc
cs=0000 ss=0000 ds=0000 es=0000 fs=0000 gs=0000 efl=00000000
cdb!mainCRTStartup:
01042345 e8e0060000 call cdb!__security_init_cookie (01042a2a)
ChildEBP RetAddr Args to Child
00000000 00000000 00000000 00000000 00000000 cdb!mainCRTStartup (FPO: [0,0,0])
start end module name
01000000 01060000 cdb cdb.exe Mon Feb 01 13:08:18 2010 (4B6734B2)
Closing open log file c:debuglog.txt

 

Data dump

So, what can I do now?

 

Data dump

How long can I expect to have a running laptop, if I can't fix the BSOD's?

 

I don't think anybody can answer that question. Hopefully the next dump will tell something that will help.

 

Data dump

So how long can I keep getting these BSOD's, before it totals my laptop?

 

Depends on the BSOD.

 

You should have several dump files now. When you get the analyser working, review them.

They seem to be based on 0x0000008e, see how much that occurs.

If the problem appears to be hardware, try disconnecting any connected hardware until you need it (for example, a printer).

The debugwiz should list other programs/drivers that were involved. That is what we would be hoping to see.

One thing that can be involved with crashes is RAM. If you can't check anything else, check your RAM. There are diagnostics in my signature.

Matt