LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does labview generate Dr. Watson error "C0000005 access violation"

I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration

*----> System Information <----*
Computer Name: ANDANTE
User Name: Administrator
Number of Processors: 2
Processor Type: x86 Family 6 Model 8 Stepping 3
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free

I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.

When the crash occurs, I see a dialog appear with the error

labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.

The Dr. Watson error log is generated and the error is

Application exception occurred:
App: (pid=1160)
When: 4/25/2004 @ 01:57:56.640
Exception number: c0000005 (access violation)

I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.

Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.

Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.

Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:

State Dump for Thread Id 0x574

eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246


function: StrLen
00748230 55 push ebp
00748231 8bec mov ebp,esp
00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
0074823b 84d2 test dl,dl
0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
0074823f 8a10 mov dl,[eax] ds:00000062=??
00748241 40 inc eax
00748242 84d2 test dl,dl
00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
00748246 2bc1 sub eax,ecx
00748248 48 dec eax
00748249 5d pop ebp
0074824a c3 ret

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA

*----> Raw Stack Dump <----*
0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....
0 Kudos
Message 1 of 3
(3,384 Views)
For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.
0 Kudos
Message 2 of 3
(3,384 Views)
Pardon me. I completely forgot an obvious solution. See if you get the error if you run the evaluation version of LabVIEW 7. It could be the solution to the problem has already been found.
0 Kudos
Message 3 of 3
(3,384 Views)