BSOD on Zenbook only when using Zoom

zbook · May 29, 2024

Restart WDV with the same customized tests.

Test all non-Microsoft drivers except:

dlcdcncm dlcdcncm c:\windows\system32\drivers\dlcdcncm660.sys

Code:

Name    [00000001] DisplayLink Network Adapter NCM
Adapter Type    Ethernet 802.3
Product Type    DisplayLink Network Adapter NCM
Installed    Yes
PNP Device ID    USB\VID_17E9&PID_4323&MI_05\8&3658094&3&0005
Last Reset    5/29/2024 11:06 PM
Index    1
Service Name    dlcdcncm
Driver    C:\WINDOWS\SYSTEM32\DRIVERS\DLCDCNCM660.SYS (3.81.0.0, 148.27 KB (151,832 bytes), 5/29/2024 9:13 AM)

Code:

dlcdcncm660.sys Fri Sep  1 02:10:50 2023 (64F18E7A)

zbook · May 29, 2024

What was the source used to replace:
DisplayLink Network Adapter: dlcdcncm660.sys

druekberg · May 30, 2024

I didn't see your last two posts (61 & 62) until just now. In the meantime, when I got up this morning, the screen was black and laptop unresponsive. I did a hard reboot and Windows started normally. I ran V2; here's the log.

I will run WDV again as instructed in #61.

The source of the updated DisplayLink file was Synaptics, which makes it. It's also available on the Plugable site, which makes the dock I use that requires it, but I didn't get it from there this time.

Last year when I first tried getting help with this problem I did contact Plugable. Based on my dump files, they blamed the problem on Norton. Here's the thread at Norton, which wasn't much help. Plugable blamed it on my old HP monitor (from 2006 or something) so I bought a new monitor, which made no difference.

PS Before I ran the new WDV (omitting the DisplayLink driver) I uninstalled DisplayLink again, and then ran a Cleaner utility they make to ensure all traces are gone. After reboot I ran a registry scan with CCLeaner to see if there were any traces, which there were not. Then I reinstalled the latest DisplayLink driver (I didn't do any cleaning with CCLeaner, just ran it to see.) Now I'll reboot to start the new WDV test.

zbook · May 30, 2024

Please run ACP:

Code:

PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post a share link.

Indicate whether you can / cannot remove all hardware / software related to Display Link for testing purposes.

Code:

LastWriteTime        Size (MB) FullName            
-------------        --------- --------            
5/30/2024 8:42:35 AM   1804.77 C:\WINDOWS\MEMORY.DMP

Code:

Event[49593]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2024-05-30T08:43:05.8640000Z
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: Info

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RUEK_ZENBKPRO15
  Description:
Unable to produce a minidump file from the full dump file.

Code:

Event[49594]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2024-05-30T08:43:05.8640000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RUEK_ZENBKPRO15
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000014f (0x0000000000000004, 0x0000000000000002, 0xfffff8071169f650, 0xffffa288de10f9a0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

druekberg · May 30, 2024

Here's the memory dump (I renamed it with today's date).

Yes, I can remove the DisplayLink hardware and software. (Sometimes when using Zoom and got a BSOD when I was disconnected from the dock that uses DL, but I hadn't uninstalled the DL software. Worth trying.)

So far no BSOD today after running the DisplayLink cleaner and reinstalling DL.

zbook · May 30, 2024

The memory dump file was not able to be used.

Please continue running WDV with all customized tests except:
[ ] 0x00000004 Randomized low resources simulation.

Code:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************

druekberg · May 30, 2024

Do you want me to rerun WDV to include the DisplayLink drivers, which I left out of the current test?

Also, I can run V2 again if you advise.

zbook · May 30, 2024

Please run WDV without testing display link. If after approximately 24 hours there are no BSOD then post new share links. Then restart WDV including display link drivers.

See if you can create a support ticket for the driver. Was it designed for Windows 10? Was it designed for Windows 11? How come Microsoft is only offering Windows 10 drivers through Windows update? Is or is not the driver DCH?

The support questions may be academic but at some point you may want to know if this is most likely a driver or a hardware problem.

druekberg · May 30, 2024

Thanks, the test without DisplayLink has been running all day. So far so good. I have contacted Plugable support and forwarded your questions. I will let you know.

druekberg · May 30, 2024

Ryoma at Plugable said this in response to your questions about the DisplayLink driver: "Regarding your questions, we would expect the DisplayLink drivers to be fully compatible with Windows 10 and 11, and Microsoft has recently updated the DisplayLink version automatically installed by Windows." Not really a definitive answer.

Then she said that looking through my error logs (Plugable has a utility to collect minidump info) she said my BIOS was out of date. My BIOS is 310 and she gave me a link to 315. I went to the page for my laptop model on the ASUS site and looked for the most recent BIOS version, and it's 310. I then chatted with ASUS support and they verified that 310 is current for my model. So it doesn't look like I am going to get much useful help from Plugable.

BTW when I came back to my laptop after being away for a few hours, it would not wake from sleep again, as happened last night. Not exactly a BSOD, but not normal. The only way to get out of it was a hard shutdown and then start it up again. It started normally.

It's still running the same verifier settings (testing everything except [ ] 0x00000004 Randomized low resources simulation and the DisplayLink Network Adapter: dlcdcncm660.sys)

verifier /querysettings report here

In the morning when 24 hours is up I will run WDV with DisplayLink drivers included.

zbook · May 30, 2024

Please post a new V2 share link into the newest post.

druekberg · May 31, 2024

Here are the V2 results.

No BSOD during this past 24 hour test, just that it wouldn't wake from sleep as noted in last night's post. It woke from sleep fine this morning.

I'll wait until I hear from you before I run the verifier to include the DisplayLink driver.

zbook · May 31, 2024

1) Turn off WDV

2) Turn off windows fast startup:

Turn On or Off Fast Startup in Windows 11

This tutorial will show you how to turn on or off fast startup in Windows 11. There are three startup modes in Windows: Cold (traditional) Wake-from-hibernation Fast Starting with Windows 8.x, the default shutdown and restart scenario has been updated and named fast startup. Fast startup...

www.elevenforum.com

3) Create a new restore point.

4) Restart WDV with all customized tests except

[ ] 0x00000004 Randomized low resources simulation.

and test only one driver: dlcdcncm660.sys

Code:

Event[48460]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2024-05-30T22:19:28.3570000Z
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RUEK_ZENBKPRO15
  Description:
Windows failed fast startup with error status 0xC00000D4.

druekberg · May 31, 2024

Done.
I will post when something fails or in 24 hours if nothing fails, whichever comes first.

druekberg · May 31, 2024

After using my laptop intermittently throughout the day, waking from sleep a few times, this evening at 9:10 I woke it from sleep to find a BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL.

What failed: dlcdcncm660.sys

V2 logs are here.

I was in the middle of writing this post when it crashed again. Same stop code and driver failure. I didn't run a new V2 for that crash.

New response from Plugable, which makes the dock that uses DisplayLink drivers:

1) The latest DisplayLink drivers are DCH compliant and fully compatible with Windows 11.
2) They suggested that this points to there potentially being an issue with the USB port or firmware on the ZBook itself and suggested I contact ASUS support, which I will do, though I have my doubts about how much help I might get.

druekberg · May 31, 2024

ASUS support had me remove NVIDIA and its drivers from Device Manager, than Scan for Hardware Changes to reinstall. Then they had me reset the BIOS. They suggested I then test Zoom. I'm headed for bed but will try in the morning.

zbook · Jun 1, 2024

Restart WDV with these customized tests:

[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

and test only one driver: dlcdcncm660.sys

druekberg · Jun 1, 2024

After I reset the BIOS last night I also installed an NVIDIA update which was pending. Soon after BSOD.

V2 report is here.

I'm now running the tests in the last message (#77).

druekberg · Jun 1, 2024

That didn't take long.

BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL.

What failed: dlcdcncm660.sys

V2 logs here.

zbook · Jun 1, 2024

The collected mini dump files and current V2 still displayed all WDV customized tests except:
[ ] 0x00000004 Randomized low resources simulation.

Restart WDV with only these customized tests:

[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

and test only one driver: dlcdcncm660.sys

BSOD on Zenbook only when using Zoom

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer