Download a fresh copy of Avast
Uninstall Avast,
Run the Avast removal tool (free from here: avast! uninstall utility )
IMMEDIATELY install and update the fresh copy of Avast
Older drivers on the system again:
AGRSM.sys Mon Nov 10 09:56:37 2008
FwLnk.sys Sun Nov 19 09:11:12 2006
rimmptsk.sys Sat Feb 24 00:42:21 2007
rimsptsk.sys Tue Jan 23 02:40:19 2007
rixdptsk.sys Wed Mar 21 09:02:02 2007
SynTP.sys Thu Aug 14 22:02:22 2008
UVCFTR_S.SYS Thu Jun 26 04:25:19 2008
It sounds like you found something important that would lead you to believe Avast is the cause? It is impossible to find any of those drivers/updated versions of those drivers. Thanks so much. Keep up the good work, you help so many people out and you don't expect anything in return.
I used to post a lot more info about what caused the errors - but the demand for help with BSOD's has grown, and we've lost a couple of members who were helping (so the workload is overwhelming at times).
As for the drivers...
- google the driver name
- compare the google results to what's installed on your system
- that should give you an idea about which device or program is involved with the error
- then remove that device/program and replace it with a new version from the manufacturer's website (not from Windows Update or the Update drivers function of Device Manager).
These 3 drivers are for your SD/Memory card reader:
rimmptsk.sys Sat Feb 24 00:42:21 2007
rimsptsk.sys Tue Jan 23 02:40:19 2007
rixdptsk.sys Wed Mar 21 09:02:02 2007
This driver is for your Synaptic touchpad:
SynTP.sys Thu Aug 14 22:02:22 2008
Synaptic has drivers (64 bit) dated Aug 28, 2009 here: Drivers | Synaptics
I did what you said and uninstalled Avast, rebooted, and reinstalled avast. It ran fine and no BSOD at wakeup untill today. It BSOD when I was actually reading these forums, but I noticed that it BSOD when Avast popped up with an update notifier. Could avast be the source of all my problems? Here is the latest minidump.
As for the Drivers, I meant that it was impossible to find any newer versions because with all the research those were the drivers I had left that I could not find newer versions of.
It's difficult to say what's the latest available driver - and finding something newer is always a pain if you can't get them from the manufacturer.
Usually it's the user who solves these things - we just poke around and make suggestions. The observation about the BSOD and the Avast update is a good one, and I'd suspect that it will turn out to be the issue.
No specific information from the dump file - so I'd have to suggest Driver Verifier (we'll deal with Avast after this):
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
I used driver verifier twice already as recommended by Microsoft. Nothing comes up. It just crashes before I can log in again and each time i've had to do system restore. I'm not using that tool again, sorry.
Here is the latest crash file. I want to ask how come it seems alot of people's dumps say what the reason it crashed yet mine don't have any idea. I wish MS would just make a system that points to the cause of the problem.
Thanks as always.
Quote