Windows 10: Fixing BSOD due to amd_xata.sys System32 driver.

Hello,


I've been getting BSOD when gaming regularly for months. I've done sfc/ scannow, used memory diagnostics and performed hardware checks on my memory and ssd but didn't find any issues.


I followed the instructions here - https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983 and identified that the System32 driver amd_xata.sys is causing these BSODs.


How do I fix this driver?


Thanks,

JD

:)

 

Frequent BSODs - L1C63x64.sys


Hi bobjbain,

Welcome to the 10forums.

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Alcohol120% and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.


Please check Qualcomm or Atheros for driver updates.
The Qualcomm Atheros network driver is old and needs updating
Code:

Code:

1: kd> lmvm L1C63x64 start             end                 module name fffff801`baca0000 fffff801`bacc2000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update links for drivers:
AMD - amd_xata and amd_sata
Check iTunes for software updates - GEARAspiWDM
Realtek - RtNdPt60
VMware software or VMWare site - vmwvusb, hcmon
Motherboard manufacturer - stwrt64 (audio)
Citrix

Old drivers
Code:

Code:

PxHlpa64	fffff801`b78f0000	fffff801`b78fb380	Fri Feb 02 22:24:22 2007 (45c3ac06)	0001320c		PxHlpa64.sys RtNdPt60	fffff801`b9550000	fffff801`b955c000	Mon Jul 20 04:27:32 2009 (4a63d614)	0000ceac		RtNdPt60.sys vmwvusb	fffff801`bae70000	fffff801`bae7f000	Sat Jul 24 04:30:08 2010 (4c4a5030)	0000ea69		vmwvusb.sys GEARAspiWDM	fffff801`bad70000	fffff801`bad76c00	Thu May 03 21:56:17 2012 (4fa2e2e1)	00008963		GEARAspiWDM.sys amd_sata	fffff801`b7770000	fffff801`b778d000	Fri Nov 30 10:00:42 2012 (50b875ba)	0001959b		amd_sata.sys amd_xata	fffff801`b7810000	fffff801`b781a000	Fri Nov 30 10:00:46 2012 (50b875be)	00010bf8		amd_xata.sys L1C63x64	fffff801`baca0000	fffff801`bacc2000	Mon Apr 01 05:15:17 2013 (5158fbc5)	000245c4	None	L1C63x64.sys hcmon	fffff801`b8ee0000	fffff801`b8ef1000	Tue Aug 06 03:10:44 2013 (52004d14)	00016f0e		hcmon.sys stwrt64	fffff801`bb000000	fffff801`bb08c000	Fri Aug 16 12:26:26 2013 (520dfe52)	0008bd1c		stwrt64.sys dnelwf64	fffff801`b8970000	fffff801`b8995000	Thu Oct 03 05:45:14 2013 (524ce84a)	00021cb3		dnelwf64.sys

AMD Overdrive driver, known for causing BSOD's.
Recommended to remove the software and driver.
Code:

Code:

AODDriver2 c:\program files\ati technologies\ati.ace\fuel\amd64\aoddriver2.sys

 

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.

 

BSOD while using the internet. error (L1C63x64.sys)


Hi trainman81,

Welcome to the 10forums.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window


AVG is trying to request data from the internet, which is why the network driver is marked as the cause.
Code:

Code:

*** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys 0: kd> lmvm L1C63x64 start             end                 module name fffff801`89700000 fffff801`89722000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

AVG drivers that have been flagged
Code:

Code:

*** WARNING: Unable to verify timestamp for avgwfpa.sys *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys *** WARNING: Unable to verify timestamp for avgfwd6a.sys *** ERROR: Module load completed but symbols could not be loaded for avgfwd6a.sys

Please uninstall AVG and see if it helps
Uninstall AVG | AVG
It is further recommended to check your Qualcomm network driver for updates, its driver is not supported for Windows 10.
Driver Reference Table - L1C63x64.sys