How do I fix this Code 39 driver issue?

I'm using Windows 10 22h2

On a Lenovo Yoga 510 14ast (x64 based AMD processor).

About 3 months ago, I got hit with a blue screen error while trying to boot windows. This is after the system tried to repair drive errors (which came out of nowhere , everything was working fine before, save for a crash or two).

So I was stuck on the blue screen, trying anything to get the system to boot, and nothing actually worked, except for a system image.

That worked, but several drivers in device manager were corrupted and needed reinstalling (touch screen, sound drivers, usb mouse, Xbox controller, bios, wifi, Bluetooth and a few others I can't recall).

Went to the Lenovo website and got different driver software and I successfully reinstalled just about everything that matters except the touchscreen one and the usb mouse, and Xbox controller ones.

I can live without the touchscreen but the controller and mouse are ones I really need to fix.

For the mouse, in device manager it's listed as a USB input device under HID devices, all drivers under HID devices have a yellow exclamation symbol next to them, including the mouse driver.

The mouse works, just not on my laptop.

The Xbox controller I have does the same thing in device manager but it's listed under Xbox peripherals, with that yellow exclamation symbol.

I've tried installing the drivers by manually chooing inf files for both devices, and windows recognizes the drivers, but gives me this error whenever I try to install them through the device manager

"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing (Code 39).

{Bad File}

The attributes of the specified mapping file for a section of memory cannot be read"

I've tried allot to fix this error.

I tried updating windows twice,

I've tried using SFC, which eventually worked, but the drivers weren't repaired.

I've tried DISM to repair the image a bunch of different ways;

Online using Windows Update as a source.

Using a Windows setup ISO as a source,

Using a Windows WIM file as a source,

Using a Windows ESD file as a source,

Extracted files from the WIM file and mounted the files, then used those as a source,

Used the Repair image command in PowerShell, the same as I listed above.

Nothing worked to repair the drivers.

I tried looking for ways to install the drivers through third party driver software, and that didn't work either.

It's not a hardware issue, that I'm sure of. The mapping file issue is still persistent, all I'm left with is to try and reinstall windows, which i can't do since I doubt have anywhere to backup up my files, what can I do here if anyone knows anything.

BSOD - Posting Instructions

dalchina said:

Hi,

Have you checked your disks? All of them? E.g. Crystal Diskinfo, Hard Disk Sentinel (better- covers SSDs too). Result immediately on GUI. This sounds too much like potential disk failure.

Please complete system specs.....tutorial available in the searchable Tutorials section. Include your disk(s) - click My Computers below my post for an example.


No backups? You said you had a system image.

Strongly recommend you look for a large enough external disk and start using 3rd party disk imaging regularly. Endlessly recommended here- just search the forum for
disk imaging

I used both the apps you suggested both say my drive is in good condition, I re ran tests and the same result came up.

Thanks for the tip about specs, I've updated mine same as your example.

Also the backup I used was a restore point, that's when got windows to then boot into the OS, sorry I didn't make that clear.

- - - Updated - - -

bro67 said:

BSOD - Posting Instructions

I followed the tutorial, thanks for the tip, I haven't figured out how to edit my post yet so here's the zip file link

ZAIDEN-SHEEZUS-(2024-01-06_20-06-53).zip - Google Drive

dalchina said:

Thanks. As you used a restore point, what you report

is really puzzling, suggesting substantial random corruption.

As you've not been using disk imaging (which could well have rapidly let you get your PC back to 'as it was'), then unless the report you've uploaded provides more, I'd suggest you
- run chkdsk c: /scan from an admin command prompt (result right on the screen - scroll to end).
- if ok, then try an in-place upgrade repair install which like any 'upgrade' keeps all progs, data and most settings - tutorial available.

But wait until one of the BSOD experts inspects your report.

Okay I found the issue, it was in the registry, they keys attached to my controller, USB devices and touchscreen all were affected by a dysfunctional lower filter value called "steamxbox", I deleted the values (after creating a restore point), and its worked, all my devices work now.

Thank you for the tips though, I'll hold into them and keep my drives healthy.

Please run tuneup plus > post a share link

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging


2) Move the page file from D: to C: during the troubleshooting > then reboot


3) Run: Sea Tools Long Generic test > post a share link

https://www.seagate.com/content/dam/...sInstaller.exe

https://www.seagate.com/content/dam/...00869623_B.pdf



4) Run HD Tune: (free or trial) > post a share link
HD Tune website
a) Health
b) Benchmark
c) Full error scan

Code:

Event[226]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2023-12-08T11:23:18.8690000Z
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: ZAIDEN-SHEEZUS
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: C:, DeviceName: \Device\HarddiskVolume3.

           Failure status: STATUS_DEVICE_NOT_CONNECTED

           Device GUID: {df29db6c-e22c-8839-5c90-5763e60a4590}
           Device manufacturer: 
           Device model: WDC WD10SPCX-24HWST1
           Device revision: 02.01A02
           Device serial number:      WD-WX11A86A78CT
           Bus type: SATA

           Adapter serial number:

Code:

Event[6765]:
  Log Name: System
  Source: disk
  Date: 2024-01-06T15:46:23.7480000Z
  Event ID: 15
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ZAIDEN-SHEEZUS
  Description: 
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Event[6766]:
  Log Name: System
  Source: disk
  Date: 2024-01-06T15:46:23.7480000Z
  Event ID: 15
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ZAIDEN-SHEEZUS
  Description: 
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Event[6767]:
  Log Name: System
  Source: disk
  Date: 2024-01-06T15:46:23.7480000Z
  Event ID: 15
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ZAIDEN-SHEEZUS
  Description: 
The device, \Device\Harddisk0\DR0, is not ready for access yet.