win32K.sys blue screen

[needlove]

0x08E (0xC0000005, 0xBF859A28, 0xB6C7C5AC,0x00000000)

KERNAL_MODE_EXCEPTION_NOT_HANDLED

win32k.sys

I overclock like the dickens so I can't protest too much, but sometimes
overclocking will illuminate problem areas. I have the hardware under
control and have researched several discussions (mainly those of ignorant
overclockers like myself) to no firm resolution.

My question here is -- is there a known bug in windows XP home edition sp2
that may be partially responsible?

Also, I have all the settings right to create mini-dumps but rarely will a
blue screen create a mini-dump and when it does it overwrites an older one.
I use windbg to analyze a dump, that being the extent of my knowledge on the
use of windbg.

 

[Gerry Cornell]

http://snipurl.com/l6o7

If the problem is associated with Win32k.sys, the source of the
error might be a third-party remote control program. If such
software is installed, the service can be removed by starting the
system using the Recovery Console and deleting the offending
system service file.

Does the last paragraph ring any bells?

Otherwise try Start, Run, type "sfc /scannow" without quotes and hit Enter.

Description of Windows XP and Windows Server 2003 System
File Checker (Sfc.exe)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310747

After doing this reboot the computer,

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Ron Martell]

0x08E (0xC0000005, 0xBF859A28, 0xB6C7C5AC,0x00000000)

KERNAL_MODE_EXCEPTION_NOT_HANDLED

win32k.sys

I overclock like the dickens so I can't protest too much, but sometimes
overclocking will illuminate problem areas. I have the hardware under
control and have researched several discussions (mainly those of ignorant
overclockers like myself) to no firm resolution.

My question here is -- is there a known bug in windows XP home edition sp2
that may be partially responsible?

Also, I have all the settings right to create mini-dumps but rarely will a
blue screen create a mini-dump and when it does it overwrites an older one.
I use windbg to analyze a dump, that being the extent of my knowledge on the
use of windbg.

Try declocking your system back to factory specs and see if the error
persists.

That is the only way to determine if your problem is related to the
overclocking or not.

The STOP code you are getting is most often associated with a hardware
problem of some sort. See http://www.aumha.org/win5/kbestop.htm and
click on the "8E" Kernel Mode Except" link in the left side column for
more details about this error. Note that the link to the MSDN article
does not work. Use
http://msdn.microsoft.com/library/d..._299217d6-98d1-4d1d-8068-883e89933845.xml.asp


Good luck

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

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

 

[Gerry Cornell]

Ron

What exactly do you think Microsoft had in mind when they
used this expression "third-party remote control program"?


--

Regards.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Ron Martell]

Ron

What exactly do you think Microsoft had in mind when they
used this expression "third-party remote control program"?

Probably PC Anywhere and similar products.

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

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

 

[Gerry Cornell]

Thanks for your thoughts Ron.


--

Regards.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[needlove]

There is little doubt that backing off the fsb clock will eliminate this
blue screen error. But, something has to break somewhere. I hoped that
there was an existing problem with the win32k driver -- A seach showed
several old versions and the latest in the dll cache and system32 files.

One fellow described it well, I thought, when he said overclocking the CPU
can make "0"s begin to look like ".1"s and "1"s begin to look like ".09"s
and so forth, until the CPU is not sure if it recieved a "1' or a "0",
hence, blue screen.

I have tested my RAM and BIOS is up-to-date but I have a lot to learn before
reassigning IRQs or editing driver files.

For some reason Windows has decided to allow a pagefile on C:\, a dynamic
drive, so I should be getting some dumps from my blue screens and I
unchecked the box to overwrite.

Thanks for the replies...