Several times in the last week my dual monitor setup (BENQ GW2765HT and DELL U2414H) has blacked out, flickered and then either failed to come back or left me with only one display working.
This is normally coupled with a popup error message in the system tray:
Display driver stopped responding and has recovered. Display driver NVIDIA Windows Kernel Mode Driver, Version 331.82 stopped responding and has successfully recovered.
I’m not sure why it says it has “successfully recovered” because I am unable to launch NVIDIA control panel until I’ve restarted the computer.
My display adapter is an NVIDIA NVS 310, computer is a DELL Precision T5610 running Windows 7 Pro 64-bit. Continue reading “NVIDIA: Display driver stopped responding and has recovered [maybe a FIX]”
Sage have recently ventured into the cloud storage arena with their new Sage Drive feature for Sage 50 Accounts. This constantly updates a copy of your accounts database to Sage Drive servers so that remote workers and mobile devices can access, view and edit things and syncs changes made remotely back to your main locally stored master copy.
However, they’ve had more than their fair share of teething problems with their servers being offline/down for some time. This shouldn’t cause a huge problem because your main accounts database is actually stored locally on your local computer (or server in a multi-user network setup) but it seems like Sage didn’t allow for Sage Drive failures or program a clean failover into Sage Accounts should Sage Drive be unavailable. Inevitably, when Sage Drive goes down, your Sage 50 Accounts program will freeze and become unresponsive, if you are lucky you might be present with a warning saying:
The Sage Drive Service is currently unavailable and may be unavailable for some time.
To check again to see if Sage Drive is available, click Retry.
To stop accessing your data on Sage Drive, click Disconnect.
To discard your changes and close Sage 50 Accounts, click Close.
This error message is very misleading, OK so the click to Rety is quite obvious but as long as Sage Drive is down you just end up with the same error message. You probably won’t be brave enough to try the Disconnect option nor the Close button, especially if you have been entering transactions all day into Sage along with several other team members. Instead you’ll probably do the sensible thing and pick up the phone to Sage for support (you all pay for Sage Support right!?), but since Sage Drive has gone down for all users globally, you’ll be on hold for over an hour in most cases.
So for those who have staff members twiddling their thumbs because they can’t get into Sage 50 Accounts to carry on working locally, let me reassure you that clicking Disconnect is the option you want to carry on working on your local copy of your data. This isn’t clear from the error message shown but since I had a backup of my sage from 5 mins prior to the downtime I had nothing to lose so thought I’d take the risk and try the disconnect option. Effectively what happens is you disconnect from Sage Drive and continue working on your local copy of the data (assuming you are the host for your data on your local network) and then when Sage Drive comes back online you will need to reconnnect and it will push a new copy of your entire local database to Sage Drive. It will NOT just push the most recent transactions to Sage Drive since you last connected, you would think this is logically but it doesn’t work like that. As you have disconnected, when you reconnect to Sage Drive it will have to push an entirely fresh copy of your data to Sage Drive. This might not be a problem for some with small databases, but if you have a slow connection and a huge Sage backup file it may take a while.
WARNING: If you are working remotely and accessing your accounts via Sage Drive then do not click disconnect or close, wait and wait and wait clicking retry every now and again. The above suggestions to click disconnect is only useful for those working locally with their Sage 50 accounts on a local or networked computer.
If by chance you did a Google Search for 0102100 and you are still on the phone to these muppets, hang up.
We have 30 sequential direct line telephone numbers and over the last few days we’ve been receiving calls from 0102100 to each DDI one by one. My employees said it was “Microsoft Technical Support” on the phone saying they had a virus or vulnerability on their computer and that they needed to install an easy patch/fix immediately. Thankfully all my staff are clever and spot a scam a long way off, some even suggested putting them through to our IT Department (me) which they didn’t like.
I was looking forward to them calling my DDI (I know, sad isn’t it!) so I could play along with their little charade and at the end tell them I’m on a Mac but I missed their call. Fortunately they were stupid enough to think that my voicemail was a real human and left a message which comes through to me as an email so I upload it to SoundCloud:
I was hoping to speak to them to see exactly what it was they tried to get you to install and post more detailed description here to help warn others or aid with malware removal. My guess is they send you to a URL which would be some crappy trying-to-look-like-microsoft-tech-support-domain and ask you to download an .exe which would then give them access to your machine to do as they please, perhaps cryptolocker, perhaps just a key or screen logger or just install an unnecessary PC Protection app for an annual fee.
Long story short. If you get a call from 0102100 it is FAKE, HANG UP!