Plagued with Unhandled Access Violation errors!

[Anonymous]

Hi all.

The subject says it all.It isn't drawing or machine specific. The common
things are that we are all using LDD3 and we are hwavy users of XREF's. I
have tried multiple times to do the following which sometimes work, but not
really 100%:

1. Recover the drawing (which reports nothing was wrong). Then I save the
drawing as a new drawing name.
2. Purge and Audit the drawing.
3. Detached all XREF's, bring them in one at a time
4. Go into each XREF and Purge and Audit them (which reports no errors).
5. Defrag the hard disk which the problem resides.
6. Installed SP1, but error still happens.

Things to try tomorrow:

1. Look at the Virus program to see if the latest definitions are there,
trun the program for virii.
2. Reinstall LDD on one machine to see if it fixes the problem.

Anyone have other thoughts? It is cutting down on porductivity because
users are grumbling and have to to this perhaps 3-4 times a day. Tried
looking on Adesk support for answers, but found nothing specific. The exact
error is:

Unhandled Access Violation Reading 0x0000 Exception at 34004cbh (the
exception number can change, but the last three 'cbh' remains the same if
that helps at all.)

Thanks,

Rick

[Anonymous]

Well, tried all my 'things to try tomorrow', but still am plagued by this.
Doesn't ANYONE have any ideas? Gurus? AutoDesk?

Rick
"Rick Graham" wrote in message
news:754A5B749BC170C004D924106E5B99BB@in.WebX.maYIadrTaRb...
> Hi all.
>
> The subject says it all.It isn't drawing or machine specific. The common
> things are that we are all using LDD3 and we are hwavy users of XREF's. I
> have tried multiple times to do the following which sometimes work, but
not
> really 100%:
>
> 1. Recover the drawing (which reports nothing was wrong). Then I save the
> drawing as a new drawing name.
> 2. Purge and Audit the drawing.
> 3. Detached all XREF's, bring them in one at a time
> 4. Go into each XREF and Purge and Audit them (which reports no errors).
> 5. Defrag the hard disk which the problem resides.
> 6. Installed SP1, but error still happens.
>
> Things to try tomorrow:
>
> 1. Look at the Virus program to see if the latest definitions are there,
> trun the program for virii.
> 2. Reinstall LDD on one machine to see if it fixes the problem.
>
> Anyone have other thoughts? It is cutting down on porductivity because
> users are grumbling and have to to this perhaps 3-4 times a day. Tried
> looking on Adesk support for answers, but found nothing specific. The
exact
> error is:
>
> Unhandled Access Violation Reading 0x0000 Exception at 34004cbh (the
> exception number can change, but the last three 'cbh' remains the same if
> that helps at all.)
>
> Thanks,
>
> Rick
>
>

[Mehlhop]

couple of options that i've seen work in the past:

1 - make sure that all users have their AutoCAD options configured to 'enabled with copy' for xrefs.

2 - make sure that none of the files to be xref'd into a drawing were closed with xref's still attached.

In my experience, xref's are the 'base' file for plansheets (or some similar use). by having other files to be xref'd in another file that is also to be xref'd you'll get what i've always knwon as circular references. to many of these and AutoCAD chokes. This may not be the case with you problem but it is worth looking into.

Jason Mehlhop
Freelance AutoCAD User & Customizer
jasonmehlop@adelphia.net

[Anonymous]

I had this problem on my workstation......it turned out to be incompatible
memory strips. Supposedly
they were built by different manufactures. Does the blue screen appear only
with acad open or with other
programs?

Good luck

jt

"Rick Graham" wrote in message
news:754A5B749BC170C004D924106E5B99BB@in.WebX.maYIadrTaRb...
> Hi all.
>
> The subject says it all.It isn't drawing or machine specific. The common
> things are that we are all using LDD3 and we are hwavy users of XREF's. I
> have tried multiple times to do the following which sometimes work, but
not
> really 100%:
>
> 1. Recover the drawing (which reports nothing was wrong). Then I save the
> drawing as a new drawing name.
> 2. Purge and Audit the drawing.
> 3. Detached all XREF's, bring them in one at a time
> 4. Go into each XREF and Purge and Audit them (which reports no errors).
> 5. Defrag the hard disk which the problem resides.
> 6. Installed SP1, but error still happens.
>
> Things to try tomorrow:
>
> 1. Look at the Virus program to see if the latest definitions are there,
> trun the program for virii.
> 2. Reinstall LDD on one machine to see if it fixes the problem.
>
> Anyone have other thoughts? It is cutting down on porductivity because
> users are grumbling and have to to this perhaps 3-4 times a day. Tried
> looking on Adesk support for answers, but found nothing specific. The
exact
> error is:
>
> Unhandled Access Violation Reading 0x0000 Exception at 34004cbh (the
> exception number can change, but the last three 'cbh' remains the same if
> that helps at all.)
>
> Thanks,
>
> Rick
>
>

[BluScarab]

Sounds like you have a bad or incompatible stick of ram.

[SOssowicz]

I don't think it has anything to do with RAM only because I am having the same problem with one drawing out of the hundreds that I have on my machine. I also tried to open it on all of the machines in our office and it has the saem result with the same error code. I am stumped and aggravated. This base drawing came from another company and I have a feeling it has something to do with that. I have saved the drawing over - I have created a totally new drawaing and copied the info that I needed into it but I still have the same result.

[Anonymous]

I am also having the same unhandled access violation errors as rick
described when opening drawings saved in LDD3. It appears that the
problem occurs when the drawing that I am attempting to open has an xref
in 2003 format. The exact error message is "Fatal Error: Unhandled
Access Violation Reading 0x0004 Exception at 3009FDA0H". Has there been
any solutions to this problem published yet?

Thanks

Josh

SOssowicz wrote:

> I don't think it has anything to do with RAM only because I am having
> the same problem with one drawing out of the hundreds that I have on my
> machine. I also tried to open it on all of the machines in our office
> and it has the saem result with the same error code. I am stumped and
> aggravated. This base drawing came from another company and I have a
> feeling it has something to do with that. I have saved the drawing over
> - I have created a totally new drawaing and copied the info that I
> needed into it but I still have the same result.

[Anonymous]

Check your xref's by using the filter at the top of the properties dialog box for OLE2FRAME's and for raster images. (textmask) If they exist nuke 'em.

We had users that put *&^%$ textmask in the xrefs when we used LDD3. It causes fatal errors in the drawings that reference that xref when we try to open them in LDD2004

I swear I'm gonna fire the next guy I catch putting textmask in our drawings.

Good Luck

[Anonymous]

I tried selecting the xref and using the properties palette but I can't
seem to fine where to fine the filter to search for OLE2frame or raster
images. Can you please clarify your instructions.

Thanks

Latka wrote:

> Check your xref's by using the filter at the top of the properties
> dialog box for OLE2FRAME's and for raster images. (textmask) If they
> exist nuke 'em.
>
> We had users that put *&^%$ textmask in the xrefs when we used LDD3. It
> causes fatal errors in the drawings that reference that xref when we try
> to open them in LDD2004
>
> I swear I'm gonna fire the next guy I catch putting textmask in our
> drawings.
>
> Good Luck
>

[Anonymous]

My apoligies,

After opening the xref look at the top of the properties dialog. to the right of the box the reads "No selection"
there is a filter icon. Click the filter icon- it will bring up the "quick select" dialog box. There will be several boxes where you can set parameters.
Apply to: leave this set to Entire Drawing
Object type: Click on this and scroll until you find OLE2FRAME

[Anonymous]

Sorry I closed the reply.

after you scroll to find OLE2FRAME click OK.

You should then see at the top of the properties dialog box
OLE2FRAME (1) the number in parentheses is the number of OLE2FRAMES that are in the drawing.

This also indicates that these items are selected. All you have to do is press the delete key and they should go away.

repeat the process to rid yourself of raster images as well

[dbernard]

type WHIPARC at command line and change the system variable back to 0 instead of 1. this has worked for me. i changed this to 1 when trying to figure out how to help a coworker keep his viewres to 20000. I was confused about how WHIPARC associates with VIEWRES, so I tried it, but didn't notice any difference... except for the occasional FATAL ERRORS during panning and my AutoCAD completely vanishing without ANY errors. My acad has been running just fine for the past 3 hours without any problem... this is new record since I messed with the WHIPARC variable last week.

[dbernard]

This was definately the problem. My computer has been running fine for over a week now! This is great! (note to self: never WHIPARC to 1)