Results 1 to 8 of 8
  1. #1
    Star Lounger
    Join Date
    Jul 2002
    Posts
    54
    Thanks
    0
    Thanked 0 Times in 0 Posts

    memory error (XP and access 2000)

    MS Access 2000 runs kind of weird on my XP box - sometimes I get the following error and it just locks up: Application error...instruction "0x77f83aed" referenced memory at "0x0000000000". The memory couldn not be "written". I looked into the MS Knowledge base but to no avail. Any ideas? Any way to test the memory in the box...maybe it's the problem.

    Thanks in Advance.....Grady

  2. #2
    Gold Lounger
    Join Date
    Feb 2003
    Location
    Wardrobe Malfunction Junction, Derry
    Posts
    2,953
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: memory error (XP and access 2000)

    Grady--

    Haven't searched this yet--I will some but in general a Stop 0X0077 error is a Kernel Stack Inpage Error and one of the 5 most common stop errors that alerts you a page of kernel data requested from virtual memory can not be found. Since virtual memory is stored on the hard disk, the disks that store this memory are the focus of troubleshooting efforts. The main culprits (and I'll have to look for the 83aed suffix:

    1) Disk corruption fixed by running "chkdsk /f" but having said that my preferred way to do that is to run "chkdsk /r" from the recovery console because I think it is superior and will imply or include "f."

    2) Disk hardware failure--ck. all disk hardware that is implied by a 0X0024 error as well--which means the NTFS file system or the FAT file system indicating some kind of corruption on the disk. If you can't start Windows, boot to the Recovery Console by using the CD--and I would run a chkdsk /r for this as I said from the Recovery console whether or not you can boot to Windows. If you find physical corruption on thedisk resolved by chkdsk that may fix the problem, but if it keeps coming up then youneed to look further for ffailed hardware including:

    a malfunctioining IDE controller
    a bad IDE cable
    a malfunctioining SCSI controller
    bad SCSI cable
    improper scsi termination

    3) Also software can cause the corruption. If software has been recently installed, this should be the first place to look. Make sure you check any defrag, virus scanner, or backup utilit installed is XP compatible.

    4) Virus infection can do this so make sure you have the latest definition and run a scan.

    SMBP

  3. #3

  4. #4
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: memory error (XP and access 2000)

    Do you have the entire Office 2000 Pro suite installed, and only Office 2000? Are you updated to SP3? If so, try a Repair from the Help menu. If not, that is, you have only part of Office or you have a mixture of versions, there could be a problem with the components as between applications and suites. Those can be more difficult to debug.

    Assuming the Office installation checks out, it certainly doesn't hurt to test memory. More often, however, there could be some application code that is misbehaving. Do you have any add-ins or your own modules in Access that use any Windows API functions? What is Access doing when these problems occur? Updating? Printing?

  5. #5
    Star Lounger
    Join Date
    Jul 2002
    Posts
    54
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: memory error (XP and access 2000)

    Office Professional 2000 has been installed and the error seems to happen when creating PDF's with Adobe.

    Thanks for your help in Advance!
    Grady

  6. #6
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: memory error (XP and access 2000)

    Well, that changes everything. <img src=/S/grin.gif border=0 alt=grin width=15 height=15> Is there anything special about these reports (I assume you are printing reports) that would be different from other types of documents printed to Acrobat? For example, are they 3 feet wide or several thousand pages long? Assuming not, I wonder whether any updates or patches from Adobe might help. I use pdfFactory, not Acrobat, so I don't know if this is relevant: can you set the printer to emulate and, if so, does it help to change the printer that Acrobat is emulating?

  7. #7
    Star Lounger
    Join Date
    Jul 2002
    Posts
    54
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: memory error (XP and access 2000)

    The reports are created in MS access and then printed to Adobe.....they can range from 1-2 pages up to 23, but there seems to be no pattern as to when there is a problem. Any Ideas?

    Thanks!

  8. #8
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: memory error (XP and access 2000)

    If you can print these reports to the printer without crashing, I have to think there's an Acrobat problem. What version of Acrobat? Have you checked for patches at http://www.adobe.com/?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •