Book a Demo

Author Topic: BSOD in EA  (Read 3934 times)

Pawel Miechowiecki

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
BSOD in EA
« on: January 09, 2015, 06:26:50 am »
Windows 7 patch KB2993651 causes Blue Screen of Death in Enterprise Architect 9.3 when user is trying to open some kind of diagrams.

Windows patch modified win32k library - when Enterprise Architect is trying to use NtGdiGetPath method from that library system crashes.

The problem does not occur in Windows 8.

[code]
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22411.amd64fre.win7sp1_ldr.130801-1934
Machine Name:
Kernel base = 0xfffff800`03464000 PsLoadedModuleList = 0xfffff800`036a86d0
Debug session time: Thu Oct 30 15:16:18.629 2014 (UTC + 1:00)
System Uptime: 0 days 0:32:21.529
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960002e0954, fffff8800d1618d0, 0}

Probably caused by : win32k.sys ( win32k!NtGdiGetPath+b0 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960002e0954, Address of the instruction which caused the bugcheck
Arg3: fffff8800d1618d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!NtGdiGetPath+b0
fffff960`002e0954 488b4120        mov     rax,qword ptr [rcx+20h]

CONTEXT:  fffff8800d1618d0 -- (.cxr 0xfffff8800d1618d0;r)
rax=fffff8800d162310 rbx=fffff900c2c03010 rcx=0000000000000000
rdx=fffff900c02419e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002e0954 rsp=fffff8800d1622b0 rbp=fffff8800d162440
 r8=0000000000000000  r9=0000000000002114 r10=0000000000000000
r11=fffff8800d162278 r12=0000000000000000 r13=000000000008fd20
r14=000000000008d4b0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
win32k!NtGdiGetPath+0xb0:
fffff960`002e0954 488b4120        mov     rax,qword ptr [rcx+20h] ds:002b:00000000`00000020=????????????????
Last set context:
rax=fffff8800d162310 rbx=fffff900c2c03010 rcx=0000000000000000
rdx=fffff900c02419e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002e0954 rsp=fffff8800d1622b0 rbp=fffff8800d162440
 r8=0000000000000000  r9=0000000000002114 r10=0000000000000000
r11=fffff8800d162278 r12=0000000000000000 r13=000000000008fd20
r14=000000000008d4b0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
win32k!NtGdiGetPath+0xb0:
fffff960`002e0954 488b4120        mov     rax,qword ptr [rcx+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  EA.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960002e0954

STACK_TEXT:  
fffff880`0d1622b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiGetPath+0xb0


FOLLOWUP_IP:
win32k!NtGdiGe

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: BSOD in EA
« Reply #1 on: January 09, 2015, 06:46:02 am »
Pls. use the search button top left (with one year extend). You'll find some threads about BSOD and Windoze patch.

q.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: BSOD in EA
« Reply #2 on: January 12, 2015, 08:10:51 am »
Basically, you're right. Microsoft screwed up GDI Path handling and doesn't appear to be planning to fix it. We've worked around it on our current builds, but we don't generally provide patches for old versions.