Answers (N/A if not applicable)
Provide a detailed description of the issue AND 'does it fail every single time, or only sometimes?' If you can offer a % rate please do.
Windows 10 bugchecks and restarts when clicking 'Next' on the Office 2013 first run wizard, citing ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY. Resulting memory.dmp blames igdkmd64.sys
Brand and Model of the system.
Dell Latitude E7440, Dell Latitude E7450
Hybrid or switchable graphics system? ie Does it have AMD or NV graphics too?
Make and model of any Displays that are used to see the issue (see note2 below).
LFP = Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
LFP in both cases
How much memory [RAM] in the system (see note2 below).
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Hardware Stepping (see note1 below).
Intel HD Graphics 5500 revision 9
Operating System version (see note2 below).
Windows 10 Enterprise 64-bit (build 10240)
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).
SW/Apps version used to replicate the issue.
Microsoft Office 2013 Standard
Single display, clone, or extended (see note2 below).
Display resolution & refresh rate setting of each display (see note2 below).
AC or DC mode, i.e. is power cable plugged in or not?
AC or DC, reproduces on either
How to repro
Please provide steps to replicate the issue. These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
1. Launch an Office 2013 app for the first time
2. Click Next on the first run wizard
3. PC bugchecks
Video attached to post
This repros on every system I've tried it on with the 4256 driver, so I'm hoping it's pretty simple for you to repro it and fix it. I can provide the memory.dmp kernel memory dump from an affected machine if you need it.
bugcheck.mp4 3.4 MB