Windows 10: SGdrv64.sys

How do I remove 'SGdrv64.sys' from my laptop.

I was at 75% of my windows 10 update from 1703 to 1803 when it notified me that the said file was a problem. I tried removing it from the device manager however, I wasnt able to properly locate it under system files.


I am using a Samsung Series 5 laptop. I'vre read that this issue is common for Samsung laptops but I am not really well versed with computer softwares and I'd like to ask for a step by step guide. Thank you.

:)

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (igdkmd64.sys)

Hi Nezar,

Thank you for posting on Microsoft Communities.

I will be glad to help you with the issue you have with the computer. I understand the frustration when things don't work the way it should.

What is the make and model of your computer?

File igdkmd64.sys is the Intel Graphics Kernel Mode Driver for Microsoft Windows 8.

I would suggest you to follow the steps provided below:



Step 1:

Uninstall the Device from Device Manager

• Open Device Manager
• Expand the Display Adapter section.
  
• Find the Display card Driver.
• Right click Display card Driver and select
  Uninstall.
• Select the check box delete the driver software for this device.
• Reboot the computer after uninstall process has finished.

Step 2:

Uninstall the Device Drivers from Program List in Control Panel

• Click on start, select Control Panel
• Now click on Programs and select Programs and Features.
• Find the Display card Driver.
• Right click Display card Driver and select
  Uninstall.
• Reboot the computer after the uninstall process has finished.

Hope this helps and do let us know if you need any assistance.

 

Blue Screen because of cm11264.sys

Hi,

Cm11264.sys
is a vital SYS file and it's a component of the software C-Media USB Audio Driver (WDM) developed by Windows Software Developer. Without it, it will be very difficult for your Windows system to run. Usually, cm11264.sys blue screen
errors occur when you install a new hardware or software.

For us to provide you the possible resolution and the accurate information as to why you're having the issue, answer
the following questions:

• When did the issue start?
• Where there any changes made on your computer prior to this concern?
• To make sure that we have not missed on anything, what troubleshooting steps have you done so far?

Looking forward to the requested information for us to assist you further.

 

Steelseries Merc Keyboard driver alpham164.sys disabled after windows 10 creator update why? how to undo/force it?

well I'll do the best I can to go step by step:

• Boot With Driver Signing disabled
• With Zengine installed, go to your "Saved Bettam folder"\Kernel2k\Bettam12.inf.
• Right click and select install.
• Go to your %SystemRoot%\System32\DriverStore\FileRepository\ and make sure the Bettam12_* folder is created... *being the alphanumeric hash that is generated when you install a driver.
• If this folder is created then go to regedit
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham164.sys
  • Edit the Source entry to your %SystemRoot%\System32\DriverStore\FileRepository\ bettam12_*\Bettam164.sys
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam164.sys
  • Verify it contains the same information
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham264.sys
  • Edit the Source entry to your %SystemRoot%\System32\DriverStore\FileRepository\ bettam12_*\Bettam264.sys
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam264.sys
  • Verify it contains the same information
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham164.sys
  • Edit Source to your %SystemRoot%\System32\DriverStore\FileRepository\bettam12.inf_*\Bettam164.sys
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham264.sys
  • Edit Source to your %SystemRoot%\System32\DriverStore\FileRepository\bettam12.inf_*\Bettam264.sys
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam164.sys
  • Verify it contains the same information
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam264.sys
  • Verify it contains the same information
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB in a VID Key
• If not Search for Alpham1 in that tree and change LowerFilters to Bettam1
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Alpham1
  • Change ImagePath to your "Saved Bettam Drivers\Kernel2k\Bettam164.sys" folder
• Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Bettam1
  • Verify it contains the same information
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB in a VID Key
• If not Search for Alpham1 in that tree and change LowerFilters to Bettam1
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Alpham1
  • Change ImagePath to your your "Saved Bettam Drivers\Kernel2k\Bettam164.sys" folder
• Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Bettam1
  • Verify it contains the same information
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\oem34.inf
  • Change both Default and Active to your "bettam12.inf_*" folder thats in System32
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\oem35.inf
  • Change both Default and Active to your "bettam12.inf_*" folder thats in System32
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\alpham12.inf_*
  • Change InfName to Bettam12.inf
  • Change OEMPath to your "Saved Bettam Files\Kernel2k" folder
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\alpham12.inf_amd64_932fbe5113b0010d\Configurations in a HID_Keypad entry
• If not Search for Alpham1 in that key and change LowerFilters to Bettam1
• Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\bettam12.inf_*
  • Verify it has the same information as the previous Alpham1.inf_* entry
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\bettam12.inf_*\Configurations in a HID_Keypad entry
• If not search for Alpham1 and change LowerFilters to Bettam1

If any of the Alpham entries are missing, or you previously renamed any of the Alpham keys, reinstall Zenginge from scratch and then start from the beginning of these steps.

Reboot your computer with Driver Signing Disabled again and See if Zengine is working. If Zengine is red Open Device Manager. Verify the Bettam164.ys and Bettam264.sys are listed, If they are missing and if there is no Alpham164.sys or Alpham264.sys then
begin updating drivers. Use the saved Bettam drivers in your Kernel2k path. If everything is working you can reboot normally.