Jump to content

Bluescreen with v3 TNI Agent on Windows 7

Recommended Posts



I experience a bluescreen on Windows 7 x64 every time i run the tniwinagent.exe from the version 3.0.0 build 1601 and build 1627 on workstations with a certain ahci controller.


The bluescreen occurs in the driver iaStorS.sys (Fileversion: of the “Intel C600 Series Chispet SAS”-Controller. At the moment I have Lenovos S30 and D30, where this happens.

The driverexeption does not happen, when I scan the pc with the tniwinagent.exe from the TNI version 2.


I could not attach the minidump file from a scan I ran today. If you need it, I will send it via E-Mail.


If you need further information, I would be happy to help.



Link to comment
  • 2 weeks later...

We haven't implemented TNI v3 yet due to logistics and other projects taking precedence. But this bluescreen issue reported by karel brings up a question.


Are there new command line switches for the new v3 TNIWINAGENT.EXE program?  Is there one that maybe tells it not to do a 'low level' hardware scan, or something similar to avoid this potential issue?

Link to comment
  • 4 weeks later...

First I would like to emphasize the idea of customizing the TNIWINAGENT.EXE with command line parameters. This would be helpful for systems that work with scripted scans (as we do).

Secondly a possible workaround for the BOSD issue:
Use the TNIWINAGENT.EXE from the TNI version 2.x. This scanner did never cause any blue screens, because the deep hardware scan is possibly not being used. The .inv files which are created with the agent v2.x can be read with the TNI version 3.x.

Link to comment

Yes, it will happen in 3.1.0 too, the agent there is the same.


The problem is in bugs in the Intel driver (iastors.sys) which show themselves when the driver is being queried in a certain way for low-level hardware information.


The low-level hardware scan is now disabled by default in TNI itself (when you run the online scan from the TNI console), but it's enabled by default in tniwinagent.exe. To disable this type of scan, you should add a /nodriver switch to the command line calling the agent.


I would also suggest updating the drivers to the latest versions.


We will update the agent to disable the low-level scan by default when in the /scripted mode.

Link to comment
  • 4 weeks later...

Good news for everyone: tniwinagent.exe in the latest TNI version 3.1.1 released on July 14 was updated so that it does not cause BSOD on affected systems (the ones that have faulty Intel storage drivers "iastor*.sys"). tniwinagent.exe version is


We have added a new command-line option /driver:X, where X is 0-3, and the explanations can be found in "Options - Storage". In short, 0 - completely disable low-level scan (same as /nodriver), 1 - skip disk drive scan on all systems, 2 - skip disk drive scan if iastor*.sys driver is detected (default option), 3 - always scan everything (unsafe, previous default).


So now specifying nothing related to the driver in the command-line is the same as specifying /driver:2, i.e. default setting. Please check the new agent on the affected systems and let us know if it works well.


If you have not renewed your license for version 3.1 and later, you can still use TNI 3.0.1 or even version 2 and substitute the existing tniwinagent.exe with the new tniwinagent.exe from the installation of TNI 3.1.1.


P.S. We have also implemented the /? command-line switch in the latest agent.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...