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

0 Members and 1 Guest are viewing this topic.

Offline beammeupscotty

  • Jr. Member
  • **
  • Posts: 33
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: 23
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: 33
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.