V
*Vanguard*
I just did a fresh install of Windows XP about 2 weeks ago. Since then
I have had 2 or 3 BSODs (blue screens of death) reporting the problem
was with win32k.sys. I did a search and found:
You Sporadically Receive a "STOP 0x1E" Error Message in Win32k.sys in
Windows XP
http://support.microsoft.com/?kbid=329052
which says:
"A null pointer may be used for pwndStart if all the child windows of
the desktop are topmost windows, and this null pointer causes the access
violation."
What I've noticed just before the crash is that I will have some windows
that somehow get forced to be topmost similar to, say, Task Manager when
it is configured for "Always on top". For example, I'll have Explorer
open, then open the Disk Management MMC, and maybe Help and Support. At
some point, when I click on a window to raise it to the top, it won't.
Instead one of the other windows is forcing itself to remain topmost. I
try clicking on that stubborn window and back on the one that I do want
on top but that doesn't work. I have to drag the stubborn window out of
the way until I can get back to it and close it. However, a few times
before I get back to that stubborn window, the system crashes to a blue
screen.
Anyone have any more information on why windows sometimes get stuck in
the always-on-top mode and/or why win32k.sys is so flaky to cause the
blue screen crashes. Maybe there is some configuration setting I could
use until Microsoft builds a patch for this defect.
I have had 2 or 3 BSODs (blue screens of death) reporting the problem
was with win32k.sys. I did a search and found:
You Sporadically Receive a "STOP 0x1E" Error Message in Win32k.sys in
Windows XP
http://support.microsoft.com/?kbid=329052
which says:
"A null pointer may be used for pwndStart if all the child windows of
the desktop are topmost windows, and this null pointer causes the access
violation."
What I've noticed just before the crash is that I will have some windows
that somehow get forced to be topmost similar to, say, Task Manager when
it is configured for "Always on top". For example, I'll have Explorer
open, then open the Disk Management MMC, and maybe Help and Support. At
some point, when I click on a window to raise it to the top, it won't.
Instead one of the other windows is forcing itself to remain topmost. I
try clicking on that stubborn window and back on the one that I do want
on top but that doesn't work. I have to drag the stubborn window out of
the way until I can get back to it and close it. However, a few times
before I get back to that stubborn window, the system crashes to a blue
screen.
Anyone have any more information on why windows sometimes get stuck in
the always-on-top mode and/or why win32k.sys is so flaky to cause the
blue screen crashes. Maybe there is some configuration setting I could
use until Microsoft builds a patch for this defect.