Unsolved

1 Rookie

 • 

5 Posts

78

January 8th, 2025 13:59

XPS 8930 (i5 8400), U3824DW, DDM 2.3.2.18 & BSOD

Running the config in the subject line with Intel UHD graphics (31.0.101.2134). Getting periodic BSOD. Debug of dump shows:

Program running is DDM.EXE (Dell Display Manager)

Error: KMODE_EXCEPTION_NOT_HANDLED (1e)

MODULE NAME: igdkmd64

Display Manager is at latest released version.

It seems some call to the graphics driver from DDM.EXE is causing the crash. Any advice/observations welcome. If I don't run DDM.EXE there are no issues I'm aware of, but I do like the functionality Display Manager provides with my monitor.

Rolling back to the last supported Dell graphics driver ( (27.20.100.9664) )for this machine causes all kinds of issues with video rendering, so that does not appear to be a viable option. Thanks in advance for your responses.

9 Legend

 • 

14.8K Posts

January 9th, 2025 14:06

DDM sounds like Dell bloatware giving user ostensible sophisticated interface w monitor but in actuality buggy.

this is a good example of it.

you would do better get rid of it 

I suggest all clean Windows install w zero Dell software 

10 Elder

 • 

45.2K Posts

January 11th, 2025 02:19

Exactly which monitor do you have?  Does your monitor have a "joystick" on the back?  If it does, you can make all the same changes using the joystick that you can do with DDM software but without installing the software.

I have DDM 2.2.1.14 running on my XPS 8930/Win 10, and it works perfectly, but I'm using an NVidia GPU, not onboard Intel Graphics, with Dell P2423D monitor. I frequently use the joystick if I want to make one quick display change and get on with whatever...

There's a brand new DDM version 2.3.2.20, just released 08 Jan 2025. Check to see that your specific monitor is on the Applies to list at that link to confirm your monitor is supported.

If it applies, uninstall DDM using either Windows Add/Remove, or use Revo Uninstaller (free) for more thorough removal. If you use Revo, be sure to let it create a System Restore point when it asks, to be safe. And after it runs, it will show you several screens with any leftover files/folders. Select only the items marked in bold, and click Delete to move to next screen.  When Revo is done, reboot PC and install new DDM version.

1 Rookie

 • 

5 Posts

January 13th, 2025 02:09

@RoHe​ Monitor is a new Dell U3824DW paired with an older PC. All drivers (including Intel UHD Graphics) and firmware are up to date. I did go to the website and pull down the latest Dell Display Manager release and did a clean install, but the problem continues to occur. Always the same: DDM.EXE is the running process and igdkmd64 (Intel on-board graphics driver) is the module being called and returning the error. 

Thanks for the suggestions.

10 Elder

 • 

45.2K Posts

January 13th, 2025 18:18

What version of  Windows are you using?

What antiviral app are you using, eg, McAfee, Windows Defender...?

What onboard Intel Graphics port are you using, DP or HDMI?  Are you using the same type port on monitor or an adapter cable to a different type port on monitor?

You said "firmware" is up-to-date, but does that include the monitor's latest firmware update?  (Read/follow installation instructions carefully.)

Did you install the U3824DW monitor driver on the XPS 8930?

You might try version DDM v2.3.1.14. That's the version running on my XPS 8930/Win 10/i7-9700, with add-in NVidia video card.

And try this:

  1. At desktop, open a CMD prompt window, Run as administrator
  2. At the prompt, type in: chkdsk c: /r and press Enter. Accept offer to run chkdsk at next boot. Reboot and chkdsk runs before Windows loads. This takes a while, so be patient.
  3. Back at desktop, open CMD as in #1.
  4. At the prompt, type in: DISM.exe /Online /Cleanup-image /Restorehealth and press Enter. Be sure to include a space in front of each / and note any error messages when that's done.
  5. Assuming no "unfixed" errors in #4, at the CMD prompt, type in: sfc /scannow and press Enter. Be sure to include a space in front of the / and note any errors when that's done.
  6. Assuming no "unfixed" errors in #5, reboot PC and try running DDM again.
No Events found!

Top