You've given us very little context here - we don't know what scope you're using, we don't know what has changed since things were working correctly, how long ago things were working correctly, etc. Have you always been using the rotator? If so, have you routinely been changing the rotator position when you slew to a new location? Your use of 'Resist Switch' for guiding in RA makes no sense at all, you need to put that back to 'Hysteresis' until you get your problems sorted out. So we can't do much with what you've sent us. I am suspicious that your rotator may need to have it's angle position reversed but I can't tell. To eliminate that as a source of the problem, you have three choices:
1. Don't connect to the rotator temporarily and see if guiding works like you expect at various positions in the sky
2. Go ahead and keep the rotator connected but do a fresh PHD2 calibration and don't move the rotator as you run test guiding sessions in various parts of the sky
3. Follow the procedure for determining how to configure your rotator property for 'Reverse Angle'
That calibration procedure is described in the User Guide:
If you don't follow this procedure, you will just end up running in circles and wasting time.
The other thing I noticed is that your problems started when you slewed to a northern declination of 61 degrees. You should also make sure you don't have cabling problems at that pointing position that interfere with the smooth movement of both axes in all 4 directions.
Good luck,
Bruce