You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

While the BSOD/memory dump may blame a file, it's not necessarily the one that actually caused the problem.

For example, we often see ntoskrnl.exe as being at fault.

It's the core (kernel) of the OS. If that was the case, then there'd be many other problems than just the occasional BSOD.

Most likely it's another driver - usually a 3rd party driver (non-Windows) that's corrupted the memory space used by ntoskrnl.exe

In this case, the memory dumps are scattered about and don't blame any one thing in particular.

There are video, antivirus, wireless, kernel, and Phoenix Technologies SecureGuard drivers that are blamed.

Most often these random errors suggest a problem with hardware or low-level drivers.

Your UEFI/BIOS (version P09ABE) dates from 2013. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.

TrueCrypt is no longer being developed, is not secure, and is not certified as compatible w/Win10.

Finally, remove MalwareBytes - it's memory resident component may be conflicting with your Avast.Should you decide to reinstall it, DO NOT accept the default trial of the Pro version (that's the portion that resides in memory).

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. ** If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

The first thing to do would be to install a fresh copy and then uninstall it. That works in most cases.

Beyond that, there are ways to remove drivers manually, but it's risky.

Here's what to do (if you decide to try it):

1) Create a Restore Point using System Restore2) Create a Repair disc (Recovery Drive in Win8.1):Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair DiscWin 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTERWin 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).

Win 10 - Should be similar to the Win8.1 instructions.3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)4) Download this free program (http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx) and use it to disable any instances of SGdrv64.sys that are starting (or any other SecureGuard entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of SGdrv64.sys (or any other SecureGuard entries) are "Uninstalled" (DO NOT DISABLE THESE).6) Check in the Services applet (services.msc) to be sure any instances of SGdrv64.sys or any other SecureGuard entries are disabled.7)EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself). Search the registry (use regedit.exe) to locate any entries that have the driver name (SGdrv64.sys) or the program name (SecureGuard). Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1. Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this guide).8) Go to C:\Windows\System32\drivers and rename the SGdrv64.sys driver to SGdrv64.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).

In the event that the system doesn't boot:

1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename SGdrv64.BAD to SGdrv64.sys

2) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

Edited by usasma, 19 August 2015 - 07:37 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. ** If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

I tried uninstalling from the Device Manager the System Service "Secureguard driver". No problem for now, even though the file SGdrv64.sys didn't get deleted in the process. Will check if it's still active or of it's there but not used.