Can someone please tell me what the smurf this is?

Attachment 33692

We had to get our computer reformatted around mid-January due to a pretty nasty virus. But since then, this window has been popping up at random intervals. Sometimes, it won't show up for a week or so, and sometimes, it will come up every five minutes. It seems harmless, so can anyone tell me what it is?

EDIT: By request, this is the continuation of the text in the dialogue box:

Quote:

---

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

************** Exception Text **************
System.ArgumentOutOfRangeException: Cannot anchor balloon at position '{X=1071,Y=1002}.' The point is not contained within the visible bounds of any screen.
Parameter name: point
Actual value was {X=1071,Y=1002}.
at Rilling.Common.UI.Forms.BalloonWindow.MoveAnchorTo(Point point, Point pivot)
at Rilling.Common.UI.Forms.BalloonWindow.MoveAnchorTo(Point point)
at Rilling.Common.UI.Forms.BalloonWindow.Show(Point pt)
at Swapdrive.Client.Screens.FormMain.ShowCustomBalloon(CustomBalloonType balloonType)
at Swapdrive.Client.Screens.FormMain.OnTrayMouseOver(Object sender, MouseEventArgs e)
at System.Windows.Forms.NotifyIcon.:bou::bou::bou::bou::bou::bou::bou:Move(MouseEventArgs e)
at System.Windows.Forms.NotifyIcon.WmMouseMove(Message& m)
at System.Windows.Forms.NotifyIcon.WndProc(Message& msg)
at System.Windows.Forms.NotifyIcon.NotifyIconNativeWindow.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.4206 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
DataSafeOnline
Assembly Version: 1.1.0.8998
Win32 Version: 1.1.0.8998
CodeBase: file:///C:/Program%20Files/Dell%20DataSafe%20Online/DataSafeOnline.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4205 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SdbShared
Assembly Version: 1.1.0.8998
Win32 Version: 1.1.0.8998
CodeBase: file:///C:/Program%20Files/Dell%20DataSafe%20Online/SdbShared.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
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.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
BalloonWindow
Assembly Version: 1.2.0.0
Win32 Version: 1.2.0.0
CodeBase: file:///C:/Program%20Files/Dell%20DataSafe%20Online/BalloonWindow.DLL
----------------------------------------
SdbUI
Assembly Version: 1.1.0.8998
Win32 Version: 1.1.0.8998
CodeBase: file:///C:/Program%20Files/Dell%20DataSafe%20Online/SdbUI.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
SdbShared.XmlSerializers
Assembly Version: 1.1.0.8998
Win32 Version: 1.1.0.8998
CodeBase: file:///C:/Program%20Files/Dell%20DataSafe%20Online/SdbShared.XmlSerializers.DLL
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
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:





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'm moving this to the help forum. The computer whizzes of this forum can help you out there, I'm sure! :)

If the balloon is what I think it is, a file in windows has a typo that sets the notification window that pops up from the system tray to some location off screen and its throwing an error because the location doesn't exist on screen. My guess is windows is trying to alert you and it can't so it shows that instead. More than likely its just a downloadable update alert anyway so ignoring it wouldn't be a huge deal. But I'm one of the lesser techie types around here so take my opinion with a grain of salt. Someone more knowledgeable will come along sooner or later. But FYI we have a help forum for these things :D

What's your resolution (if you know what that is)? I don't know anything about that error, but it's saying it's trying to print something to the screen that's bigger than what you can see. If possible, the easiest solution might just to set your screen size larger than '1071x1002'. Though if it's already bigger than that, then... hmm.

Gotta find out which application this error originates from. Clues might exist in further down in the error message details. If you (we) find out which app it is, we would have a better chance of helping you

from the looks of it, its most likely coming from Windows live messenger... at least that's what the border suggests to me.

As for your problem I'm afraid I can't really help much other then what the others have already said.

Quote:

---

Originally Posted by JKTrix

What's your resolution (if you know what that is)? I don't know anything about that error, but it's saying it's trying to print something to the screen that's bigger than what you can see. If possible, the easiest solution might just to set your screen size larger than '1071x1002'. Though if it's already bigger than that, then... hmm.

---

My boyfriend had a similar theory, that when we sent it into Staples, they adjusted the resolution size to a screen bigger than our own (Which is 1024 x 764) for their computer, and never set it back. We tried, but the computer is still adjusted to a monitor size we don't have. So basically, the computer is trying to find a pixel point that doesn't exist on my monitor. Thanks, everyone!

I'd agree with the error but not the reasoning. It'd have to be a really old or obscure (or stupid) computer to not recognize the monitor it's currently using and think its still using a previous monitor. They tend to recognize different hardware when its plugged in. The error might be stuck to the old resolution, but I don't think your computer itself is stuck to the old resolution. But everyone seems to agree you're right on the main issue, it's trying to pop something up off-screen. Have you tried changing your resolution to something else and then back again? That might re-write whatever file or value that is throwing the error. Even adjusting it down and then back might fix it

Edit: I just realized I didn't clarify why I made that pointless argument. I was trying to illustrate that its not really Staple's fault. Your computer would have recognized the change in monitor. Just one of the files or values must be glitching over it

Quote:

---

Originally Posted by KaiserDragon

from the looks of it, its most likely coming from Windows live messenger... at least that's what the border suggests to me.

---

Huh, what are you yalking about?

Quote:

---

Originally Posted by Mirage

Quote:

---

Originally Posted by KaiserDragon

from the looks of it, its most likely coming from Windows live messenger... at least that's what the border suggests to me.

---

Huh, what are you yalking about?

---

That's what I was wondering. We don't have Windows Live...

well, I'm still saying posting the complete error message would help.

I can't, it's at least 2 pages worth of information.

What exactly is stopping you from posting two pages worth of information?

The fact that it hasn't popped up recently. If you want, the next time it does, I'll post it here.

Sounds good.
Actually, it might be under your system's event log.

If you could tell me how to access that, I can see if I can pull it up or not.

Uninstall/disable the Dell DataSafe Online thingy :p That seems to the crapware trying to do something, looking at the loaded assemblies :p

I'm not sure if that will harm anything else on my computer or not, though, since I don't know what it is.

crono's one of the techiest people around here. He's not gonna tell you to do something that could harm your computer. Though considering its name I would wager its some kinda wanna-be file protector or back-up or something. If you require the kind of service it offers, more than likely there's a better program out there for it than some standard Dell installation

Unless you explicitly paid extra for it when you bought your machine, it's some 1-year trial backup service to the internet for something like 2 GB of data. At least that's what it is on my laptop, which I will also be promptly removing as soon as it arrives, since I prefer doing my own backups without this extra tool running all the time using extra resources, and certainly not to some random location on the internet :p

But you can disable it rather than uninstall, if you feel you might make use of it in the future :p

Hmm, I'll have to try that. Thanks, man! Here's your prize.

oh yeah, sorry, i forgot to tell you that I didn't figure out exactly where in the event log it would be stored, because it's all organized differently in Win7 than what i'm used to :p.

anyway, the complete error log did indeed help with pinpointing the problem, it seems