Author Topic: BSOD, unknown origin in win7 SP1  (Read 11859 times)

0 Members and 1 Guest are viewing this topic.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
BSOD, unknown origin in win7 SP1
« on: July 22, 2011, 01:25:09 AM »
As the topic states I have had a couple of BSODs in the last 4 days and there has been zero file/driver name, etc. that is usually attributed to a BSOD.

Stop error is 0x0000007E (0xC0000005, this is variable, 0x8078631C, 0x80785F00), see low res screen capture image attached.

I have uploaded DavidR_dump_files.7z to the ftp avast incoming location, 14,301KB compressed size. It contains one minidump from 17/7/2011, one minidump from 21/7/2011 and the full memory.dmp file from 21/7/2011.

I have my suspicions that this may well be an Outpost Firewall Pro 7.5.1 related BSOD as I had recently installed that update and not directly related to avast 6.0.1203. Though I have no supporting evidence in the actual BSOD screen and I can't analyse the dump files.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline jvidal

  • Sr. Member
  • ****
  • Posts: 325
Re: BSOD, unknown origin in win7 SP1
« Reply #1 on: July 22, 2011, 02:09:14 AM »
use the utility bluescreenview to examine the minidumps. It gives you a lot more info and usually points to the offending driver (in this case, most likely, aswsp.sys)

Offline Rednose

  • Pirate Party Member
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 3739
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: BSOD, unknown origin in win7 SP1
« Reply #2 on: July 22, 2011, 02:38:13 AM »
We have a better BSOD " tool " here on the forum called Petr Kurtin ;D

Greetz, Red.
OS: Win 10 / iOS 17 / Debian 12 / Tails 5
Real Time: Avast Premium Security
On Demand: Malwarebytes
VPN: NordVPN ( NordLynx ) with Threat Protection ( Lite )

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: BSOD, unknown origin in win7 SP1
« Reply #3 on: July 22, 2011, 02:43:05 AM »
Which is why I posted it ;D

Whilst the bluescreenview if fine for minidumps as far as I'm aware it doesn't handle the full kernel memory dumps and it is these that reveal the full information.

Edit:
Having said that I have just updated my copy of bluescreenview and there are 4 drivers listed (two OS drivers) and aswSnx.sys (avast! Virtualisation Driver, a.k.a. sandbox) and Sandbox.sys (Agnitum Ltd {Outpost}. Host Protection Component).

So it could well be a conflict between these two drivers, hopefully the memory.dmp file will reveal more information. 
« Last Edit: July 22, 2011, 02:57:38 AM by DavidR »
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Rednose

  • Pirate Party Member
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 3739
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: BSOD, unknown origin in win7 SP1
« Reply #4 on: July 23, 2011, 12:31:02 AM »
Maybe Petr missed this topic and the dump(s), OR he is just lazy ;D I will ( virtualy ) kick his ass for you ;)

Greetz, Red.
OS: Win 10 / iOS 17 / Debian 12 / Tails 5
Real Time: Avast Premium Security
On Demand: Malwarebytes
VPN: NordVPN ( NordLynx ) with Threat Protection ( Lite )

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: BSOD, unknown origin in win7 SP1
« Reply #5 on: July 23, 2011, 12:40:45 AM »
I'm going to drop him an email ;D
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Rednose

  • Pirate Party Member
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 3739
  • Bits of Freedom : https://www.bof.nl
    • Nederlandstalig Avast! forum
Re: BSOD, unknown origin in win7 SP1
« Reply #6 on: July 23, 2011, 12:46:56 AM »
I have already done that :)

Greetz, Red.
OS: Win 10 / iOS 17 / Debian 12 / Tails 5
Real Time: Avast Premium Security
On Demand: Malwarebytes
VPN: NordVPN ( NordLynx ) with Threat Protection ( Lite )

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: BSOD, unknown origin in win7 SP1
« Reply #7 on: July 23, 2011, 12:55:25 AM »
Well my virtual boot reminder will only push yours a little higher ;)
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline jvidal

  • Sr. Member
  • ****
  • Posts: 325
Re: BSOD, unknown origin in win7 SP1
« Reply #8 on: July 23, 2011, 07:01:36 AM »
Which is why I posted it ;D

Whilst the bluescreenview if fine for minidumps as far as I'm aware it doesn't handle the full kernel memory dumps and it is these that reveal the full information.

Edit:
Having said that I have just updated my copy of bluescreenview and there are 4 drivers listed (two OS drivers) and aswSnx.sys (avast! Virtualisation Driver, a.k.a. sandbox) and Sandbox.sys (Agnitum Ltd {Outpost}. Host Protection Component).

So it could well be a conflict between these two drivers, hopefully the memory.dmp file will reveal more information. 

Hmm, try disabling/uninstalling Outpost and see what happens...

jamjar

  • Guest
Re: BSOD, unknown origin in win7 SP1
« Reply #9 on: July 23, 2011, 09:47:10 AM »
After updating Outpost Firewall Pro from 7.5 to 7.5.1, I got my first BSODs on start up. After Windows Startup Repair, System Restore, Outpost Firewall was no longer listed in Programs and Features but folders and files remained. It looked a bit of a mess, so I decided to do a full recovery and now I'm back with Windows Firewall.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: BSOD, unknown origin in win7 SP1
« Reply #10 on: July 23, 2011, 03:37:21 PM »
Which is why I posted it ;D

Whilst the bluescreenview if fine for minidumps as far as I'm aware it doesn't handle the full kernel memory dumps and it is these that reveal the full information.

Edit:
Having said that I have just updated my copy of bluescreenview and there are 4 drivers listed (two OS drivers) and aswSnx.sys (avast! Virtualisation Driver, a.k.a. sandbox) and Sandbox.sys (Agnitum Ltd {Outpost}. Host Protection Component).

So it could well be a conflict between these two drivers, hopefully the memory.dmp file will reveal more information. 

Hmm, try disabling/uninstalling Outpost and see what happens...

As I said there was 4 days between the two instances of a BSOD, so that really isn't an option; who knows how long it might be before the next instance. Not to mention removing one element of any conflict doesn't find the true cause/culprit, essentially that doesn't help anyone.

Only perseverance and the submission of BSOD dump files is likely to get to the real issue so that it might be resolved to the benefit of all users.

I have been using outpost firewall for even longer than the 7+ years of using avast and never once an issue like this and it is only on my win7 system and not this XP Pro SP3 one.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: BSOD, unknown origin in win7 SP1
« Reply #11 on: July 24, 2011, 01:10:33 AM »
Thanks DavidR for memory dump. Yes, this was a bug in virtualization driver and it's already fixed now. Your system can bluescreen only during driver loading (not later when you logon to Windows).

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: BSOD, unknown origin in win7 SP1
« Reply #12 on: July 24, 2011, 01:22:16 AM »
Well That doesn't appear to be the case, the first BSOD happened on a boot before I ever got to a logon screen.

The last one, whilst it also happened on a boot, I don't know if there was some sort of conflict coming out of standby as my win7 netbook computer flatly refused to come out of standby (not hibernation) and I ended up having to use the power button to restart.

This gave me the usual windows recovered from improper shutdown (etc.) and I opted for a normal restart and that was when it got the second BSOD.

You say this has been fixed, I take it you mean in an internal build, otherwise it wouldn't have happened ?

If and internal build, then if there is a patch I would be happy to install it and see how it effects the problem.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: BSOD, unknown origin in win7 SP1
« Reply #13 on: July 24, 2011, 01:59:40 PM »
Any information on this "bug in virtualization driver and it's already fixed now," as in where it is fixed, internal build (?) and when this is likely to be released.

I have had it happen again today when I tried to start my netbook, I let it collate the bsod data and restarted the netbook. Since you said it only happens during driver loading before on restart I told windows to boot normally (not go through a repair, which can't fix this bug) and it went into another bsod.

So I have rebooted and an running through the supposed Startup Repair option knowing it can't do anything. So I'm going to cancel (only to find I can't cancel it) that and see if I can get in on the third attempt to reboot.

Do want some of these minidumps and memory.dmp uploaded again to the ftp location ?
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

miscreant

  • Guest
Re: BSOD, unknown origin in win7 SP1
« Reply #14 on: July 24, 2011, 06:51:45 PM »
Do you actually use avast sandbox with outpost ,as the only way to allow avasts sandbox to work correctly with outpost is to let it create a global TCP rule ,though you can restrict it to your home lan.
« Last Edit: July 24, 2011, 06:55:47 PM by miscreant »