Error Message - Memory could not be read : Part 2

RFJ · 2006-09-20T10:34:21+00:00

This is a continuation of a message posted yesterday that 'memory could not be read'.Tx to everyone who contributed so far. As the thread was getting complicated I thought I'd summarise things - together with some /new information/ that suggests it may not be a hardware fault.Just in case it is substantive, it is a UK edition.The detailed message I get is :Window Title for ErrorQB Regular 2005 qbw32.exe - Application Error.Detailed MessageThe instruction at "0x00407634" referenced memory at "0x032bb1ffc". The memory could not be "read". Click OK to terminate the programme. Original Problem a.. If I try to open my QB datafile from my pc I always get this error message independent of whether that file is on the server or my pc. b.. There are no other preceding error messages. c.. I /can/ open the datafile from another pc (ie it is not corrupt - but see below anyway).What I've Done so Far a.. I've taken out the memory chips and re-inserted them. I've also run a complete memory check using memtest86 v1.65; there were no errors. b.. I've reindexed the data file and verified it. c.. /NEW/ I can also open the data file on my pc if it is running in safe mode or in diagnostic start-up. d.. /NEW/ I can also open the data file on my pc if I log on as a different user.Bottom LineIt seems that there is something in my current user profile that is triggering the problem.QuestionShort of recreating another user (ie having to set up all email accounts, MSOffice settings, etc, etc, etc,.) does anyone have any ideas of isolating and removing the problem.TIARob

Sep 20, 2006 22 Replies

Rate this thread:

RFJ 19 years ago

Dropping the Keylogger Guard setting from High to Medium in Onguard seems to get around the problem.

Vote

RFJ 19 years ago

I've now got the solution from PCTools. Go to the keylogger results screen and you'll see entries for the QB exe file there. Just click on one of them and enable the Allow file option. Alternatively enter the path manually in the keylogger screen.

Vote