LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

event id 1060 - cvintdrv.SYS has been blocked from loading due to incompatibility with this system

On a Windows 7 - 64 Bit Machine we are getting the below event ID just before the PC Blue Screens.

Any help appreciated

 

Event Type: 

Error Event Source: Application Popup

Event Category: None

Event ID: 1060

Date:  17/05/2012

Time:  16:28:16

User:  N/A

Computer: pc0408.domain.local

Description: \SystemRoot\SysWow64\Drivers\cvintdrv.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data: 0000:  00 00 00 00 02 00 30 00   ......0. 0008:  00 00 00 00 24 04 00 c0   ....$..À 0010:  00 00 00 00 6b 03 00 c0   ....k..À 0018:  00 00 00 00 00 00 00 00   ........ 0020:  00 00 00 00 00 00 00 00   ........

 

THEN FOLLOWED BY

 

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7000

Date:  17/05/2012

Time:  16:28:16

User:  N/A

Computer: PC0408.domain.local

Description: The cvintdrv service failed to start due to the following error: %%1275

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

 

0 Kudos
Message 1 of 3
(9,555 Views)

This patch resolves security vulnerabilities related the Port I/O and Physical Memory functions of the low-level CVI/CVI Runtime driver cvintdrv.sys. The functions in an unpatched state work as intended, but they have been identified as a security risk in the Operating System. 

 

I hope that this helps.


Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD)

0 Kudos
Message 2 of 3
(9,537 Views)

Hello Phil,

 

If you're running in a 64-bit OS, then the security patch linked above is probably not going to make this event notification go away. The patch is intended to address a security vulnerability that this driver can introduce when it executes, but this security vulnerability does not exist in a 64-bit OS since this driver is inoperable in a 64-bit OS.

 

The likely reason for this event to be triggered is because you installed some NI software that includes very old versions of the component that installs this driver -- it either installed the driver because it didn't yet support Vista and Windows 7 (ref. 46BHE3O7) or it installed a version of this driver that was not digitally signed (ref. 250518).

 

In any case, this event is harmless and is almost certainly completely unrelated to the blue screen that you've run into. This event notification is simply letting you know that the OS refused to load this driver, which should not have been installed in the first place, but no harm should come from this.

 

Luis

0 Kudos
Message 3 of 3
(9,523 Views)