DAQmx error 200361, on board device memory overflow problem

[ghillisniper]

I'm not sure if this is the proper place to post this question but it seems to be.  I also notice that several people have had similar issues; however, in my case I'm not sure that I can change any settings inside the software.

Specifics:

I have a machine that performs tensile tests on materials.  The machine uses a force sensor and extensometer which both communicate with a signal conditioner and that is compiled inside software that our company made based on some NI software.  We use our software and NI DAQmx (the current version that we link on our website is NI-DAQmx Run-Time Engine (core) v9.0.2.

The PC in the test machine had a mother board failure and we purchased a new PC to replace it.  We had been using Windows XP but I upgraded to Windows 7 for the new PC.  After installing our software and the NI-DAQmx (both the version we link on our website and the latest version 9.7) I've been receiving the "On board device memory overflow" error 200361 AND another error about the transfer being aborted by the client (error 50405).  I've installed both our software and the drivers in the Program Files X 86 folder and in the C drive and while the behavior sometimes changes in when it occurs it always occurs.  We have also been able to run up to 5 or 6 tests in a row with no errors but we always wind up getting an error.  Sometimes error 50405 occurs as soon as our software is opened.

The problem with our software is that it is meant to be interfaced in a very simple and rigid way.  The tests are always the same and minimal user input is requred.  This being the case, there is no way for the user (me in this case) to adjust any sampling rate settings.

From my reading it appears that this could be an issue with Windows 7.  I hope to wipe the OS off the computer and reinstall a Windows XP OS to see if it helps but I am looking for any help on any work arounds or clarification on what can be done to fix the issue on Windows 7, if such a thing exists without being able to adjust the software.

Thanks.

[Deagle]

Ghillisniper,

If I understand you correctly, this setup was working on your previous computer and seems to be a result of upgrading your system. Can you provide some more information about the specific hardware you are using?

[ghillisniper]

I aplogize, Bryan, for not responding to this.  I had trouble finding it for awhile then we had some other changes to our system and I wound up starting a new thread (since I couldn't find this one).  It may not help and I don't mean to have two threads going but I really need to get this worked out and I'm kind of at a brick wall.  I have 3 different high priority test jobs that are waiting for this machine to get fixed.

So, we did have a setup that worked correctly on our previous computer.  The new computer we purchased is basically identical to the old one.  We specifically bought the same specs. Memory is DDR2, PC2-6400, 800MHz, 2 GB.  The processor is a Socket 775, Core 2 Duo, 2MB L2 cache, 2.20 GHz.  It has on board video with a NVIDIA GeForce 7050 GPU although I don't know that it matters.  Also possibly of no consequence, it has a 200 Watt power supply.  The only difference initially with the new computer is that it ran Windows 7 as an OS.

The test machine itself has a hydraulic pump and accumulator that provide hydraulic pressure to a cylinder that pulls samples for tensile tests.  There is an extensometer and a load cell that measure data during the test.  The load cell is a PCB 224C and it communicates first with a PCB signal conditioner.  That signal conditioner and a Honeywell extensomter communicate to a printed circuit board that has an NI USB-6009 OEM attached.  That USB-6009 then sends the signal through USB to the computer.

The only other USB device connected to this computer is the touch screen monitor.

The error had been happening fairly often but somewhat intermittently at first.  We switched to Windows XP and that seemed to fix the problem initially.  However, it resurfaced after a week or so.  I've reinstalled the drivers, updated the drivers, rolled the drivers back, reinstalled our software, and finally purchased a new USB-6009 OEM board.  I installed the new USB-6009 but our software could not "see" it.  I installed MAX and it can't see it either although the device does show up in Windows Device Manager.  I put the old USB-6009 in, now the Windows Device Manager can see it and our software can see it but MAX still can't and it just threw the original error at me again.  I'd like to test the new board but if my software can't see it then I can't run the test so I'm not really sure what to do.

I think that catches you up to speed on the matter.  Here is the other thread where we basically went over all the new developments:  http://forums.ni.com/t5/Real-Time-Measurement-and/DAQmx-Software-package-not-working-in-Windows-7/m-... 

Thank you for your time and again, I aplogize for not replying to this for so long.