Quick Access Popup: Rare But Persistent Memory Crashes

Hi! Most of the time, my version of Quick Access Popup works fine, but occasionally, I get an Invalid Memory Read/Write error when I try to access its menu. This happens rarely, but when it happens, it happens every time I try it, and the error persists through several sessions. Can I get around this?

 

Does "several sessions" mean restarting Quick Access Popup, or restarting Windows as well? That distinction would help separate a process that has not really exited from a problem that returns after a clean start.

Before changing settings, back up your QAP configuration. When it happens again, save a screenshot of the complete error, including any script file and line number, and note the QAP version, Windows version and whether opening the menu with the keyboard shortcut gives the same error as clicking. Please remove personal folder paths before posting the screenshot.

If you have already restarted Windows and the same error immediately returns, I would avoid repeatedly deleting settings or changing Windows memory options. The exact error and a reproducible trigger would be more useful to the QAP developer than the generic "Invalid Memory Read/Write" wording alone. Does it happen with every menu, or only a particular submenu/item?

Disclosure: AI-assisted reply from a contributor working with CounterStrikeGO; these are diagnostic suggestions, not a claim that I have reproduced your crash.

 

Several sessions means rebooting Windows. It's working now: as I said: the error's rare but persistent. It happened when I use the hot key; the menu doesn't successfully appear, and the mouse pointer changes but doesn't change back until I restart Quick Access Popup.

 

Thanks, that rules out my first interpretation: you do mean a Windows reboot, and the failure is at the menu-opening stage rather than when launching a particular menu item.

Since it is working again, I would preserve the current configuration rather than reset it now. On the next occurrence, capture the complete error before restarting QAP and note what happened immediately beforehand (for example waking from sleep or changing displays), if there is a consistent pattern. Those are possible triggers to record, not diagnoses.

The pointer remaining changed tells us the operation did not finish normally, but it does not establish defective physical RAM. I would not change paging-file or memory settings on that evidence alone. If you report it to the QAP developer, include the exact QAP version, Windows version, full error text and the fact that the hotkey fails before the menu appears. That is a much narrower reproduction description than a generic memory-crash report.

Disclosure: AI-assisted follow-up; same CounterStrikeGO affiliation as above, without a reproduced diagnosis.

 

Thank you.

 

BTW, I have a program called Template Creator. It handles template files and allows you to derive new files from them. I can give you an URL. Want it?