Vaio Software using old .NET? Causing machine freezes?

VPCZ128GG
Freeze blank screen. Hard reboot needed.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileLoadException: Assembly is still being loaded. (Exception from HRESULT: 0x80131016)
at System.Windows.Forms.Control.WmGetObject(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
VCsystray
Assembly Version: 6.1.2.7220
Win32 Version: 6.1.2.07220
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/VCsystray.exe
----------------------------------------
VCUtility
Assembly Version: 6.1.0.4300
Win32 Version: 6.1.0.04300
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/VCUtility.DLL
----------------------------------------
KeyUtilities
Assembly Version: 6.1.0.3290
Win32 Version: 6.1.0.03290
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/KeyUtilities.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Metrics
Assembly Version: 6.0.0.13290
Win32 Version: 6.0.0.13290
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/Metrics.DLL
----------------------------------------
SelfHeal
Assembly Version: 6.0.0.13270
Win32 Version: 6.0.0.13270
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/SelfHeal.DLL
----------------------------------------
IntelMonitor
Assembly Version: 6.0.0.13290
Win32 Version: 6.0.0.13290
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/IntelMonitor.DLL
----------------------------------------
analyzer
Assembly Version: 1.0.909.1
Win32 Version: 1.0.909.1
CodeBase: file:///C:/Program%20Files/Sony/VAIO%20Care/analyzer.DLL
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

I had some .NET type errors being thrown randomly in vaio messenger and another error being thrown at shutdown, until I un-sandboxed the Vaio stuff in my Comodo firewall app. Do you have anything like that going on or does your Z throw those errors from the factory? Try selective startup to pin down what could be causing it