STOP 0x0000008e error - win32k.sys

jrt01uk used Ask the Experts™

I've been getting a BSOD Stop error for a short while now. I originally thought it might be a software issue, from reading other posts, but on further investigating, I don't think it is.

I'm running Windows XP Home on a P4 3.0Ghz laptop, (Hyperthreading enabled), 1Gb RAM, 80Gb HDD (Partitioned ~30Gb C:, ~50Gb D:), ATi Radeon 9600 Mobile graphics.

I have been getting the following error:

STOP 0x0000008e ( 0xc0000005, 0x <this varies>, 0x <this varies>, 0x00000000)

it has been reporting win32k.sys as the problem.

I would be minding my own business using the computer, then without warning, and with no apprarent pattern (could be within 5 mins, could be within 25 mins), it BSOD's on me, with the same error. If I restart again immediately, it will boot, but won't load windows again, it will get to the welcome screen (but not actually say welcome), and then reboot. If however, after the win32k.sys message, I wait for a short period (10 mins or so) and then turn the system on, it loads up windows fine.

I don't know if I'm due for another BSOD anytime, so I will post this now, and then write more in a minute (if I'm still here - if not, expect more in 20 mins or so)

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®


... Today, after getting fed up of this message, I reinstalled Windows (I've done this about 3 times in the past week!!!), but this time I went for a COMPLETE format of my C partition. Same problem still exists.

Before today, I did a check on the installed memory (2 x 512Mb sticks) with the Microsoft Memory Checker and it came back with no errors.

Yesterday, after viewing a post with a similar issue, performed a CHKDSK command, which returned no errors, then I forced a CHKDSK /p (I think that was it..) and it found errors, so I CHKDSK /r and corrected them... (this was before I recently reinstalled windows).

At the moment, I am running without my graphics drivers, I installed them before today, and they didn't seem to help, so I haven't bothered this time.



I have the minidump file, which I can post somewhere, or email to someone. Just let me know where to send it!!

At the moment, I have nothing more installed than the Windows XP SP1 CD I used to install windows, and the drivers for my internet (NetGear 54Mbps Wireless USB 2.0 Adapter), so I'm at a loss as to how to proceed. I would really welcome any input into this. I'm normally able to solve minor computer issues, but this has been giving me a headache!

Thanks in advance,
Hi jrt01uk,
Tough Luck! You may want to see this page:

Good Luck!
Learn SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Most Valuable Expert 2018
Distinguished Expert 2018

You could try to install SP2 if you haven't done so yet, as there are several issues with the win32k.sys, for example those:

Random "0x0000008E" Error Message on a Blue Screen in Windows XP

"Stop 0x0000008E" error message in Win32k.sys when you use the keyboard to access a program menu in Windows XP

Attach 3 to 4 minidumps at any webspace. I will examine the dump and find out the culprit. You can find the minidump at the folder \windows\minidump.



Sorry for the delay - its been VERY hard to do this with the computer crashing randomly :(

Thanks for your help! Much appreciated!

I've proessed your minidump. I can't determine the root cause. It looks like it is hardware error as the failing instruction address are windows kernel which is unlikely to crash. As you know hardware error occurs randomy and I don't know why you only get bugcheck 8E as I expect hardware error always have bugcheck code 0A, 50, 8E and D1.  Attach more minidump so I can confirm whether it is hardware error or not.

Mini030105-01.dmp 8E (c0000005, bf827d9c, f76f1188, 00000000) win32k!NtGdiModifyWorldTransform+20e
Mini030105-02.dmp 8E (c0000005, bf827d9c, f664d188, 00000000) win32k!NtGdiModifyWorldTransform+20e
Mini030105-03.dmp 8E (c0000005, 80594b34, f6c52bc0, 00000000) nt!NtAllocateVirtualMemory+350
Mini030205-01.dmp 8E (c0000005, bf827d9c, f67da25c, 00000000) win32k!NtGdiModifyWorldTransform+20e

Your XP SP1 is two years behind. Upgrade your windows XP SP1 latest patch level.


Hi cpc2004,

Thanks for you help :)

Here's some more minidumps as requested!



I'm in the process of updating windows files using the Windows Update site, but each time I try, a number of the downloads fail both on download and some on installation...I'm slowly getting them all installed though - at least during the time I have between crashes ;)

I've processed the dump and the new finding there have one crash with bugcheck code 0a. All the dumps failed at the same routine  nt kernel and win32k. Right now I can't determine the culprit.  The failing module is very consistent and I've searched and no hit is similar to your case. If it is hardware error, the crash should have multiple Bugcheck code. 90% of the crash is bugcheck code 8E and only one occurence of 0A. Your windows has the hardware failure symptom but I can't find the hardware failing message from the minidump. Usually it is hardware error, the analyze report of windbg displays the CPU failure or memory corruption.

1. Some component is corrupted after some software was de-installed.  You may try re-install the windows.  If the same problem still occurs, it must be hardware problem
2. Run memtest to stress test your ram.

Mini030305-01.dmp 0A (c01850d8, 00000002, 00000000, 80514674) win32k!NtGdiCreateDIBSection+15c
                      nt!ProbeForWrite+0x37:805f1127                   8a06    mov     al,[esi]    ds:0023:02a90000=??
Mini030405-01.dmp 8E (c0000005, bf827dfe, bafa50ec, 00000000) win32k!NtGdiModifyWorldTransform+9d
                      win32k!NtGdiModifyWorldTransform+0x9d:bf827dfe 8939      mov     [ecx],edi   ds:0023:6199887c=????????

Most Valuable Expert 2018
Distinguished Expert 2018
Since you've reinstalled anyway, it might be worth the try to use a slipstreamed install:
Slipstreaming Windows XP with Service Pack 2 (SP2)

Slipstreaming Windows XP Service Pack 2 and Create Bootable CD

But then again, seeing as how the machine seems to have been running OK for some time before this started, and it now displays this behaviour even after a fresh install, I'd agree with cpc2004 that this seems to be a hardware issue that developed over time.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial