Memory Error

[dregischan]

For some reason, out of the blue, when I start Solidworks 2001Plus, I get a window titled, "sldworks.exe - Application Error" The instruction at "0x76fc7103" referenced memory at "0x00000058". The memory could not be "written".

I'm at a loss, can anyone help?

Thanks in Advance!

 

[APPENG]

Please do me a favor and list your hardware specs, Operating system (and service pack), and system settings like Paging file size, and the amount of disk space you have avaliable on your hard drive. Type of video card, amount of physical ram etc.

Generally speaking, those types of sporadic crashes can be difficult to diagnose. But there are a lot of places that we can look. Regards,
Jon
jgbena@yahoo.com

 

[Standing]

dregischan,
I get those types of errors also. Ever since I upgraded to SolidWorks 2001 Plus SP 2.0. One of our engineers reinstalled SP 1.2 and has not crashed since.
Bradley

 

[BBJT]

I was told by one our outsource companies that they are not going to 2001Plus until Service Pack 3 is released. They heard that sp2 crashes allot. I and another gentleman are testing SP2. We also have been experiencing sporadic crashes. SolidWorks seems to be getting more careless with each SP. BBJT CSWP

 

[dregischan]

APPENG:

I run a PIII-733MHz, 256MB PC133 RAM, PageFile Size: 256MB, ATI All in Wonder RADEON 32MB AGP, 5GB Hard Drive space remaining, Windows 2000 Pro (SP2). I was working fine for a while but it just stopped working yesterday. The identical error occurred with the same PC while running Solidworks 2001. We upgraded to the Plus package and all seemed fine until yesterday.

Dregischan

 

[SBaugh]

I'm still using SP0 and I haven't had a single problem with it. So since there isn't anything I really need in any of the other SP I'm not going to switch till the next big release or SW has something to offer in their next SP.

I'll let you guys fight it out in the trenchs

Good luck, Scott Baugh, CSWP
credence69@REMOVEhotmail.com

http://home.insightbb.com/~scott.baugh/

 

[dregischan]

Thanks BBJT, Scott, Bradley and Appeng:

I'm still not sure how to overcome this obsticle. To me it's very strange. I'll keep trying. I guess that's all I can do.

Once Again,
Thanks

 

[APPENG]

Dregischan,

First thing that I would do if I were you would be to upgrade to 512 MB of Ram, although SWX runs on 256 you will see really nice performance gain.

Set you paging file size to 1500MB minumum and 1500MB maximum that way you system will set aside that much for swap space instead of trying to vary it on the fly, this will prevent your swap data from becoming fragmented. This in itself can cause a system crash like that It has happened to me as well.

As to the radeon vid card, I have found these cards to be a bit "twitchy" at best. I would suggest first making sure that you have the latest driver available for your video card. Then I would try to work with the settings of the video card. For instance I have seen people that have set their screen resolution over 1280x1024 and have their machines lock up like crazy. Try lowering your screen res below this number and see if this makes it any better.

Personally, if it were me wanting to make the most of my tube time, I would replace the card with one of the passing video cards, I have had great success with the Diamond FireGL-1 and 2, and the Nvidia Quadro2 pro 64.

I realize that a video card can cost a great deal of money to replace, but you have to consider how much you value your design time!

Try the things I outlined here and get back with me if you still have issues.

Regards,
Jon
jgbena@yahoo.com

 

[dasarge]

I recently had an issue with memory leaks and SP1.2 and 2.0.
SW was grabbing alot of virtual memory. By going to event viewer I could watch as SW would just grab more and more, Even after SW was closed down. I tried to uninstall then reinstall same thing happened. I had to uninstall SW and clean out the registries it has been a few days and the problem has not returned

 

[APPENG]

Ive seen that too dasarge, And if I remember correctly it was due to an issue with excel, and the use of design tables, Two things would happen, excel would still be present in the background and not release the memory space, and solidworks would keep grabbing up more and more mem space, and then SLOWLY trickle it away. Sometimes it would take up to 15-20 minutes to dump it all.

If this was happening to you while NOT using a DT, the I am not sure what the cause could be.

Anyone else have any ideas?

Regards,
Jon
jgbena@yahoo.com

 

[dregischan]

Dasarge:
Thanks for the registry and uninstall info. I performed those tasks before I asked for help here. I cleaned the registry but one thing is very strange with my system. I had SW2001 on my PC previously and although I cleaned my registry and it's not on my hard drive, the title SW2001 is still resident in my Add/Remove programs area. When I intall SW2001+, it installed in the same area as the straight 2001 but in the Add/Remove programs area, it shows both 2001 and 2001+. I've never encountered these problems before and I've been around PCs a real long time. It's always something.

APPENG:
Thanks a million for your advice, I will take it with great regard as I definitely cannot afford to be down much longer. I agree, the ATI card is a bit twitchy. I may if at wits end rebuild this system completely. I would like to have the Diamond but I use this ATI card for Video in as well so I'm kind of stuck with it. I do have ALL the current drivers intalled for ALL my hardware and the updated SPs as well.

I'll let you know the results of your recommendations.

Thanks,
Dregischan

 

[dregischan]

Well guys - I did everything I could but no cigar. I really do appreciate all your advice. I'm left with the unwanted task of "Let's rebuild Mr. PC" solution. That's my next step. I truly believe I'm having problems with residuals left by the SW2001 installation/uninstall. I've also worked as a software developer using Delphi and when the Application Error occurs, I have a choice to debug SW. Can you believe that? I can actually view the compiled errors. I should be back in business within a day or so. I look forward to your responses.

Once Again,
Thanks,
Dregischan

 

[APPENG]

Best of Luck!

I still the the vid card is a major part of your headaches and for what its worth, I use an Nvida RIVA TNT2 at home with great success with 2001+ (gateway P3 650, 320Mb ram)

If you cant afford the big guns, you can shop a little lower. Check out the solidoworks site for more info on approved vid cards.

Regards,
Jon
jgbena@yahoo.com

 

[Standing]

I am running SolidWorks 2001 plus SP 2 on a Compaq 1.8 meg, 1 Gig memory. I crash about 3 times a day. I could live with the crashing. I opened an assembly, which has no mate errors. When I inserted a new component into that assembly, one of the original parts, before the insert came up with a new mate error. The one I just inserted has no mate errors. So I delete the mate with the error. Then another part gets a mate error. This continues on until all of those errors have been removed. A total of 32 errors for this assembly. I gave up and uninstall SP 2 and reinstalled SP 1.2. I reinserted the part above, from the beginning, (We have PDM/Works so I can start from the beginning). No mate errors at all. Not enough time has pasted to see about the crashing. I suggest we down grade to SP 1.2.

 

[SBaugh]

If you reinstall SW why don't you just stay with SP0 and try your assembly. If it does or doesn't work then you will know it has to do with that particular SP.

Also, just because you installed a newer SP doesn't mean that your files should be saved backwards to work with older SP of SW01+. It is only major releases of SW when you can revert back. SP are different.

I hope that helps, Scott Baugh, CSWP
credence69@REMOVEhotmail.com

http://home.insightbb.com/~scott.baugh/

 

[dregischan]

Hello Again:
Okay, I replaced the ATI Video Card with one I had in my Server, an NVidia TNT2. I still get the same exact error. I have finally backed up all my stuff so now I'm going to rebuild my PC. Once Again, thanks for all your helpful attempts at my freaky dilemma.

Dregischan