enabling NSP module causes front end error Joomla 3.4

I just updated to Joomla 3.4 yesterday. I have a news group on the home page that consists of a main item (left banner) and three smaller items (I, II, III) to the right in right banner. These are all NSP5 modules. With a new article in the main position, the older items rotate (main, I II and then III)

Today I opened module Home Highlights -Right III to change the selected position of the image so it would show. When I saved it and went back to the front end, I got this error:

"1064You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DESC LIMIT 3,1' at line 21 SQL=SELECT content.id AS id FROM xxxx3_k2_items AS content WHERE content.published = 1 AND content.trash = 0 AND content.access IN (1,1) AND ( content.publish_up = '0000-00-00 00:00:00' OR content.publish_up <= '2015-03-01 22:29:11' ) AND ( content.publish_down = '0000-00-00 00:00:00' OR content.publish_down >= '2015-03-01 22:29:11' ) AND ( content.catid = 2 ) ORDER BY content. DESC LIMIT 3,1;
It appears the page you were looking for doesn't exist. Sorry about that."

If I unpublish the Home Highlights -Right III NSP module, the error disappears. This is repeatable. Just republish and the error appears again. Unpublish this module and it goes away. At present the home page shows a white space where the module should be.

Do you have an idea what might be causing this? I've never seen this before.

Hi,
about NSP we talked about this problem on forum few times since last Monday.

But in most cases :
0) Install new current version of NSP GK5
1) Open module in edit mode
2) Click Refresh button in browser
3) Change data source to another from list
4) Change order of showing items
5) Save changes - check on front page
6) If okey, change data source back to option which you have at the beginning

About Highlights module - I don't know solution yet, so please add new question on forum. Sorry. Maybe developer will see it.

Following your six-step method worked until the NSP module can be updated for 3.4.

I used this method to recover site after migration to J3.4, when NSP crashed and then worked again.