ill check the memory next time haven't checked in a while,
i don't restart often, but when this started happening i tried restarting couple of times and didn't have the any effect on the bug

but this could point to some system connection afterall because i had an issue with spybot sd 1.62 version, which would start saying 'Error during Check (Out of Memory)'
but since spybot 2.2 worked fine and there was no useful solutions online i just stopped using it after couple of tries to fix

yes (not every time) after an alarm runs, winstep stops responding to right clicks, wont extend subdocks and in properties i get the OCX error, wasn't able to pinpoint if it happens right after an alarm or some time after

then when alarm starts again, while it runs everything is fine, until i stop it again

My guess is that all that weird behavior is caused by the same exact thing: not enough memory to create the right-click context menus, sub-docks, tabs in Preferences, etc...

That it doesn't crash when this happens and simply does not open whatever it was supposed to open, is actually quite good already.

But why on earth does it suddenly start behaving normally while playing the MP3?! I'm sure there is some kind of reason, but it doesn't make any sense to me. lol

and what would be causing the memory issue
it ONLY happens when alarms or mp3 voice are enabled

What the exact mechanism is, I haven't the faintest idea... but, apparently, a bad codec?

another StackHash_1abe appcrash
WsxService.exe 1.388 K USER Objects 0 GDI 0
WorkShelf.exe 15.400 K K USER Objects 368 GDI 293

Normal usage.

Look, this is either a bad codec, AV software interfering, overclocking taken too far, or bad RAM. Pick one.

yea, but what has an audio codec got to do with spybot sd, if the two errors are indeed connected

not overclocking, so that's out, bad ram would probably cause more issues
so that leaves bad codec and avast
and since avast is one of popular free AV, more users would probably come forward

if you do think it could be avast id be willing to uninstall it and replace it with something else for a test period

IIRC, another user complaining about problems was also running AVAST. Read back.

Sorry, we cross-posted.

Doesn't Avast have several exclusion lists? One of them being for Active Protection?

Actually, the first thing I'd do would be to go to the official Memtest website, download the thing, make a bootable USB stick, boot the computer with that and let it run a full test for a couple of hours.
Just make sure your RAM is working properly. I've seen a lot of weird things coming from there.
You might also want to press F2 at startup of Memtest to enable the use of all CPU cores.
Cheers!

i forgot that he was using avast.
what would be more useful to you, that i try replacing avast now, or to wait until you implement the fix?



Yes it does, would that be enough to resolve the conflict?

thank you, will do that when i get the chance