Time for a workstation? Is my Laptop aging? How can I tell?

[huskermcdoogle]

So I hate to start another hardware thread, but I think what I want to ask is a question we all need answered from time to time.

So I have a decently equipped Sager workstation laptop, and it was needed when I bought it as I was part time here and was working from home on the weeknights, then driving a few hours up to SA on the weekends and working in the office.  Well now I am full time in the office and don't need full time blazing fast mobile capability.

Anyway, I think the lappy is starting to show its age.  I can't tell if it is software, hardware, or both.  I am having issues with Mastercam crashing constantly.  I have to close and reopen at least once every hour, and reboot the machine at least once or twice in the middle of the day (4-6 or so hours of use).  I am experiencing issues with things like toolpath editor being unusable even for simple paths.  I have extensive lag opening the moduleworks path parameters dialog.  I just can't tell what is wrong and have hesitated to just blow everything away and build software fresh as I don't have the time to invest into that if it isn't guaranteed to help.

If I had to guess, I am losing at least an hour a day due to computer/software issues.  Frustrating, just plain frustrating.  We are a small company and have been struggling to get some things up and running the last few months as some projects have unexpectedly all but dried up that were our cash flow kings.  Its a blessing and a curse, as we need the down time to get caught up on maintenance, but I don't have time to program and work on machines at the same time...  I have lots of small run / sample jobs to get out the door, average time to cutting chips on a programming job right now is 2 long days for a simple part.  I think I could cut this significantly if I were able to get rid of interface lag issues, and didn't need to restart MCAM all the time.

How often do you upgrade or replace hardware? Entire machine or just components?

Is the value of what BOXX sells worth it?  How do you decide how to configure?  Do they help you with that?

I am not very interested in building my own system, but at the same time can't afford to drop 5k on a machine right now.  Do any of you guys lease workstations?  What are your lease terms if you do?

TIA

Husker

 

[gcode]

The Boxx machines are very nice but they are expensive.

I'd go with a APEXX 2 2402 and upgrade the video card to at least a K2200

That will run about $3500

We have four here running 32gig of ram and K4200 video cards.

I like them enough that I bought one for myself to use at home.

If money is tight, I'd go to the Dell Business Outlet store and buy a refurb workstaion

Those will run from $1K on up.  You should be able to get a Mastercam worthy workstation for about $1500

If money is really tight, go to Best Buy and pick up a good gaming tower with a GEForce video card

 

[Matthew Hajicek - Singularity]

Those kinds of issues I would expect are software related.  You might try a clean reinstall of your OS.

[John@WMM]

I would agree with Matthew... Many times its software related.

Here at WMM I manage our network with 15 Mastercam computers. Most of our newer machines are Dell XPS i7's running in the 3.5 GHz range with 16 GB ram. We have been upgrading these Dells with the NVIDIA Quadro K2200 graphics card. This is about a $1200 computer setup and its been working very well for us. Maybe a setup like this could be a good option for you?

[So not a Guru]

Have you ran a memory test? That would be my 1st thought, if I was suspecting a hardware issue.

[huskermcdoogle]

Mem test yielded nothing.  Neither did a benchmark on the graphics card.  Though I wonder what some of you guys are getting benchmark wise with your graphics cards.  If you look in my signature, my laptop has 3 year old top notch mobile hardware.  I guess I should plan a day to reload my OS.  

Now starts the creation of a list of things to save before I format....  I always forget something.

[huskermcdoogle]

BOXX has K2200 and M4000 listed at a decent price range.  What was the card that people were having issues with?  I don't feel my card is all that great, has issues with things like the tool manager not displaying.

[Matthew Hajicek - Singularity]

Look at reinstalling Windows then.  MS has recommended reinstalling every six months...

[huskermcdoogle]

Just reinstall without formatting?  Or clean install?

[Matthew Hajicek - Singularity]

AFAIK a format shouldn't be required.  Be sure to back up everything first.

[gcode]

On ‎3‎/‎27‎/‎2017 at 0:42 PM, huskermcdoogle said:

BOXX has K2200 and M4000 listed at a decent price range.  What was the card that people were having issues with?  I don't feel my card is all that great, has issues with things like the tool manager not displaying.

Some people have had trouble with the M4000, I know they run hot and require good ventilation.

I have an M4000 on my home workstation and have not had any trouble with it.

I believe the K4200 is an older model, the M4000 is the newer model .

We've got several of these and have had no trouble with them either

 

[Colin Gilchrist]

I don't think this is Windows related, at all. That is just based on my own anecdotal experience with 2017. I just went through a nightmare of a project, programming Shotgun Stocks for a client. I could not get more than 60 minutes out of Mastercam 2017 without a major crash. It got to the point where I was saving every 5 minutes, and I was still getting crashes. This wasn't during "crunching" for tool paths. This was strictly design work, where I was manipulating surfaces and wire frame geometry.

It got so bad that I ended up saving all my files, and did a complete Format and Reinstall of Windows 10.

Even after going through a fresh install of Windows, and then 2017, I still experienced similar issues. It probably cut down on the crashes by half, which is to say that it was still a major headache. The worst part is that there were no "reproducible" steps to take. I have no idea what was causing the crashes, but I noticed that many of them would occur when I was changing my graphics view. If I would "scroll" with my mouse wheel to "zoom in/out", and then try to "rotate" the geometry with the mouse wheel by holding down, this would crash about 20% of the time. Again, nothing I could "duplicate" so that it could be sent into QC.

Had I known that 2017 was going to be that awful, I would have just stuck with X9. At least that version seemed to be stable, with the hardware that I have. My laptop isn't "super high-end". It is a run of the mill "gaming laptop" from MSI. 24 Gb of RAM, with GeForce GTX 870M card.

I was encountering some other strange stuff as well. If I untrimmed a surface, and then extended the surface, without saving in-between, then I'd end up with between 10-100 "copies" of the geometry on that level. It was literally creating dozens of the exact same surface. And of course, only some of those would get tagged as "duplicates". So "Delete Duplicates" wouldn't clean up all of the extra surfaces. I'd have to go and delete them manually. I finally figured out that I could use "Vector" selection method, and draw a line on the screen that would "project" down onto all these extra surfaces. I'd "delete" them all, and then press "undelete" a single time, to get back one copy of the surface I wanted to save.

As a test, use your same laptop, and install X9. Then see if you are getting the same crashing behavior. I would put money on it not being your current OS configuration, but a fundamental flaw in Mastercam 2017.

The real issue for me is that I can't find a set of steps to duplicate the issue. So how do I report those errors to QC? I can't without having something to go on.

I really wish I had just taken on that former project in X9. All the issues with 2017 caused me to double the number of hours that I estimated it would take. I did great on creating the tool paths, but wish I had used any other CAD program to do the work I needed to get done. I finally had to give up and go to Rhino to do some of the surface modifications, because Mastercam wouldn't let me work with the surfaces I had without crashing every 10 minutes.

I was able to find a little information on the problem by using "System Information" in Windows 10.

I tried changing settings on my Graphics Card, tried forcing Mastercam to use the GeForce card. (profile already set to use it.) I also tried turning off the "Mastercam Logger" in the system tray. I tried to do that for each time I had to restart Mastercam. Sometimes I would forget, so I included some of the MCLogger.exe errors as well.

I also deleted all of the TEMP data from Mastercam, and set my Configuration File to point to C:\TEMP\MCAM for all of my Temp Files.

 

Husker,

Try going to the Windows Start Menu > Run and typing in "System Information". In the dialog box, go to the "Software Environment > Windows Error Reporting" section (at the bottom).

Here are some of my entries:

2/17/2017 3:30 PM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.13088.0, time stamp: 0x5821f60d
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000409
Fault offset: 0x000000000006dd27
Faulting process id: 0x1eb4
Faulting application start time: 0x01d288d3168efd9a
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll
Report Id: 4f6bec36-f096-4b0b-94aa-7e631d088c04
Faulting package full name: 
Faulting package-relative application ID:

 

2/17/2017 4:09 PM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.13088.0, time stamp: 0x5821f60d
Faulting module name: nvoglv64.DLL, version: 21.21.13.7849, time stamp: 0x58820dae
Exception code: 0xc0000409
Fault offset: 0x0000000000f8d778
Faulting process id: 0x1b18
Faulting application start time: 0x01d28932e5b65bd5
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\nvoglv64.DLL
Report Id: abc9906b-02a5-48c2-88ea-2e50741f2826
Faulting package full name: 
Faulting package-relative application ID:

 

2/18/2017 7:30 AM    Application Error    Faulting application name: MCLogr.exe, version: 19.0.15109.0, time stamp: 0x5858c7c9
Faulting module name: MCLogr.exe, version: 19.0.15109.0, time stamp: 0x5858c7c9
Exception code: 0xc000041d
Fault offset: 0x0000000000003892
Faulting process id: 0x16cc
Faulting application start time: 0x01d289ad03f61a40
Faulting application path: C:\Program Files\mcam2017\MCLogr.exe
Faulting module path: C:\Program Files\mcam2017\MCLogr.exe
Report Id: d371df2b-7d64-4979-9ea5-069e0fa12fd8
Faulting package full name: 
Faulting package-relative application ID:

 

 

2/18/2017 7:30 AM    Application Error    Faulting application name: MCLogr.exe, version: 19.0.15109.0, time stamp: 0x5858c7c9
Faulting module name: MCLogr.exe, version: 19.0.15109.0, time stamp: 0x5858c7c9
Exception code: 0xc0000005
Fault offset: 0x0000000000003892
Faulting process id: 0x16cc
Faulting application start time: 0x01d289ad03f61a40
Faulting application path: C:\Program Files\mcam2017\MCLogr.exe
Faulting module path: C:\Program Files\mcam2017\MCLogr.exe
Report Id: dc04336c-2371-44a5-8953-c0f8fff551d7
Faulting package full name: 
Faulting package-relative application ID:

 

2/18/2017 7:30 AM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.15109.0, time stamp: 0x58866305
Faulting module name: nvoglv64.DLL, version: 21.21.13.7849, time stamp: 0x58820dae
Exception code: 0xc0000409
Fault offset: 0x0000000000f8d778
Faulting process id: 0x19a0
Faulting application start time: 0x01d289ad036e2d43
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\nvoglv64.DLL
Report Id: 4eca24d9-539d-4834-833d-8abbd2181114
Faulting package full name: 
Faulting package-relative application ID:

 

2/18/2017 7:36 AM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.15109.0, time stamp: 0x58866305
Faulting module name: nvoglv64.DLL, version: 21.21.13.7849, time stamp: 0x58820dae
Exception code: 0xc0000409
Fault offset: 0x0000000000f8d778
Faulting process id: 0x195c
Faulting application start time: 0x01d289b8f1777669
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\nvoglv64.DLL
Report Id: 7437c821-4e01-4229-b56a-d4e59674c16b
Faulting package full name: 
Faulting package-relative application ID:

2/18/2017 7:36 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 7896dd35-9bd3-48e9-807a-90e71b299874

Problem signature:
P1: 141
P2: ffffa683005174a0
P3: fffff8088a827508
P4: 0
P5: 1d4
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170218-0230.dmp
\\?\C:\Users\colin_000\AppData\Local\Temp\WER-55045968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF646.tmp.WERInternalMetadata.xml
\\?\C:\Windows\Temp\WERA828.tmp.csv
\\?\C:\Windows\Temp\WERABE2.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_576ed286aef1aef6e9da6066d4c69b0822e97c8_00000000_cab_1d9dad2a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 24370337-f5ac-11e6-aea9-8056f2a5c124
Report Status: 0
Hashed bucket:

 

2/18/2017 7:36 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa683026754a0
P3: fffff8088a827508
P4: 0
P5: 195c
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170218-0235.dmp
\\?\C:\Users\colin_000\AppData\Local\Temp\WER-55386750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FD0.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_f73616aa4f77c096e968da34651f3c8ef45cdfa_00000000_cab_12257fe0

Analysis symbol: 
Rechecking for solution: 0
Report Id: ef5651ce-f5ac-11e6-aea9-8056f2a5c124
Report Status: 4
Hashed bucket:

 

2/18/2017 7:37 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 34ff9627-4a7c-49fe-a7fc-6934190e528d

Problem signature:
P1: 141
P2: ffffa683026754a0
P3: fffff8088a827508
P4: 0
P5: 195c
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170218-0235.dmp
\\?\C:\Users\colin_000\AppData\Local\Temp\WER-55386750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FD0.tmp.WERInternalMetadata.xml
\\?\C:\Windows\Temp\WERC69F.tmp.csv
\\?\C:\Windows\Temp\WERC6FE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f73616aa4f77c096e968da34651f3c8ef45cdfa_00000000_cab_1d9dc95c

Analysis symbol: 
Rechecking for solution: 0
Report Id: ef5651ce-f5ac-11e6-aea9-8056f2a5c124
Report Status: 0
Hashed bucket:

2/18/2017 7:41 AM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.15109.0, time stamp: 0x58866305
Faulting module name: nvoglv64.DLL, version: 21.21.13.7849, time stamp: 0x58820dae
Exception code: 0xc0000409
Fault offset: 0x0000000000f8d778
Faulting process id: 0x1d7c
Faulting application start time: 0x01d289ba220dcb79
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\nvoglv64.DLL
Report Id: fce44644-1fa9-4c9d-aa78-58a7d5f2243e
Faulting package full name: 
Faulting package-relative application ID:

 

2/18/2017 7:42 AM    Windows Error Reporting    Fault bucket 116329913036, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Mastercam.exe
P2: 19.0.15109.0
P3: 58866305
P4: nvoglv64.DLL
P5: 21.21.13.7849
P6: 58820dae
P7: 0000000000f8d778
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\Users\COLIN_~1\AppData\Local\Temp\Mastercam Event Log.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E78.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Mastercam.exe_2461e9f8cdc1c1424a434b81a3620ec30e7b696_9f9c0330_21fb9cce

Analysis symbol: 
Rechecking for solution: 0
Report Id: fce44644-1fa9-4c9d-aa78-58a7d5f2243e
Report Status: 0
Hashed bucket: 199476efd53177384bc607bc467092e8

 

2/18/2017 7:42 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 735c622b-c4b7-4e43-9220-dc23ba8ae90a

Problem signature:
P1: 141
P2: ffffda8fc17b64a0
P3: fffff801924a7508
P4: 0
P5: 1d7c
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170218-0241.dmp
\\?\C:\Users\colin_000\AppData\Local\Temp\WER-187531-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BF7.tmp.WERInternalMetadata.xml
\\?\C:\Windows\Temp\WER93E4.tmp.csv
\\?\C:\Windows\Temp\WER93F5.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e5294414c7b087a3b151ca105a5a6f13a4abd74_00000000_cab_18c394a0

Analysis symbol: 
Rechecking for solution: 0
Report Id: a8930c3e-f5ad-11e6-aeaa-8056f2a5c124
Report Status: 0
Hashed bucket:

 

2/18/2017 7:42 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffda8fc17b64a0
P3: fffff801924a7508
P4: 0
P5: 1d7c
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170218-0241.dmp
\\?\C:\Users\colin_000\AppData\Local\Temp\WER-187531-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7BF7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_e5294414c7b087a3b151ca105a5a6f13a4abd74_00000000_cab_21f37c84

Analysis symbol: 
Rechecking for solution: 0
Report Id: a8930c3e-f5ad-11e6-aeaa-8056f2a5c124
Report Status: 4
Hashed bucket:

 

2/18/2017 7:43 AM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.15109.0, time stamp: 0x58866305
Faulting module name: nvoglv64.DLL, version: 21.21.13.7849, time stamp: 0x58820dae
Exception code: 0xc0000409
Fault offset: 0x0000000000f8d778
Faulting process id: 0x2198
Faulting application start time: 0x01d289ba883beaaf
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\nvoglv64.DLL
Report Id: c19aac1d-b147-4c11-8ac9-a68b50695985
Faulting package full name: 
Faulting package-relative application ID:

 

 

 

 

[huskermcdoogle]

Colin,

Interesting that you were having that trouble on a shotgun stock.  I was last working on a rifle stock....  I would be willing to pay for some of your time to see how you go about some things if you are willing.  Always looking for other ways to slice and dice these things.  Seemingly simple rest milling ops can take hours to create a good smooth efficient path for that won't rub the hell out of the tool or tear the wood grain.  The in-letting is the only easy stuff, but you still have to worry about chipouts....  

Anyway, maybe we need to team up with QC on this one and have them do some testing on a few files to see if they can't repeat some of the frustration we have been experiencing, I am guessing they would run into similar troubles immediately upon attempting to follow the sequence of events that we do.  I think partially the lack of being able to repeat it is due to things we don't think about, or can't control at the time.  Things like streaming music over Bluetooth, I just had to stop using a Bluetooth speaker as it was causing instability with my mouse and keyboard (also Bluetooth to avoid dongle).  Most of the time it was fine, then all of a sudden it would freeze my mouse any time a clicked a key.  Then with a different brand of keyboard my shift key would be stuck and I would get repeating //////  whenever I clicked in a box.  Haven't tested that keyboard since I figured out the speaker aspect.  My - key is the problem with keyboard right now, it broke off in my backpack a month ago, just have to hunt a little harder now to type it in.

I don't believe it has to do with any specific set of commands that we use but rather something more in the video drivers aspect things.  My suspicion on this is due to the fact that the toolpath editor is useless for me right now and it is a very useful and needed tool for making a multi-axis path not gouge a part at high speed.  If I set to integrated graphics, toolpath editor isn't as bad but still sucks and many of the problems go away, but others crop up, like hovering over the gnomon on lower left will blank the screen.  Surface tessellation takes forever but its stable.  This is why I deal with the problems when set to the graphics card, these activities take much less time and things look great.

 

Some examples from the logs from yesterday:

3/26/2017 1:24 AM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.15109.0, time stamp: 0x58866305
Faulting module name: Mastercam.dll, version: 19.0.15109.0, time stamp: 0x58866285
Exception code: 0xc0000005
Fault offset: 0x000000000033ae90
Faulting process id: 0x3a38
Faulting application start time: 0x01d2a5cac6bdd4b8
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\Program Files\mcam2017\Mastercam.dll
Report Id: ed683b5a-11c2-11e7-b871-8086f2bd4d30
 

3/26/2017 1:24 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Mastercam.exe
P2: 19.0.15109.0
P3: 58866305
P4: Mastercam.dll
P5: 19.0.15109.0
P6: 58866285
P7: c0000005
P8: 000000000033ae90
P9: 
P10: 

Attached files:
C:\Users\Doogle\AppData\Local\Temp\Mastercam Event Log.xml
C:\Users\Doogle\AppData\Local\Temp\Mastercam Error Log.txt

These files may be available here:
C:\Users\Doogle\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Mastercam.exe_2347b83d910b68c41c91f1b827343391cd8c130_2901a10a

Analysis symbol: 
Rechecking for solution: 0
Report Id: ed683b5a-11c2-11e7-b871-8086f2bd4d30
Report Status: 0
 

3/26/2017 3:39 PM    Application Error    Faulting application name: Mastercam.exe, version: 19.0.15109.0, time stamp: 0x58866305
Faulting module name: interfacial12.dll, version: 2016.1.19.0, time stamp: 0x5668feb4
Exception code: 0xc0000005
Fault offset: 0x000000000001d1a0
Faulting process id: 0x2a38
Faulting application start time: 0x01d2a646da6cc572
Faulting application path: C:\Program Files\mcam2017\Mastercam.exe
Faulting module path: C:\Program Files\mcam2017\interfacial12.dll
Report Id: 5b383644-123a-11e7-b61c-8086f2bd4d30

3/26/2017 3:39 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Mastercam.exe
P2: 19.0.15109.0
P3: 58866305
P4: interfacial12.dll
P5: 2016.1.19.0
P6: 5668feb4
P7: c0000005
P8: 000000000001d1a0
P9: 
P10: 

Attached files:

These files may be available here:
C:\Users\Doogle\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Mastercam.exe_13c82798fb497861f9a3d95fb980e080191f4b_0baafc69

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5b383644-123a-11e7-b61c-8086f2bd4d30
Report Status: 0

 

I also have a bunch from this app, not sure what it is but will be looking into it.

3/27/2017 2:44 PM    Application Error    Faulting application name: devicecontrol.exe, version: 0.0.0.0, time stamp: 0x5309a791
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000374
Fault offset: 0x00000000000c4102
Faulting process id: 0x1f00
Faulting application start time: 0x01d2a708a043cabc
Faulting application path: C:\Program Files (x86)\Hotkey\devicecontrol.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ded27856-12fb-11e7-8044-8086f2bd4d30
3/27/2017 2:44 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: devicecontrol.exe
P2: 0.0.0.0
P3: 5309a791
P4: StackHash_4c95
P5: 6.1.7601.18247
P6: 521eaf24
P7: c0000374
P8: 00000000000c4102
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_devicecontrol.ex_2a9c9b5a4a3ef727875925a825549670b255fc_1f59d23c

Analysis symbol: 
Rechecking for solution: 0
Report Id: ded27856-12fb-11e7-8044-8086f2bd4d30
Report Status: 0
3/27/2017 2:44 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: devicecontrol.exe
P2: 0.0.0.0
P3: 5309a791
P4: StackHash_4c95
P5: 6.1.7601.18247
P6: 521eaf24
P7: c0000374
P8: 00000000000c4102
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_devicecontrol.ex_2a9c9b5a4a3ef727875925a825549670b255fc_1f59d23c

Analysis symbol: 
Rechecking for solution: 0
Report Id: ded27856-12fb-11e7-8044-8086f2bd4d30
Report Status: 4
 

But overall those are pretty much it that in there.  Nothing else seems to be having many problems.

 

Husker

[Colin Gilchrist]

Hi Husker,

I'd be happy to do some online training with you. Being that is is custom, you can ask anything you'd like, and I'll help you explore toolpath options. I'm sure I could help impart some wisdom somewhere. I've got a lot of experience with the ModuleWorks tool paths, which is what much of the 5X strategies are now based around.

For the last project I was working on, I'm not sure if there is much to be gained from that specific strategy, but I'm happy to share it. The customer basically dictated the approach, and it was stupid from the beginning. Their clamping method was a joke. Basically it was a face plate with some spikes on the A-Axis, and a Tail Stock that "pushed" the block of wood into the face plate. All the clamping forces were pushing against the stock. Even when we roughed, semi-finished, and finished, the wood itself was bowing and starting to split from the forces. I told them they needed to get some type of chuck to actually grip the part on the Rotary end, but my pleas were ignored.

The paths themselves worked great on the roughing part though. We were cutting the part 3 + 2 (again, their request), and the Inlet was "facing up" at A0.0 (like you were shooting it). We roughed at A90. and A270, using Dynamic Opti-Rough. We left 3 mm of stock, and used a 2 mm step-up. That left a pretty consistent amount of finish stock on the part, while still making good time on the machine.

For finishing, I used Hybrid for Semi-Finish, and got some good results with a combination of Waterline (set to 30-90 degrees), and Raster set to 0 - 45 degrees. There were a couple places I needed to add some additional Waterline paths (very funky stock design), but that was just to clean up a few little areas. I didn't see much point in trying to use a Rest Milling type path. Since wood cuts so quickly, my thinking was to get the part semi-finished leaving about 1mm of stock all over, then finish it with a long .375 ball endmill, as that would get the smallest radius. Frankly, the machine we were using was also very, very cheap. So I was worried about trying to blend anything on that machine.

 

[jeff]

18 hours ago, huskermcdoogle said:

 

Is the value of what BOXX sells worth it?  

 

Don't ever use those 2 words in the same sentence ever again. They are SO overpriced it's amazing people still buy their product.

Their stuff is nothing special,and they have no magic wand like they would lead you to believe.

If you're really wanting a new workstation, I highly suggest looking at the new AMD Ryzen processor. It's VERY good in multi-threaded applications. 

[jeff]

18 hours ago, huskermcdoogle said:

 

Is the value of what BOXX sells worth it?  

 

Don't ever use those 2 words in the same sentence ever again. They are SO overpriced it's amazing people still buy their product.

Their stuff is nothing special,and they have no magic wand like they would lead you to believe.

If you're really wanting a new workstation, I highly suggest looking at the new AMD Ryzen processor. It's VERY good in multi-threaded applications. 

[huskermcdoogle]

On 3/27/2017 at 8:26 PM, Colin Gilchrist said:

Hi Husker,

I'd be happy to do some online training with you. Being that is is custom, you can ask anything you'd like, and I'll help you explore toolpath options. I'm sure I could help impart some wisdom somewhere. I've got a lot of experience with the ModuleWorks tool paths, which is what much of the 5X strategies are now based around.

For the last project I was working on, I'm not sure if there is much to be gained from that specific strategy, but I'm happy to share it. The customer basically dictated the approach, and it was stupid from the beginning. Their clamping method was a joke. Basically it was a face plate with some spikes on the A-Axis, and a Tail Stock that "pushed" the block of wood into the face plate. All the clamping forces were pushing against the stock. Even when we roughed, semi-finished, and finished, the wood itself was bowing and starting to split from the forces. I told them they needed to get some type of chuck to actually grip the part on the Rotary end, but my pleas were ignored.

The paths themselves worked great on the roughing part though. We were cutting the part 3 + 2 (again, their request), and the Inlet was "facing up" at A0.0 (like you were shooting it). We roughed at A90. and A270, using Dynamic Opti-Rough. We left 3 mm of stock, and used a 2 mm step-up. That left a pretty consistent amount of finish stock on the part, while still making good time on the machine.

For finishing, I used Hybrid for Semi-Finish, and got some good results with a combination of Waterline (set to 30-90 degrees), and Raster set to 0 - 45 degrees. There were a couple places I needed to add some additional Waterline paths (very funky stock design), but that was just to clean up a few little areas. I didn't see much point in trying to use a Rest Milling type path. Since wood cuts so quickly, my thinking was to get the part semi-finished leaving about 1mm of stock all over, then finish it with a long .375 ball endmill, as that would get the smallest radius. Frankly, the machine we were using was also very, very cheap. So I was worried about trying to blend anything on that machine.

 

Colin,

I was hoping you had done some fancy dancy stuff and had a way cool machine at the customer.....  Guess I was dreaming.  I have been told how to program parts in the past, done it and hated every step along the way.  I like a box with ladders on the sides to make getting out of it a bit easier.  In the three years I have been cutting wood.  I have developed or improved upon a few different methods for cutting gun stocks.  All I can say is that my programming skills are far behind my imagination, and certainly also need brushed on up machine technology and options to get the smoothest fastest running programs possible.

The joke method of clamping is pretty much how it goes.  We do something similar on that front.  However, I prep blanks with precision drive keys and don't have to push very hard.  Repeat-ability isn't usually an issue in most types of wood.  A couple thou isn't going to hurt anyone in most situations.  If it needs to be tight, press fit in wood is easy...  Now one thing I have to say is that I don't have a clue on roughing anymore.  Just don't need to do it.  No point about 99% of the time.  I usually go straight to finish, then rest finish the tight areas, it gets sanded anyway...

I am going to send you a PM to discuss how I think you can help me training wise, and see if you think you can help me out.

I am not sure, but I have noticed that migrated gun stock files have much more trouble than un-migrated files.

Thanks,

Husker

[Matthew Hajicek - Singularity]

I was doing guitar necks in v7.  Coons patch surfaces, flowline toolpaths, and phenolic vacuum fixtures.  Toolpaths would take about half an hour to generate with the tolerance and stepover set; I had to test generate them with loose tolerances and wide stepovers.  Used a 6" long 1" diameter carbide ball and didn't have to do any roughing.

http://olsonguitars.com/the-artisan/jims-shop/the-fadal/

 

[Jayson Kramer]

I think one thing that was never asked what is the current system what Processor ,ram video and so on. your stuff may be outdated and really the best move it to move to a new system.

 

[huskermcdoogle]

My signature hardware is up to date.

[jeff]

On 3/27/2017 at 1:38 PM, Matthew Hajicek™ - Conventus said:

Those kinds of issues I would expect are software related.  You might try a clean reinstall of your OS.

Yep, this was the very first thing that came to mind reading the OP.

[Matthew Hajicek - Singularity]

If you go desktop instead of laptop you can easily get past 4GHZ, and close to 5 if you push it.  Laptop versions of CPUs are often slower for power and heat reasons.

[jeff]

On 3/27/2017 at 4:45 PM, huskermcdoogle said:

Just reinstall without formatting?  Or clean install?

You can do a "Windows Refresh" which is relatively quick and really easy. It asks you which files to keep and which ones to discard.

[SlaveCam]

On 28.3.2017 at 2:53 PM, jeff said:

Don't ever use those 2 words in the same sentence ever again. They are SO overpriced it's amazing people still buy their product.

Their stuff is nothing special,and they have no magic wand like they would lead you to believe.

If you're really wanting a new workstation, I highly suggest looking at the new AMD Ryzen processor. It's VERY good in multi-threaded applications. 

I'm deciding between i7-7700k and Ryzen 7 1700X for our new budget workstation. Programming mostly 3-axis stuff with "legacy" toolpaths such as flowline, surface parallel finish etc. Would the 7700k with its superior single core performance be a better buy than the Ryzen, which excels at multithreaded computing, but I'm not exactly sure if the toolpaths mentioned above utilize that?

[jeff]

4 minutes ago, SlaveCam said:

I'm deciding between i7-7700k and Ryzen 7 1700X for our new budget workstation. Programming mostly 3-axis stuff with "legacy" toolpaths such as flowline, surface parallel finish etc. Would the 7700k with its superior single core performance be a better buy than the Ryzen, which excels at multithreaded computing, but I'm not exactly sure if the toolpaths mentioned above utilize that?

I honestly don't know. But if you're on the fence about AMD, you might want to wait until their "ThreadRipper" cpu's launch in August. They will be should be a lot better for multi threading applications.

http://www.pcworld.com/article/3197184/components-processors/amd-ryzen-threadripper-prices-specs-release-date-and-more.html

https://www.extremetech.com/computing/252362-amd-announces-threadripper-launch-window-speeds-prices-details-upcoming-ryzen-3

If I didn't just get a new computer a year ago for Mastercam, I'd definitely buy an AMD ThreadRipper build.