1 Rookie
•
5 Posts
•
28 Points
2
1367
March 10th, 2026 16:20
Dell Latitude 7420's crashing
Hi,
We're having issues with about 15 Dell Latitude 7420's as of about a month ago. They seem to randomly crash/freeze up so that the only thing that can be done is a long hold of the power button.
These are the things I've tried:
- Re-installing Windows
- Re-installing specific device drivers (serial, chipset, wlan)
- Updating Windows
- Updating BIOS (v.1.47 -> 1.48)
Any other ideas? Seems to occur more when plugging in a USB-C dock or charger. Just strange that it's affecting all Dell's of that model, but other Dell's are fine.
No Events found!


RIT-Chad C
1 Rookie
•
12 Posts
•
41 Points
0
June 17th, 2026 13:08
@FC2026 @EnterpriseTech01
We have incrementally applied a script to force Intel's driver version 32.0.101.7085 to each individual affected user as they report the issue and have not heard back since. We also performed extensive internal testing before deploying that script. From what we can tell, yes, it is fixed with that version.
However, you will need to execute a clean installation by removing all other graphics driver packages, set policy to prevent driver updates with Windows Update quality updates, disable driver searching on Windows Update, and add device install restrictions for the affected hardware IDs (mainly PCI\VEN_8086&DEV_9A49 and PCI\VEN_8086&DEV_9A60 for our organization, though theoretically all devices with 11th generation processors are affected).
If you do not take all of these steps, there is still a chance for Windows Update or Dell Command Update to override it with the older version. For example, per the Microsoft Update Catalog for Dell's unique subsystem ID for the graphics driver on Latitude 7420 devices (PCI\VEN_8086&DEV_9A49&SUBSYS_0A361028), version 32.0.101.7077 is the latest that is offered. Dell Command Update will only update to 32.0.101.7084, as that is the latest version packaged by Dell, and Windows Update will leave it alone since it also includes said unique subsystem ID.
DELL-Daniel V
Community Manager
•
614 Posts
•
3.5K Points
0
March 10th, 2026 18:32
Contact Dell GHN (Get Help Now) chat technical support Monday through Friday. Click the blue "Get Help Now" on the right to start a private live chat session. Share the private Service Tag with them so that they can verify the ownership and warranty status. This will also generate a unique Technical Support case for your unique Service Tag. If already out of warranty, click here for the Dell out of warranty offerings.
I'd recommend running the preboot diagnostic on the units. If this test is also freezing or if the units freeze while idle in the menu or in the BIOS, then you're likely looking at hardware failures. Seeing as the RAM is integrated on the motherboard, that will limit hardware you can test to really just the SSD.
Since you mentioned freezing when plugging in a charger, does physically moving the unit cause it to freeze up? If its freezing when being picked up or on movement, that too will typically point to the motherboard.
Zeal_LG
1 Rookie
•
5 Posts
•
28 Points
0
March 11th, 2026 09:39
Hi Daniel,
Thanks for your response.
I'm anticipating this to be a software issue, as it's extremely unlikely that 15 of the same make/model all have a similar hardware fault at the same time. The devices don't seem to freeze as a response to movement.
It's worth noting that these devices all worked perfectly fine a month ago, which makes me think that a specific update has caused these issues.
Kind regards,
Ben
ejn63
12 Elder
•
31.3K Posts
•
154.8K Points
0
March 11th, 2026 15:36
If you have one of the systems you can use as a test, remove (uninstall) any updates that have been installed at or since the time the issue began. Does that solve the problem? This includes any firmware updates, Windows or driver updates you know where either manually or automatically installed. If you have system protection turned on, you can also try reverting to a restore point before the issue began.
petermuss
2 Intern
•
261 Posts
•
6 Points
0
March 11th, 2026 17:22
@Zeal_LG
1) use DELL Command | Update to grab the lastst drivers for your machines
2) USB-C Dock: make sure, you got the latest firmware for the docks
3) if you on W11, make sure to get the release 25H2 26200.8037
HTH
Peter
jamiehallghs
1 Rookie
•
8 Posts
•
11 Points
0
April 2nd, 2026 12:14
We're also having this with 183x 7420's. Seems to be a mix of either Windows Update, Intel Chipset Driver or BIOS... Disabling modern standby/sleep has helped to some degree but it's not perfect.
RIT-Chad C
1 Rookie
•
12 Posts
•
41 Points
0
April 3rd, 2026 17:14
We are also encountering this with multiple 7420s.
We performed detailed analysis of the system state at the time of the incidents, and have narrowed down the issue to an inconsistent deadlock condition inside of the Intel Graphics kernel-mode driver when toggling power to the internal display that crashes csrss.exe.
We have an open case with Dell Support. Potential workarounds for the time being that we have not tested could be falling back to the Microsoft Basic Display Adapter and/or disabling the lid switch in BIOS and disabling sleep and screen off in Windows. Downgrading the Intel Graphics driver should also be tested, but it's difficult to work around Windows Update and DCU attempting to automatically reinstall it.
Johnnyendo
1 Rookie
•
3 Posts
•
2 Points
0
April 8th, 2026 19:04
This has been not good for our organization.
We had to replace several with Lenovo laptops to avoid the issue.
Driver & BIOS updates having zero effect.
Thanks all for the recent posts!
DriftKing
1 Rookie
•
3 Posts
•
14 Points
0
April 9th, 2026 13:23
Our organization has encountered exactly the same issue with 4 (reported by now) Latitude 7320 laptops. BIOS + drivers via Dell Command | Update are up to date.
No solution or fix found so far.
DELL-Daniel V
Community Manager
•
614 Posts
•
3.5K Points
0
April 10th, 2026 15:50
Hi all,
Can you try updating the GPU driver with this version here? Please let us know if that possibly helped with the freezing.
DELL-Nat M
Community Manager
•
3.7K Posts
•
21K Points
0
April 10th, 2026 17:03
Hi everyone,
Per guidance from our engineering team, please install the following driver and let us know if it resolves the issue on your system: 32.0.101.7084, A19
Once installed, please reboot your system and share your results with us.
Your feedback will help us confirm the resolution across affected systems.
Thanks for your cooperation!
(edited)
LM-GW
1 Rookie
•
1 Message
•
2 Points
1
April 13th, 2026 12:24
Hi all,
Just wanted to add that we've seen this issue sporadically on our fleet of ~175 7420s as well. It's resulted in random total system freezes (sometimes at a black screen, sometimes not) with no Windows BSOD logs being written.
@DELL-Daniel V @DELL-Nat M There was a new Intel graphics driver released on 4/9/26 on the 7420 support page: 32.0.101.7084, A19. Would you please be able to confirm whether we should continue with the engineering recommended driver A13 (which is ~1.5 years old) or attempt to use this new version that was just released.
Thank you!
DELL-Nat M
Community Manager
•
3.7K Posts
•
21K Points
0
April 16th, 2026 13:21
Hi everyone,
We see that several users have reported this issue. Thank you for bringing it to our attention.
To help us escalate this properly, our engineering team has asked if we can gather a bit more information to assist with reproducing and investigating the behavior. If possible, we kindly ask for the following:
You can share the video directly in this thread or provide it via a secure link.
Your input is extremely valuable and will help speed up the investigation and resolution.
Thank you for your cooperation!
RIT-Chad C
1 Rookie
•
12 Posts
•
41 Points
0
May 8th, 2026 18:33
The issue is reproducible on the latest version, 32.0.101.7084. The fastest way that we have found to replicate it is to set the "Turn my screen off after" timeout in Windows settings to the lowest (1 minute) and just tap the touchpad each time the screen turns off.
After a variable but reasonable amount of attempts, the condition will trigger and the console will freeze. Most often, it freezes on a black screen with only the cursor visible. If you perform a manually-initiated crash while it is frozen, WinDbg analysis will reveal the exact cause of the fault.
Our next posts will include one instance in which we performed this analysis. It is a clear circular wait deadlock which sometimes occurs after the Windows console process (csrss.exe) defers to igdkmdn64.sys (Intel Graphics kernel-mode driver) via dxgkrnl!DxgkPowerOnOffMonitor and toggles power to the internal display. Additionally, we have all but confirmed that the problem does not occur with the oldest version published on Dell's website, which is 31.0.101.3222.
This should be more than enough information for the engineering team.
(edited)
RIT-Chad C
1 Rookie
•
12 Posts
•
41 Points
0
May 8th, 2026 18:34
0: kd> !thread ffffba8effe93080
THREAD ffffba8effe93080 Cid 0464.04b8 Teb: 000000f45e473000 Win32Thread: ffffba8efffd9060 WAIT: (Executive) KernelMode Non-Alertable
ffffba8efe9fbcb0 Mutant - owning thread ffffba8f23068080
IRP List:
ffffba8f24a68ee0: (0006,0118) Flags: 00060000 Mdl: 00000000
Not impersonating
DeviceMap ffffcd8c00290ca0
Owning Process ffffba8effe11080 Image: csrss.exe
Attached Process N/A Image: N/A
Wait Start TickCount 163897 Ticks: 3503 (0:00:00:54.734)
Context Switch Count 800 IdealProcessor: 6
UserTime 00:00:00.015
KernelTime 00:00:18.171
Win32 Start Address 0x00007ffefe133b90
Stack Init ffffdf8dd3eaf570 Current ffffdf8dd3eacab0
Base ffffdf8dd3eb0000 Limit ffffdf8dd3ea9000 Call 0000000000000000
Priority 16 BasePriority 13 Decay Boost 1 Unusual Boost 15 Priority Floor 16 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
ffffdf8d`d3eacaf0 fffff805`f22a7064 : 00000000`00000047 00000000`00000000 00000000`00000000 ffffe501`f41222b0 : nt!KiSwapContext+0x76
ffffdf8d`d3eacc30 fffff805`f2340fbd : 00000000`00000000 00000000`00000000 ffffdf8d`d3eacdc0 00000000`00000050 : nt!KiSwapThread+0x6d4
ffffdf8d`d3eaccc0 fffff805`f233f1b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x39d
ffffdf8d`d3eacd50 fffff805`35e488cc : ffffba8e`fe9fbcb0 fffff805`00000000 ffffcd8c`1eacfb00 fffff805`2f7a5300 : nt!KeWaitForSingleObject+0x859
ffffdf8d`d3eace30 fffff805`3597909b : 00000000`00000000 00000000`000004b8 ffffba8e`fb602000 00000000`00000040 : igdkmdn64+0x4d88cc
ffffdf8d`d3eace70 fffff805`359c6e76 : ffffba8e`febc1698 00000000`00000000 ffffdf8d`d3ead020 ffffba8e`febc1000 : igdkmdn64+0x909b
ffffdf8d`d3eaceb0 fffff805`35bb64b7 : fffff805`2f89d5a8 00000000`09b1864c ffffba8e`febba000 ffffdf8d`d3ead020 : igdkmdn64+0x56e76
ffffdf8d`d3eacf20 fffff805`35bb8188 : ffffdf8d`d3ead358 ffffdf8d`d3ead320 00000000`00000000 fffff805`2f928a8b : igdkmdn64+0x2464b7
ffffdf8d`d3ead060 fffff805`35bb715b : ffffdf8d`d3ead830 00000000`00000000 ffffdf8d`d3ead460 00000000`00000000 : igdkmdn64+0x248188
ffffdf8d`d3ead2a0 fffff805`35b9f494 : ffffb7dd`4793c000 fffff805`35b5fa30 00000000`00000000 00000000`0000000a : igdkmdn64+0x24715b
ffffdf8d`d3ead360 fffff805`35b9ea42 : ffffba8e`feba8388 fffff805`3597919f ffffba8e`f9d10000 ffffba8e`f9dbb6a5 : igdkmdn64+0x22f494
ffffdf8d`d3ead670 fffff805`35b6b788 : ffffba8e`fea51de0 ffffdf8d`d3ead759 00000000`00000008 fffff805`35b86282 : igdkmdn64+0x22ea42
ffffdf8d`d3ead6c0 fffff805`35b72e26 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : igdkmdn64+0x1fb788
ffffdf8d`d3ead7c0 fffff805`35b30fe8 : ffffba8f`26b07bc0 ffffdf8d`d3eadbd0 ffffdf8d`d3eadbd0 00000000`00000000 : igdkmdn64+0x202e26
ffffdf8d`d3eadad0 fffff805`35b0c6a9 : ffffba8e`f9d10000 ffffdf8d`d3eadea0 ffffba8e`fb602000 00000000`00000000 : igdkmdn64+0x1c0fe8
ffffdf8d`d3eadda0 fffff805`359a622a : ffffcd8c`1a5c8900 ffffba8e`fece8a60 00000000`00000000 ffffba8e`fb602000 : igdkmdn64+0x19c6a9
ffffdf8d`d3eae190 fffff805`2e9b85fb : ffffdf8d`d3eae3c0 00000000`00000000 ffffba8e`ffec8c10 fffff805`f225df90 : igdkmdn64+0x3622a
ffffdf8d`d3eae2c0 fffff805`2e92ceab : 00000000`00000000 ffffdf8d`d3eae530 ffffcd8c`1a5c7960 ffffdf8d`d3eae750 : dxgkrnl!ADAPTER_; : ffffcd8c`083ac2c0 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VIDPN_MGR::SetTimingsFromVidPn+0x7bb
ffffdf8d`d3eae6d0 fffff805`2e80d016 : 00000000`00000000 ffffdf8d`d3eae900 00000000`00000000 fffff805`f225df90 : dxgkrnl!VIDPN_MGR::PowerOnOffVidPnTarget+0x14e
ffffdf8d`d3eae8b0 fffff805`2e83dfdc : ffffcd8c`082df750 ffffba8e`fe9bacf8 00000000`00000002 00000000`00000000 : dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x4c6
ffffdf8d`d3eae930 fffff805`2e83d986 : ffffba8e`fee56c20 00000000`00000002 ffffba8e`fe9bad18 ffffdf8d`d3eaec01 : dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0x2cc
ffffdf8d`d3eaea80 fffff805`2e83d55a : ffffba8e`fe9bad58 00000000`00000000 ffffdf8d`d3eaeb80 ffffba8e`fe9bacf0 : dxgkrnl!MONITOR_MGR::_EnableDisableMonitorInternal+0x152
ffffdf8d`d3eaeb00 fffff805`2e9de032 : 00000000`00000000 ffffba8e`fedab000 00000000`00000000 ffffba8e`f60560d8 : dxgkrnl!MONITOR_MGR::_EnableDisableMonitor+0x1a6
ffffdf8d`d3eaebb0 fffff805`2e9d7acc : ffffba8e`f6055000 ffffdf8d`00000001 ffffdf8d`d3eaee50 ffffba8e`f6055100 : dxgkrnl!MonitorEnableDisableMonitor+0x216
ffffdf8d`d3eaec60 fffff805`2e9dc49e : ffffdf8d`d3eaeed9 fffff805`2e5d480f ffffdf8d`d3eaef10 fffff805`2e85c1df : dxgkrnl!DxgkPowerOnOffMonitor+0xf8
ffffdf8d`d3eaeda0 fffff805`2e94a82f : ffffba8e`ffffffff ffffba8f`24a68ee0 ffffdf8d`d3eaef19 ffffba8e`fed9de60 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x5fe
ffffdf8d`d3eaee50 fffff805`f23741fb : 00000000`00000000 fffff805`34033912 00000000`c0000002 00000000`00000014 : dxgkrnl!DpiDispatchInternalIoctl+0xff
ffffdf8d`d3eaef80 fffff805`f2374173 : ffffcd8c`0851f001 ffffdf8d`d3eaf050 ffffdf8d`d3eaf040 fffff805`34037332 : nt!IopfCallDriver+0x5b
ffffdf8d`d3eaefc0 fffff805`34037363 : 00000000`00000001 00000000`00000004 ffffcd8c`04032350 fffff805`341054f4 : nt!IofCallDriver+0x13
ffffdf8d`d3eaeff0 fffff805`3406cfc8 : ffffcd8c`04032350 ffffdf8d`d3eaf0f9 00000000`00000001 ffffba8e`fee58820 : win32kbase!GreDeviceIoControlImpl+0xff
ffffdf8d`d3eaf090 fffff805`3406cbbf : 00000001`0000000e 00000000`00000000 fffff805`2e58e9c8 00000000`00000001 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x3e8
ffffdf8d`d3eaf160 fffff805`34104555 : 00000000`00000011 fffff805`2e58e9c8 ffffdf8d`d3eaf1f0 fffff805`2e58e9c8 : win32kbase!DrvSetMonitorPowerState+0x2f
ffffdf8d`d3eaf190 fffff805`34109ff6 : 00000000`00000000 00000000`00000000 00000000`00000020 00000000`00000000 : win32kbase!PowerOffMonitor+0x255
ffffdf8d`d3eaf230 fffff805`3410980d : ffffba8e`fffd9060 ffffba8f`348c4a30 00000000`00000001 00000000`00000020 : win32kbase!xxxUserPowerEventCalloutWorker+0x376
ffffdf8d`d3eaf300 fffff805`3a2ed792 : ffffba8e`ffe93080 ffffdf8d`d3eaf460 00000000`00000000 00000000`00000020 : win32kbase!xxxUserPowerCalloutWorker+0x13d
ffffdf8d`d3eaf380 fffff805`2e4b7b2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtUserUserPowerCalloutWorker+0x22
ffffdf8d`d3eaf3b0 fffff805`f26be355 : 00000001`5e5f5f19 00000000`00000108 ffffba8e`ffe93080 00000000`00000000 : win32k!NtUserUserPowerCalloutWorker+0x2e
ffffdf8d`d3eaf3e0 00007ffe`ff19caf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 (TrapFrame @ ffffdf8d`d3eaf3e0)
000000f4`5e97fd08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`ff19caf4