Application Crash. Only OLE32 and rpcrt4 shows up in the callstack

We have suddenly started getting this crash in one of our product workflow from past 1 month. This crash always happens from time to time at our Integration Testing Site in Germany but not in the product development site in US. We have tried to reproduce the same workflow in US multiple times but have been unsuccessful in getting the crash.

The user.dmp which gets created by Dr Watson always comes up with a stack like the following..

Using the  windows symbols directly from Microsoft symbol library I am getting the following call stack.

1128f9d0 77600f3d 14592718 774ecc08 1128fa00 0x12be423e
1128f9f0 77600ee9 001c1f1c 0b2c4688 14592718 ole32!GetChannelCallMgr+0x58
1128fa38 77600ba0 001c1f1c 001ce6d8 0eb841f0 ole32!AsyncStubInvoke+0x66
1128fa88 7751317f 001c1f1c 0eb841f0 0b2c4688 ole32!StubInvoke+0x7e
1128fb60 775130a4 0e6ed080 00000000 0b2c4688 ole32!CCtxComChnl::ContextInvoke+0xe3
1128fb7c 776007f5 001c1f1c 00000001 0b2c4688 ole32!MTAInvoke+0x1a
1128fbac 77602dd8 001c1ec8 0e6ed080 0b2c4688 ole32!AppInvoke+0x9c
1128fc80 77600715 001c1ec8 0b2b55c8 001ce6c0 ole32!ComInvokeWithLockAndIPID+0x2c2
1128fccc 77e794a5 001ce394 001ce6c0 001ce394 ole32!ThreadInvoke+0x1cd
1128fd00 77e7940a 776005d0 001ce394 1128fdec rpcrt4!DispatchToStubInC+0x38
1128fd54 77e79336 00000000 00000000 774ebfc8 rpcrt4!RPC_INTERFACE::DispatchToStubWorker+0x113
1128fd78 77e8a33c 001ce394 00000000 774ebfc8 rpcrt4!RPC_INTERFACE::DispatchToStub+0x84
1128fdb8 77e8a37d 001ce394 001ce350 00000000 rpcrt4!RPC_INTERFACE::DispatchToStubWithObject+0xc0
1128fdf8 77e7bc99 0eaa2e68 0016e538 001ce138 rpcrt4!LRPC_SCALL::DealWithRequestMessage+0x2cd
1128fe1c 77e7bbdd 0016e574 1128fe38 001ce138 rpcrt4!LRPC_ADDRESS::DealWithLRPCRequest+0x16d
1128ff80 77e76c9f 1128ffa8 77e76ac1 0016e538 rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+0x310
1128ff88 77e76ac1 0016e538 7c9106eb 00000000 rpcrt4!RecvLotsaCallsWrapper+0xd
1128ffa8 77e76c87 001601b8 1128ffec 7c80b683 rpcrt4!BaseCachedThreadRoutine+0x79
1128ffb4 7c80b683 0e88dcf0 7c9106eb 00000000 rpcrt4!ThreadStartRoutine+0x1a
1128ffec 00000000 77e76c6d 0e88dcf0 00000000 kernel32!BaseThreadStart+0x37

As can be seen all it comes out with is with functions inside rpcrt4.dll or ole32.dll. It doesnt show up any functions from our own modules. This is what has lead to this issue being not tracked down for over a month now...

All our application modules is UNICODE compliant. The systems on which IT testing happens at Germany are the same type of systems we have here in US for product development testing.Start Free Trial