crashes... desperate for a fix

System built July 03 Win 2000 sp3 P4 2.6Ghz Kingston 1Gb RAM Motherboard: Gigabyte 8ipe1000 Graphics card: 3DLab Wildcat VP870 WD HDD 120Gb (not connected thru SATA) Runnig Solidworks 2003 sp3.1

I have been experiencing crashes during SWX sessions. It happens randomly: opening a file, starting a new part (calling up the template), switching from one window to another (within SWX), basically anytime. SWX just crashes and diplays this message: Solidworks has terminated due to an unhandled error. Please contact?.blah blah blah Swx creates a performance log file. Following are 2 examples of the file. I have only copied the very last part of the files, just to show what "happened" when crashing. Example 1: [1.53] "Floating Point Divide by Zero";

3dlICD:Unknown,sldrglu:createOglShadeObject,sldworks:Unknown,sldgfxu:gfxSgView_c::gfxSgView_c;

1066612820 T=7370;I=0;

Example 2: =4 34251 0 "Access Violation at 00000000 (virtual address 00000000), attempt to read from memory"; sldworks:Unknown,MFC42u:Ordinal6330;

1066601208 T=809;I=0;

1066601208 T=809;I=0;

I am desperate for a fix. Any suggestion would be greatly appreciated.

Reply to
john
Loading thread data ...

probably due to graphics card -what is your graphics driver? is it one approved by SW? try updating to latest

Reply to
neil

Sorry, I forgot to mention. I run the ver. 3.01-450 driver. I did try the 3.01-535 (the latest), but it has a "bug" (it did with me anyway) with the help file in SWX: the actual content of the Help dialog box would disappear. I reverted back to the 450. To me, it seems to be related to memory/graphics card or a conflict of some sort between the two?. Just before crashing, the pc sort of "hang" for a couple of seconds, and bang CTD. Again, I am desperate to find an answer, as it is really hard to work knowing that the SWX can crash at any time. Thanks.

Reply to
john

First of all there is a long list of troubleshooting information on

formatting link

Second, you can easily eliminate graphics related issues by running in OpenGL mode or rebooting in safe mode.

When you quote the log file make sure to grab about a dozen l> System built July 03

3dlICD:Unknown,sldrglu:createOglShadeObject,sldworks:Unknown,sldgfxu:gfxSgView_c::gfxSgView_c;
Reply to
kellnerp

3dlICD:Unknown,sldrglu:createOglShadeObject,sldworks:Unknown,sldgfxu:gfxSgVi ew_c::gfxSgView_c;
Reply to
bill allemann

My crashes where similar, but I'd get the old BSOD with a simialr access violation. But once I updated the mother board drivers (aka inf update or 3 in 1 update), it was fixed and have never experienced other crash.

HTH

R> "Floating Point Divide by Zero";

3dlICD:Unknown,sldrglu:createOglShadeObject,sldworks:Unknown,sldgfxu:gfxSgView_c::gfxSgView_c;
Reply to
gtosan1

First of all, I appreciate the time you guys take to look at my issue.

1/ I've gone through the documentation from swx re. "troubleshooting crash prone systems", but to no avail. BTW, the hard disk is partitioned into 3 (approx equal sizes). I have the swap file (2500Mb) currently on C: as well as all apps. The 2nd partition has a little bit of data, and the SWXtemp dir on the 3rd partition. 2/ The ram was swapped for a new one (2x 512 sticks) although they are still Kingston. 3/ Following are again 2 examples of the log file as per kellnerp advice. The 1rst one was a short session... I have shortened the 2nd one. Again, thanks for the assistance.

Example 1: 2 SP3.1 eDrawings2003:Enabled PhotoWorks release 2:Disabled SldTrans

1.0:Disabled SldUg 1.0:Disabled SolidWorks 2D Emulator:Disabled SolidWorks 3D Meeting:Enabled SolidWorks DXF3D:Disabled SolidWorks HCG:Disabled SolidWorks HSF:Disabled SolidWorks Inventor:Disabled SolidWorks JPEG:Disabled SolidWorks MDT:Disabled SolidWorks MTS:Disabled SolidWorks Pro/E:Disabled SolidWorks SE:Disabled SolidWorks ZGL:Disabled 3dlDD V4.01 X1280 Y1024 32 bits 75Hz :3Dlabs :Wildcat VP870 - GL2 :1.3.1 :1.3.0 :3DLabs Installable Client Driver :3Dlabs Inc. Ltd :OpenGL Installable Client Driver DLL :Copyright © 3Dlabs Inc. Ltd 1994-2000 :4.10.01.2105-3.01.0450 6.0.2800.1106 english,english,3081 =4 37619 0 [0.00] =4 33949 0 [2.22] =4 57601 0 uiDVEDefaultDialog_c [4.78] =4 57603 0 PART [2.67] =4 57602 0 [0.05] =4 33949 0 "Access Violation at 6aa722d6 (virtual address 0000144c), attempt to read from memory"; MSVBVM60:EbLibraryUnload,MSVBVM60:EbResetProject;

1066169324 T=80;I=0;

1066169333

Example 2: [3.75] =4 57607 0 [5.19] =4 33055 0 [17.34] =4 57607 0 [33.23] uiDVEDefaultDialog_c =4 33826 0 [0.00] =4 33047 0 uiDVEDefaultDialog_c [0.13] =4 33640 0 =4 34127 0 [0.00] [0.11] =4 32805 0 [0.81] =4 57607 0 [7.94] =4 57602 0 PART DRAWING [7.22] =4 33055 0 [12.66] =4 57607 0 [32.17] =4 33055 0 [12.05] =4 57607 0 [13.27] =4 57602 0 [2.38] =4 57602 0 [0.05] =4 57601 0 [16.50] =4 57601 0 [5.70] =4 57601 0 uiDVEDefaultDialog_c [98.19] "Floating Point Divide by Zero"; 3dlICD:Unknown,sldrglu:createOglShadeObject;

1066195749 T=4582;I=0;
Reply to
john

I see in your log file that you've got photoworks, among other add-ins, enabled. I'd suggest disabling them and seeing if it makes any difference.

Reply to
Michael

Thanks for the suggestion. I checked and Photoworks is actually disabled, but somehow 3D content central and 3D meeting were enabled. I've turned those off. I am currently stuck on a particular drw. Assembly 6mb, drw 8mb. I try to create another named view, click in the model, click back in the drw to locate the view on the sheet, the view is displayed on the screen for a split second and then bang SWX crashes, not even the standard message... Same crap at the end of the log file: [3.72] =4 57601 0 [2.39] =4 33311 0 [35.48] =4 33311 0 [4.67] =4 57601 0 uiDVEDefaultDialog_c [15.17]

0 =4 33874 0 [0.19] =4 33047 0 uiDVEDefaultDialog_c [0.34] =4 57651 0 [0.19] =4 32973 0 uiNamedViewDveDlg_c [0.47] "Access Violation at 00000000 (virtual address 00000000), attempt to read from memory"; sldworks:Unknown,MFC42u:Ordinal6330;

1066698750 T=1313;I=0;

The same operation works fine on another (lower specs) machine. I am really stuffed here. I have to get the job done though and I am just about to loose the plot... and I mean it.

Reply to
john

snipped-for-privacy@hotmail.com (john) wrote in news:80fa716e.0310201420.50a4ef94 @posting.google.com:

This is going to seem counterintuitive, but try setting your swap file so the min and max are each 1000 Mb. Please post the results.

matt (the guy who wrote the troubleshooting crash prone systems doc)

Reply to
matt

I was getting the old 'blue screens of death' with a similar memory access violation message, a half a dozen times, the first day I installed sw2004.

Then I updated the motherboard drivers, AKA inf update or 3in1 update, it's seperate update from the bios flash update. It's basically an os patch for your mother board.

Haven't had a single crash since.

R> "Access Violation at 00000000 (virtual address 00000000),

Reply to
gtosan1

After trying many suggestions, I finally returned the VP870 to where it came from (my VAR)!. I've installed a nVidia Quadro FX500 4 days ago, and haven't experienced a single crash... while performing similar tasks. I keep my (left) fingers crossed, and I am finally able to do my work now ! My VAR was very supportive during this ordeal I must add. Thanks all for taking the time to answer my call.

And on a lighter note, a quote from Rob Hirst (Midnight Oil drummer/Author): Politicians and nappies have something in common. They should both be changed regularly. And for the same reason.

Reply to
john

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.