Author Topic: Boot Scan  (Read 5444 times)

0 Members and 1 Guest are viewing this topic.

AvastUser015

  • Guest
Boot Scan
« on: December 04, 2013, 09:13:37 PM »
I just did a Boot Scan for the first time and discovered these errors.

File C:\Windows\System32\DriverStore\FileRepository\prncacla.inf_amd64_9b92c72816d21e9\Amd64\CNBJ2530.DPB|>_5_Kolt50vpJyqlets20vm3zt2n4b Error 0xC000009C {STATUS_DEVICE_DATA_ERROR}
File C:\Windows\System32\DriverStore\FileRepository\prncacla.inf_amd64_b353adcdce8a187f\Amd64\CNBJ2530.DPB|>_5_Kolt50vpJyqlets20vm3zt2n4b Error 0xC000009C {STATUS_DEVICE_DATA_ERROR}
File C:\Windows\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB|>_5_Kolt50vpJyqlets20vm3zt2n4b Error 0xC000009C {STATUS_DEVICE_DATA_ERROR}
File C:\Windows\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.20531_none_fe58af2da47e1433\Amd64\CNBJ2530.DPB|>_5_Kolt50vpJyqlets20vm3zt2n4b Error 0xC000009C {STATUS_DEVICE_DATA_ERROR}
File C:\Windows\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB|>_5_Kolt50vpJyqlets20vm3zt2n4b Error 0xC000009C {STATUS_DEVICE_DATA_ERROR}

What do these messages mean? Are they serious? I am running the latest version of Avast with latest defs. I am running Windows 8 Pro 64 bit.
I am thinking that it has to do with 64 bit system and Avast is 32 bit. Also, I am using TrueCrypt on system partition, but it asks for my TC password before Avast starts scanning. Thanks.

Btw, no infections were found.
« Last Edit: December 04, 2013, 09:24:37 PM by AvastUser015 »

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37534
  • Not a avast user
Re: Boot Scan
« Reply #1 on: December 04, 2013, 09:16:57 PM »
when avast display scan errors it usually display a reason to the right of the scan result.... what was it?


AvastUser015

  • Guest
Re: Boot Scan
« Reply #2 on: December 04, 2013, 09:28:04 PM »
No reason was given. It just displayed the 5 messages that i copied and pasted in the original message.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37534
  • Not a avast user
Re: Boot Scan
« Reply #3 on: December 04, 2013, 09:34:47 PM »
are you sure.... can you attach a screen shot?

anyway scan errors are not something avast can anything with .... and usually nothing to worry about
it just display the error and the reason why




« Last Edit: December 04, 2013, 09:37:10 PM by Pondus »

AvastUser015

  • Guest
Re: Boot Scan
« Reply #4 on: December 04, 2013, 10:18:40 PM »
Yes...I am sure. I copied the text from aswboot.txt and pasted it in the message.

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot Scan
« Reply #5 on: December 04, 2013, 10:21:17 PM »
0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk

AvastUser015

  • Guest
Re: Boot Scan
« Reply #6 on: December 05, 2013, 03:38:16 AM »
Problem Solved...I ran Error Checking (Windows) on the drive and it showed errors. It ask me to restart to fix the errors. I then ran Error Checking again it said no errors were found. I then ran Avast Boot Scan and this time no errors and no infections. Thanks for all your help. I wish programs could provide a more user-friendly error message and solution.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11851
    • AVAST Software
Re: Boot Scan
« Reply #7 on: December 05, 2013, 11:09:41 AM »
Well, it would be nice (to have "clear" error messages), but unfortunately it's not that easy.
The program asks the operating system "get me the data from this file" - normally, everything goes well and the operating system says back "No problem, here you are". But sometimes the operation fails - and the system says "Reading failed with error 123456". There are hundreds of error codes, thousands of places where those errors may occur... and the reason is not always clear.
Preparing a program for every possible problem (software, hardware, filesystem etc.) with a specific message isn't really possible.