Author Topic: aswBoot.log .......... can someone please explain what this means?  (Read 4650 times)

0 Members and 1 Guest are viewing this topic.

833P

  • Guest

CmdLine - quick
aswBoot.exe /M:85e1616c5a194
CmdLine end
Processing file operations...
Unhandled exception! Error:17041289
GetErrorText
Unhandled exception Error:0xC0000096 {EXCEPTION}
Unschedule
61,00,75,00,74,00,6F,00,63,00,68,00,65,00,63,00,
6B,00,20,00,61,00,75,00,74,00,6F,00,63,00,68,00,
6B,00,20,00,2A,00,00,00,61,00,73,00,77,00,42,00,
6F,00,6F,00,74,00,2E,00,65,00,78,00,65,00,20,00,
2F,00,4D,00,3A,00,38,00,35,00,65,00,31,00,36,00,
31,00,36,00,63,00,35,00,61,00,31,00,39,00,34,00,
00,00,00,00,
Unschedule end

Avast 4.8.1367.0

Thanks

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 87645
  • No support PMs thanks
Re: aswBoot.log .......... can someone please explain what this means?
« Reply #1 on: February 13, 2010, 03:47:55 AM »
Not a lot to the user, but more to a developer for debugging if you had a problem. The file you want to look at is aswBoot.txt (in a different folder).
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.4.6062 (build 23.4.8118.762) UI 1.0.762/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

833P

  • Guest
Re: aswBoot.log .......... can someone please explain what this means?
« Reply #2 on: February 13, 2010, 04:36:50 AM »


That file was in the root of a drive that wouldnt boot. There appears to be no aswBoot.txt file anywhere on the drive.

ibell63

  • Guest
Re: aswBoot.log .......... can someone please explain what this means?
« Reply #3 on: February 13, 2010, 05:26:06 AM »
This type of error occurred for me in avast 4.8 when I would scan all drives with the BTS because I had an HFS+ (Mac) formatted disk visible in windows.  Do you have any disks with filesystems other than NTFS or FAT16/32?  Also, do you have a weird partition map scheme (basically something other than MBR).

Basically the only time any of this would be a problem is if you're dual booting OSes other than Windows based OSes.

I'm pretty sure the BTS in Avast5 is now smart enough to ignore HFS+ disks, as this is no longer an issue for me.
« Last Edit: February 13, 2010, 05:28:52 AM by ibell63 »

833P

  • Guest
Re: aswBoot.log .......... can someone please explain what this means?
« Reply #4 on: February 13, 2010, 05:31:52 AM »

All NTFS Sata Drives. Got up one morning and the PC which I usually leave on was switched off and wouldnt boot......... well only to a blue screen loop. Still trying to figure out why.