Please use the search function if you are getting a BSOD in Windows 8 caused by Avast!'s system drivers!Please turn off Network Shield if you are affected we are working on fix but it's quite difficult... and your dumps are really welcome!
Please use the search function if you are getting a BSOD in Windows 8 caused by Avast!'s system drivers!Please turn off Network Shield if you are affected we are working on fix but it's quite difficult... and your dumps are really welcome!
thank you
Lukas.
No offence, but how exactly did Avast 7 get the Windows 8 compatible badge from Microsoft when it quite clearly isn't?
How can a product that BSOD's the system be compatible?
No offence, but how exactly did Avast 7 get the Windows 8 compatible badge from Microsoft when it quite clearly isn't?
How can a product that BSOD's the system be compatible?
That Windows 8 compatible badge is not a big deal. As far as I know it's quite easy to get it.
No offence, but how exactly did Avast 7 get the Windows 8 compatible badge from Microsoft when it quite clearly isn't?
How can a product that BSOD's the system be compatible?
That Windows 8 compatible badge is not a big deal. As far as I know it's quite easy to get it.
Avast has gone through intensive testing, finished by roughly 8 hour-long tests in Windows Hardware Cerification Kit - WHQL for WFP botch x86 and X64 platforms. Of course with some problems at first, but after a few weeks all were eliminated, these test on top of general stability (tested for all drivers) also test Network specific scenarios such as uninterrupted network streaming a connections in different situations - such as power events, network adapter removal etc., after these test were completed for aswnet.sys driver (and some others), the whole avast7 installation package went through the Application Certification Kit, which also reviled a few things. With successful pass of these test, the application (avast 7) was tested for 10 days in Microsoft labs, until the Logo was granted.
Hi guys,
we are still trying to come up with some fix for the frequent Win8 crash inside aswnet.sys.
Could you please try the following updated driver and post here if it performs any better?
The link and instructions are here:
http://public.avast.com/~rypacek/patches/ (http://public.avast.com/~rypacek/patches/)
It is still possible we didn't hit the right bug, so if you can, please follow the instruction on the page above and enable extra logging. Any possible dump files will be more usable for us! Thanks a lot.
Lukas
Edit: please enable Network Shield, if you have previously disabled it as a workaround. Thanks.
Hi guys,Been running over 30 minutes now with this patch on and all shields enabled. Seems to be working great!
we are still trying to come up with some fix for the frequent Win8 crash inside aswnet.sys.
Could you please try the following updated driver and post here if it performs any better?
The link and instructions are here:
http://public.avast.com/~rypacek/patches/ (http://public.avast.com/~rypacek/patches/)
It is still possible we didn't hit the right bug, so if you can, please follow the instruction on the page above and enable extra logging. Any possible dump files will be more usable for us! Thanks a lot.
Lukas
Edit: please enable Network Shield, if you have previously disabled it as a workaround. Thanks.
SugarD-x,Ironically I get that on my Windows 8 system which isn't crashing. This Web Rep crash started for me today on my BSOD-affected Windows 8 system after I installed the above patch to resolve the BSOD's. That's why I brought it up here, just in case it was related. :)
They are working on the Chrome web rep issue. For me it is grayed out and with the srajer mail address for account. srajer is an avast team member.
Maybe he is working on the coding of avast web rep?
polonus
I have no crashes on Windows 8 (32 and 64 bit computers)I have the patch installed on my 32-Bit system as I mentioned, but I have that Web Rep issue only on my 64-Bit, system as well. I'm beginning to think it may be a version issue. :P
I have the srajer email issue on the 64 Windows 8 system.
(Didn't install a patch sine I didn't have the problem)
No offence, but how exactly did Avast 7 get the Windows 8 compatible badge from Microsoft when it quite clearly isn't?
How can a product that BSOD's the system be compatible?
That Windows 8 compatible badge is not a big deal. As far as I know it's quite easy to get it.
That's actually a great point!No offence, but how exactly did Avast 7 get the Windows 8 compatible badge from Microsoft when it quite clearly isn't?
How can a product that BSOD's the system be compatible?
That Windows 8 compatible badge is not a big deal. As far as I know it's quite easy to get it.
Microsoft changed something in a recent very major Windows 8 update pack, and it's only with that installed did the issues start. I was probably the first to come across it since I had access to this update before Microsoft officially released it through Windowsupdate or on the download site :)
This large update may have caused other issues with network drivers, so definitely upload the dumps where possible! It would be unfair to blame Avast if it is caused by a network driver. For example, I have read on another forum that an Intel network driver is causing BSODS with this update.
It's possible that the reason why the update causes issues is last minute changes ('behind the scenes') n network security. This is just a thought!
This is definitely not a network driver issue. Build 1466 is working fine, only 1473 and 1474 is affected, and the BSOD is not only the issue.If your experiencing any BSOD issues with win8 then read Lukor's post here on a driver patch http://forum.avast.com/index.php?topic=107886.msg858781#msg858781
Please use the search function if you are getting a BSOD in Windows 8 caused by Avast!'s system drivers!Please turn off Network Shield if you are affected we are working on fix but it's quite difficult... and your dumps are really welcome!
thank you
Lukas.
I still can't figure out what systems are affected. Personally, running 32 bit Windows 8 Pro almost for one week and no BSOD caused by avast, so I can't understand, why some Windows 8 gets blue screen, some not... :)
Same here. I have 2 systems and there's no consistency to the bug. ;DPlease use the search function if you are getting a BSOD in Windows 8 caused by Avast!'s system drivers!Please turn off Network Shield if you are affected we are working on fix but it's quite difficult... and your dumps are really welcome!
thank you
Lukas.
I still can't figure out what systems are affected. Personally, running 32 bit Windows 8 Pro almost for one week and no BSOD caused by avast, so I can't understand, why some Windows 8 gets blue screen, some not... :)
I know this thread is for 8 BSOD's, but you haven't fixed the BSOD's I get when I try to install avast! on 7 64bit.
First things first. Maybe if you fixed 7 then....
I know this thread is for 8 BSOD's, but you haven't fixed the BSOD's I get when I try to install avast! on 7 64bit.When did your issue start? It sounds like your problem is likely caused by something conflicting with Avast! itself.
First things first. Maybe if you fixed 7 then....
To all those NOT having issues with BSODS under Windows 8, do you have KB2756872 installed?On my unaffected Windows 8 x64 system, I do have that update installed. I also have it installed on my affected Windows 8 x86 system.
Just curious, because the original BSOD issue was caused by a new ndis.sys that came with that update (I reported it starting back with build 1468). This ndis.sys issue is fixed, but this new BSOD has been introduced since. I ask, because it is a means of elimination.
Avast -on the other side- is claiming full Win8 compatibility.Which is exactly what I have on my 5 Windows 8 systems.
Bhakakhan I fail to understand... ;) not my problem ...
some users that were experiencing BSOD'she he ... underestimated - in all ways - you are playing down a very serious thing - avast was creating the FIRST BSOD for me after about 10 years - i didn't even know BSODs are still existing until avast published the new update - and "some users" is very likely very underestimated
If your happy to go to avirano - i don't go to avira - where did you read that? i just mentioned, that they -in contrast to AVAST- are true to their customers - means:
coming here to complain is rather pointless imo when you have not even stated if you had a problem yourself and needed directions to fix it
This is a support forum so you are bound to see people with problems here, there are also million of user's with no problems who you wont see here.what do you want me to understand? Do you think i am a kiddie who doesn't know, what a forum is? Or do you want to cut out feedback? Didn't you learn, that user feedback is existential for software companies?
There are unfortunately some computer that have a problem.
Or do you want to cut out feedback? Didn't you learn, that user feedback is existential for software companies?If you are going to quote me then quote the whole text so to put it in context, I understand perfectly fine what you were saying! it is you who fail to understand ???
If you are going to quote me then quote the whole text so to put it in context, I understand perfectly fine what you were saying! it is you who fail to understand ???
If you want to give feed back then do so with something constructive and state your problem, replies such as " is this a joke " which you placed in another thread is very childish and you wonder wheather we think your a kiddie ::)
If you are on win8 and you have the BSOD problem then apply the patch and we are not playing down anything, as lukor mentioned in another thread if they had known this release was going to cause issue's they would not have released it but at the time of testing it was fine.
If you are not using the software, you are not a customer.QuoteIf you are going to quote me then quote the whole text so to put it in context, I understand perfectly fine what you were saying! it is you who fail to understand ???
If you want to give feed back then do so with something constructive and state your problem, replies such as " is this a joke " which you placed in another thread is very childish and you wonder wheather we think your a kiddie ::)
If you are on win8 and you have the BSOD problem then apply the patch and we are not playing down anything, as lukor mentioned in another thread if they had known this release was going to cause issue's they would not have released it but at the time of testing it was fine.
1st - you say you fail to understand - 2nd you say you perfectly understand ... weird.. 3rd you say i am the one who fails to understand - even more weird - what is your problem? The usage of "i" "you" and "they" ?!? As said before: Ignore me if you have problems with my post...
And: Please: Don't quote me out of context, my dear - if you want people to do the way you like, then give a good example and do not do the opposite.. ;) - you even quote off-thread - what an example ;) - nice one..
Next: I am not willing to let you tell me, how i should give my feedback - you don't want to tell the rain how to fall, do you? As a customer, i give feedback the way i think it is appropriate - i didn't offend you -as a person- in any way - you did the opposite - this says all.
Firstly I said " I fail to see how you find the patch dubious " as there is clearly nothing dubious about it so you are very mistaken and confused.QuoteIf you are going to quote me then quote the whole text so to put it in context, I understand perfectly fine what you were saying! it is you who fail to understand ???
If you want to give feed back then do so with something constructive and state your problem, replies such as " is this a joke " which you placed in another thread is very childish and you wonder wheather we think your a kiddie ::)
If you are on win8 and you have the BSOD problem then apply the patch and we are not playing down anything, as lukor mentioned in another thread if they had known this release was going to cause issue's they would not have released it but at the time of testing it was fine.
1st - you say you fail to understand - 2nd you say you perfectly understand ... weird.. 3rd you say i am the one who fails to understand - even more weird - what is your problem?
First law of forums: Don't get sucked in by the troll.Have you tried the patch on top of that build yet? :)
Yeah, I knew there would be some issues with the brand-new release of Windows, but I did it, anyway. (I still have the bruises, too.)
I hadn't said anything earlier, but build 1474 did not fix my crashes. I posted (via FTP) 2 mini dumps with that build installed. Unfortunately I've had to uninstall Avast! until we get a little further along. Well, it's either that or go back to Windows 7 (I do have a dual-boot system), which seems even more counter-productive.
I'm going to be patient. I only wish I could go back out on the bleeding edge and suffer through this troubleshooting effort, but I'm trying to finish an important project. So ... my choices are Windows 7 (which works fine), or no Avast!
Have you tried the patch on top of that build yet?
It should solve your problem. When you get a chance, just update to the latest version of Avast!, slap on the patch, reboot, and turn on all shields. From there, just let us know if you have any more crashes. If so, dump it so Avast! can analyze it. If not, enjoy! :)QuoteHave you tried the patch on top of that build yet?
Not yet. Must ... finish ... project ... :o
puturaya I believe you have been instructed previously to install the patch, why not do so and put an end to your BSOD and the stupid replies ::)
Please re-read the first post of this topic and I'm fairly certain it will resolve your issue.(http://www.imgjoe.com/x/201211070904.jpg)
Intel Core i7 2630QM 16GB RAM , Nvidia GeForce GTX 560M 3GB ,Win8 Pro 64, IE10 , Malwarebytes Pro 1.65 , Outpost Firewall Pro 7.6On my computer ;D and whats that got to do with you applying the patch and fixing your problem ::)
where its avast ?
until when avast bsod fix this ?
To all those NOT having issues with BSODS under Windows 8, do you have KB2756872 installed?
Just curious, because the original BSOD issue was caused by a new ndis.sys that came with that update (I reported it starting back with build 1468). This ndis.sys issue is fixed, but this new BSOD has been introduced since. I ask, because it is a means of elimination.
Edit: Bhakakhan, if your are still with us, please do the same, turn of Network Shield for a while. The crashes will stop. Thanks and sorry. It was really a fault in our driver, I fully understand your are not happy! It got several people here awake for several days until the solution was found, we've released an update, fixing some of the problems, the rest took as a few days more. Not happy here either, so sorry again.
First BSOD after applying the patch yesteday and again just after sleep state wakeup.
Minidump Sepil-0712-10593-01.dmp should be there. I do not have any pagefile, so no memory.dmp.
sadly i got my first bluescreen after patch since yesterday. netio.sys. i may be forced to uninstall avast until a new version comes out
here is my mimidump
https://dl.dropbox.com/u/20179993/110712-22078-01.dmp (https://dl.dropbox.com/u/20179993/110712-22078-01.dmp)
i did apply the patch and restarted man.... didnt help
Installking the pathc is no problem. but that the patch spontanic get reverted after a few days is a BIG problem.The patch does not get "reverted". If you installed it over an older version of Avast!, then the updates are overwriting the file. You need to update to the latest version first, then install the patch. :)
I payed for avast. so i want a patch that keeps resident and dont get reverted. or just a normal avast. I cant have BSOD screen.
seems i lost already some thread message because that. But i dotn want to lower the security level.
Since I patched, I was relieved from a lot of trouble while installing numerous software, however in the middle of the night the computer BSODed on me. Here is the minidump. Please fix this soon guys.You updated to the latest version before applying the patch, correct?
Thanks.
https://www.dropbox.com/s/al6ac8jg3gurshv/111712-17937-01.dmp
Since I patched, I was relieved from a lot of trouble while installing numerous software, however in the middle of the night the computer BSODed on me. Here is the minidump. Please fix this soon guys.You updated to the latest version before applying the patch, correct?
Thanks.
https://www.dropbox.com/s/al6ac8jg3gurshv/111712-17937-01.dmp
Next week I will update my Vista 64 to Windows 8 64. Can I reinstall Avast IS directly or should I apply the patch suggested in this thread to prevent BSODs?After your upgrade, assuming Avast works as intended, you should just make sure it's up-to-date, and only apply the patch if you get the BSOD's themselves.
Thanks in advance
Simone
more than 1 person is facing this problem on win 8 64 and it may be getting buried under the bsod posts..I've alerted the Mods to that post.
http://forum.avast.com/index.php?topic=109872.0 (http://forum.avast.com/index.php?topic=109872.0)
Since I patched, I was relieved from a lot of trouble while installing numerous software, however in the middle of the night the computer BSODed on me. Here is the minidump. Please fix this soon guys.
Thanks.
https://www.dropbox.com/s/al6ac8jg3gurshv/111712-17937-01.dmp (https://www.dropbox.com/s/al6ac8jg3gurshv/111712-17937-01.dmp)
Hi K.electron,
I have looked at your dump - it's something different, seems like another (perhaps) unrelated problem. Would it be possible to upload a larger dump? (e.g. kernel dump).
Thanks.
Lukas.
Two BSODs with aswnet.sys at Windows 8 and self-defense module on. I'll disable the self-defense module again...I've applied the patch and next boot, the computer BSODed. On the second boot, seems stable. I've set full log.
The first BSOD was without the patch.Can anybody say a word to me? Thanks.
The other three were with the patch applied.
I still have problems and the patch is not the solution for me :-X
1. http://www.sendspace.com/file/4hvyck
2. http://www.sendspace.com/file/o1pfzy
3. http://www.sendspace.com/file/7qwd2w (I think this was with the full log option on).
4. http://www.sendspace.com/file/7iri5j
tech, in all your dumps, the aswnet.sys driver is the same -- UNPATCHED!!!I swear that I did what is posted in the 1st post of this thread.
Can you please verify what is your latest emeregency update, from "C:\ProgramData\AVAST Software\Avast\AvastEmUpdate.ini"I've uninstalled AIS, use aswclear, install again and patch (copy the files) before rebooting.
Tech, I don't know if what has been happening to others in an unrelated patch could have an affect on you. For these patches it requires the corresponding .sum file placed in the same folder (aswnet.sys.sum in this case) as the aswnet.sys file.I've copied both files in the C:\Windows\System32 folder as per instructions.
I've copied both files in the C:\Windows\System32 folder as per instructions.
Tech, please, just look into the avastEmUpdate.ini and post here the number, is it 103, 104 or 105?Now it's written:
And rebooted afterwards?Yes, I think so.
This is a dumb question, but just in case you had forgotten, since you didn't mention it in your other posts that I see...did you update to the latest version of Avast! before installing the patch, just in case it hadn't auto-updated itself that far yet?Yes Sugar, I did have the latest avast! version.
I've copied both files in the C:\Windows\System32 folder as per instructions.
This "Sticky" is now my unofficial time to upgrade to W8 indicator.Well, that's most likely to happen after the new program update...I hope! :D
Once it is removed as a "Sticky" or posts to it have ceased for a bit then it will become time to seriously thinking about updgraded to W8 :)
>:( :o ??? :-\What file did the BSOD say? You should upload your BSOD dump files to Avast!. :)
Bad news, i just got the BSOD again, so i patched after it worked for maby 2-3 weeks fine the aswnet again.
DOnt know why ther'es still not a patched version so you can work normal, and have fully working avast.
Right now i dont know what works and what not works. Lets say most is broken to keep safe.
Sofar avast dont start to run beter, it only create more problems, fix asap.
Got the feeling windows ius sabotage avast, or doing something like reverting drivers ?
wellthe common one: MODULE_NAME: aswnetMake sure your Avast! is up-to-date before applying the patch, else updating it after will overwrite it. :)
Again, the have already 7 dump files from the last weeks. ;D well up for nr. 8.
Hmmm. Timestamp: Mon Oct 29 16:02:23 2012 (508E9A7F)
for some reason the driver reverted back to the old one again,
and this not the first time the patched one get replaced. And it worked fine for a few weeks.
Understanding Early Launch Anti-Malware (ELAM) technology in Windows 8
September 23, 2012 Author: AnandK@TWC Category: Windows Tags: Features, Security, Windows 8
Windows 8 introduces a new security feature called Secure Boot, which protects the Windows boot configuration and components, and loads an Early Launch Anti-malware (ELAM) driver. This driver starts before other boot-start drivers and enables the evaluation of those drivers and helps the Windows kernel decide whether they should be initialized. By being launched first by the kernel, ELAM is ensured that it is launched before any other third-party software. It is therefore able to detect malware in the boot process itself and prevent it from loading or initializing.
Windows Defender takes advantage of Early-Launch Anti-Malware and you therefore see that it no longer loads after the start-up process is complete, but early on during boot process.
Third-party antivirus software too are able to take advantage of the ELAM technology. To do so, they will have to integrate the same Early Launch Anti-Malware (ELAM) capability in their own software. To help security software vendors get started, Microsoft has released a whitepaper that provides information about developing Early Launch Anti-Malware (ELAM) drivers for Windows operating systems. It provides guidelines for anti-malware developers to develop anti-malware drivers that are initialized before other boot-start drivers, and ensure that those subsequent drivers do not contain malware. Several antivirus companies, who have released their updated solutions for Windows 8 already incorporate this technology.
The Early Launch Antimalware boot-start driver has classified the drivers as follows:
Good: The driver has been signed and has not been tampered with.
Bad: The driver has been identified as malware. It is recommended that you do not allow known bad drivers to be initialized.
Bad, but required for boot: The driver has been identified as malware, but the computer cannot successfully boot without loading this driver.
Unknown: This driver has not been attested to by your malware detection application and has not been classified by the Early Launch Antimalware boot-start driver.
By default, Windows 8 loads those drivers which have been classified as Good, Unknown and Bad but Boot Critical; ie 1, 3 and 4 above. Bad drivers are not loaded.
Hi guys,Did you ever try the fix described in the first post?
I'm just wondering when the problem will be solved for good. I used to run under avast as it was the best free protection I could use, tho when I switched under Windows 8... It became a hell because of the random BSOD... These happened while:
- I was copying files from my external HDD to my new Windows 8 installation;
- I was launching a program (.exe)
- I was installing new drivers (my computer BOSD'ed while installing NVIDIA drivers, though I can't really make a link between avast and this...)
I'm currently running under Windows Defender, but I don't know if I can rely on it. I'm seriously scared to try to install avast again, since I'm often working on my computer for college and I wouldn't want a BSOD to cause data/work loss...
I can't upload dump files since I had to reinstall my computer, which was messed up pretty bad due to the BSOD's I suppose...
Is that aswnet.sys driver that important for the program to work?
And again my sistem started to behave like i described in this post : http://forum.avast.com/index.php?topic=110624.msg869853#msg869853 (http://forum.avast.com/index.php?topic=110624.msg869853#msg869853), are you guys experiencing this too, or you only got the BSODS ?I have only had a BSOD on one of my two Windows 8 systems so far. Others have complained about the network issues, though. For that problem, I would recommend finding one of the applicable topics so your requests for help don't get lost in this one. :)
Did you ever try the fix described in the first post?
Hello everyone :)
firstly i just want to say keep up the good work avast is ace (when it works ) but in this case i too have had the lock screen of death <----- yes the lock screen of death , i have installed windows 8 today and everything went fine i did all the usual driver installs and everything went well did the usual updates from microshaft and still everything went well.
anyways moving on i usually install avast as a last thing before i do a ghost or drive image then if anything goes wrong i can get back without having to reinstall all again down to a major driver issue or software Muck up.
well i went to the website and downloaded the latest version for windows 8 , no problems so far installed everything at this point was great then it asked me to reboot , which is normal , so i goes ahead and does this.
My laptop is a acer 7720z 4 gb ram intel celeron 550 cou @2.00ghz runs really well
so it reboots and i am thinking ooooh this is good the windows 8 logo appears and then it asks me to log in with my password as normal and then NOTHING !!!!!!!!! but a arrow on a black screen , sooooo i thinks to myself hmmm ok give it a forced reboot as i could not do the task manager thing because it would open then close so i reboots , still nothing , good job i did the image so ghosted back my image before i installed avast and everything was fine again , so i tried to install avast again thinking it was a install error only to my surprise of using avast for 4 years it did it again , so here i am waiting patiently for the fix , i did try the patch but that did nothing for me and i turned off windows defender and also when i installed avast i did turn of the web shield but still no go.
sorry to bore you all with this but that's where i am at with it so far :)
Lee B
Thanks but that couldn't help me . Hope you understand the problem with avast! on my PC .
Thanks but that couldn't help me . Hope you understand the problem with avast! on my PC .
If you start a new topic, we can try to troubleshoot...
SgarD, check the date of the aswnet.sys , windows8 or some other program seems to replace it sometimes here with the orginal version."Modified: Monday, October 29, 2012, 8:01:49 AM"
Lucky it happens only very rare this days.
It would be enormously helpful if somebody could explain the problem and a solution/options in plain English for the techies stuck in the obsolete world of Windows 7 and who have not--until now--had to deal with stuff like this.If you are getting the BSOD crashes under Windows 7 caused by Avast!, then I suspect you have something else wrong, as this issue is caused by Windows 8 itself. ;)
How many of those who are having the crash problem are actually running the
final Windows 8 Pro release ???
Not a trial or older build but the actual release ???
How many of those who are having the crash problem are actually running the/me raises his hand.
final Windows 8 Pro release ???
Not a trial or older build but the actual release ???
Hi all ,
I have upgraded my PC from Windows XP Professional service pack 3 to Windows 8 Pro 32 bit . I have installed " avast! free antivirus 7.0.1474 " and also updated its virus definitions . When I restarted the PC , avast! stops Windows 8 from booting . After the user login page , a " Black Screen with working mouse pointer " appears . Nothing appears more than this . Uninstalling avast! in safe mode and restarting again boots up Windows 8 in normal mode without any problem . I have been using for more than 2 years and never had a problem with avast! . Now avast! is troubling me . Does any one of you have a fix for this problem so that avast! can be used without any problem in windows 8 ??
Please help me out .
Thank you .
the .sum files also have to be copied across as it is these that prevent the modified files from being replaced.
what's BSODBSOD=Blue screen of death http://en.wikipedia.org/wiki/BSOD
copied the files to System32\DriversSorry if it is silly, but, did you overwrite the existent files?
The problem came back for me too Tech. I've been using the patch since it first came out, and it worked fine until a month or so ago.copied the files to System32\DriversSorry if it is silly, but, did you overwrite the existent files?
Sugar, sorry, only Lukas could help. My technical knowledge does not go that far.Not a problem. Just figured I'd throw it in there since a lot of people lately have been saying the same.
aswnet.sys BSOD crashing two of my computers win8 64bit pro...one very often directly after booting..patch does not work
The patch works for me, but I have to stop all avast shields to run cryengine3. That is not a major problem though.If the patch is working, you should be able to enable all the shields. If it's not, then the only one you need to turn off is the Network Shield. The issue with CryEngine3 is a separate problem that you should probably make another topic for. :)
Can I re enable the self defense module?
Windows 8 has a severe internal bug in several of its drivers, notably :That isn't the case with all 64-Bit installations with multi-core CPU's, because my laptop is running it just fine. Also, you should probably post this in a separate thread as it is unrelated to this. This topic is about Windows 8 BSOD's caused by Avast! itself.
- for handling large disk partitions (more than about 2 TB : the bug is in ntfs.sys notably it will immediately fail with a BSOD as soon as backup starts : Windows backup apparently uses (in ntfs.sys) a 32-bit variable to test the amount of free disk space, and gets some random negative value, and then fails to allocate some buffers and ntfs.sys gets a NULL pointer that it tries to reference, causing a fatal exception that causes the system to go to BSOD as NTFS.SYS MUST NOT be terminated!). This affects users with large disks (e.g. those trying to install the 64-bit version of Windows 8 over a large RAID volume). But it can also cause AVAST to hang as well (as it also depends on ntfs.sys). NTFS.SYS does not work correctly in its 64-bit version (visible this system driver was incorrectly compiled and has mixed 32-bit and 64-bit compile-time flags.
- in a new API related to DirectX11, where WinSat fails with 64-bit processors and NVIDIA display drivers (a new DDK API with DDI 1.1 apparently requires that WDDDM display drivers MUST report their shadow memory as "*_SEGMENT3" structures instead of "*_SEGMENT" structures in previous WDDM versions; MSDN says that this API is new to Windows 8, OK, but it does not require drivers to support it, and WinSat will fail the API returns a "not supported" error. This new API is just there to indicate how virtual memory segments are mapped to hardware memory segments, as before, but this new structure has had its members swapped with flags at the begining instead of at and, for only adding a new member containing the size of the segment to save in case of hibernation; if this API is not supported because there's nothing to save in case of hibernation, WinSat should not complain and repeat itself constantly every 3 minutes trying to perform the same test! It should use the previous supported API 'using "*_SEGMENT" and assume that the whole reported memory segment is to save to the hibernation; this is in fact very strange because it makes this false assumption only if you are running a multicore Windows kernel, so you can paliate the problem in WinSat by first disabling all cores but 1 and disabling hyperthreading, the time to run WinSat once; then you can reboot with all cores enabled in the BIOS and hyperthreading enabled.
These bugs all occur in the 64 bit version of Windows 8 (and most Windows 8 PC sold for tablets or subnotebooks are running a 32-bit version).
In summary : Windows 8 does not work with its 64-bit installation ! These bugs are critical, and still not solved (some OEMs are trying to implement their own patches differently and not compatible with each other ! Microsoft should instead develop corrections to its kernel and instruct the OEMs to remove thier attempted patches.
So : don't use Windows 8 in 64-bit mode for now, if you have a multicore CPU or hyperthreading CPU, or if you have partitions larger than 2 TB.
That isn't the case with all 64-Bit installations with multi-core CPU's, because my laptop is running it just fine. Also, you should probably post this in a separate thread as it is unrelated to this. This topic is about Windows 8 BSOD's caused by Avast! itself.My 64 bit also has no problems and has never needed the "fix".
I've used Avast for years on XP and love it but now have a Win8 system and was about to install Avast IS on it. After reading several posts on this forum about BSOD's on Win8 I'm scared to jump into the Avast water. When will we know if it's safe to start using it on Win8 ???Since this is a support forum, you're looking at mostly users who have run into a problem.
I'm one of those who has windows 8 installed on 5 computers and have never had a problem with avast! 7Heh, I know what you mean. I have 2 systems running Windows 8 right now with the latest version of Avast!, and only one is affected by the bug. It's a confusing issue.
Just curious. Are you using any tune up or tweaking utilities ???I'm one of those who has windows 8 installed on 5 computers and have never had a problem with avast! 7Heh, I know what you mean. I have 2 systems running Windows 8 right now with the latest version of Avast!, and only one is affected by the bug. It's a confusing issue.
Nope. Happened on a clean install of Win8 Pro x86. :(Just curious. Are you using any tune up or tweaking utilities ???I'm one of those who has windows 8 installed on 5 computers and have never had a problem with avast! 7Heh, I know what you mean. I have 2 systems running Windows 8 right now with the latest version of Avast!, and only one is affected by the bug. It's a confusing issue.
I don't think I can find any alternative to Avast!, so can somebody help me, please?
Please use the search function if you are getting a BSOD in Windows 8 caused by Avast!'s system drivers! There is now 8 or 9 different topics for the same, exact subject in this board. Don't make more unless you've read through them all and know for sure that your issue is not the same!
Here are a few from just the first two pages alone:
http://forum.avast.com/index.php?topic=108272.0
http://forum.avast.com/index.php?topic=108087.0
http://forum.avast.com/index.php?topic=108204.0
http://forum.avast.com/index.php?topic=107811.0
http://forum.avast.com/index.php?topic=108270.0
http://forum.avast.com/index.php?topic=108433.0
http://forum.avast.com/index.php?topic=107886.0
http://forum.avast.com/index.php?topic=108324.0
http://forum.avast.com/index.php?topic=108619.0
http://forum.avast.com/index.php?topic=107930.0
http://forum.avast.com/index.php?topic=108731.0
A patch has been made as a temporary solution, which is also meant to help the Avast! team resolve the issue for the next update. Please update to the latest version of Avast! available, and then follow the instructions found here:
http://public.avast.com/~rypacek/patches/
(See the one titled "aswnet patch: Patch for aswNet.sys, BlueScreen in NETIO.SYS on Windows8")
That is the only version affected under Windows 8.Please use the search function if you are getting a BSOD in Windows 8 caused by Avast!'s system drivers! There is now 8 or 9 different topics for the same, exact subject in this board. Don't make more unless you've read through them all and know for sure that your issue is not the same!
Here are a few from just the first two pages alone:
http://forum.avast.com/index.php?topic=108272.0
http://forum.avast.com/index.php?topic=108087.0
http://forum.avast.com/index.php?topic=108204.0
http://forum.avast.com/index.php?topic=107811.0
http://forum.avast.com/index.php?topic=108270.0
http://forum.avast.com/index.php?topic=108433.0
http://forum.avast.com/index.php?topic=107886.0
http://forum.avast.com/index.php?topic=108324.0
http://forum.avast.com/index.php?topic=108619.0
http://forum.avast.com/index.php?topic=107930.0
http://forum.avast.com/index.php?topic=108731.0
A patch has been made as a temporary solution, which is also meant to help the Avast! team resolve the issue for the next update. Please update to the latest version of Avast! available, and then follow the instructions found here:
http://public.avast.com/~rypacek/patches/
(See the one titled "aswnet patch: Patch for aswNet.sys, BlueScreen in NETIO.SYS on Windows8")
Jeff, The patch you are referring to is for Avast 7 only.....
The behavior shield causing black screen on startup on Windows 8 has been reported many times but it hasn't been fixed yet. :(You've posted about it in the wrong topic, my friend. This topic is about Windows 8 having Blue Screens Of Death caused by Avast! 7's usage.
Moreover, Avast Adblock lacks the ability to add more subscriptions and even the ability to manually block an ad on a page. :(
There're also the performance issue. It slows down my Windows 8 startup significantly compared with Avast 7 on Windows 7. :(