The initial message said something like 'cocoa -1'. I am currently waiting for my most recent backup to install fully so I can't answer your questions exactly at the moment until the restore is complete. In my efforts to try to see if earlier backups had the actual photos rather than blanks, I restored earlier versions of my backup including back to Catalina (I am using Big Sur now). It is only these batches of photos from nearly 10 years ago. I don't have problems loading photos currently. but am not 100% sure about that (as I can't see the photos.). I thought initially that they may have been photos that I had scanned from slides or printed photos. I think they all have the label CIMGxxxx.jpg (where the x's are numbers.). They were definitely not blank until many years after that. The blank 'photos' in question were largely loaded in early 2012, but there were a few prior to that, in 2011. I have had this large Photos library for many years, and add to it progressively from a camera card or my iPhone. And I am assuming that the drivers for the other parts of the USB connection are similarly affected, but have not tried it yet. So I am really trying to find out why this one (2 applications of the same driver - presumably because there are USB2 and USB3 ports in the PC) did not work (installed, and then crashed the machine). Having resolved the grief and identified which driver was causing the grief, and recovered again, the question was why (this post)?ĭriver updates are issued for reason. Caused lots of re-boot grief when originally tried as part of a batch, as I indicated in the safe mode start query I referenced. So I did expect that the update was both current (or least, the most current one there was) and would work. And the update driver announced is dated 2010, also in a driver booster image in the original post. The original driver for the laptop is dated 2006 - see the driver properties picture in the original post. Yes, I understand the timing and circumstances. Vista and windows 7Īny ideas why this (driver update failure) is happening? This is a screen shot of the restored (working) driver details, which appear to be the original Microsoft items for XP3. It worked, and the restored "extremely old" drivers are again working without any error boxes, whereas the newer ones were not. Considering that the originals had been working for years without apparent issues, I began a restore process. When the install was completed a windows message box reported a windows failure for one of the devices (which one, not stated or even referenced by a number). I chose only these 2 PCI- drivers for update (unticked the selection boxes for all the others in the booster list), and proceeded. Of the 6 USB drivers to be updated, I picked these 2 items to update first because 1) they looked to be the oldest (the replacements were dated in 2010), and 2) as I understand the technology, these bits connect the processor bus to the actual host and hub chips. See this screen shot of the Device Manager list: There are 6 USB-related drivers in this extremely old/aged list and clearly they relate to the number of installed hardware items on the laptop. In the following image, the 2 PCI-to-USB host drivers caused a windows failure message after the update. After 7 one-by-one driver updates, I found the (or, at least) one causing the problem. This topic is a follow-up to my query on this thread, regarding safe mode start/restoring after a failed driver update:Īnd as i reported there I begam doing a one by one update to locate what caused the original problem with the bulk update. Last time I can recall doing this was nearly 2 years ago. I have been doing a periodic update of the system drivers on the laptop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |