My system - W2000 (sp2), pci-gpib(Ni-488.2 1.6), at-mio16e-10 (NI-DAQ 6.9.1), _ NO _ Visual Basic - blue screens using MAX twice resulting in BAD_POOL_CALLER. Is there a solution?

[andy_psu]

I realize that this sounds like something already posted, BUT I don't have visual basic installed. Actually, MAX causes the blue screen when I use the "Scan for Instruments" on GPIB0 or "Commuticate with Instrument" on the individual instrument. I have an HP33120A using instrument driver v2.1, an HP34401A using instrument driver v2.11, an HP34970A using instrument driver v1.1. All were downloaded here yesturday.

I haven't begun to use LabView 6i yet, although was installed.

Any help would be appreciated. I will provide more info if my situation is unique.

Thanks
,
Andy Doller
Penn State University

[Kim L]

This crash indicates that unit descriptors to some GPIB resources were not properly closed. When your program ends, make sure to insert an ibonl(n,0) call for each unit descriptor that was used in the program in whatever language you are using. Also, make sure you have a VISA Close for every VISA open if using VISA. If this does not work, run NI-SPY whenever you do any GPIB communication and have it "log to file" so that you can see what function happened just before the blue screen. If the problem persists, contact NI using the following website: http://sine.ni.com/apps/we/niae_asc.main

Kim L.
Applications Engineer
National Instruments

[alukacsk]

It is apparent that the Applications Engineer did not bother reading the problem. Obviously, the person posting the problem had did a search on NI's site and saw the comments regarding VB, which the Application's Engineer just repeated. Hmmm...I need to insert an ibon(n,0) call to clean up? Well, where can I download the source code to MAX so I can fix the problem.

I too have this same problem - new install, Win2k SP2, and MAX. Nothing else. Yet, scan for instruments and its BSOD. This is clearly poor programming on the part of NI - BSOD are the responsiblity of the developer to prevent whilst running their applications.

[Boonton1]

The "BSOD" is also a problem in Windows XP(pro).I am using VB 6.0,taking the gpib board offline using ibonl(0,0)did solve the crashing problem,but i agree with you that there should be a better solution to this from national.

[Joji]

I have seen this error before. It is when resources don't get properly released. A simple solution is to reinstall MAX. This is available from our website. Go to www.ni.com>>download>>current drivers and updates>>MAX.

Buddy Curtis
Applications Engineer

[Randy Solomonson]

Hello-

There's a Knowledge Base titled "MAX 2.0 Crashes While Doing a GPIB 'Scan for Instruments' under Windows 2000". It suggests updating VISA to solve this problem. VISA is available at ftp.ni.com/support/visa.

Please let me know if this problem continues.

Randy Solomonson
Application Engineer
National Instruments

[FredM]

Max 2.2.0.3010 self terminates every time it is started. This is an upgrade from prior versions locking up the machine so hard the BSOD looks good. This is not an improperly closed operation, since it is fresh from a boot. Laugh it off, but at our overhead rates this is costing us big time.