DAQmx Error -50152: A Hardware Failure Has Occurred

Issue Details

Error -50152 occurred at XXXX
Possible reason(s):
A hardware failure has occurred. The operation could not be completed as specified. 

Solution

• Reset MAX Configuration and test with a finite or continuous task in MAX.
  • If you are using any custom scales or tasks, create a backup of the MAX Configuration so they can be imported later.
• Change the card to a different slot in the PXI chassis.
• If the Chassis is operating via a MXIe connection to a host PC, it is recommended to test the module on a PXI system that does not include MXI connections. If you have a different chassis that you can use, try plugging the module into a different chassis and check if the issue persists.
  • If you cannot test on a non-MXI system, then make sure that you have installed the MXI-Express BIOS Compatibility Software.
  • Before creating any changes in the BIOS or installing the BIOS Compatibility software, make a backup or restore point for your computer.
  • Before or after installing the BIOS Compatibility Software, set the DIP switch 1 of your MXI Card to the ON position. Do not set any other switch to the ON position.
  • Try changing PCI/PCIe slots inside the computer. 
  • Try changing the PCIe power setting in Windows. To do so, follow these steps 
    • Open the Settings click on System and then click on Power & Sleep.
    • Click on Additional power settings.
    • Click on Change plan settings next to your current power plan.
    • Click on Change advanced power settings.
    • Expand the PCI Express section.
    • Expand the Link State Power Management option and change the power settings.
• If using a Thunderbolt MXIe Expansion, try the steps outlined in the following Knowledgebase articles:
  • Cannot See PXIe Chassis When Using Thunderbolt 
  • Driver Verifier DMA Violation Blue Screen With MXIe or Thunderbolt Modules.
• Verify other cards in the system can perform continuous or finite acquisition. If they cannot, reinstall their drivers. 
• If you have another module of the same model that you can use, test it on the same slot of the module that shows the error.
• Ensure that the hardware firmware is up to date. If not, upgrade it to the latest version.

Additional Information