Hi, I have been away for the weekend. I am currently investigating the rdyboost.sys. I don't know about this program and if it is there it is not by my intention. Will get back to you as I have finished. At present it is quite a challenge to work on my computer as I am getting a BSOD on average every 5 min
Here follows my investigations i.r.o. of rdyboost.sys on my computer.
According to the site that you pointed me to (rdyboost.sys Windows process - What is it?) rdyboost.sys is a windows core system file which can be found in C:\Windows\System32\drivers folder and the file size should be 173 440 bytes or 173648 bytes in size.
I checked in the C:\Windows\System32\drivers folder and found a file named rdyboost.sys but the size did not correspond to the above info. According to the properties dialog the file size is 215 094 bytes and size on disk 217 088 bytes. The file version is 10.0.14393 dd 16 Jul 2016. I don’t know whether this would indicate a corrupt driver file. The link on the above site pointing to a test of rdyboost.sys was flagged for virus activity by my AVAST virus program so I didn’t go there. Another site who claimed to test if your drivers are up to date was flagged by Malware antibytes as being a PUP. I could also not find another rdyboost.sys file on the net. As my win 10 was upgraded with Microsofts upgrade option via the internet I also don’t have a DVD disk from which I can run a repair and also as I have said I’m not sure that the driver is corrupt in the first place.
In answer to the question whether I am using rdyboost.sys with an external usb drive? No, I haven’t used one since before the BSOD plague started.
To determine whether it was running as a service on my computer I checked in the task manager under services but could not find a service named readyboot or alternatively superfetch.
On one of the sites that Google pointed me to (unfortunately it got lost with the many BSODs so I can’t supply a link to it) I got the following instructions on how to turn off the rdyboost.sys process. Insert usb flash drive, right click on it and select properties. Then go to the rdyboost tab where there will be three options:
1) turn rdyboost off
2) use entire drive for rdyboost or
3) use a specified amount of drive space for rdyboost
I followed the above instructions and found the rdyboot option was marked as turned off. As I have said before I was not aware of the rdyboost option so it is unlikely that I would have activated it. As far as I could determine as described above it is not active.
Should I try to run the DM_Log.exe program again?
The frequency of the BSODs have become such (on average between 2 and 5 min, with an occasional run of about 10 to 15 min and even a BSOD halfway through a boot sequence) that it is fast becoming almost impossible to do anything constructive with my computer. I hope you can still help me. Thanks again for your help and patience with me. J I really appreciate it.
Run DM_Log_collector again, just to make sure the latest is uploaded here.
Edit: Mine is: 07/16/2016 06:42 AM 267,104 rdyboost.sys
Here are the latest dmlog files
created with the Bat file
And here are the files creared by the DM_log exe program
Latest dump has this:
The first two are Microsoft driver files and unlikely to cause a BSOD. The last one, l260x86.sys may be a problem. It belongs to Atheros L2 Fast Ethernet Controller ndis miniport driver. It is old, with a date of 17-Mar-09. If you are still using this device, see if there is an updated driver for it.Code:BugCheck D1, {9230ca06, 2, 0, a30c1ffe} *** WARNING: Unable to verify timestamp for rspndr.sys *** ERROR: Module load completed but symbols could not be loaded for rspndr.sys *** WARNING: Unable to verify timestamp for wfplwfs.sys *** ERROR: Module load completed but symbols could not be loaded for wfplwfs.sys *** WARNING: Unable to verify timestamp for l260x86.sys *** ERROR: Module load completed but symbols could not be loaded for l260x86.sys Probably caused by : rspndr.sys ( rspndr+1ffe )
Thanks. I will get the updated driver and report back on how it went.
I downloaded a l260x86.sys file from l260x86.sys free download - Sysfiledown.com and copied it to the directory C:\windows\system32\drivers. The BSOD's are still happening however.
Attached are the latest log file dd 1 Dec 2016
You need to install a new, uplevel driver, not just the one .sys file.
If the Atheros LAN is an onboard device, can you borrow a PCI LAN card to install and try? Disable the onboard if you do.
Quote