Question

Q: Windows 7 Blue Screen halmacpi.dll errors

Hello everyone, since last night i got blue screen error on my system two times, its first time it happend since i installed win 7 like year ago or so.
First two times happend during game called World of Warcraft, after that my google chrome browser literaly was gone, like i never had it installed, right after i started installing it and 3rd crash happend during that, but somehow it didnt finish in error log.
I dont know to read those error reports and what do they mean, but i wanted to post them here in hope someone will be able to point me into whats cosing problem.
I did scan my memory and HDD for errors via win 7 tools made for it, and found none, yet im not sure if i can say for sure that tests are 100% correct.

My system and hardware:
Windows 7 Ultimate (86 aka 32bit) , fully updated but without SP1 (didnt see point in installing it when i already had all updated and fixes installed)
Amd Atlon 6000+ dual core 64x working on 3.1k+
Asus M2N mobo
Kingston 3x 1gb ddr2 800mhz
ATI EAH 3850 HD VGA ( with latest Ati catalyst drivers aka 11.5)
Western Digital 160gb system Hdd
Western Digital 1tb storage Hdd
Always running protection : Comodo Firewall and Avira AntiVir Premium Antivirus. 
Only on demand scans: Spy both search and destroy, HiJackThis, Ad-Aware, IObit Security 360, Malwarebytes' Anti-Malware.
If u need me to post any more info regarding my system i will gladly do so just ask.

As i cant find way to upload errors here i will give u link where i uploaded them, i promise its not any kind of virus or so, just rared error reports from Windows.
Here is link, there are two minidump reports inside: http://www.megaupload.com/?d=8WJYKJGE
And here is link for BSOD_Windows7_Vista_v2.64 tool report: http://www.megaupload.com/?d=8DXJKR9P
System and performance monitor tool report : http://www.megaupload.com/?d=NFJIGDF7

Thanks!


Answer

A:

Hi,

Results verified by WinDBG, DumpCHK, and BlueScreenView.

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
FAILURE_BUCKET_ID:  0xBE_avipbb+289c
BUCKET_ID:  0xBE_avipbb+289c

The Bug_Checks were BE CAUSE avipbb.sys which is Avira.

Both times the PROCESS was GoogleUpdate was running.

PROCESS_NAME:  GoogleUpdate.e  <-- exactly as shown in both minidumps.

Try Disabling or Uninstalling the GoogleUpdate Program.

If no luck uninstall Avira to see the effect. Avira is not known to cause or aggravate BlueScreens however
anything is possible. Recommendations to use as replacements in a later message.

-------------------------------------------------------------------------------------------------------------------------------------------

Are all the Malware scanners running only on demand? Adaware is loading one of its services - Lbd.sys.
That and any of those running resident could be involved.

I use Adaware as an on-demand scanner only, none of the resident parts loading, and it loads
very slowly. Try LavaSoft's Support and Forums. There is a possibility that another program,
or even malware, is preventing it from loading.

Adaware Support
http://www.lavasoft.com/support/supportcenter/

Adaware Forums
http://www.lavasoftsupport.com/

In AdAware - Settings (for the Free version) either Remove it or set it up as an on-demand
scanner - be sure to update it before running - you probably will not need it however having
it setup as on-demand is probably a good idea and I use it that way.

Updates Tab - set it to Do Not Automatically Check - you will then need to check for updates
when you run it on-demand. Also do same for Information Updates.

AdWatch Live! tab - Uncheck Processes

Close AdAware (Right Click on the Icon in the Notification Area - EXIT)

Start - type in Search box ->  Services    find at top of list - Right Click on - RUN AS ADMIN

Find Lavasoft Ad-Aware Service  - double click on it and set to MANUAL and STOP

Now you can run AdAware as an on-demand Scanner. After you run it then Right Click on its
Icon in the Notification Area near the clock - EXIT

==================================

This link has some possible solutions.

BCCode: be   0x000000be  <-- read this link
http://www.faultwire.com/solutions-fatal_error/An-attempt-was-made-to-write-to-read-only-memory-0x000000BE-*1191.html?order=votes

Use the troubleshooter previously posted.


Hope this helps.

Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.



 
Question Info

Views: 5,295 Last updated: February 7, 2018 Applies to: