AnsweredAssumed Answered

Fatal System Crash

Question asked by Ian Slocombe on Dec 17, 2007
Latest reply on Mar 31, 2008 by 1-4QBWL5

Like • Show 0 Likes0
Comment • 11

I have found that after SolidWorks 2008 has been left on for an extended period of time or if I use it hard, when I close a document my entire computer crashes to the BSOD (Blue screen of death)...I have the right video card drivers, plenty of hard drive space, a Gig of Ram, Win XP Pro, SW2008 1.1. Anyone else have this happen yet, or any suggestions?

No one else has this question

Outcomes

11 Replies

Steve Hildinger Dec 17, 2007 2:23 PM
Mark Correct
Correct Answer
What kind of info is on the BSOD? In particular look for something THAT_IS_LIKE_THIS followed by something like this: (0x0000009e, 0x000341d3, etc). You will want to know what the capital letters say and what the first number after it is (by number i mean 0x0000009E or whatever). You should be able to find the blue screen info in the system event log (right click on my computer, choose manage, there will be an event log section). When you get to the system event log you will find a red entry that will tell you the same info. Do a google search for the words in capital letters and/or the first number and you should be able to find what that blue screen pertains to. Chances are it's not SolidWorks itself causing the problem, but something wrong with some of your hardware or the way it's setup. If you want to post what kind of error you keep getting I can look it up also and put in my 2 cents(I've dealt with lots of BSODs).
Like • Show 0 Likes0
Actions
- Ian Slocombe @ Steve Hildinger on Dec 17, 2007 3:08 PM
  Mark Correct
  Correct Answer
  This is what I get from the Event Log.
  
  Event Type: Error
  Event Source: System Error
  Event Category: (102)
  Event ID: 1003
  
  Description:
  Error code 1000008e, parameter1 c0000005, parameter2 bfa4756a, parameter3 b02876ec, parameter4 00000000.
  
  Data:
  0000: 74737953 45206d65 726f7272 72452020
  0010: 20726f72 65646f63 30303120 38303030
  0020: 50202065 6d617261 72657465 30632073
  0030: 30303030 202c3530 34616662 61363537
  0040: 3062202c 36373832 202c6365 30303030
  0050: 30303030
  Like • Show 0 Likes0
  Actions
1-70W0UV Dec 17, 2007 2:37 PM
Mark Correct
Correct Answer
Take a look at your RAM ussage. SW2008 seems to use a lot of RAM, my system is more stable since I went from 2Gig to 4. How many people are sucessfully running SW2008 on 1GB RAM?
Like • Show 0 Likes0
Actions
- Mike Lydon @ 1-70W0UV on Jan 10, 2008 12:42 PM
  Mark Correct
  Correct Answer
  Daniel,
  
  I am running on 1Gig of RAM. I don't know how successfull I am. I am having issues with cosmetic threads that are driving me mad.
  
  Mike Lydon
  Like • Show 0 Likes0
  Actions
  - 1-4QBWL5 @ Mike Lydon on Jan 10, 2008 6:52 PM
    Mark Correct
    Correct Answer
    I have a similar issue after installing SW'08 and SP 1.1, when I close solidworks using the X button in the upper right corner, the machine shuts down as if I had turned the surge protector off.
    
    It has happened three times in the last week when working with smaller assemblies (<10 parts) and with a couple parts open.
    
    Any ideas??
    Like • Show 0 Likes0
    Actions
    - Rob Wolkers @ 1-4QBWL5 on Jan 15, 2008 11:46 AM
      Mark Correct
      Correct Answer
      I have exactly the same problem since I installed SW2008. Sometimes after I close a part I get the blue screen, but I can't read the message cause it reboots almost immediately.
      
      I tried to solve it by upgrading from 1 to 2Gig Ram and updated to Service Pack 1.1, but the problem is still there. Videocard&driver are ok/listed.
      Like • Show 0 Likes0
      Actions
      - Jonathan Hunter @ Rob Wolkers on Jan 15, 2008 12:52 PM
        Mark Correct
        Correct Answer
        
        Rob Wolkers wrote:
        
        I have exactly the same problem since I installed SW2008. Sometimes after I close a part I get the blue screen, but I can't read the message cause it reboots almost immediately.
        
        For anyone having this problem, in Win XP:
        
        Control Panel > System > Advanced Tab > Startup and Recovery "Settings" Button > Uncheck "Automatically restart" in the System failure frame.
        
        That will force you to manually restart the computer, and let you write down the error info without digging through the Event Log.
        
        Like • Show 0 Likes0
        Actions
        Erik Spofford @ Jonathan Hunter on Jan 30, 2008 11:14 AM
        Mark Correct
        Correct Answer
        I have a number of users at my company experiencing the same thing since we've gone to 2008. The blue screen points to the ATI driver as the faulting module, all our engineers use ATI Fire GL V3100 video cards. We have since updated to the latest driver available on ATI's site, it is newer than the Solidworks recommended driver, and so far no crashes.
        Like • Show 0 Likes0
        Actions
        1-4QBWL5 @ Erik Spofford on Mar 31, 2008 12:53 PM
        Mark Correct
        Correct Answer
        In working with my VAR, we upgraded to SP 3.1 and installed an Nvidia Quadro graphics card (from the ATI I had been using). In the 4 days or so that I have been using it, so far so good.
        
        I need to get the loaner graphics card back to the VAR so will see if SP 3.1 or the card fixed the issue..
        Like • Show 0 Likes0
        Actions
Steve Hildinger Dec 18, 2007 1:04 PM
Mark Correct
Correct Answer
The BSOD error 1000008e is for KERNEL_MODE_EXCEPTION_NOT_HANDLED_M.

This error typically pertains to hardware. Personally I'd say RAM or video card because that's where many BSOD's come from. Have you installed/replaced any new hardware recently? Try testing your memory with memtest86+. You can get it at memtest.org(it's free). You'll just have to burn a disk and boot from it. You don't really have to let it go through all the tests, you'll know by the third or forth test because it will give an error by then if the memory is bad(going through all the tests can take a long time and I've never seen errors past the forth test if there weren't any already). Another thing you might want to check into is the timings on your RAM. This can be set in your BIOS. You will need to know what the timing for you RAM is supposed to be.

You can also take a look at the minidump file. To do this though you will need a debugging tool from microsoft that reads dump files.
http://www.microsoft.com/whdc/...debugging/default.mspx
Is where it is at, if the link works. You will need to download the a symbol package as well. You might want to find a tutorial online if you want to look at the dump file, just google for "Microsoft Debugging Tools". It can really give you insight as to what's causing the problem though and is the best way to find out what's happening, but it might confuse some people if they aren't too computer savvy.

HTH
Like • Show 0 Likes0
Actions
- Ian Slocombe @ Steve Hildinger on Dec 18, 2007 4:27 PM
  Mark Correct
  Correct Answer
  Thanks Steven. My video card and driver should be good, since I made sure I had the ones listed on the SolidWorks site. The RAM is the one that keeps popping up in people's replies and comments. I am getting to test a new computer here at work that has 4 Gig, so I doubt I will run into this problem on it.
  
  Thanks again
  Like • Show 0 Likes0
  Actions

Fatal System Crash

Outcomes

Related Content

Recommended Content