[fharris@technavac.com.au]

SIW technician hangs on my Win 10 (build 10061).

[gtopala]

SIW technician hangs on my Win 10 (build 10061).

Please follow instructions from http://www.gtopala.com/forum/Thread-What...lue-screen

[fharris@technavac.com.au]

1. Check if you have the latest version of SIW (Help --> Check for Updates)
   
2. Add siw.exe to your antivirus exclusion list.
   
3. Run the DEBUG version of SIW. It automatically creates few C:\siw_debug*.* files. Please send us the C:\siw_debug*.txt files.
   
4. Check if you have the latest drivers and BIOS
   
5. Use Driver Verifier to identify issues with Windows drivers
   
6. 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.
   
7. Run DXDiag, select “Save All Information” and send us the result.
   
8. 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

[gtopala]

1. Check if you have the latest version of SIW (Help --> Check for Updates)
   
2. Add siw.exe to your antivirus exclusion list.
   
3. Run the DEBUG version of SIW. It automatically creates few C:\siw_debug*.* files. Please send us the C:\siw_debug*.txt files.
   
4. Check if you have the latest drivers and BIOS
   
5. Use Driver Verifier to identify issues with Windows drivers
   
6. 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.
   
7. Run DXDiag, select “Save All Information” and send us the result.
   
8. 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

I will investigate.

[fharris@technavac.com.au]

Hi Gabriel,

my apologies for this confusion, I have been distracted by grand-children.

After further tests there seems to be inconsistency as to when the problem occurs. With UseProcessor and UseACPI both on (and the rest off), there will be a hang most of the time, but not every time. Different combinations of settings seem to have an affect.

My test involves starting the program and clicking the first ten items in the Hardware section. Failure, when it occurs, is generally after the third or fourth item; at this point, the program is stalled and After a few clicks in Windows, Windows also stalls; I have to manually kill the power and reboot.