Mystery of the "sometimes" driver (sometimes works, sometimes not)..?

Page 1 of 2 12 LastLast

  1. Posts : 80
    10
       #1

    Mystery of the "sometimes" driver (sometimes works, sometimes not)..?


    I have this old-ish Midi interface.
    The last driver was a windows 8 driver. So, I restart in unsigned driver mode and browse manually to the driver. I made alterations in the .INF file so Win10 would be happier.
    Win10 loads it up but complains. So a bit sad I do a normal reboot. To my surprise, the driver has installed and the Device Manager shows the right name!! Great, it seems to have worked.

    Then a few days later, it goes back to "unrecognized device". So I do the same procedure again and it complains but works! Then I use it happily for a few days, even rebooting into normal mode, and it works. But after a few days it goes off again!

    This is really weird. Any advice?
    (1st image - not working) (2nd image - it works!)
    Attached Thumbnails Attached Thumbnails Mystery of the "sometimes" driver (sometimes works, sometimes not)..?-um1error.jpg   Mystery of the "sometimes" driver (sometimes works, sometimes not)..?-um1works.jpg  
      My Computer

  2. dalchina's Avatar
    Posts : 29,869
    Win 10 Pro (1903)
       #2

    If Windows finds a driver version different to what it expects, it will typically replace it. If you need to use a version different to that because of hardware compatibility, you need to protect the driver you have installed by preventing its update.

    The tutorial section here can help you there- it's free to browse and search.Windows 10 Tutorial Index Windows 10 Tutorials

    Windows 10 Tutorial Index Windows 10 Tutorials
    Windows 10 Tutorials
      My Computers


  3. Posts : 80
    10
    Thread Starter
       #3

    dalchina said:
    If Windows finds a driver version different to what it expects, it will typically replace it. If you need to use a version different to that because of hardware compatibility, you need to protect the driver you have installed by preventing its update.
    OK thanks, I found something in there which lets me turn off automatic driver updating when windows is updated. I hope that fixes it. Looks hopeful. We'll see.
      My Computer

  4. dalchina's Avatar
    Posts : 29,869
    Win 10 Pro (1903)
       #4

    In that tutorial (I'm guessing which one you found) there's a link here:
    Hide or Show Windows Updates in Windows 10 Windows 10 Windows Update Activation Tutorials

    You should be able to prevent the specific update, leaving others to functional normally as they should.
    Last edited by dalchina; 16 Sep 2017 at 12:32.
      My Computers


  5. Posts : 80
    10
    Thread Starter
       #5

    Actually I tried everything (above) and it worked for a few days, then the driver was knocked out again. So basically I am back to square one: a drive that works for days, then suddenly is knocked out.
      My Computer

  6. dalchina's Avatar
    Posts : 29,869
    Win 10 Pro (1903)
       #6

    Can you identify an update just before the time that occurred?
      My Computers


  7. Posts : 80
    10
    Thread Starter
       #7

    dalchina said:
    Can you identify an update just before the time that occurred?
    Thanks. I used the Get-WindowsUpdateLog powershell to give me this:


    Mode LastWriteTime Length Name---- ------------- ------ ----d----- 9/16/2017 3:23 PM SymCacheInput----------------File(s):
    C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.175236.692.2.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.180444.380.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.185115.095.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.190412.082.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.191539.327.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.213250.627.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170911.215024.786.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170912.073110.099.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170912.180544.683.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20170912.180544.683.2.etl0.00%16.16%32.32%48.48%64.65%80 .81%96.97%100.00%

    However, the driver was knocked out today sometime (16th Sept). It was working fine this AM, then lunchtime, it stopped working. Is there another way to see what happend to my computer at lunchtime. I gather from the above that the last update was 2017-09-12 , ie. a few days ago.
      My Computer


  8. Posts : 80
    10
    Thread Starter
       #8

    And then in the control panel:
    Mystery of the "sometimes" driver (sometimes works, sometimes not)..?-image.png
      My Computer

  9. dalchina's Avatar
    Posts : 29,869
    Win 10 Pro (1903)
       #9

    Possible ideas:
    1. Reliability History (Type Reli in Cortana search e.g.)
    Mystery of the "sometimes" driver (sometimes works, sometimes not)..?-1.jpg

    2. Command Prompt
    Driverquery
    - I'm not certain if the date listed is the installation date though

    3. Event log
    Event id 20001 is driver installation complete
    (You might need to research other possible event ids)
      My Computers


  10. Posts : 80
    10
    Thread Starter
       #10

    dalchina said:
    Possible ideas:
    Aha, I did find a Windows Defender update at 12pm, just about the time when my driver failed.
    Mystery of the "sometimes" driver (sometimes works, sometimes not)..?-image.png
    But I looked into the settings and I can't find out where I can tell Defender to leave my drivers alone...?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:09.
Find Us




Windows 10 Forums