Delphi 2007 + Themed support + WinXP64Pro + Side Taskbar = System Crash + Taskbar not working.

Hello,

The following happened:

1. A few days ago I moved the taskbar from the bottom to the left side of
the screen (might be related)

2. Today I opened Delphi 2007 and opened an older application.

3. I enabled "runtime theme support" for the older application.

4. This (other) older application does not use any custom page control I
think...

5. Then while upgrading the application to use newer units and using outlook
express and debugging etc the screen went blank, like it was switching
resolution or something.

6. Then a few seconds later the system crashed !

Crash in:

Win32K.sys

page_fault_in_nonpaged_area

stop 050, etc

(Memdump made I think...)

7. I rebooted the system

8. Wanted to look at event log, noticed the Taskbar is not responding.

9. Opened outlook express via running explorer instance to write this
report.

I will post this first before it crashes again, then I will try to find more
information via the event log in case any developer reads this and wants
more info to fix any possible bug in themed support on Windows XP x64 Pro.

(Me busy with themed support in Delphi 2007 ! System hanged first and now
crashed ! All within a few minutes ! )

Bye,
Skybuck.

 

I decided to put available all minidumps I currently have on my system !

27 system crashes ! Gje !

The latest (27 august 2007) is related to the Delphi, Themed support crashes
?!

(Not all minidumps complete, but this one should be complete ?! )

Webdrive is located at:

http://members.home.nl/hbthouppermans/

Specifically:

http://members.home.nl/hbthouppermans/WinXPx64ProMinidumps/


(Delete unzipped files from virtual robot contest and ufo to make some room,
I should delete some other stuff also.. but at least there is a winrar for
the contest )

I like other files so this one had to go lol

Bye,
Skybuck.

 

Oh shit,

I just noticed all the date/time on the webdrive have be changed to the day
I uploaded them SHIT.

The minidump for today/themed crash is:

Mini082707-01.dmp

Bye,
Skybuck.

 

Short Crash Analysis by WinDbg:

I am definetly no expert...

Seems like something did a try except where that is not allowed, also seems
resource related ????:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini082707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
Debug session time: Mon Aug 27 15:17:04.640 2007 (GMT+2)
System Uptime: 0 days 0:27:21.571
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...................................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8804c21090, 0, fffff97fff0a7742, 5}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!HmgAllocateDcAttr+1b6 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: fffffa8804c21090, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff97fff0a7742, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: fffffa8804c21090

FAULTING_IP:
win32k!HmgAllocateDcAttr+1b6
fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h]

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: bds.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffadfc478e990 -- (.trap fffffadfc478e990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed.
rax=00000000ffffffff rbx=0000000000000888 rcx=fffffa8004c21080
rdx=fffffa8004c21080 rsi=fffffa80051f6280 rdi=fffff97fff0cda0e
rip=fffff97fff0a7742 rsp=fffffadfc478eb20 rbp=fffffadfc478ecf0
r8=fffffa8004b9b0c0 r9=5000984210000000 r10=500098421117001d
r11=00000000000007ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po nc
win32k!HmgAllocateDcAttr+0x1b6:
fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h]
ds:fffffa88`04c21090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800010a5416 to fffff8000102e950

STACK_TEXT:
fffffadf`c478e8b8 fffff800`010a5416 : 00000000`00000050 fffffa88`04c21090
00000000`00000000 fffffadf`c478e990 : nt!KeBugCheckEx
fffffadf`c478e8c0 fffff800`0102d519 : fffffa80`00cad9e0 00000000`00000009
00000000`00000000 fffffa80`05009b50 : nt!MmAccessFault+0x395
fffffadf`c478e990 fffff97f`ff0a7742 : 00000000`00000000 fffff97f`ff0ce249
fffffa80`0445f780 fffffadf`c478ecf0 : nt!KiPageFault+0x119
fffffadf`c478eb20 fffff97f`ff0ce004 : 00000000`00000888 00000000`00000000
00000000`1e011591 fffffa80`051f6280 : win32k!HmgAllocateDcAttr+0x1b6
fffffadf`c478eb60 fffff97f`ff0cdf0e : fffffa80`051f6280 fffffa80`051f6280
fffffadf`cba85cd0 fffffa80`0133b000 : win32k!GreSetupDCAttributes+0x34
fffffadf`c478eba0 fffff97f`ff0a36c6 : fffffa80`01351010 fffff97f`ff0ced20
00000000`00000000 00000000`7efdb000 : win32k!GreCreateDisplayDC+0x1c4
fffffadf`c478ec30 fffff800`0102e3fd : 00000000`7d814cc6 fffff97f`ff0ced20
00000000`7d814cc6 00000000`7d814c30 : win32k!GreCreateCompatibleDC+0x77
fffffadf`c478ec70 00000000`78b842d9 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`0012edf8 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : 0x78b842d9


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HmgAllocateDcAttr+1b6
fffff97f`ff0a7742 488b4cc118 mov rcx,qword ptr [rcx+rax*8+18h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!HmgAllocateDcAttr+1b6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310

FAILURE_BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6

BUCKET_ID: X64_0x50_win32k!HmgAllocateDcAttr+1b6

Followup: MachineOwner
---------

Bye,
Skybuck.

 

Re: Short Crash Analysis by WinDbg:

P.S.: I followed instructions on this link to setup WinDBG properly for
symbol support

http://forums.majorgeeks.com/showthread.php?t=35246

Simply add something like:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

to symbol path.

Then symbols will be downloaded...

(I set mine to C:\Tools\WinDBG\WebSymbols )