PDA

View Full Version : "Cinema 4D Caused A Exception in.." Well It's Buggy Now


Scott M C4D
12-30-2003, 09:32 PM
CINEMA_4D caused an exception 10H in module CINEMA_4D.EXE at 0177:007ea5fc.
Registers:
EAX=00000002 CS=0177 EIP=007ea5fc EFLGS=00210206
EBX=00000001 SS=017f ESP=018757f0 EBP=00000002
ECX=0000000c DS=017f ESI=00000018 FS=4447
EDX=0187591c ES=017f EDI=018757f0 GS=445e
Bytes at CS:EIP:
d8 c9 db 5c 24 24 d9 42 04 d8 c9 db 5c 24 28 d9
Stack dump:
0001d804 000000c6 ffed218d 0001d8c6 000000be ffecf086 0001e2a6 000000c2 ffecda29 00000000 00000000 00001897 00000000 00000000 00001897 00000000

Thats what i get when using cinema R8.2.
I can't even load a scean or do very much at all without it crashing.

:cry:

How great is that ?

smoke
12-30-2003, 09:38 PM
I haven't had any problems with 8.2, sounds like time for a un-install/re-install for you

JamesMK
12-30-2003, 09:43 PM
That has to be caused by something else than Cinema... The only crashes I've ever had with 8.1 - 8.2 were due to very strange alpha-level plugins (and my own crappy coding)... Uninstall C4D and make a full systems check - scan all your disks properly and so on, then make a fresh install.

Scott M C4D
12-30-2003, 09:54 PM
I tryed re-installing 8.2 but still got the problem so i guess i will have to do what you suggested James.

I will be getting a new faster PC this next month so hopefully Cinema will fly without problems :)

bcbarnes
12-30-2003, 10:10 PM
Just an "off the cuff" guess, but it looks like it might be video related. 10H is the older video interrupt, and EFLGS shows that the code was in V86 mode at the time of the exception. What kind of video card/drivers do you have?

flingster
12-30-2003, 10:27 PM
what changed on your system?

Scott M C4D
12-30-2003, 10:40 PM
Hiya,
I am using an old Ati Rage 128 GL card on my system spec below.
Yes i know it's old but my motherboard only supports 2X AGP as far as i know so not much point getting one of the latest cards.

The Adapter/Driver Information is as follows. (Taken from 3D Mark 2001se)

Description: Primary Display Driver
Manufacturer: ATI Tech. - Enhanced
Name: ATI Rage 128 GL SD TV AGP (English)
Total Local Video Memory: 32 MB
Total Local Texture Memory: 32 MB
Total AGP Memory: 24 MB
Display Driver: ATI2DRAA.DRV

( More info added from current files in the Adapter tab *vdd,*vflatdATI2VXAA.VXD )

Display Driver Version: 4.12.6288
Driver WHQL Certified: No
Max Texture Width : 1024
Max Texture Height: 1024
Max User Clipping Planes: 0
Max Active Hardware Lights: 0
Max Texture Blending Stages: 3
Textures In Single Pass: 2
Vertex Shader Version: N/A
Pixel Shader Version: N/A
Max Vertex Blend Matrices: 0
Max Texture Coordinates: 2
Vendor ID: 0x1002
Device ID: 0x5246
Sub-System ID: 0x00481002
Revision: 0x00

Resolution: 320x200x16-bit RGB [565]
Resolution: 320x200x32-bit RGB [888]
Resolution: 320x240x16-bit RGB [565]
Resolution: 320x240x32-bit RGB [888]
Resolution: 400x300x16-bit RGB [565]
Resolution: 400x300x32-bit RGB [888]
Resolution: 512x384x16-bit RGB [565]
Resolution: 512x384x32-bit RGB [888]
Resolution: 640x400x16-bit RGB [565]
Resolution: 640x400x32-bit RGB [888]
Resolution: 640x480x16-bit RGB [565]
Resolution: 640x480x32-bit RGB [888]
Resolution: 800x600x16-bit RGB [565]
Resolution: 800x600x32-bit RGB [888]
Resolution: 848x480x16-bit RGB [565]
Resolution: 848x480x32-bit RGB [888]
Resolution: 1024x768x16-bit RGB [565]
Resolution: 1024x768x32-bit RGB [888]

3D Capabilitys :
AGP Texturing
Additive Texture Blending
Bilinear Filtering
Factor Alpha Blending
Multiplicative Texture Blending
Point Sampling
Range Fog
Rendering to a Window
Specular Gouraud Shading
Subpixel Accurate Rasterizing
Table Fog
Texture Alpha Blending
Texture Clamping
Texture Wrapping
Trilinear Filtering
Vertex Alpha Blending
Vertex Fog

Sorry for the list but thats spec of the card.
Whether thats the problem am not sure.

flingster
12-30-2003, 10:43 PM
has 8.2 ever been working on this computer?

Scott M C4D
12-30-2003, 10:47 PM
Yes,8.2 was working fine until i added more plugin's to the huge list i have but i removed most of the recent ones but it's still unstable.

flingster
12-30-2003, 10:52 PM
scott for now just take out all your plugins and remove that as an issue for stability first i would say. then we can start looking at things like og settings and g card...since that hasn't changed and it worked before then can't be issue...unless it has changed more info please..:thumbsup:

Scott M C4D
12-30-2003, 11:03 PM
I did have a graphics tablet connected before which is not attached now but cinema was working when that was attached.
Maybe the drivers are screwing things up without the tablet as the drivers are still installed for that.

flingster
12-30-2003, 11:11 PM
maybe...edit>preference>common>graphic tablet
setting...dunno...give it a go.

JamesMK
12-30-2003, 11:18 PM
I bet Flingster's suggestion to remove ALL your plugs is a good one - and take it from there. If it works OK then, just add them again one by one until you find the culprit.

Scott M C4D
12-30-2003, 11:28 PM
Cheers guys, i will give it ago but am not holding my breath.

Can't wait till i get a new faster PC as cinema is pretty slow on my system anyway.

sinai_1
12-31-2003, 01:31 AM
Whenever Cinema behaves like that,..what should come to mind first is plugins; before getting to the comment about plugs,...as i was reading your post Scott,...i suspected plugs and (memory),....but you're not runinng Mac Os9,....so probably plugs..

Srek
12-31-2003, 07:29 AM
Originally posted by Scott M C4D
I am using an old Ati Rage 128 GL card

Well this can be the problem.
Try to deactivate Open GL (by deleting the prefs) and see if it works. The ATI Rage series has the crappiest OGL support you can get Software Shading should be faster and much more stable.

Cheers

Srek

JamesMK
12-31-2003, 08:06 AM
Originally posted by Srek
The ATI Rage series has the crappiest OGL support you can get
Just popping in to second that. Had one of those before, and boy did it suck... Endless driver problems in numerous different 3D apps...

Thalaxis
12-31-2003, 02:44 PM
Originally posted by JamesMK
Just popping in to second that. Had one of those before, and boy did it suck... Endless driver problems in numerous different 3D apps...

The only thing worse is the S3 SuperSavage piece of $&*#$# in
my IBM Stinkpad at work. Were it not for that poor choice, this
would actually be a pretty nice machine. :/

JamesMK
12-31-2003, 04:09 PM
Originally posted by Thalaxis
S3
:scream:

/me runs off screaming

imashination
12-31-2003, 05:05 PM
Originally posted by Scott M C4D
Hiya,
I am using an old Ati Rage 128 GL card

Hang on, I just need to sit down for a moment, I'll be with you in a minute or two.



OK, the solution is easy, take a screwdriver and ram it through the centre of the gfx card until you see blue sparks. Orange sparks aren't good enough, you need to keep doing it til you see a blue one.

Alternatively, remove your plugins folder to somewhere else and delete your prefs folder. Now try again, this time, don't activate openGL.

Scott M C4D
12-31-2003, 09:04 PM
Hiya people,

I found the problem and it appears it's one of the things i thought it was.
It seems that because the tablet was removed and replaced with a single mouse,that there awas a conflict with the drivers somehow.
C4D is now working with the tablet only now and c4d is now working without problems.
Thanks for everyone's advice,it's much appriciated :)
ps I never had to re-install C4D either.

Cheers

Scott M C4D
12-31-2003, 09:59 PM
Forgot to say that will be putting a screwdriver through my graphics card when the clock strikes 12 ;)

Happy New Year Everyone !!!!

flingster
01-06-2004, 06:51 PM
did you get blue and orange sparks...very cooooollll.

glad you got it working again...happy nu year:beer:

CGTalk Moderation
01-17-2006, 01:00 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.