-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Video, Display and Touch
- Teams call triggers dxgkrnl.sys BSOD

Create an account on the HP Community to personalize your profile and ask a question
01-27-2021 09:32 AM
Hello,
Two machines started experiencing BSOD when calling or receiving calls on Teams a few days ago. Both are PRodesk 490 G2 with Nvidia 210 vga.
The driver mentioned as causing the 0x0000003b is dxgkrnl.sys.
The Nvidia driver is from 2016 v.342.01 and no recent one from the HP support page is saying to be supported so no driver update possible.
SFC found no issues, no recent Windows update (as of 2 weeks back).
Disabling the hardware acceleration on Teams did not change anything.
Could you please advise what could cause the issue?
01-28-2021 08:45 AM
Hello
I have the same issue with a HP Compaq 8200 Elite SFF with Windows 10 Enterprise 2016 LTSB.
We have this issue since Teams Desktop client is updated to version 1.3.00.34662.
I have downgraded Teams to an older version and since then I don't have any BSOD.
But I know this is just a temporary solution because Teams will be updated automatically.
I will now re-install Windows 10 to 20H2 to see if this error persists with the newest Teams version.
01-28-2021 10:05 AM - edited 01-28-2021 10:06 AM
I'm getting the exact same issue.
I've tried a few PCs, but it only seems to effect those that have Core 2 Duo CPUs.
All the PCs I tried have the exact same Windows 10 Image (enterprise 2015 ltsb).
It seems to be related to DirectX, my knowledge isn't that great but I think it might be related to the Core 2 Duo onboard GPU, as it only seems to effect Core 2 Duo PCs.
02-04-2021 08:23 AM
Hi, I have opened a support ticket to MS but so far we had no luck.
There is a new version of Teams they asked me to install but the issue is still same.
The only workaround for now is to use web version of Teams.