Can someone please help me find a solution to this problem. Many search engines have indexed my site pages as follows

http://www.wsysa.com/Default.aspx?TabId=532&ctl=Register&SkinSrc= 

Here's an excerpt from my log, my guess is that it's something to do with the print feature, but I need to find out how to fix it.  If anyone has any input I would greatly appreciate it.

AssemblyVersion: 04.05.03
PortalID: 0
PortalName: WSYSA
UserID: 1
UserName: somthing
ActiveTabID: 532
ActiveTabName: HYSC
RawURL: /Default.aspx?TabId=532&ctl=Register&SkinSrc=
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.wsysa.com/AboutUs/tabid/79/ctl/Login/Default.aspx?returnurl=%2fDefault.aspx%3fTabId%3d532%26ctl%3dRegister%26SkinSrc%3d
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: b85df711-8e9e-4c87-b11a-270cabaf7ace
InnerException: Unhandled error loading page.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.Util.CheckVirtualFileExists
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Unhandled error loading page. ---> System.Web.HttpException: The file '/~.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.Framework.DefaultPage.LoadSkin(String SkinPath) --- End of inner exception stack trace ---
Source:
Server Name: SRVWEBSITE

No my best guess is that this problem is because of the way the search engines handle / index the print feature on the modules.