Closed sarf2k4 closed 5 years ago
Is it reproducible with the current 1.42.0-alpha3? Sorry, we are not going to fix the current release, we are working full steam on 1.42.
Hi, I turned on all other settings previously to match my 1.41.0 especially background processing. I did try the above method that led me to BSOD along with playing with other stuffs like adding custom support enforcer that also quite resource intensive that led youtube fps dropped. Unfortunately there are no BSOD occurrence as of yet. Unsure about the future
Unfortunately there are no BSOD occurrence as of yet.
It is my hope that these crashes due to the background processing are cured in 1.42.
I think I know what caused the BSOD. It may have to do with the latest gpu driver and I did read that there are few people who had bsods with the latest nvidia 417.17 driver. Today I had about 3 bsods unrelated to slic3rpe, those are all due from playing games which was from unity engine.
I'm sorry to raise a false alarm about slic3rpe causing bsod. As of now, I am using an older driver version that is hopefully no bsod occurs. Therefore, I'm closing this issue down
Version
slic3rpe 1.41.2
Operating system type + version
windows 10 64 bit
System Info
Behavior
I sliced this thing https://www.myminifactory.com/object/3d-print-jabba-the-hutt-2559, oriented to face the front of the printer platform, exported the gcode. Slic3r wasn't responding, I clicked X then picked close the program. I have a youtube streaming during the process and I use dual screen setup. I use firefox 64.0.2 64bit version. After clicking "close the program", I got struck with blue screen of death with POWER_DRIVER_STATE_FAILURE. If I remember correctly, this isn't the first time ever happened. almost exact same scenario led me to have a BSOD about 2 weeks ago.
STL/Config (.ZIP) where problem occurs
The file I tried to slice https://www.myminifactory.com/object/3d-print-jabba-the-hutt-2559
P.S I tried to replicate the steps that led me to BSOD earlier, I couldn't produce the problem. Problem might lies at slic3r usage for gpu processing where it binds itself to a process then a deadlock occur. Force closing it led to a state hanging and unrecoverable error which is BSOD. I wonder if the slic3r dev team able to check on this problem?