Visual C++ Runtime Error on WLM/WIN7


Recommended Posts

post-2-1258283957.png

This started happening recently, does anyone know what could cause it?

I have latest version of WLM and A-Patch applied (ages ago, but this problem only just started).

i have the Exact same.

This started happening about 2 weeks ago Also, opening a conversation takes about a minute for the whole application to respond again.

What i have tried:

Uninstalling, removing all entries in Appdata from WLM.

Reinstalled: same thing occurs.

Also, when someone sends me an IM i get the message instantly, and its on my taskbar, but once i want to open the conversation it takes another minute for it to load.

That plus i get the exact same error as the OP

start WinDbg and attach to the WLM process and wait for the error

Okay, simple enough, if i wouldve looked before i asked... :p

Anyways, i attached it to the process after i logged in, i dont know what its doing now but messenger is unusable at the moment after i attached the process.

Now i just wait ?

This is what it said after the list of dll files btw

(118c.940): Break instruction exception - code 80000003 (first chance)
ntdll!DbgBreakPoint:
00000000`7782f190 cc			  int	 3

next hit F5 to run the program after attaching.

Okay, it has ran since then, finally today something happend after which i could not resume the debugging with F5.

The errors on the bottom are from trying to resume the debugger.

However when this occured i did not get a runtime error from messenger

loads_o_text.txt

you're getting a STATUS_GUARD_PAGE_VIOLATION (0x80000001) exception.

A guard page provides a one-shot alarm for memory page access. This can be useful for an application that needs to monitor the growth of large dynamic data structures. For example, there are operating systems that use guard pages to implement automatic stack checking.

To create a guard page, set the PAGE_GUARD page protection modifier for the page. This value can be specified, along with other page protection modifiers, in the VirtualAlloc, VirtualAllocEx, VirtualProtect, and VirtualProtectEx functions. The PAGE_GUARD modifier can be used with any other page protection modifiers, except PAGE_NOACCESS.

If a program attempts to access an address within a guard page, the system raises a STATUS_GUARD_PAGE_VIOLATION (0x80000001) exception. The system also clears the PAGE_GUARD modifier, removing the memory page's guard page status. The system will not stop the next attempt to access the memory page with a STATUS_GUARD_PAGE_VIOLATION exception.

The cause is Adobe flash. Which version do you use? Can you try to upgrade to the newest version?

you're getting a STATUS_GUARD_PAGE_VIOLATION (0x80000001) exception.

The cause is Adobe flash. Which version do you use? Can you try to upgrade to the newest version?

I have updated it now, however Messenger is still VERY slow, its like its running on 100% CPU, thats how it feels..(but it isnt)

It logs in normally, i open a chat window, it appears instantly but the window is empty after 30 seconds i can see whats in the widow(typing box etc) but it still takes another 30 seconds for me to be able to type anything in it.

It is exactly the same when someone sends me an IM, the IM is received instantly, but when i open the IM window, the above happens.

Ive set the debugger to run again, im gonna see what happens now.

you could try to run the Windows performance toolkit (xperf) to capture what is causing the high CPU usage:

https://www.neowin.net/forum/index.php?show...#entry591870700

Nothing is getting high cpu usage.. if only it would be that easy.

Anyways ive gotten another thing in the Debugger, this happens when i Select TEXT in the IM window, after this error however i can reusume with F5 and continue using messenger.

(a40.a44): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
KERNEL32!IsBadWritePtr+0x37:
75d1c3b7 8a08			mov	 cl,byte ptr [eax]		  ds:002b:000010ea=??
0:000:x86> g

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.