SW 2008 causes explorer.exe to crash

[retatton]

Ever since upgrading to SW 2008 SP2.1 from 2007 I have had the problem of explorer.exe freezing (all windows become frozen, computer is unresponsive). This generally happens after working in SolidWorks and then closing the program. I can't always reproduce the problem though (I have tried with different programs running, etc.). I can use Task Manager to kill the explorer.exe process and then start the process again and everything is fine. I am using an ATI FireGL V3400 with the 8.44 driver version and I have a 3D Connexion Space Explorer with driver version 3.6.4. I have coworkers with identical computer systems and they have not experienced the problem. I had SW reinstalled to no avail. Any suggestions other than re-Ghosting my computer?

 

[CADFlyer]

I have encountered the same problem. Our IT thinks it is a 64x bit problem, and is not entirely unusual for Windows. I will try to re-tell his reason...I am new to 64 bit, so I may be wrong & buying into a wonderful story....

When Explorer gets closed down at the end of the day, along with everything else, the 32 bit programs close slower than the 64 bit programs (such as SolidWorks). Apparently Windows doesnt like that, so it locks up explorer.

I am hoping I am wrong, because it would be nice to fix this minor, but irritating problem

SolidWorks 2008 3.0
Dell T3400, XP 64x

 

[retatton]

I am running the 32-bit version on XP Pro SP2.

 

[Standing]

retatton,
Try this:
Turn off PDM in SolidWorks add-in. Then after SolidWorks starts up, turn on PDM. This means do not have PDM start when you start SolidWorks.


Bradley
SolidWorks Pro 2008 x64, SP3.0
PDMWorks Workgroup, SolidWorks BOM,
Dell XPS Intel(R) Pentium(R) D CPU
3.00 GHz, 5 GB RAM, Virtual memory 12577 MB,
nVidia Quadro FX 3400
Use SolidWorks BOM
e-mail is Lotus Notes

 

[Eltron]

I've had the same problem on a 32bit system. I'm not 100% sure it's a SW issue though. I've had it happen without SW open or running.

The only solution that I've found is to be sure to clear out temp files and cache folders religiously.

Dan

http://www.eltronresearch.com

 

[fcsuper]

It may be a memory management/allocation issue. Are you using the /3GB switch in your .ini? If so, you may need to adjust its value.

Matt Lorono
CAD Engineer/ECN Analyst
Silicon Valley, CA
Lorono's SolidWorks Resources
Co-moderator of Solidworks Yahoo! Group
and Mechnical.Engineering Yahoo! Group