If you run into this error while trying to update your Xperia device using "Sony PC Companion", then PC companion is really having issues starting the Sony Mobile Update engine. The solution is a fairly simple one.

Here is how to get it solved:

  • Go to Programs and Features, by search "Start" for "Programs and Features".
  • Scroll to Sony PC companion and  uninstall it.
  • After uninstallation, scroll to "Sony Mobile Update Engine" and uninstall that too.
  • Optional: You can also clear out the "C:\Users\All Users\Sony\Sony PC Companion", you can delete the folder "Sony Pc Companion Folder itself".
  • Restart

Now you can redownload PC Companion from support.sonymobile.com.

NB: After installation, if you're behind proxy you must reset your proxy settings as your system settings would all have been reset.

Early today, 10th of September 2015, Xperia Z users accross Nigeria all got pop ups of a new Available system update. The update brings forth the offical Android 5.1 for users of he Xperi Z device.

Its a wonder Sony is still supporting this device, even after 2 years of its innitial release. Good job Sony.

The update is approximately 407mb and overall, improves stabilty and general performance of the O.S, List of features will be added to this post soon, just began the download of the update.

Learn of the different methods of obtaining the update here.

Enjoy men.

Barely 6 days to the release of this year's edition of the Pro Evolution Soccer series, PES 2016, published by Konami. This year's release also coincides with the 20th anniversary of the PES team. The demo released last month, has left fans anticipating the release of the game; but a question still baffles many,

Metal Gear Solid: Phantom Pain was released sometime last week and featured the Denuvo DRM security, same as Fifa 15, Dragon Age: Inquisition, Lord's of Fallen etc. Will PES 2016 adopt this same technology too.

Denuvo is an anti-tamper technology designed to slow down attacks on DRM e.g Steam. The technology has so far made life difficult for piracy of PC games, and has considerably increased the amount of time it takes for cracks / genuine security bypass of games to be released. 

With more games adopting the Denuvo technology,  Pro Evolution Soccer built using same engine as MGS: PP and published by same manufacturer may adopt this technology. Well, that's good news for the developers (more money); as more people would buy the game before it makes its way to the pirate market, and bad news for those who like to test games first before buying.

Will PES 2016 feature Denuvo?

How long will it take for it to be cracked?
The answer to these questions remains unknown, see you on the release day guys, can't wait to grab a copy :D

This error is a fairly new one, only recently surface on Windows 10; it is sometimes very similar to KERNEL_DATA_INPAGE_ERROR, have very similar symptoms. PCs on Windows 10 haven't been experiencing the KERNEL_DATA_INPAGE_ERROR but have been experiencing this, especially those that were formerly getting KERNEL_DATA_INPAGE_ERROR.

Possible Symptoms 

NB: The list of symptoms listed here are not exhaustive and are from experience only
  • Very random occurrence (hard to replicate)
  • Happens mostly when the system has either been on for hours / just recently resumed from hibernation
  • Frequency of occurrence is also random, sometimes frequent and sometimes not.
  • Most times no dump file is created as the system abruptly restarts before even the message can be read.
  • You experience "Critical Process has died" Exception once after a couple of this error
  • If the system is left for long after BSOD, it restarts but doesn't show bios logo, until forcefully shut-down and boot back up.
This and many more are experiences from this error, the problem is sometimes caused by software (especially drivers and bugs) and sometimes hardware. 

Possible Solutions

Possible Fix 1 (Windows Update):

Check for the latest update for windows; you can access this by searching for "updates" in "Start" menu and clicking "Check for updates" under the Settings group. You can also;

  • click on Start or Windows Logo on your taskbar.
  • click on Settings.
  • click on Updates and security.
  • click on Check for updates.
If any update is found, wait for Windows to complete the update and restart. 

It is also possible your system was working perfectly before a recent update screwed it up, if that's the case, update can be uninstalled by searching in "Start" menu for "programs and features" and selecting "Programs and Features" from the result; when the screen shows up, click on "View installed updates" on the left side of the screen, scroll to the suspected culprit, right click and uninstall; use the "Installed on" column to help ease your search.

Possible Fix 2 (System File Checker):

Before resorting to a clean install of Widows (which should always be the last resort IMO), run the system file checker tool (SFC). This can help replace any corrupt windows file, and can be very helpful when the exception is caused by a bad system file. To run this, 
  • click on "Start" or Windows Logo on your taskbar
  • search for CMD.
  • right-click Command Prompt from the menu and "run as administrator".
  • or Press Window + X.
  • click on Command Prompt (Admin).
After command prompt shows up, enter:

        sfc /scannow            

press enter after entering this command, wait for windows to complete it's task.

Possible Fix 3 (Checkdisk)

Another possible fix is to check your hard drive for errors, by running the disk checker utility on all Partitions. This can help remap dead sectors, which by happenstance may be the reason for the  ...STORE... exception is being caused by that.

Run Command Prompt as Administrator
  • click on "Start" or Windows Logo on your taskbar
  • search for CMD.
  • right-click Command Prompt from the menu and "run as administrator".
  • or Press Window + X.
  • click on Command Prompt (Admin).
In the prompt, enter the drive letter for your partition, the enter 
"chkdsk /f /r"
and press "enter".  Sample for Drive C below;

 chkdsk /f /r /x                                                           

The /x tries to unmount the drive, if it can't and asks you for a boot time schedule, enter "y" and restart. Wait for the scan to complete, please don;t interrupt once started.

Possible Fix 4 (Turn off Fast Startup)

A possible fix for this error is also to turn off  "Fast Start-up". Some users on the internet have reported this worked for them, Disable it by:

  • Go to Power Options
    • click on "Start" or Windows Logo on your taskbar
    • search for "Power Options"
    • right-click the battery icon 
    • select Power Options
  • Click on "Choose what the power buttons do" (located on the left side of the window)
  • Click on "Change Settings that are currently unavailable"
  • Disable "Fast Startup" and save changes.
After disabling, restart and hope for the best.

Possible Fix 5 (Drive update):

An Outdated Driver may also be the cause of this dreadful error, visit your manufacturer site and download the latest Windows 10 drivers for your device or simply download "slimdriver" or "drive the life" and search your system for drivers that need updating.

Possible Fix 6 (Antivirus)

Case 1:
You may have harmful viruses on your system interfering with normal windows operations, it is recommended you update your Antivirus  and perform "Boot-time Scan" of your system.
Case 2:
 Your Antivirus may be the original culprit of this error, for now, try uninstalling your Antivirus and use Windows 10's default Anti-virus. Try that for a week and see if the BSOD will pop up again

Possible Fix 7 (Clean install or Refresh)

If after all this, before attempting Step 8, perform a clean install of your O.S, or do a system refresh.

Possible Fix 8 (Hardware Maintenance)

At this point, I'll recommend you confirm if you are still under Warranty, 
if not!!! 
If you believe in your repair skills, I'll recommend you do the following else take it to a repair-man to help do the following:
  • simple RAM connector cleanup
  • Clean or eliminate dust from your PC fan
  • make sure all cables are plugged in tightly

Possible Fix 9 (Watch this Space)

Bless You "My Brother", the Lord is your strength....(I'll definitely update this post as soon as more solutions are discovered)

Finally Sony unveils its flagship smartphone today, Xperia Z5. This time Sony, wows everyone with the super clear display, fitting a 5.5 inch display with a 4k resolution (. Hence, earning it the title of the world's first 4k resolution screen (806 PPI). "Son, It can't get any crispier than this".

The lineup of devices feel alot fresher (and "New") than the release of the previous Xperia Z3+ (which felt so much like an improved Z3). The Xperia Z5 comes in 3 variants which are:

  •  Xperia Z5 (5.2" 1080p screen, 3GB RAM)
  •  Xperia Z5 compact (4.6" 720p screen, 2GB RAM)
  •  Xperia Z5 Premium (4k / UHD / 2160p SUPER crisp screen, 3GB RAM)

The devices really aren't so different from each other, aside from those listed above and obviously their battery size and dimensions, the Xperia Z5 family are all same; and all come equiped with the sleek power button embeded with a finger print sensor;

Other Notable features and Specs are:
  • Qualcomm Snapdragon 810 64-bit Octa Core processor. 
  • Waterproof and dust tight.
  • 32GB internal Storage expandable to 200GB.
  • Fingerprint Sensor 
  • Google Android™ 5.1 (Lollipop).
  • Rear Camera: 23 MP Sony Exmor RS™ with Hybrid Auto Focus 0.03 sec, 4k video (and 8mp still image capability while recording)
  • Front Camera: 5 MP front camera Sony

More on Xperia Z5, click here.