Jump to content
Welcome to our new Citrix community!
  • 0

RdrCEF.exe Crashing VDA with BSOD Stop 0xA


Campbell Kay

Question

Hi Guys,

 

Just wondering if anyone has had any issues running Adobe Reader on Citrix with AppLayering, currently running 1906.

 

we have found in our crash dump that RdrCEF.exe is causing the BSOD.

 

we are running the latest version of Adobe Reader DC.

 

Crash dump below

 

Debugging Details:
------------------
KEY_VALUES_STRING: 1

Key  : Analysis.CPU.Sec
Value: 2
Key  : Analysis.Elapsed.Sec
Value: 40
Key  : Analysis.Memory.CommitPeak.Mb
Value: 68
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1
DUMP_QUALIFIER: 402
BUILD_VERSION_STRING: 14393.3053.amd64fre.rs1_release_inmarket.190612-1836
SYSTEM_MANUFACTURER:  Microsoft Corporation
VIRTUAL_MACHINE:  HyperV
SYSTEM_PRODUCT_NAME:  Virtual Machine
SYSTEM_VERSION:  7.0
BIOS_VENDOR:  American Megatrends Inc.
BIOS_VERSION:  090007 
BIOS_DATE:  06/02/2017
BASEBOARD_MANUFACTURER:  Microsoft Corporation
BASEBOARD_PRODUCT:  Virtual Machine
BASEBOARD_VERSION:  7.0
DUMP_TYPE:  0
BUGCHECK_P1: 0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff802b7af70dc
READ_ADDRESS:  0000000000000000 
CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeliverApc+ec
fffff802`b7af70dc 483910 cmp     qword ptr [rax],rdx

CPU_COUNT: 8
CPU_MHZ: a86
CPU_VENDOR:  GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 55
CPU_STEPPING: 4
CPU_MICROCODE: 6,55,4,0 (F,M,S,R)  SIG: FFFFFFFF'00000000 (cache) FFFFFFFF'00000000 (init)
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  RdrCEF.exe
ANALYSIS_SESSION_HOST:  BANLESTHERBEENA
ANALYSIS_SESSION_TIME:  07-18-2019 14:08:31.0982
ANALYSIS_VERSION: 10.0.18914.1001 amd64fre
TRAP_FRAME:  ffffcd80cf0fde90 -- (.trap 0xffffcd80cf0fde90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffbb0e10d31598
rdx=ffffbb0df5e23288 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802b7af70dc rsp=ffffcd80cf0fe020 rbp=ffffcd80cf0fe070
r8=0000000000000000  r9=0000000000000000 r10=ffffbb0df5e23278
r11=fffff802b7aee130 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDeliverApc+0xec:
fffff802`b7af70dc 483910          cmp qword ptr [rax],rdx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff802b7be9c29 to fffff802b7bd9b70

STACK_TEXT:  
ffffcd80`cf0fdd48 fffff802`b7be9c29 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffcd80`cf0fdd50 fffff802`b7be6d66 : 6f496465`6c65636e 276e646c`756f6320 4320646e`69662074 46464646`78303a42 : nt!KiBugCheckDispatch+0x69
ffffcd80`cf0fde90 fffff802`b7af70dc : 00000000`00007aa0 fffff80b`1bd10b80 00000000`00007bf4 fffff802`b7b7e919 : nt!KiPageFault+0x426
ffffcd80`cf0fe020 fffff802`b7bdd96c : 00000000`00000000 fffff80b`1bd02600 fffff80b`00000000 ffffbb0e`10d31500 : nt!KiDeliverApc+0xec
ffffcd80`cf0fe0b0 fffff802`b7f8b9cd : ffffa702`14c9db01 ffffbb0e`10d31b68 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0x29c
ffffcd80`cf0fe240 fffff802`b7f8cb47 : ffffffff`fffe7960 ffffbb0d`fb9a7840 ffffcd80`cf0fe2c0 ffffbb0e`10d31500 : nt!IoCancelThreadIo+0x7d
ffffcd80`cf0fe280 fffff802`b7e7e902 : 00000000`00000000 ffffbb0e`10d31500 00000000`00000000 ffffbb0e`0cd80840 : nt!PspExitThread+0x24f
ffffcd80`cf0fe3c0 fffff802`b7e7e800 : ffffbb0e`10d31500 00000000`00000000 ffffbb0e`10d31500 00000000`00000000 : nt!PspTerminateThreadByPointer+0x96
ffffcd80`cf0fe400 fffff802`b7be9703 : ffffbb0e`10d31500 ffffcd80`cf0fe4c0 00000000`00000000 ffffbb0d`f09138f0 : nt!NtTerminateThread+0x44
ffffcd80`cf0fe440 00000000`67dc223c : 00000000`67dc21ff 00000023`7700edac 00000000`00000023 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`084aebf8 00000000`67dc21ff : 00000023`7700edac 00000000`00000023 00000000`00000000 00000000`085afb08 : wow64cpu!CpupSyscallStub+0xc
00000000`084aec00 00000000`67d7bf51 : 00000000`00000000 00000000`00000000 000044ce`f4ff04a0 00000000`00000000 : wow64cpu!Thunk0Arg+0x5
00000000`084aecb0 00000000`67d6cb60 : 00000000`00000000 00000000`084aed60 00000000`00000001 00000000`00000000 : wow64!RunCpuSimulation+0xf311
00000000`084aed30 00007fff`1c53848d : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : wow64!Wow64LdrpInitialize+0x120
00000000`084aefe0 00007fff`1c53832e : 00000000`084af0b0 00000000`00000000 00000000`00000000 00000000`0526c000 : ntdll!_LdrpInitialize+0x109
00000000`084af060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

Any info would be great.

 

Thanks,

Link to comment

15 answers to this question

Recommended Posts

  • 0

As Rob noted, did it ever work? We do not have 1906. Which version of App Layering are you working with? Are you using Elastic Layering? Yes. Is the app delivered elastically? Which version of Adobe are you working with? One test could be an image with only the OS, Platform and Adobe app layer. Does it work? Maybe there is a layer conflict. Which version of Windows, with build are you using?

Link to comment
  • 0

Hi Ray,

 

i think it has always caused the server to crash.

 

we supplied citrix the crash multiple times, but they thought it was App Layering drivers causing the crash, so we have updated App Layering about 3-4 times to fix this.

 

we are on ELM 1905 with Citrix VDA 1906.

 

initially they thought it was ESET, which there was a citrix fix for ESET, so we updated that version, then it still crashed, so we completely removed this from the image, but still crashing.

 

Adobe is built into the image, not elastically, we have Elastic layering enabled though. as we delivery some applications elastically, although i could test it without this, as the image would still work.

 

the thing is the VDA(s) work fine each day on 4 our of 5 VDA servers, only 1 seems to crash only once a day.  i have never seen a server crash twice in one day, the do get recreated daily with MCS. we went went for like 2 weeks with out a crash, no changes to the VDA then it starts again, its so weird. 

 

Running Windows 2016, i have recently updated it to the latest version, as we had issues with the Office Layer crashing as well, so i had to recreate that layer with the latest OS version, which seems to have fixed that weird issue. 

 

i have been working with Citrix on this for along time and really struggling with any solution..

 

i personally think its a layering issue rather than Adobe Reader, but how do i identify that? i guess disabling elastic layering would prove this?

 

any thoughts would be appreciated.


Thanks,

 

Cam 

Link to comment
  • 0

Hi,

 

I have since had MS analyze the dump and found it to be the elastic layer driver.

 

Disabling elastic layering fixes it, but as you say I really need this too.

 

Citrix has told me to update my ELM to 1908, but they dont mention any fixes in this release for this issue, so I dont have much faith.

 

Haven't tested it yet, will let you know once we can get it into production, as it only seems to happen under load.

 

Thanks

 

 

Link to comment
  • 0

Hi,

 

i spent along time on this with Citrix. 

 

got no where, i had to turn off elastic layering in the end, as my client had enough, i probably worked on this for 6 months with citrix and couldn't get it fixed :(

 

would be great to know if we can turn it back on, but the only way for me to test was to turn it on production and put user load on the VDA, as i dont have any load tools to run that sort of performance testing.

 

would be great to know if its fixed..

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...