f3 path for Labview 2009 will not install.

[ed_Z]

I received the following error when I tried to install the f3 patch for Labview 2009. I am using a laptop running Windows XP SP3. 

Is there a workaround? 

What should I try next?  

Structured Exception number 0xC0000005

Exception Report:
Exception code: C0000005 (ACCESS_VIOLATION)
Fault address:  01662A50 0001:00011A50 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll

Registers:
EAX:00000000
EBX:00000000
ECX:0159E518
EDX:7C97E140
ESI:0159E518
EDI:00000190
CS:EIP:001B01662A50
SS:ESP:00230159E4D4 EBP:0159E554
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010246

Stack Trace
Address  Frame    LogicalAddr    Module    SymbolName + Offset
01662A50 0159E554 0001:00011A50 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll
01653DEC 0159EA44 0001:00002DEC C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll
016547BA 0159EDA8 0001:000037BA C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll
01654D75 0159F2A0 0001:00003D75 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll
01655592 0159F620 0001:00004592 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll
016619F7 0159F81C 0001:000109F7 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\bin\NISysInf.dll
004A0CDB 0159F8F4 0001:0009FCDB C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\setup.exe
00474363 0159FBF8 0001:00073363 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\setup.exe
00476A43 0159FC6C 0001:00075A43 C:\National Instruments Downloads\LabVIEW\2009 f3 32-bit\setup.exe

[altenbach]

Maybe the downloaded patch file is corrupt. What is the exact size?

Have you tried to clear the browser cache and download it once more? Same result?

Message Edited by altenbach on 01-19-2010 08:32 AM

[ed_Z]

The first time I tried to run the f3 patch I had pasted it from an external harddrive.  The second time I downloaded it directly from NIs website.  Both attempts had the same results.  For the direct download, the file size of the downloader  lv2009_f3devandrtepatch_downloader.exe is 132 KBytes. 

The file size of the extraction folder is

Size 173 MB (182,449,928 bytes)

File size on disk 174 MB (182,878,208 bytes)

231 Files 30 Folders

[JÞB]

Sounds like a good download.

Do you have administrative privilages on the machine?  

[ed_Z]

I contacted the administrator and they received the same error.  They performed a memory check on the RAM and there are no problems with the memory.  Are there any known issues with installing the f3 patch?

[Robbob]

Access violation exception happens sometimes with the installation of any program, and can be caused by:

Bad memory - you did a memcheck, but what happens if you just run on one stick of RAM? If that works, try the other stic. Ive had bad memory that passed a memcheck just fine, but would cause many crashes

Bad installer - You are the only customer I am aware of with this issue, and you have verified file size, so I will assume the installer is OK.

Corrupt software - It is possible a previous install became corrupt somehow...hard to diagnose, but may require a reinstall of everything

Malware/adware - another hard to diagnose, but some sites report that this can cause the issue as well.

Have you successfully installed either the f1 or f2 patch before? f3 patch includes both of those, but maybe an incremental approach would be successful?

[ed_Z]

I tried to install the Labivew 2009 Service Pack 1 update and I got the same error.  I finally gave up and removed Labview from the laptop.  When uninstalling Labview I got the blue screen of death.  I think that something is wrong with the machine.  I have installed Laview on another computer with no problems.   

[JÞB]

---

ed Z wrote:

I think that something is wrong with the machine.  I have installed Laview on another computer with no problems.   

---

Minor correction.

You have evidence that there is undoubtedly "something" wrong with the laptop.  Its time to get the Geek Squad.  Glad we were able to assist your troubleshooting efforts though.  

[craigc]

Definitely sounds like a memory fault.  I found mine out using a linux live cd; free, bootable and a detailed memory check all in one (ubuntu or similar will do)

Craig