Windows XP Rebooting

[LouL]

We have an instrument configured as follows:
- Windows XP
- VB6 with MStudio. I try to keep everything to latest and greatest.
- PCI-1200 for external triggered DAQ.

Here is what happens:
1. System is at one of the acquisition screens armed and waiting for an external trigger.
2. Operator walks away.
3. Operator returns and causes an external trigger
4. XP reboots

I haven't ascertained how long it has to set before this would occur but it appears to be in 10 - 20 minute range. The work around is to press one of the buttons on the screen that would cause access to the DAQ board (reconfigure etc). This has been going on since we switched to XP but I haven't had time to deal with it. Also we have all power saving turned off (XP and BIOS).

Any help would be appreciated.

TIA
Lou

[George M.]

Hi,

Which driver version are you using? Can this behavior be duplicated on another computer? Can you run one of the shipping examples and exhibit the same behavior?

Let me know. Thanks.

George

[jreichert]

Hello,
I've had a similar problem with Win 2000 rebooting when I was working with NI GPIB.

Win2000, XP have a default setting for rebooting when driver faults occur ("bluescreen").
But perhaps you want to see yout bluescreen instead of automatically reboot?
That might provide you more error infos...

Sorry, I have a german windows, the descriptions might differ...

1) Choose "Start/ System settings/ System
2) Here choose thar last Tab "Extended"
3) Choose "settings" of "Start and recover"
4) => Uncheck: Automatically reboot

Effect: You should see the bluescreen with your driver error next time the error occurs.

Hope this helps,
Jörg

[LouL]

Finally saw this happen on a system yesterday (it has been reported but I never actually saw it happen).

We have taken to unchecking the Automatically Reboot what was displayed is as follows (not to mention all the other fun stuff on the blue screen):

DRIVER_IRQL_NOT_LESS_OR_EQUAL

The offending driver is listed as  NIDAQ32K.sys

As we send more systems into the field with WinXP on, we are seeing this more.

Any help would be appreciated.

[Shawn B.]

LouL,

Unfortunately all we can tell is that NI-DAQ is probably responsible for the crash.  My first recommendation would be to install the latest version of NI-DAQ.  It is possible that this problem has already been fixed in a newer version of the driver.

I would also recommend having your machine create a kernel memory dump when it crashes.  You can turn this feature on in the same location where you turned off the Automatically Reboot setting.  The Kernel Memory dump will give us more information about why the machine is crashing.  The dump file normally gets stored in c:\WINDOWS\MEMORY.DMP

Shawn B.
National Instruments