04-24-2015, 04:18 AM
SIW technician hangs on my Win 10 (build 10061).
(04-24-2015, 04:18 AM)[email protected] Wrote: SIW technician hangs on my Win 10 (build 10061).
(12-22-2011, 12:03 AM)gtopala Wrote:
- Check if you have the latest version of SIW (Help --> Check for Updates)
- Add siw.exe to your antivirus exclusion list.
- Run the DEBUG version of SIW. It automatically creates few C:\siw_debug*.* files. Please send us the C:\siw_debug*.txt files.
- Check if you have the latest drivers and BIOS
- Use Driver Verifier to identify issues with Windows drivers
- Save this file (siw.ini) in same directory with siw.exe, then run SIW again.
If it works, edit siw.ini, and replace "=0" with "=1", one by one (siw.ini should have only one "=1"), until the problem occurs again.
Then send an email mentioning which "1" is responsible.
- Run DXDiag, select “Save All Information” and send us the result.
- Run CPU-Z, select "About", "Save Report(.TXT)" and send us the result.
(04-25-2015, 12:17 AM)[email protected] Wrote:I will investigate.(12-22-2011, 12:03 AM)gtopala Wrote:
- Check if you have the latest version of SIW (Help --> Check for Updates)
- Add siw.exe to your antivirus exclusion list.
- Run the DEBUG version of SIW. It automatically creates few C:\siw_debug*.* files. Please send us the C:\siw_debug*.txt files.
- Check if you have the latest drivers and BIOS
- Use Driver Verifier to identify issues with Windows drivers
- Save this file (siw.ini) in same directory with siw.exe, then run SIW again.
If it works, edit siw.ini, and replace "=0" with "=1", one by one (siw.ini should have only one "=1"), until the problem occurs again.
Then send an email mentioning which "1" is responsible.
- Run DXDiag, select “Save All Information” and send us the result.
- Run CPU-Z, select "About", "Save Report(.TXT)" and send us the result.
The problem seems to occur when CheckVM = 1, and also when ConfigServerSafe = 1. SIW hangs, but so does Windows 10. I am using V5.1.0312b. The requested files are attached.
Update to my last post. the "UseProcessor = 1" is also causing problems.
Hi Gabriel,
More information for debugging. In my initial tests I turned on each parameter (set to 1) and left the parameter on if it didn't cause any problems. In this way I determined there were problems with CheckVM, UseProcessor and ConfigServerSafe.
However, with each of the above three parameters, if I turn them on individually with all other parameters turned off, there is no problem.
Cheers