I did a lot of testing on a BTM and immediately upon X-ing IDE I got a BSOD! 0x0000008E win2k.sys: 0xBF841F29 It's the first BSOD I've seen in years and the first on this machine.
BSOD! I'd be *really* interested to know (1) if this is reproducible, and (2) how it is that IDE & TCC (which have no ring 0 code) could be implicated in a BSOD. Rex Conn JP Software
On Sat, 13 Nov 2010 15:08:10 -0500, rconn <> wrote: |---Quote--- |> I did a lot of testing on a BTM and immediately upon X-ing IDE I got a |---End Quote--- |BSOD! | | |---Quote--- |> |> 0x0000008E |> win2k.sys: 0xBF841F29 |> |> It's the first BSOD I've seen in years and the first on this machine. |---End Quote--- |I'd be *really* interested to know (1) if this is reproducible, and (2) how |it is that IDE & TCC (which have no ring 0 code) could be implicated in a |BSOD. If it's reproducible, it won't be easy. I opened/edited/ran/debugged the same BTM a few times afterward and nothing bad happened. The BTM itself does nothing fancy ... TYPEs a URL (to file), uses my plugins GREPP, NOTAGS, @AVG, calls one text-based external (cut.exe). Do you know what win32k.sys does?
It's the kernel-mode driver for the Windows GUI subsystem. It's called by things like user32.dll, and one of its requirements is that it must never, ever, BSOD.
I got this (below) in the event log. Is the dump of any value to you? The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf841f29, 0xab891604, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini111310-01.dmp.
On Sat, 13 Nov 2010 16:18:59 -0500, vefatica <> wrote: |---Quote (Originally by rconn)--- |It's the kernel-mode driver for the Windows GUI subsystem. It's called by things like user32.dll, and one of its requirements is that it must never, ever, BSOD. |---End Quote--- |I got this (below) in the event log. Is the dump of any value to you? | |The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf841f29, 0xab891604, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini111310-01.dmp. I opened the dump in WinDbg ... can't make sense of most of it but did find a call stack just before the crash. Code: ab891678 bf878d2a bc72b4d8 bc71d340 bc72b4d8 win32k!_IsDescendant+0xa ab89168c bf87c6e0 bc72b4d8 00000000 e13a3800 win32k!ConvertRedirectionDCs+0x3c ab8916a4 bf841d40 bc72b4d8 bc72b4d8 ab8916d0 win32k!RemoveRedirectionBitmap+0x22 ab8916b4 bf841db7 bc72b4d8 00000001 e13a3800 win32k!UnsetRedirectedWindow+0x2f ab8916d0 bf8461dc bc72b4d8 e13a3800 bc72b4d8 win32k!UnsetLayeredWindow+0x15 ab891710 bf845e93 bc72b4d8 ab891750 bc72b514 win32k!xxxFreeWindow+0x2b5 ab891760 bf845b8f 00000000 00000002 bc73d460 win32k!xxxDestroyWindow+0x42d ab89177c bf845ec0 00000000 bf8457b9 ab8917e4 win32k!xxxDW_DestroyOwnedWindows+0x6e ab8917c8 bf8457d6 00000000 0112f594 ab8917e4 win32k!xxxDestroyWindow+0x23f ab8917d8 8054161c 01910296 0112f5b0 7c90e4f4 win32k!NtUserDestroyWindow+0x21 ab8917d8 7c90e4f4 01910296 0112f5b0 7c90e4f4 nt!KiFastCallEntry+0xfc WARNING: Frame IP not in any known module. Following frames may be wrong. 0112f5b0 00000000 00000000 00000000 00000000 0x7c90e4f4
Wouldn't be of any use to me, as none of it is my code and there's no source available to trace it. You either had a memory error or you found a Windows bug (more likely the former). If it happens again you might want to pass it along to Microsoft.
