.net framework error

[ImportBot]

Originally Posted by vis_ionmas_ter*:

 

In the past two days I have had multiple pop up windows from .net framework with no visible info. When these occur, I can still click on things/type in procon, but it isnt being sent to the server, nor is the in-game chat updating in procon. Ive had this happen a handful of times since I started using the program a few months ago, but the past few days it has been occurring within a few minutes of booting procon almost without fail. Usually [but not always] procon will lose connection for a few seconds after the window pops up, then reconnect automatically [which is when I am no longer albe to make changes via procon]. Attempting to close the .net window gives me a "Procon is not responding" dialogue, and I am forced to close it.

 

Running Windows 7 Ultimate x64 with .NET Framework 3.5 [via windows features] and 4.6.2 installed.

 

1343bf3e87746deba78720ef427f6482.png

[ImportBot]

Originally Posted by vis_ionmas_ter*:

 

UPDATE: The error window [for the first time ever] displayed text!!

update.png

This is the details text:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

at System.Windows.Forms.UnsafeNativeMethods.CallWindo wProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)

at System.Windows.Forms.NativeWindow.DefWndProc(Messa ge& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.RichTextBox.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(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.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

----------------------------------------

PRoCon

Assembly Version: 1.5.1.1

Win32 Version: 1.5.1.1

CodeBase: file:///C:/Users/VisionMaster/Desktop/Games/Related/Procon/PRoCon.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

PRoCon.Core

Assembly Version: 1.5.1.1

Win32 Version: 1.5.1.1

CodeBase: file:///C:/Users/VisionMaster/Desktop/Games/Related/Procon/PRoCon.Core.DLL

----------------------------------------

System.Core

Assembly Version: 3.5.0.0

Win32 Version: 3.5.30729.5420 built by: Win7SP1

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

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.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

PRoConPluginEnumAssembly

Assembly Version: 0.0.0.0

Win32 Version: 1.5.1.1

CodeBase: file:///C:/Users/VisionMaster/Desktop/Games/Related/Procon/PRoCon.exe

----------------------------------------

PRoConPluginEnumAssembly

Assembly Version: 0.0.0.0

Win32 Version: 1.5.1.1

CodeBase: file:///C:/Users/VisionMaster/Desktop/Games/Related/Procon/PRoCon.exe

----------------------------------------

Accessibility

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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.

[ImportBot]

Originally Posted by vis_ionmas_ter*:

 

Nothing in 3 months? Not even a "me too"? Because I know of at least 3 other people that have this problem occasionally....I get it literally EVERY time I have procon up and I start playing. Just DGAF? K then.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Everyone has really been silent about procon itself because the devs have been gone for a long time and people haven't reported issues with it. Obviously not including plugins in that, those are constantly evolving.

 

I haven't seen this issue before over the last 5 years, or heard of anyone reporting it other that this thread. I think you're alone on this one man.

 

AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

 

You said it happens when you have procon up and you start your game, so considering this is dealing with memory being accessed from places it shouldn't be that sounds like an OS memory management issue.

 

The only odd thing i can see about your system is that it's running a 32 bit OS. A 32 bit OS can only manage 4GB of memory, so if you're running battlefield on top of hosting a procon layer and all your other applications whatever they may be, you could be running out of memory.

[ImportBot]

Originally Posted by ty_ger07*:

 

Video card manufacturers don't even support 32-bit Windows any more. Time to format and upgrade. You probably should have swapped to 64-bit Windows 8 years ago; when the rest of us did.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Video card manufacturers don't even support 32-bit Windows any more. Time to format and upgrade. You probably should have swapped to 64-bit Windows 8 years ago; when the rest of us did.

He mentions in the first post that he's running x64 windows 7, but procon is reporting he's running 32, or at least it appears that way.

 

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

 

Looked up that message and it's not procon specific, the 'Win32 Version:' part, but i'm still not sure if that actually means it's a 32 bit system or if that's just a message from ages old that they haven't updated.

 

EDIT: If he isn't actually on 32bit then i'm not sure what it could be. The issue is happening when he has a lot of memory churning around when he boots up the game, several gigs, so it's still likely an issue with his system in some aspect. I wonder if any other .NET applications are having issues on his system when he boots up battlefield.

[ImportBot]

Originally Posted by vis_ionmas_ter*:

 

Im def running x64 windows. Heres my system specs:79d839509653b1c08ffc3f6e637e5213.png

What other .net apps would be running while Im playing BF?

 

EDIT: Forgot the gfx: 2048MB ATI AMD Radeon HD 7700 Series (MSI)

 

Also, thank you for responding

[ImportBot]

Originally Posted by leibhold*:

 

If this is a problem, I would remove/update/reinstall all .net versions

 

This is not an issue with procon but with your system, which occurred in the 1st October 2017 - assuming as you said it worked before.

 

So reinstall/update the .nets 2,3,4,5 what ever you have.