M17x R2 osd error on program startup

Okay this has been going on since my last two fresh installs and its really starting to get on my nerves. Has anybody else ran into this problem and how did they fix it?

Also i don't know where to go to do what it says in the message which isn't a fix but something less annoying

An error occurred while querying for WMI data: Not supported

Unhandled exception occurred in your application. If you click continue, the application will ignore this error and attempt to continue. If you Quit the application will close immediately.

Input string was not in a correct format.

details

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

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at OSD.OSD.Get_WMI_Bri()
at OSD.OSD.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at OSD.OSD.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OSD
Assembly Version: 1.0.0.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/OSD/OSD.exe
----------------------------------------
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.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.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 can't be sure, but I think I had this same kind of trouble with OSD when I was experimenting with different builds (driver sequences) when re-doing my R2. At one point, when I was using a sequence that a tech told me to use, wherein the OSD driver was installed right after the video driver, I would get a persistent error like this one, and it would happen right at startup like you claim is happening here. I didn't think there was any way to correct it, and I rebuilt the system using a much better driver sequence.

I have posted a full set of instructions here on NBR that details my driver install sequence for an R2. It is a very long post, but if you are already comfortable with doing freshies, just check it for the sequence. If you cannot correct this error any other way (which might be the case; I couldn't either) and you resort to another fresh install as you claim you have already been "enjoying", try this out:

http://forum.notebookreview.com/ali...r2-full-detailed-description.html#post6978195

 

I also started getting this error after a clean install. I did Not try another build with a different sequence. I took OSD_Launch out of my start-up sequence since I didn't need/use it anyway.

 

Ok, but then doesn't that mean that the screen feedback doesn't happen until you "launch" it? The OSD application is supposed to run as a daemon in the background so that you get immediate on-screen feedback to touch panel (and a few other) commands. I can imagine that many people don't mind not seeing the on-screen markers, but I find I often can't tell what has registered on the touch panel easily without seeing a report on screen.

 

Did you uninstall your Dell 5870 drivers? I get this error every time I do so and end up having to system restore to a point before I updated my drivers. It's really stupid...

 

Response to Voice in the Wilderness. Unfortunately, it does indeed mean that I no longer get the screen feedback. In my case, 95% of the time I'm on an external monitor & don't use the the touchpanel anyway.

 

@villosa not sure it has to do with graphics driver

i finally got osd to work properly but not a 100% sure how it was fixed

uninstalled osd
uninstalled command center (had alien fx disabled)
ran ccleaner
restarted in safe mode
tried installing 110
install but failed to start osd
uninstalled osd 110
restarted window
installed osd 110
osd installed perfectly
updated to osd 113
reinstalled latest command center

 

Okay, desu. That's remarkable, and I don't exactly know what happened under the hood that fixed it, but I guess you're out of the woods.

 

I always get that error when my gpu drivers are messed up, after I reinstall them it goes away