- #FLEXISIGN PRO 10 KEEPS CRASHING HOW TO#
- #FLEXISIGN PRO 10 KEEPS CRASHING INSTALL#
- #FLEXISIGN PRO 10 KEEPS CRASHING DRIVERS#
#FLEXISIGN PRO 10 KEEPS CRASHING HOW TO#
It shows how to point to a plug-in folder. This is a tutorial from the makers of Flexisign.
#FLEXISIGN PRO 10 KEEPS CRASHING INSTALL#
Use the custom install option to send the plug-in to that folder. Make an new folder here called "32-bit Plug-ins".You can put this anywhere and call it anything but this path and name work well.Installer Create a folder where the plug-in will go. How long do we need to wait until its fixed From the event viewer: Faulting application name: GoPro Webcam.exe, version: 1.2.0.738, time stamp: 0圆13bb461 Faulting module name: ucrtbase.dll, version: 1. Use this installer link, it has the 32-bit support required for FlexiSign.Įye Candy 7. Webcam software doesnt work for me either. Once you’ve done that, you can point Flexisign to that folder. Because of this you’ll need to create a special 32-bit folder to install Eye Candy to. Installation for other sign programs will be similar.įlexisign is a 32-bit program, and many newer versions of Photoshop are 64-bit only. I have disabled the Virtual Adapter: Hardware Acceleration as other VMs have that disabled in the environment.Eye Candy 7 isn't officially supported with Flexisign, but we've got plenty of customers using it. Not sure how to troubleshoot potential RAM or overclocking issues with a VM as opposed to a thick client. With this being a VM is it possible for RAM to be faulty? If their are faulty ram sticks that are used by the pool of VMs currently setup wouldn't all machines be affected? Many of the forum posts I have read point to a faulty memory issue or CPU overclocking. Reviewed the event log for any specific applications that may have caused the crash but unable to locate anything obvious. Ran all built in Windows 10 troubleshooting diagnostics for Hardware and Devices, Windows Updates, DriversĤ. I was interested in the temps seen in MacOS for comparison if there is an underlying cooling issue in the hardware that is something else you can do to help the situation. Capping the fps ought to help until the bug is fixed. However the dmp file indicates DRIVER_CORRUPTED_EXPOOLģ. The fact you crash in 10-20 minutes is typical of overheating problems.
#FLEXISIGN PRO 10 KEEPS CRASHING DRIVERS#
Verified no obvious issues with Device Drivers in Device Manager/Ran driver verifier utility built into Windows 10 and found no errors. I checked the Mini Dump file using the BSODīug Check String : DRIVER_CORRUPTED_EXPOOL On the new VM the user is still experiencing crashes - In the Event Log I don't see any obvious application crashes causing the issue. A totally new VM was builtįor the user - new ISO file, new version of Office - a complete fresh rebuild. Their where issues with it constantly crashing and receiving BSOD. Issues are only isolated to this particular user. It is a Hyper-V VM and the one created mirrors all other users VMs. I have a user who accesses a VM via a VDI.