Announcements
IMPORTANT. Forum to be archived in several phases. You can no longer submit new questions - but can only answer existing threads until Oct 17th 2016. Please read this message for details
Mechanical Desktop (Read Only)
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

FATAL ERROR: Unhandled Access Violation Reading...

7 REPLIES 7
Reply
Message 1 of 8
Anonymous
494 Views, 7 Replies

FATAL ERROR: Unhandled Access Violation Reading...

When working on a part or assembly (it started when saving an assembly and then opening a part which was part of the assembly, so I stopped doing that), after I save the model and try to open another one, in Single Drawing Mode, I'm getting this sickening, sickening error, "FATAL ERROR: Unhandled Access Violation Reading 0x409ad07c Exception at 65456b43h." Anyone know what this ridiculously annoying error stems from? Cuz, if you do, man, I'd like to know why.
7 REPLIES 7
Message 2 of 8
Anonymous
in reply to: Anonymous

any one of a thousand million
things...

 

usually I start with a reboot, does that fix
it?


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
When
working on a part or assembly (it started when saving an assembly and then
opening a part which was part of the assembly, so I stopped doing that), after
I save the model and try to open another one, in Single Drawing Mode, I'm
getting this sickening, sickening error, "FATAL ERROR: Unhandled Access
Violation Reading 0x409ad07c Exception at 65456b43h." Anyone know what this
ridiculously annoying error stems from? Cuz, if you do, man, I'd like to know
why.
Message 3 of 8
Anonymous
in reply to: Anonymous

Well. Only nine hundred ninety-nine million, nine hundred and ninety-nine thousand, nine hundred and ninety-nine things to go.
Message 4 of 8
Anonymous
in reply to: Anonymous

What are you machine specs?

proc

mem

os/sp level

virtual memory setting (min =max=2xram is usually
good)

video board and driver version

is mdt6 at sp2 minimum

darvin
Message 5 of 8
Anonymous
in reply to: Anonymous

I'm running Inventor Series 5 on a brand new computer that has 1Gb Ram, a Pentium 4 (2.4 Ghz 53 Mhz), Intel SKT 478 D850 CHIPSET, 18GB SCSI drive, Win 2000 PRO OEM and a Fire GL 8800 graphics card (wopengl7.hdi driver).
Message 6 of 8
Anonymous
in reply to: Anonymous

Check for new chipset drivers from
intel.

Make sure you are running an IV certified driver
for the 8800.

 


The windows virtual memory min=max
setting?

And mdt at sp3 + scenes update?

    Other than that, set audit
control to "always" and run "recover" and "desktop recover" on any suspect
files. You should not have to run in SDI mode!

darvin
Message 7 of 8
Anonymous
in reply to: Anonymous

Thanks for the input. Tersely, Ter.
Message 8 of 8
Anonymous
in reply to: Anonymous

any chance multiple document mode fixes this? I do
remember (some time ago) reading about some sdi issues, I'm just wondering if
you've encountered one. also, are you running the latest service pack? (should
be sp3 for mdt 6)

 

Kevin


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Thanks
for the input. Tersely, Ter.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report