Windows 10: MSReportBuilder.exe crashed

Hi Team, can you please help me with this issue?

I can't open MSReportBuilder, once I open it, it crashed. Here are two related log:

1.

Application: MSReportBuilder.exe

Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.UriFormatException

Server stack trace:
at System.Uri.CreateThisString uri, Boolean dontEscape, UriKind uriKind
at System.Uri..ctorString uriString
at System.UriBuilder..ctorString uri
at Microsoft.ReportingServices.ReportDesign.Common.ServerConnectionFactory.OpenConnectionHelperString urlServer, Boolean useExactUrl, SiteType siteType, PromptCredentials creds, RecentServers recentServers, IBearerTokenRequestor tokenHandler
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessageIntPtr md, Object[] args, Object server, Object[]& outArgs
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessageIMessage msg, IMessageSink replySink
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelperSystem.Runtime.Remoting.Messaging.Message, Boolean
at System.Runtime.Remoting.Proxies.RemotingProxy.InvokeSystem.Object, System.Runtime.Remoting.Proxies.MessageData ByRef
at Microsoft.ReportingServices.ReportDesign.Common.ServerConnectionFactory+ServerConnectionCallback.EndInvokeSystem.IAsyncResult
at Microsoft.ReportDesigner.ReportDesigner.FinishStartUpAsynchronousServerConnectionSystem.IAsyncResult
at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessageSystem.Runtime.Remoting.Messaging.IMessage
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessageSystem.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBackSystem.Object
at System.Threading.QueueUserWorkItemCallback.WaitCallback_ContextSystem.Object
at System.Threading.ExecutionContext.RunInternalSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean
at System.Threading.ExecutionContext.RunSystem.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem
at System.Threading.ThreadPoolWorkQueue.Dispatch
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback


2.

Faulting application name: MSReportBuilder.exe, version: 15.0.1473.0, time stamp: 0x5d661239

Faulting module name: KERNELBASE.dll, version: 10.0.18362.815, time stamp: 0x67005c2a

Exception code: 0xe0434352

Fault offset: 0x00114402

Faulting process id: 0x29dc

Faulting application start time: 0x01d62060d66995b6

Faulting application path: C:\Program Files x86\Microsoft Report Builder\MSReportBuilder.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 76beb07a-2a62-478f-a6de-4d3417e6a617

Faulting package full name:

Faulting package-relative application ID:


The .NET Framework version installed was 4.8. I have tried to turn the .NET Framework off and on and restarted, but still not working. It would be really appreciated if someone can help me with it.

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

all games crash!

ive watch my temps and both the cpu and gpu are within normal ranges. when it freezes it simply freezes the image and stops the sound. i must reboot to get back to windows.

 

GPU-Z 0.8.7 crash on launch

W1zzard is asking you to test so that he can suggest next steps and be able to troubleshoot the issue you have.
If another version works, it would be one set of steps.
If several other versions also fail/crash, then it would be another.