Log-File to analyze problem with crash/bluescreen

[Onlinedachs]

Hi,

im new - not only here also in my current job.

I have got a test-sqz, which crashes after a few rounds. The test has to be finished 330 times, it only works 10...40 times (without errors), then crashes windows and get a bluescreen.

I want to log my sequenz everytime (minimum requirement: after every step) in a file (.txt), so it's possible to look at it after rebooting the pc. The content itself is not important to me, especially i'm interested in the STEP, the error occured.

How could i implement it?

[j_dodek]

Hi

There are to ways,

1.) Use On-the-Fly Reporting

     just see this http://digital.ni.com/public.nsf/allkb/C9113BE0E55F22EE86256D82005E7DDB?OpenDocument 

     here last executed step (if reporting is enabled) will be reported.

2.) Override SequenceFilePreStep.

     Here you can do some stuff, like extracing the stepname and save to disk BEFORE step is executed.

Regards

Juergen