Author Topic: Feature Request or is there already a human readable log?  (Read 3189 times)

0 Members and 1 Guest are viewing this topic.

Offline beammeupscotty

  • Jr. Member
  • **
  • Posts: 36
Feature Request or is there already a human readable log?
« on: September 03, 2023, 02:16:23 AM »
For a couple of weeks I've been experiencing a BSOD event on a daily basis. I've isolated the issue and the date of its first occurrence using Windows Event Viewer to
0x0000009f (0x0000000000000003, 0xffffbd055b0b8cf0, 0xffffce08cc48f750, 0xffffbd055ac05b50)  Apparently this indicates a driver issue.

I would like a report/log that can be generated from the GUI that lists the driver updates by date so that I can quickly find and rollback the offending driver(s) installed on the date before the first BSOD event.   

Thanks in advance for your assistance.

Offline _Uli_

  • Avast team
  • Jr. Member
  • *
  • Posts: 28
Re: Feature Request or is there already a human readable log?
« Reply #1 on: September 04, 2023, 07:34:39 AM »
Hi,
I am really sorry for all troubles associated with usage of our product. This is not intentional behavior.

In order to be able to help you I would like to ask you to send us your log files executing our Support Tool utility.
The support tool is available under c:\Program Files\Avast\Driver Updater\

Please run the “SupportTool.exe” and follow the instructions. Once it is done, please send me the file here via private message.

Thank you.
-Uli

Offline beammeupscotty

  • Jr. Member
  • **
  • Posts: 36
Re: Feature Request or is there already a human readable log?
« Reply #2 on: September 09, 2023, 02:55:10 AM »
Hi Uli,

Thanks for your reply. The issue was not directly caused by the Avast Driver Updater. It may have updated the driver that caused the issue, but there is nothing to fix from your end so there is no point in sending log files. 

The issue for me is that I have to do three clicks on each driver (one at a time) to find the install date. There are a lot of them and it's counter productive to do it one at a time when the technology exists  to automate the search process.  If I could run a report to screen I could quickly identify the date of the rogue driver and roll it back to an earlier version that doesn't cause a BSOD. .

This is a request for a new feature not for support on a specific issue.

Thanks in advance for your help.

Offline beammeupscotty

  • Jr. Member
  • **
  • Posts: 36
Re: Feature Request or is there already a human readable log?
« Reply #3 on: October 03, 2023, 04:56:27 AM »
Is anyone there who can assist with this? I would welcome a response.

I ran Avast Smart Scan today and it identified 21 drivers requiring an update.

I am loathe to do the updates because if I get a BSOD again I have spend too much time looking for the the driver that caused the issue. Providing a report to screen is not a difficult task.

I have not re-installed Avast Driver Updater since the BSOD  issue because I  fear the same issue occurring again and am unlikely to renew my subscription until I have confidence that I'm not going to end up in the same situation - having to spend hours going through all the updates one by one to find the problem driver.

So far your only communication with me has been to ask for a log file which completely misunderstands my original request.


Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48539
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Feature Request or is there already a human readable log?
« Reply #4 on: October 03, 2023, 03:13:06 PM »
Why not create a restore point, Do the updates for all drivers except the one that gave you the problem.
If that works, create another restore point and update the problem driver.
If it works great if there's a problem, just go back to the restore point.
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline beammeupscotty

  • Jr. Member
  • **
  • Posts: 36
Re: Feature Request or is there already a human readable log?
« Reply #5 on: October 04, 2023, 12:44:46 AM »
Hi  bob3160,
Thanks for your reply. I have already done a clean install of windows.

You wrote  "Do the updates for all drivers except the one that gave you the problem."

The issue is finding the one that gave me the problem quickly. Running a report to screen of all updates by date would enable me to isolate the offending driver(s). At the moment, as I said in my initial post, I have to drill down to find the install date.

This post is for a feature request.

Offline _Uli_

  • Avast team
  • Jr. Member
  • *
  • Posts: 28
Re: Feature Request or is there already a human readable log?
« Reply #6 on: October 12, 2023, 07:39:51 AM »
Hi, please excuse my late reply. Normally I will be informed about new messages in a thread, but that doesn't seem to have worked in your case. I am sorry!

To your question: That's why I wanted to get log files. :) And beside of this, our software already shows all the drivers installed so far. It is therefore counterproductive to uninstall the software directly. Then we can no longer help.

Offline beammeupscotty

  • Jr. Member
  • **
  • Posts: 36
Re: Feature Request or is there already a human readable log?
« Reply #7 on: November 07, 2023, 02:12:41 AM »
i give up! I will not be renewing my subscription. Does anyone actually read my requests. The issue is not knowing what drivers are installed its knowing quickly what driver was installed when,  so that I can isolate the offending driver and roll it back. in other words listing them by install date. I have spent years working with software developers and this is a simple report to screen. Why can't you do that? Your log files do not show windows errors so they can't identify the driver that is generating the error.