mcafee 8.7 blue screens on nipalk.sys scan

[rrrobbo]

Started getting blue screens on a few PCs after going to McAfee 8.7. MEMORY.DMP indicates nipalk.sys is the culprit. This only happens on a rootkit scan though. Running Labview 8.2. Any thoughts apart from not running that scan ? Have upgraded PC bios to no avail.

[Mathan]

quick search

[rrrobbo]

Thanks, but those posts are 5 years old and don't really relate. This is a new thing. McAfee was upgraded 8.5 to 8.7 and now a rootkit scan crashes on nipalk.sys. I can't see any reference to it on the web and McAfee are being less than helpful, suggesting that we need to upgrade this driver. But I can't for the life of me see how, without investing further in the Labview product to upgrade.

[John.P]

Hi rrobbo,

After looking into this issue unfortunatly there appears to be nothing on the LabVIEW end that will prevent this error.

The best suggestion i have is to simply exclude the sys file from the McAfee scan.  Hopefully this will resolve the blue screen issue.

I found this forum post detailing how to exclude a file or folder from a scan in McAfee 7.0, im assuming there should be similar functionality in 8.7.

I hope this information is useful.

Best Regards,

John Porter

Applications Engineer

National Instruments

[rrrobbo]

Solved. There is an update to Labview 8.2, which is allowed within the licensing. You can't actually exclude nipalk.sys very easily as I think it it loaded into memory and it only crashes as part of a root-kit scan. Thanks for the comments though.

[stock1623]

Where is the update?  I am having the same problem but am unsure which file I need.

Thanks

[Cahill]

I have the same problem, but I don't have the option of getting a new upgrade of LabVIEW. I'm getting this same problem with nipalk.sys causing a blue screen when doing a system scan using McAfee 8.7 with LabVIEW 7.1 on one machine and LabVIEW 6.1 on another. Any further help would be appreciated.

[steve h]

I have the same problem, some sort of mcafee scan & the PC blue screens and suggests NiPalk.sys is causing the error. Does this error come from LabView 7.1, TestStand 2.01 or any other Ni product or driver?

It is causing a lot of data loss; how can I get rid of this?

[Cahill]

The only way I've been able to get around it is to remove the Memory scan from the McAfee scan settings. I'm looking for a better solution, though.

[StevenH]

Hi Guys,

This KnowledgeBase article discusses the issue. It suggests that it could be due to the driver software an/or power fluctuations on the PCI bus.

Best Regards,

Steve