Slic3r hangs after some of the latest Intel HD Graphics driver updates

[ZhuDaHai]

Version

1.34.0 - 64bit
Got tired of waiting for Slic3r / About screen to appear...

Operating system type + version

Windows 10 Pro Version 1607 OS Build 14393.969 64bit
Intel Core I7-3517U CPU @1.9G0Ghz - 2.40Ghz

Behavior

Takes forever (5mins+) to load while cycling 'Not Responding"
Never finishing loading a simple STL model: 192KB
Screen updates take minutes (yes, minutes)
Just trying to run it is horribly slow.
Cura, S3D operating quick and easy

[ZhuDaHai]

Windows Error Report:
Report.wer.txt

[bubnikv]

We have a similar issue reported after the last Windows 10 update. What GPU are you using? An Intel integrated GPU? It seems that the latest Windows 10 update messed up the Intel GPU drivers.

Would you please try to update a GPU driver? This helped the other customers.

[bubnikv]

FYI
http://shop.prusa3d.com/forum/print-tips-slic3r-settings-kisslicer-model-repair--f12/slic3r-not-working-sinse-last-update-t3849.html#p29121

[ZhuDaHai]

I already updated my Intel HD Graphics 4000 drivers to the latest (last) release a few days ago - before loading Slic3r.
win64_153343.4425.exe
Today I downgraded my graphics drivers, and Slic3r is working: win64_153338.exe
Seems to be a bug in Slic3r with the latest Intel HD Graphics 4000 drivers.

[bubnikv]

I have updated my Intel HD Graphics 4600 driver to the latest one provided by Intel and I have no issues whatsoever running Slic3r. I am afraid I cannot trouble shoot this driver problem, but I am leaving the issue open to collect more feedback.

[bubnikv]

By the way, I tested this issue on one of our customer's laptop and none of our older Slic3r builds ran, every Slic3r build behaved the same.

[ZhuDaHai]

Note: This is Intel HD Graphics 4000, It appears you tested 4600

[bubnikv]

I don't have HD Graphics 4000, but 4600 in my laptop, so this is what I tested. I suppose the graphics chips are similar, but you are right the bugs in the drivers may be different.

…

On Thu, Apr 6, 2017 at 8:01 AM, ZhuDaHai ***@***.***> wrote: Note: This is Intel HD Graphics *4000*, It appears you tested *4600* — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#233 (comment)>, or mute the thread </~https://github.com/notifications/unsubscribe-auth/AFj5I1jkb0W4pcxJtCiy63pCPcqvh-hoks5rtH_JgaJpZM4My3Tf> .

[bubnikv]

You may need to update the INF files for your hardware. Normally the Intel updater tool takes care of it. It scans your computer and detects all Intel hardware. It then installs the INF files for each of the Intel hardware, which informs the operating system of the particular hardware devices installed. Before the automatic Intel updater tool there was another tool, which did exactly that:

http://www.intel.com/content/www/us/en/support/detect.html

After the INF files are updated, the graphics drivers should be updated. If the 1st step is skipped, a wrong driver may be installed for your computer.

Frankly, I cannot say I understand it thoroughly, it seems like the Intel updater tool is in a need of improvement as it allows the user to skip and shuffle the installation steps, which must not be skipped or shuffled.

[bubnikv]

This thread may be interesting to you as well. It seems that an update of the INF files really helps:

http://shop.prusa3d.com/forum/software-f13/slic3r-mk2-broken-after-plater-gt-gt-dlp-projector-t3997.html

[bubnikv]

It seems we don't receive these reports anymore. Hopefully the Redmond and Santa Clara boys sat down at a table and talked the issue over, and fixed the drivers provided by the Windows 10 automatic update. Closing.