Receiving a "Blue Screen of Death" after updating the PSoC Programmer to 3.24.2

[Len_CONSULTRON]

I recently upgraded my PSoC Programmer 3.24.2.  I started very consistently receiving the "Blue Screen of Death" when using the CY8CKIT-059.

After constructing a DoE here is the summary of the results:  

CY8CKIT-059   Plugged in …		Power Mode Change	"Blue Screen of   death"
after Sign in	before   Power Mode Change
no	no	Sign off	no
yes	no	Sign off	no
yes	yes	Sign off	no
no	no	Log off	no
yes	no	Log off	no
yes	yes	Log off	no
no	no	lock	no
yes	no	lock	no
yes	yes	lock	no
no	no	shutdown	no
yes	no	shutdown	no
yes	yes	shutdown	no
no	no	restart	no
yes	no	restart	no
yes	yes	restart	no
no	no	sleep	no
yes	no	sleep	no
yes	yes	sleep	YES
no	no	hibernate	no
yes	no	hibernate	no
yes	yes	hibernate	YES

[Len_CONSULTRON]

Here is the specifics of my system:

SW   

Win 7 Pro Service Pack 1 

Memory 16.0G 

KitProg USB-UART  CYPRESS 2.0.0.0

KitProg (1.2.3.3)  CYPRESS 1.2.3.3

PSoC Programmer  CYPRESS 3.24.2

PSoC Creator  CYPRESS 4.2  (not running in this DoE)

HW   

i7-4910MQ Octal-core Intel

CY8CKIT-059  CYPRESS Rev  B 1808SO15674

Further DoE shows that disabling the KitProg USB-UART driver, "fixes" the "Blue Screen" issue.

CY8CKIT-059   Driver…		Power Mode Change	"Blue Screen of   death"
Name	Enabled
KitProg USB-UART	yes	Sleep or Hibernate	YES
KitProg USB-UART	no	Sleep or Hibernate	no
KitProg (1.2.3.3)	yes	Sleep or Hibernate	YES
KitProg (1.2.3.3)	no	Sleep or Hibernate	YES

[Len_CONSULTRON · Accepted solution]

Here's an update:

I moved my CY8CKIT-059 to a Windows 10 Home system.

SW   

Win 10 Home  Version: 1803 OS build: 17134.285

Memory 4.0G 

KitProg USB-UART  CYPRESS 2.0.0.0

KitProg (1.2.3.3)  CYPRESS 1.2.3.3

PSoC Programmer  CYPRESS 3.24.2

PSoC Creator  CYPRESS 4.2  (not running in this DoE)

HW   

Intel Celeron 1017U @ 1.60GHz

CY8CKIT-059  CYPRESS Rev  B 1808SO15674

There appears to have NO issue of "Blue Screen" in any Power Mode change.

Len

[DheerajK_81]

I tried to reproduce your issue in Windows 10 and it doesn't occur. Must be some issue with Windows 7 Pro. Will try to test it. Glad that your issue has been resolved. Will update if I'm able to reproduce your error on Windows 7.

Regards,

Dheeraj