Windows 10: Computer crash by driver ndu.sys

Discus and support Computer crash by driver ndu.sys in Windows 10 Drivers and Hardware to solve the problem; I am having frequent BSOD crashes in the last week with error like "SYSTEM_THREAD EXCEPTION NOT HANDLED" "KERNEL_SECURITY CHECK FAILURE" along with... Discussion in 'Windows 10 Drivers and Hardware' started by Wai YenTang, Jun 1, 2020.

  1. Computer crash by driver ndu.sys


    I am having frequent BSOD crashes in the last week with error like "SYSTEM_THREAD EXCEPTION NOT HANDLED" "KERNEL_SECURITY CHECK FAILURE" along with ndu.sys as the identified driver. I have searched and checked previous related queries, so I have updated drivers, did sfc scans, windows memory diagnostics. Even did one with driver verifier.


    Here is the link will expire on 12 June with all the minidumps


    https://drive.google.com/drive/folders/1RNfdd69qxPTUc6I4aJmn0dZQkk7898Uy?usp=sharing

    :)
     
    Wai YenTang, Jun 1, 2020
    #1
  2. Junaid_A Win User

    Laptop crashes caused by 'rtkvhd64.sys'

    Hi Regal,

    Thank you for writing to Microsoft Community Forums.

    To have a better clarity on this issue and guide you accordingly, kindly help us with the following information:

    • What is the make and model of the laptop?
    • Which build of Windows 10 is installed on the machine?

      (Search winver from the Start menu to know the same)
    • Does the computer boot to the desktop?
    • Are you aware of any changes that happened on the computer prior to which this issue started to occur?

    Upon analyzing the crash dump files, seems like the crash is caused by
    rtkvhd64.sys. I suggest you to try the methods listed below and check if it works.

    Method 1

    I suggest you to uninstall the Realtek HD Audio drivers
    installed on the machine and let Windows to search for the update and install the updated drivers.

    • Right click the Windows icon on the taskbar and choose
      Device Manager.

    • Expand Sound, video and game controllers and locate
      Realtek HD Audio drivers.
    • Right click on it and choose Uninstall.
    • Check the box Delete the driver software for my device
      and reboot the machine to see if the issue persists.

    If the issue persists, try Method 2

    Method 2

    If letting windows to install the drivers automatically doesn’t resolve the issue, you may install the latest audio drivers from PC manufacturer’s website and see if it resolves the issue.

    Meanwhile, you may also want to go through Troubleshoot blue screen errors
    and see if it helps.

    If the issue persists, revert to us with the latest crash dump file.

    Let us know how it goes.

    Regards,
     
    Junaid_A, Jun 1, 2020
    #2
  3. Inokis Win User
    Steelseries Merc Keyboard driver alpham164.sys disabled after windows 10 creator update why? how to undo/force it?

    well I'll do the best I can to go step by step:

    • Boot With Driver Signing disabled
    • With Zengine installed, go to your "Saved Bettam folder"\Kernel2k\Bettam12.inf.
    • Right click and select install.
    • Go to your %SystemRoot%\System32\DriverStore\FileRepository\ and make sure the Bettam12_* folder is created... *being the alphanumeric hash that is generated when you install a driver.
    • If this folder is created then go to regedit
    • Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham164.sys
      • Edit the Source entry to your %SystemRoot%\System32\DriverStore\FileRepository\ bettam12_*\Bettam164.sys
    • Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam164.sys
      • Verify it contains the same information
    • Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham264.sys
      • Edit the Source entry to your %SystemRoot%\System32\DriverStore\FileRepository\ bettam12_*\Bettam264.sys
    • Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam264.sys
      • Verify it contains the same information
    • Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham164.sys
      • Edit Source to your %SystemRoot%\System32\DriverStore\FileRepository\bettam12.inf_*\Bettam164.sys
    • Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham264.sys
      • Edit Source to your %SystemRoot%\System32\DriverStore\FileRepository\bettam12.inf_*\Bettam264.sys
    • Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam164.sys
      • Verify it contains the same information
    • Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam264.sys
      • Verify it contains the same information
    • Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB in a VID Key
    • If not Search for Alpham1 in that tree and change LowerFilters to Bettam1
    • Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Alpham1
      • Change ImagePath to your "Saved Bettam Drivers\Kernel2k\Bettam164.sys" folder
    • Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Bettam1
      • Verify it contains the same information
    • Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB in a VID Key
    • If not Search for Alpham1 in that tree and change LowerFilters to Bettam1
    • Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Alpham1
      • Change ImagePath to your your "Saved Bettam Drivers\Kernel2k\Bettam164.sys" folder
    • Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Bettam1
      • Verify it contains the same information
    • Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\oem34.inf
      • Change both Default and Active to your "bettam12.inf_*" folder thats in System32
    • Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\oem35.inf
      • Change both Default and Active to your "bettam12.inf_*" folder thats in System32
    • Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\alpham12.inf_*
      • Change InfName to Bettam12.inf
      • Change OEMPath to your "Saved Bettam Files\Kernel2k" folder
    • Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\alpham12.inf_amd64_932fbe5113b0010d\Configurations in a HID_Keypad entry
    • If not Search for Alpham1 in that key and change LowerFilters to Bettam1
    • Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\bettam12.inf_*
      • Verify it has the same information as the previous Alpham1.inf_* entry
    • Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\bettam12.inf_*\Configurations in a HID_Keypad entry
    • If not search for Alpham1 and change LowerFilters to Bettam1

    If any of the Alpham entries are missing, or you previously renamed any of the Alpham keys, reinstall Zenginge from scratch and then start from the beginning of these steps.

    Reboot your computer with Driver Signing Disabled again and See if Zengine is working. If Zengine is red Open Device Manager. Verify the Bettam164.ys and Bettam264.sys are listed, If they are missing and if there is no Alpham164.sys or Alpham264.sys then
    begin updating drivers. Use the saved Bettam drivers in your Kernel2k path. If everything is working you can reboot normally.
     
    Inokis, Jun 1, 2020
    #3
  4. Computer crash by driver ndu.sys

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (igdkmd64.sys)

    Hi Nezar,

    Thank you for posting on Microsoft Communities.

    I will be glad to help you with the issue you have with the computer. I understand the frustration when things don't work the way it should.

    What is the make and model of your computer?

    File igdkmd64.sys is the Intel Graphics Kernel Mode Driver for Microsoft Windows 8.

    I would suggest you to follow the steps provided below:



    Step 1:

    Uninstall the Device from Device Manager

    • Open Device Manager
    • Expand the Display Adapter section.
    • Find the Display card Driver.
    • Right click Display card Driver and select
      Uninstall.
    • Select the check box delete the driver software for this device.
    • Reboot the computer after uninstall process has finished.

    Step 2:

    Uninstall the Device Drivers from Program List in Control Panel

    • Click on start, select Control Panel
    • Now click on Programs and select Programs and Features.
    • Find the Display card Driver.
    • Right click Display card Driver and select
      Uninstall.
    • Reboot the computer after the uninstall process has finished.
    Hope this helps and do let us know if you need any assistance.
     
    Ruth Buruga, Jun 1, 2020
    #4
Thema:

Computer crash by driver ndu.sys

Loading...
  1. Computer crash by driver ndu.sys - Similar Threads - Computer crash driver

  2. Computer Driver Crashing

    in Windows 10 Gaming
    Computer Driver Crashing: Hello, I am asking a question as a continuation of a previous post, which the link is here:https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/graphics-driverrealtek-network-driver-failing/f27f85d7-3cf0-4a28-ba97-b5fdaacdc9de After the problems I faced...
  3. Computer Driver Crashing

    in Windows 10 Software and Apps
    Computer Driver Crashing: Hello, I am asking a question as a continuation of a previous post, which the link is here:https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/graphics-driverrealtek-network-driver-failing/f27f85d7-3cf0-4a28-ba97-b5fdaacdc9de After the problems I faced...
  4. Computer Driver Crashing

    in Windows 10 BSOD Crashes and Debugging
    Computer Driver Crashing: Hello, I am asking a question as a continuation of a previous post, which the link is here:https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/graphics-driverrealtek-network-driver-failing/f27f85d7-3cf0-4a28-ba97-b5fdaacdc9de After the problems I faced...
  5. UsbHub3.sys driver crash with USBIP

    in Windows 10 Gaming
    UsbHub3.sys driver crash with USBIP: I've been working on a USBIP driver for Windows 10 22H2. It's been performing well so far, however I get a BSOD occasionally after enumerating a new device.The BSOD occurs when UsbHub3.sys attempts to get all the device descriptors from the USB device. The USBIP driver...
  6. UsbHub3.sys driver crash with USBIP

    in Windows 10 Software and Apps
    UsbHub3.sys driver crash with USBIP: I've been working on a USBIP driver for Windows 10 22H2. It's been performing well so far, however I get a BSOD occasionally after enumerating a new device.The BSOD occurs when UsbHub3.sys attempts to get all the device descriptors from the USB device. The USBIP driver...
  7. UsbHub3.sys driver crash with USBIP

    in Windows 10 Drivers and Hardware
    UsbHub3.sys driver crash with USBIP: I've been working on a USBIP driver for Windows 10 22H2. It's been performing well so far, however I get a BSOD occasionally after enumerating a new device.The BSOD occurs when UsbHub3.sys attempts to get all the device descriptors from the USB device. The USBIP driver...
  8. BSOD issue / NDU.Sys - Ndu!CarDisableCacheAwareReference+30

    in Windows 10 BSOD Crashes and Debugging
    BSOD issue / NDU.Sys - Ndu!CarDisableCacheAwareReference+30: Hi team, I'm facing a BSOD issue using my Dell Vostro 3681 Desktop. I tried updating all drivers & windows update also. Integrated test doesn't show a hardware issue. Please find attached the dump file >...
  9. BSOD L1C63x64.sys driver

    in Windows 10 BSOD Crashes and Debugging
    BSOD L1C63x64.sys driver: Hi, I am getting BSODs and the error message it gives is: Driver_IRQL_NOT_LESS_OR_EQUAL(L1C63x64.sys) I believe that is the Qualcomm Atheros Network driver, but mine is up to date to the last Windows8 compatible driver on the Atheros website. This leads me to believe...
  10. Driver IRQL_NOT_LESS....(bwcW10.64.sys)

    in Windows 10 BSOD Crashes and Debugging
    Driver IRQL_NOT_LESS....(bwcW10.64.sys): I just did a completely fresh install to my computer today on a new ssd. I have been getting this BSOD error since I started it the first time. I have installed all the drivers but I think that one of them is causing the error since it says its a Driver IRQL_NOT_LESS_OR_EQUAL...

Users found this page by searching for:

  1. ndu.sys system thread exception not handled