LV & WinXP makes a "blue screen"

[Ulrich]

Hello,

at work we have a mysterious but big problem. We have measurement devices (=prober) controlled by a PC. On this PC we also have our LV executables.

With Win 2000 an Win NT everthing's fine. With Win XP the PC hangs up with a "blue screen". We already get a second PC, also with "blue screen". We tried LV executables Version 7.1 and 8.01, both with "blue screen". We started the prober control SW and our LV exe. Both running but doing nothing (just in a idle state).

We get the "blue screen".

It looks like a combination of LV exe, prober software and XP. We never had this problem with Win NT or Win 2000 and the same prober software and LV exe.

Have anyone out there similar problems and can give us a hint? :headbang:

many thanks in advance and have a nice weekend

Ulrich

[crelf]

Have anyone out there similar problems and can give us a hint?

It could be a whole range of things, so we need more of a hint from you - are you calling any DLLs? how are you acquiring the data from your probes? is you code large and multifunctional? if so, can you break it into smaller chunks and then build each of those into exe's to try to zero in on the problem? can you post your code so we can have a look?

[Ulrich]

It could be a whole range of things, so we need more of a hint from you - are you calling any DLLs? how are you acquiring the data from your probes? is you code large and multifunctional? if so, can you break it into smaller chunks and then build each of those into exe's to try to zero in on the problem? can you post your code so we can have a look?

Hello crelf,

sorry for the late response but on friday I wasn't online anymore. You're right, there are many possible reasons for that. We use some dlls in Sub VIs (e.g. Hostname.dll to get the PC name). Communication and data acquiring goes over the GPIB Bus (with VISA). The code is very large (300 VIs). When we get the blue screen only the main VI was running. This is not more than a main menu, waiting which Sub VI the user is choosing. The block diagram of that is posted.

We are doing more tests to figure out the problem. Over the weekend the PC was logged on "local" and there was no blue screen. But normally we need to log on to our network domain.

Right at the moment it looks like the problem is home-made.

Many Thanks

Ulrich

[Ulrich]

Hello crelf,

sorry for the late response but on friday I wasn't online anymore. You're right, there are many possible reasons for that. We use some dlls in Sub VIs (e.g. Hostname.dll to get the PC name). Communication and data acquiring goes over the GPIB Bus (with VISA). The code is very large (300 VIs). When we get the blue screen only the main VI was running. This is not more than a main menu, waiting which Sub VI the user is choosing. The block diagram of that is posted.

We are doing more tests to figure out the problem. Over the weekend the PC was logged on "local" and there was no blue screen. But normally we need to log on to our network domain.

Right at the moment it looks like the problem is home-made.

Many Thanks

Ulrich

Hi all,

we made a workaround. Log on local and map the network drives.

we don't know the problem, we didn't solved the problem but it works

have a nice day

Ulrich

[crelf]

we made a workaround

Glad to hear that you've got it working, but there's nothing obvious in your code that calls networked files - unless it's hiding in a hidden frame or a subVI. If you'd like us to look into the problem further, feel free to post your code here.

[Ulrich]

Glad to hear that you've got it working, but there's nothing obvious in your code that calls networked files - unless it's hiding in a hidden frame or a subVI. If you'd like us to look into the problem further, feel free to post your code here.

Hi Crelf,

there is no hidden frame and no subVI is running during the VI is waiting. I attached the main VI. The only thing is to update the front panel. But for this update we don't open any files (I know there are better ways to do this update). Maybe the error is somewhere in our WinXP network scripting?

Download File:post-3940-1154938783.vi

have a nice day

Uli