search

MatterHackers / MatterControl

3D printing software for Windows, Mac and Linux
http://www.mattercontrol.com/
BSD 2-Clause "Simplified" License
455 stars 183 forks source link

Unhandled exception error on opengl32.dll while loading Gcode #4155

Open Regnad517 opened 5 years ago

Regnad517 commented 5 years ago

Bug Report

Steps to Reproduce

  1. Whenever I Slice it crashes at loading Gcode
  2. I did a clean install of Windows and it printed great for 1 day. The next day I went to print and I get the exception error in the pic attached. When the error pops up, I am frozen completely unless I quit.
  3. I have not modified any of the default settings or gcode to reproduce this error. I have even done a complete scrub and reloaded MC and still crashes.

Expected Behavior

Actual Behavior

MatterControl Build Number (To find this, go to the MatterControl menu in the top left and click "About MatterControl") V2.19.1.10116 Operating System Version Win7 64bit Printer Make/Model Monoprice Maker Select V2 opengl32

Regnad517 commented 5 years ago

So I have tried it from 2 different Win7 computers and same exact results. The computer I use for this is dedicated so I can make any changes at any time. Going to try and load Win10 on it to see if the problem still persists.

Any info I can add to help resolve, feel free to ask me.

Thanks

EDIT - HAHA, So Windows 10 is even worse. I did a clean install of Windows 10, then installed MC leaving everything default. Tried to slice and when it got to gcode this time, it went to blue screen of death and rebooted. Currently formatting and starting over with Win7 to play some more. Will update as I go.

Regnad517 commented 5 years ago

Still the same, I can print fine for a day or 2, then without changing anything I get the exception error and the program is completely unusable. I have to literally format my machine and load windows every 2 days. Any help at all here?

Regnad517 commented 5 years ago

I have to say this is getting very annoying having to completely erase my machine and install Windows, MC, etc... every 2 days. And not a single response here at all. It's too bad, I love using MC and being local in Lake Forest, visiting the store but hate being ignored. I guess you can close this thread, I will give my business to someone that wants it.

larsbrubaker commented 5 years ago

I apologize that you are feeling ignored.

GitHub is not a support forum. Please contact MatterHackers support if you need support.

This site is for the developers of MatterControl. They take the issues that are reported here and then triage them into various development cycles. They do not necessarily respond to any issue, or commit to when they will be addressed.

We very much appreciate you reporting issues, but our developers are not in a position to offer individual support.

Regnad517 commented 5 years ago

Then my apologies, I guess I completely misunderstood the purpose of posting mattercontrol issues at the mattercontrol board here.

So just an FYI, after weeks of dealing with this I have found a workaround.

If I slice and choose to print while the model is in 2D mode, than all is great and I can switch back to 3d once print has started, but if I slice in 3D mode, crash. So I guess it has something to do with my video card...

Odd part is, why does it work flawlessly for roughly 2 days then decide to crash?? And no, there are no updates turned on, anti-virus, nothing changes. This machine is dedicated to my 3d Printer with all update functions disabled. and even odder, I tried it on 2 different computers. Oh well, at least I can print again.

larsbrubaker commented 5 years ago

Again, sorry for the misunderstanding and thank you for the additional information.

We will still be investigating this when we have the time. It is very useful for us for you to report these kinds of issues.

I hope to encourage you to continue to report issues. We just don't have the capability to give individual support to issues, or prioritize them above our development schedule.

compuwar commented 3 years ago

I am having the same issue running MC from an RDP session on Win10 Pro. If I switch to 2D mode, the crash does not happen.

- 1000 2 100 0x80000000000000 1647 Application printserver - MatterControl.exe 1.0.0.0 606765e7 OPENGL32.DLL 10.0.18362.387 c7cf39ed c0000005 000000000001b919 3dbc 01d7299748915167 C:\Program Files (x86)\MatterControl\MatterControl.exe C:\WINDOWS\SYSTEM32\OPENGL32.DLL 675e5db7-3d5b-40cf-80f6-7312fd842be6 - 1001 4 0 0x80000000000000 1648 Application printserver - 1370708196825226691 4 APPCRASH Not available 0 MatterControl.exe 1.0.0.0 606765e7 OPENGL32.DLL 10.0.18362.387 c7cf39ed c0000005 000000000001b919 \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B27.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAC10.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERACDC.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERACFA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD97.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MatterControl.ex_292b68746af5c2106d6f14311868debd9cd8e47_bf2b46c8_e8de56f9-54bd-4335-b5ef-0ffbfb2743e6 0 675e5db7-3d5b-40cf-80f6-7312fd842be6 268435456 a166e661d8897850e305bbd7ba7bddc3 0 - 1000 2 100 0x80000000000000 1649 Application printserver - MatterControl.exe 1.0.0.0 606765e7 OPENGL32.DLL 10.0.18362.387 c7cf39ed c000041d 000000000001b919 3dbc 01d7299748915167 C:\Program Files (x86)\MatterControl\MatterControl.exe C:\WINDOWS\SYSTEM32\OPENGL32.DLL 5d180804-5df6-4e8f-9433-a7f473c63f72
compuwar commented 3 years ago

Again, sorry for the misunderstanding and thank you for the additional information.

We will still be investigating this when we have the time. It is very useful for us for you to report these kinds of issues.

I hope to encourage you to continue to report issues. We just don't have the capability to give individual support to issues, or prioritize them above our development schedule.

Seems like two years would be an excessive time not to address a bug. What then is the preferred reporting procedure? My guess is the memory violation here affects more that this instance, and is why I couldn’t get OS X working consistently either.