Troubleshooting browser crashes or performance issues on Windows 11
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
Our company experiences this weird issue on newly installed DELL Latitude 5420 laptops. When a user prints content of a webpage in Microsoft Edge or Google Chrome, the browser immediately crashes and does not print anything. The thing is that printing worked for a couple of hours and then suddenly stopped with this error.
Laptops are fully updated with DELL Support Assist and Windows update.
OS: Windows 11
Edge ver.: 103.0.1264.77 (Official build) (64-bit)
Chrome ver.: 103.0.5060.134 (Official Build) (64-bit)
Event Viewer gives this error:
Faulting application name: chrome.exe, version: 103.0.5060.134, time stamp: 0x62d59b43
Faulting module name: WINSPOOL.DRV, version: 10.0.22000.778, time stamp: 0xced4b72d
Exception code: 0xc0000409
Fault offset: 0x0000000000007d06
Faulting process id: 0xd34
Faulting application start time: 0x01d8a332a0974cce
Faulting application path: C:\Program Files\Google\Chrome\Application\chrome.exe
Faulting module path: C:\windows\SYSTEM32\WINSPOOL.DRV
Report Id: b84b5c86-2e4d-4e62-8d35-2fc798b68922
Faulting package full name:
Faulting package-relative application ID:
I appreciate your help.
Radim
Troubleshooting browser crashes or performance issues on Windows 11
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Ah that's very interesting. We do not use McAfee no, but a clean image of windows 10 works fine so it may be another application interfering like for you!
I'll have a little look around now 😊
Lewis
Hi Lewis,
Do you use McAfee antivirus? I performed exactly the same steps as you described with the same results.
Nevertheless, I installed a clean installation of Windows 11, put the machine to the domain, installed our network Xerox printer, and tried to print from Chrome and Edge - all worked fine.
Then I pushed the McAfee agent and other McAfee features (DLP, Web Control, Threat Prevention, etc) to the workstation, restarted it, and tried to print again, guess what? It failed with error ID 1000
Then uninstall the agent and printing went fine again.
Then install all McAfee products again and it is failing again... I am going to find out what causes the issue... which module.
Edit: it is EndPoint Security Platform 10.7.0.3468 in our scenario.
Radim
There are no extensions in both browsers. Regarding the printer's drivers, We are using the latest ones and we also tried a different one that worked on Win10 without any flaws.
I have the same issue with the HP Probook 450 G8.
I can print fine in Microsoft word for example but not Edge or Chrome. The error is very similar to yours with different winspool.drv versions:
Faulting application name: chrome.exe, version: 103.0.5060.134, time stamp: 0x62d59b43
Faulting module name: WINSPOOL.DRV, version: 10.0.19041.1806, time stamp: 0xdfd9c4d3
Exception code: 0xc0000409
Fault offset: 0x000000000000cf8c
Faulting process ID: 0x3424
Faulting application start time: 0x01d8a7497ef17671
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
Report ID: 89ee182b-1345-4721-8705-8b59b8168011
Faulting package full name:
Faulting package-relative application ID:
I've tried SFC /scannow as well as DISM /Online /cleanup-image /restorehealth
I've done Driver update, Windows updates and BIOS updates with no luck
This is an image we deploy to a range of devices. It works on none of the Probook 450s, but works fine on other HP laptops, and other make desktop computers too. I am lost with what else to try.
I'd be really interested to know if anyone comes up with a solution to this, and if I work it out I'll post here
-Lewis
Try update Windows and printer's driver.
Do you have any extensions installed in the Microsoft Edge?
If yes, then disable them and see if the problem persists?