Provide sources , information, and resolutions relating to Kollmorgen actuators…
- User
Provide sources , information, and resolutions relating to Kollmorgen actuators connected to a national instrument DAC via ethernet to a realtek NIC on a pc causing blue screen of death
Assistant
Kollmorgen Actuators with National Instruments Hardware and Realtek NIC BSOD Issues
When using Kollmorgen actuators with National Instruments data acquisition controllers (DAC) over Ethernet through a PC with Realtek Network Interface Cards (NICs), blue screen of death (BSOD) issues can occur. This comprehensive guide covers the setup, connection details, common problems, and solutions for this specific configuration.
Kollmorgen and National Instruments Integration
Kollmorgen AKD drives can be controlled by National Instruments hardware through EtherCAT communication protocol. This setup typically involves:
- Kollmorgen AKD servo drives or motors with EtherCAT capability
- National Instruments CompactRIO (cRIO) controllers
- LabVIEW software for programming and control
- Ethernet connectivity between components
The AKD EtherCAT drives connect to the network via RJ-45 connectors at ports X5 (in port) and X6 (out port), with built-in LEDs indicating communication status[2]. For National Instruments integration, the AKD drives need proper configuration through the WorkBench software before connecting to the NI hardware[1].
Common Configuration Methods
1. Using NI SoftMotion with EtherCAT
National Instruments provides dedicated hardware and software components for motion control:
- NI SoftMotion Engine (Real-Time-Based)
- FPGA-Based NI SoftMotion Components
- Hardware interfaces including:
- EtherCAT AKD Drives
- Drive Interface Modules (NI 951x C Series)
- Drive Modules (NI 950x)[10]
For EtherCAT connection to AKD drives, you typically need to:
- Configure the AKD drive with WorkBench
- Set up the basic drive functions
- Configure EtherCAT parameters
- Connect to the National Instruments hardware via EtherCAT[2]
2. Alternative Approaches Without SoftMotion
If NI SoftMotion is too expensive, alternative approaches exist:
- Modbus-based control systems: These have been successfully developed for Kollmorgen drives using Ethernet connectivity[7]
- Direct LabVIEW communication: Using LabVIEW to directly communicate with AKD drives without requiring SoftMotion modules[3]
BSOD Issues with Realtek NICs
When Kollmorgen actuators connect through Ethernet to a PC with Realtek NICs, blue screens can occur due to driver incompatibilities. These issues commonly present as:
- BSOD when connecting the Ethernet cable: System crashes immediately when the Ethernet cable is plugged in[12]
- BSOD during data transfer: System crashes when attempting to download or transfer large amounts of data[13]
- BSOD with specific error codes: Often related to memory management or network drivers
Common BSOD Error Patterns
- Error codes like
0xA_ntMiFreeWsleList+1a5 - Event logs showing "fault bucket" errors related to network components[11]
- Crashes specifically during high network activity
Solutions and Workarounds
1. Update or Downgrade Realtek Drivers
The most common solution is installing the correct Realtek driver version:
- For Windows 11 systems: Install drivers dated after October 2022, as the drivers included in Windows 11 often cause compatibility issues with Realtek gigabit LAN controllers[12]
- For older Windows systems: Try both newer and older driver versions, as sometimes newer isn't better for specific hardware combinations
2. Network Configuration Adjustments
- When using WorkBench over TwinCAT to connect to Kollmorgen drives, ensure your network configuration doesn't have conflicting subnets[2]
- For EoE (Ethernet over EtherCAT) configurations, the service port and EoE network interface must be in different subnets[2]
3. Hardware Modifications
- Consider using a different Ethernet adapter if problems persist with Realtek NICs
- Some users have resolved issues by switching to MediaTek USB Wi-Fi adapters or Intel Ethernet adapters[8]
4. National Instruments Specific Solutions
When specifically working with NI hardware:
- In the AKD position control configuration, verify that the position values are scaled correctly between the AKD's native units and the application's units[1]
- Check that all necessary parameters for EtherCAT communication are correctly set in both the NI controller and the AKD drive[1]
- Ensure the
FB1.EXTENDEDMULTITURNparameter is enabled if position values need to be maintained after power cycling[1]
Setting Up TwinCAT with Kollmorgen
For TwinCAT-based systems connecting to Kollmorgen drives:
- Install the TwinCAT System Manager first, then the NC/PTP-Mode option package
- Copy the XML description of the AKD drive to the TwinCAT system (usually to
c:\TwinCAT\IO\EtherCAT) - Restart TwinCAT as it analyzes device description files during startup
- Configure network settings in TwinCAT to properly communicate with the drives[2]
WorkBench over TwinCAT Configuration
To use Kollmorgen's WorkBench software through TwinCAT while avoiding BSODs:
- Configure TwinCAT and WorkBench to use different network subnets if using both the service port and EoE
- Note that WorkBench can connect to drives through TwinCAT's EtherCAT mailbox using Ethernet over EtherCAT (EoE)
- Be aware that firmware updates cannot be performed via WorkBench over TwinCAT and must use File over EtherCAT (FoE)[2]
By understanding these components and implementing the appropriate solutions, you can avoid BSOD issues when connecting Kollmorgen actuators to National Instruments hardware through a PC with a Realtek NIC.
- User
this setup was working fine on windows 10 and was initially setup in 2018/2019. no drivers have been updated since then. the device is now on windows 11 and the BSOD is occurring
Assistant
BSOD with Kollmorgen Actuators and National Instruments Hardware on Windows 11
Your system configuration involving Kollmorgen actuators connected to National Instruments DAC via Ethernet through a Realtek NIC is experiencing Blue Screen of Death (BSOD) issues after upgrading from Windows 10 to Windows 11. This is a common problem when migrating hardware systems with older drivers to Windows 11, especially with specialized industrial hardware.
Main Causes of the BSOD Issue
The primary reason for your BSOD issues is driver incompatibility between your 2018/2019 drivers and Windows 11. Since your setup was working properly on Windows 10 with no driver updates since the initial configuration, the following specific incompatibilities are likely causing problems:
- Outdated National Instruments drivers that aren't compatible with Windows 11's new architecture
- Realtek NIC drivers that haven't been updated for Windows 11 compatibility
- The Kollmorgen actuator drivers that may require Windows 11-specific versions
National Instruments Windows 11 Compatibility Issues
National Instruments hardware and software require specific versions to work properly with Windows 11. The BSODs you're experiencing are well-documented:
- Users have reported BSOD while using National Instruments software like LabVIEW and when installing/uninstalling NI products on Windows 11[1]
- Some NI applications that work perfectly under Windows 10 can be "very erratic" on Windows 11, causing blue screens on some machines but not others[2]
- Specific issues with NI system files like "nipbcfk.sys" have been identified as causing "PAGE_FAULT_IN_NONPAGED_AREA" stop codes in Windows 11[4]
Windows 11 Architecture Changes Affecting Your Setup
Windows 11 introduced several significant changes that affect your hardware configuration:
- Windows 11 is exclusively 64-bit, unlike Windows 10 which supported both 32-bit and 64-bit architectures[8]
- Driver signing requirements are stricter in Windows 11
- Windows 11 handles hardware resource allocation differently than Windows 10
Solutions to Resolve the BSOD
1. Update National Instruments Software and Drivers
The most critical step is updating your National Instruments software and drivers to versions compatible with Windows 11:
- According to NI's compatibility matrix, most NI software requires 2022 Q3 or newer versions to properly support Windows 11[8]
- For National Instruments DAC hardware, you'll need to install the appropriate version of NI-DAQmx drivers that support Windows 11
- If your system uses LabVIEW, you need version 2022 Q3 or newer for Windows 11 compatibility[8]
2. Update Realtek NIC Drivers
Realtek network adapters often need specific driver updates for Windows 11:
- Download the latest Realtek drivers specifically for Windows 11 from your PC manufacturer's website
- If those aren't available, get generic Realtek drivers from the Realtek website
- In some cases with Windows 11, older Realtek drivers actually work better than newer ones, so if the latest drivers don't resolve the issue, try an earlier version that's still Windows 11-compatible[5]
3. Update Kollmorgen Firmware and Software
Kollmorgen components also need specific updates for Windows 11:
- Kollmorgen Automation Suite documentation confirms Windows 11 (64-bit) is supported, but you likely need the latest version[10]
- Update your AKD drives firmware using the procedure outlined in Kollmorgen documentation
- Ensure you're using a compatible version of WorkBench or other Kollmorgen software for Windows 11
4. Run System File Checker and DISM
Corrupted system files can cause BSODs, especially after an OS upgrade:
- Open Command Prompt as administrator
- Run the command:
sfc /scannow - After completion, run:
DISM /Online /Cleanup-Image /RestoreHealth - Restart your computer[5][7]
5. Check for Hardware Conflicts
Hardware conflicts can emerge after upgrading to Windows 11:
- Temporarily disconnect any non-essential USB devices
- Check Device Manager for devices with warning symbols
- If your system has multiple network adapters, try disabling all except the one connected to your Kollmorgen/NI setup
- Verify that the EtherCAT network settings haven't been altered by the Windows 11 upgrade[7][12]
6. Disable Virtualization Features
Some virtualization features in Windows 11 can conflict with industrial hardware:
- Disable Intel Virtualization Technology for Direct I/O (Intel VT-d) in BIOS
- Disable Single Root I/O Virtualization (SR-IOV) if available
- These specific virtualization features have been identified as causing BSODs with National Instruments software on Windows 11[3]
7. Consider a System Restore or Clean Installation
If the above solutions don't resolve the issue:
- Create a system restore point before making major changes
- If you have a restore point from before the Windows 11 upgrade, consider restoring to it
- As a last resort, consider downgrading to Windows 10 until all components have confirmed Windows 11 compatibility[5][7]
Prevention of Future BSODs
To prevent further issues with your industrial automation setup:
- Create system restore points before any system updates
- Check compatibility matrices from both National Instruments and Kollmorgen before future Windows updates
- Consider using Windows 11 Pro or Enterprise, which offer greater control over updates
- Document your hardware/software configuration with version numbers for easier troubleshooting
By methodically applying these solutions, you should be able to resolve the BSOD issues with your Kollmorgen actuators and National Instruments hardware on Windows 11. The key is ensuring all components have Windows 11-compatible drivers, as the older 2018/2019 drivers are very likely incompatible with the new operating system architecture.
- User
Using LabView 2019, Kollmorgen Workbench 2.1.0.3980.
BSOD Viewer show these files,, ndis.sys+b459
Assistant
BSOD with ndis.sys When Using LabView 2019 and Kollmorgen Workbench
You're experiencing a Blue Screen of Death (BSOD) error involving ndis.sys while using LabView 2019 and Kollmorgen Workbench 2.1.0.3980. This issue is particularly common when using National Instruments software like LabView on Windows 11, and the ndis.sys error specifically points to network driver problems.
Understanding the ndis.sys Error
The ndis.sys file is a critical Windows system component that's part of the Network Driver Interface Specification (NDIS). This system file manages network connections and facilitates communication between your operating system and network drivers. When BSODView shows "ndis.sys+b459", it indicates that the crash occurred in this network driver at a specific memory offset (b459).
Several factors might be causing this BSOD:
- Compatibility issues between LabView 2019 and Windows 11
- Outdated or corrupted network drivers
- Conflicts between Kollmorgen Workbench and network components
- Hardware issues with your network adapter
Specific Solutions for LabView and Kollmorgen Users
1. Update National Instruments Software
Many users report BSOD issues with LabView 2019 on Windows 11 that were resolved by updating components:
- Update PXI Platform Services Runtime to the latest version (2024 Q1 or newer)
- Check for updates to your NI-DAQmx drivers
- Consider updating LabView itself to a version certified for Windows 11 compatibility
Some users found that their BSODs disappeared after upgrading from older runtime versions (2020) to newer versions (2024 Q4).
2. Modify BIOS Virtualization Settings
National Instruments has identified specific virtualization features that can cause BSOD with their software on Windows 11:
- Disable Intel Virtualization Technology for Direct I/O (Intel VT-d) in your BIOS settings
- Disable Single Root I/O Virtualization (SR-IOV) if available
- Restart your computer after changing these settings
These specific virtualization features have been documented to cause BSOD errors with National Instruments software, especially "nipcibrd.sys" errors which often accompany ndis.sys errors.
3. Kollmorgen Workbench Configuration Files
Sometimes Kollmorgen Workbench configuration files can become corrupted and cause system instability:
- Delete the configuration folders located at:
- C:\Users[username]\AppData\Local\Kollmorgen\WorkBench[version]
- C:\Users[username]\AppData\Local\Kollmorgen\WorkBench.exe_StrongName_...[version]
- Restart Kollmorgen Workbench to rebuild these files with default values
4. Try an Alternative Version
Some users have found that version compatibility is the core issue:
- Consider temporarily downgrading to LabView 2018 instead of 2019 (reported to work for some users)
- Try a different version of Kollmorgen Workbench if available
General ndis.sys BSOD Solutions
1. Update or Rollback Network Drivers
The most effective solution for ndis.sys errors is usually driver-related:
- Press Win+X and select Device Manager
- Expand the "Network adapters" section
- Right-click on your network adapter and select "Update driver"
- If updating doesn't help, try rolling back the driver instead (Properties → Driver tab → Roll Back Driver)
- Restart your computer after driver changes
2. Run System File Checker
Corrupted system files can cause ndis.sys errors:
- Open Command Prompt as administrator
- Type
sfc /scannowand press Enter - Wait for the scan to complete
- Follow with
DISM /Online /Cleanup-Image /RestoreHealth - Restart your computer
3. Check for Hardware Issues
Consider the possibility of hardware problems:
- Try using a different network adapter if possible
- If you're using a USB Wi-Fi adapter, try a different USB port
- For built-in adapters, consider temporarily disabling it in Device Manager and using an alternative connection method
4. Scan for Malware
Malicious software can corrupt network drivers:
- Run a full system scan using Windows Security
- Consider using a reputable third-party antivirus for a second opinion scan
National Instruments and Kollmorgen-Specific Recommendations
If you're using Kollmorgen actuators with National Instruments hardware:
- Verify that the configuration parameters in both the National Instruments controller and the Kollmorgen drive are correctly set
- Check if there are any firmware updates available for your Kollmorgen drives
- Ensure that Windows 11 hasn't changed your EtherCAT network settings after upgrading from Windows 10
By systematically applying these solutions, you should be able to resolve the BSOD issues with ndis.sys when using LabView 2019 and Kollmorgen Workbench on your system.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.