Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
  • The crash message states it is a BEX error, which is apparently a buffer overflow
  • The Fault module is stackhash, which apparently means no module, so it returns a hash of the stack
  • The crash occurs when printing to any printer including cutePDF and excepting XPS
  • Crash occurs with all addons disabled (IE run with -extoff switch)
  • BEX64 occurs when trying to print XPS. I'm assuming XPS viewer uses IE to print, or they both use the same binary somewhere
  • IE10 is in software rendering mode. Hardware rendering mode causes IE to crash on starting (identical error). Have updated graphics drivers (Intel HD) and unplugged external graphics extender for 2nd monitor without luck
  • Printing works from Firefox and Chrome and Office Apps
  • The machine is fully up-to-date with MS patching, as is IE10

Is this a bug in the Windows 7 or Internet Explorer?

share|improve this question
I don't think this is enough information to diagnose it. What you really need is to fill out a report at and to upload a dump file. – 0xFE Jun 18 '13 at 4:03
Have you tried excluding IE from DEP mode? I'm not even sure how to do that, but I know it could help. – user3463 Jun 18 '13 at 4:18
follow the steps I posted here: and uplaod the dumps and add a link here. – magicandre1981 Jun 18 '13 at 8:17

You must log in to answer this question.

Browse other questions tagged .