Thank you, Doctor, I will look in to it.

You really have to stay on top of the iLok update du jour. They change drivers often. At least the days are gone when you could hose your entire C: drive if you installed a plug-in with a system having obsolete iLok drivers (yes, it happened to me).
 
Someone once described iLok as "a virus you willingly install yourself." 

Even acting like "top dog" and shutting your system down due to failing authorization is outrageuous by itself.
 
If I ever really need something with iLok, it will be on a separate computer and running Vienna Ensemble Pro - never on my main daw computer.

Anderton
 
Someone once described iLok as "a virus you willingly install yourself." 

That sentiment seems to be pretty well shared by some.
 
The flip-side perspective on the OP is to be thankful that SONAR interdicted the "doom" of your project. SONAR intercepting that shut down request is more of a "feature" than a "bug."

Even acting like "top dog" and shutting your system down due to failing authorization is outrageuous by itself.

The interesting part is that Tone2 software does not use iLok, but for some reason it affects their plugins. They say- hey been talking with iLok company for years and it keeps happening. all four of their plugins became unusable. The Gladiator would not show up in Sonar Plugin manager and the scan was crashing when it would get to Gladiator. I dont understand how updating iLok driver can affect already installed .dll file that was there for 2 years to a point of triggering shut down operation and making Sonar Scanner crash when it sees it. There used to be "Fix"- I heard of it couple of years ago but I had no problems so I don't remember if I installed the fix or not. But the other day I reinstalled Play (EastWest) that probably updated iLok driver. Play software also can cause issues. I personally have issue with their samples being assigned to the wrong keys or sounding several tones lover that they supposed to be. But that is another story.  

I suggest you change the thread title to something like:
 
[Solved] ILok Bug - new way to shut down computer

Or iLok by design - shuts down computer.

I discovered this feature of Tone2's plugins myself several months back. They immediately sent me working replacement VST .DLLs. Despite what Tone2 says the issue is NOT a problem with iLok. It is an issue with the way that they designed THEIR plugins. 
The presence of iLok on a system may trigger their bug, but that's not iLok's fault. The fact that they have working replacements in-house pretty much confirms this. They just appear to be very lazy with updating their installers. I also suspect that the replacement .DLL versions that they send you have copy protection disabled, which is why they say that you have to buy the product to get the fixed versions.
 
This one rest solely on Tone2.
 
-e.B

I've been having this problem for ages with Tone2 plug-ins myself. I reported it to them and they offered me that patche as well but it made no difference. In fact I just installed Sonar Platinum and when scanning plug-ins windows 8 shutdown when it got to RayBlaster. Although once they have been scanned the first time the problem doesn't happen again, its just the initial scan that causes it to shut down.