BSOD on Zenbook only when using Zoom

zbook · May 27, 2024

Please restart WDV with these customized tests:

Code:

    [ ] 0x00000010 I/O verification.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

druekberg · May 27, 2024

Well, that one threw a BSOD on reboot. But I can't get back to Windows. I tried rebooting twice, then found the directions to disable Verifier from the repair command prompt, but it still gets BSOD on boot. (Entered the Bitlocker code so many times I almost have it memorized.) I didn't try to disable Verifier from Restore point because I was afraid I would override the dump files I need for V2 report. Help! I'm locked out of using my laptop (writing this on my phone).

druekberg · May 27, 2024

Okay, I was finally able to get back into Windows by running Startup Repair. MyASUS did not run when I logged in, but maybe it will next reboot.

The BSOD Stop code was DRIVER_VERIFIER_DETECTED_VIOLATION and the driver listed as failing was admakdrv.sys, which apparently is associated with AOMEI Backupper, which I have on my system. I can uninstall that if that's the culprit and look for another backup program. But I'm wondering if there are other drivers at fault.

I ran V2 and the current log is here.

zbook · May 28, 2024

1) Please make a new restore point.

2) Restart WDV with the same customized tests and test all non-Microsoft drivers except admakdrv.sys

Code:

Event[49878]
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2024-05-27T22:14:49.2940000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RUEK_ZENBKPRO15
  Description:
Startup Repair successfully completed repairs.

Code:

Event[49881]
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2024-05-27T22:14:49.2940000Z
  Event ID: 1208
  Task: N/A
  Level: Information
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RUEK_ZENBKPRO15
  Description:
Restored system to an earlier restore point.

druekberg · May 28, 2024

I set up WDV as instructed.

On reboot BSOD: DPC_WATCHDOG_VIOLATION (this is the error that I usually got when Zoom crashed).
I rebooted again: BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Failed: ndis.sys

Auto repair only offered to Restore. I skipped Restore and rebooted, entered Advanced Options, CMD prompt, disabled Verifier.
Entered Windows and ran V2.
Results are here.

Thank you for your continued help!

BTW in response to @jvickers earlier post, I ran Windows Memory Diagnostic before all this and there were no errors.

jvickers · May 28, 2024

druekberg said:
I set up WDV as instructed.

On reboot BSOD: DPC_WATCHDOG_VIOLATION (this is the error that I usually got when Zoom crashed).
I rebooted again: BSOD: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Failed: ndis.sys

Auto repair only offered to Restore. I skipped Restore and rebooted, entered Advanced Options, CMD prompt, disabled Verifier.
Entered Windows and ran V2.
Results are here.

Thank you for your continued help!

BTW in response to @jvickers earlier post, I ran Windows Memory Diagnostic before all this and there were no errors.

It's good to see that your memory is error free. It's a simple enough thing to check. Bad memory can cause all kinds of random system errors. Glad to see that's not the case with you. I hope you and zbook can get things sorted.

zbook · May 28, 2024

Please open Administrative Command Prompt (ACP) and copy and paste:

Code:

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

Post a share link with only this compressed file.

druekberg · May 28, 2024

Here is the new memory dump zipped file.

zbook · May 28, 2024

Please restart WDV with these customized tests:

Code:

[ ] 0x00000010 I/O verification.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.

Select all non-Microsoft drivers

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

druekberg · May 28, 2024

BSOD preventing me from entering Windows 4x, even when I run the WDV reset each time. I run it from command prompt in Windows Repair, then return to options, shut down, manually restart.

Each time the stop code is DRIVER VERIFIER and the driver that fails is ambaksrv.sys, which I included in the Verifier the last time along with those 3 custom tests.

Should I go ahead and run the System Restore or is there another way to get back in?

zbook · May 28, 2024

Boot to a windows RE on a flash drive Windows 11 media creation tool or iso.

Type:

verifier /reset

or

verifier /bootmode resetonbootfail

Download Official Windows 11 ISO file from Microsoft

This tutorial will show you how to download an official Windows Server or Windows 11 64-bit or ARM64 ISO file from Microsoft. Microsoft provides ISO files for Windows Server and Windows 11 to download. You can use these ISO files to clean install or in-place upgrade Windows 11. The Flight Hub...

www.elevenforum.com

Download Windows 11

zbook · May 28, 2024

It's ok to perform system restores.

druekberg · May 28, 2024

No matter how many times I tried the laptop always hit a BSOD on restart, always with ambakdrv.sys causing the failure. I tried to run Windows RE from my USB drive, and from the built-in ASUS RE option, but these did not work. When I got to repair options I opened a command prompt and ran verifier /bootmode resetonbootfail but this did not help.

After many attempts I finally did a System Restore. Booted into Windows, but not everything was loading, so I rebooted, and things loaded normally. Then I ran WDV with the 3 custom tests you listed last
[ ] 0x00000010 I/O verification.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.

and all non-MS drivers EXCEPT ambakdrv.sys.

Booted into Windows without BSOD.

Here is the verifier /querysettings result.

Should I assume ambakdrv.sys is the problem and uninstall AOMEI Backupper?

druekberg · May 28, 2024

Or rather than uninstalling AOMEI Backupper, should I just follow these instructions? (I don't need to boot from WinPE because I can boot into Windows).

zbook · May 28, 2024

Temporarily uninstall Aomei software.

Make a new restore point.

Restart WDV with these customized tests:

[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.

Select all non-Microsoft drivers

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

Tomorrow I'll have limited time.

If possible please respond quickly.

druekberg · May 28, 2024

7th run: Uninstalled AOMEI Backupper and ran WDV with 2 custom tests
No BSOD
Click for results

zbook · May 28, 2024

Test:

[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.

zbook · May 28, 2024

Click for results was not responding.

druekberg · May 28, 2024

No BSOD
Click for results

Not sure why that previous link didn't work for you, it works for me. Anyway, I'm putting all the query results in the same doc.

zbook · May 28, 2024

Test:
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x02000000 Code integrity checks.

What options to view results?

BSOD on Zenbook only when using Zoom

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

The lunatics have taken over the asylum

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Similar threads