I too have the same problem as the original poster.ģ crash dumps have been found and analyzed. This was probably caused by the following module: mwac.sys (mwac+0x90BF)įile path: C:\Windows\system32\drivers\mwac.sys This was probably caused by the following module: ntoskrnl.exe (nt+0xA48A0)īugcheck code: 0xD1 (0x88, 0x2, 0x0, 0xFFFFF8800155EAEC)įile path: C:\Windows\system32\ntoskrnl.exe On Mon 4:57:45 PM your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\070918-4898-01.dmp I have been a long-time Malwarebytes premium customer and this crash history related to this product is very disturbing.īelow are WhoCrashed results, twice the same today and I lost some valuable data not saved due to sudden BSOD. I am running Win 7 64-bit and using the following Malwarebytes product. Reason I joined is I too am experiencing a number of BSOD events related back to mwac.sys. On Thu 3:49:55 PM your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\062118-13078-01.dmpīugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF8021CA47304)īrand new to this forum. Google query: mwac.sys Malwarebytes DRIVER_IRQL_NOT_LESS_OR_EQUAL It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Protection, Malwarebytes). This was probably caused by the following module: mwac.sys (mwac+0x915B)įile path: C:\WINDOWS\system32\drivers\mwac.sysĪ third party driver was identified as the probable root cause of this system error. ![]() Possibly this problem is caused by another driver that cannot be identified at this time. The crash took place in the Windows kernel. It means that a crash dump file was properly written out. ![]() This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. Product: Microsoft® Windows® Operating Systemīug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)īugcheck code: 0xD1 (0x50, 0x2, 0x0, 0xFFFFF80F54D47304)įile path: C:\WINDOWS\system32\ntoskrnl.exe On Thu 4:47:08 PM your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\062118-14375-01.dmp I downloaded 'WhoCrashed' and had it analyze my dump file and got this: I started the app and the system crashed. I followed the directions there and did a clean install of Malwarbytes. ![]() I downloaded MemTest86, created a USB booter then tested both of my 4GB memory sticks one at a time. I installed the app and World of Warcraft.Ībout 5 minutes after WoW was running the system crashed. I installed Malwarebytes Premium and Webroot Premium. I installed all available Windows updates. I can't recreate it on cue, but there's a high chance of it happening while starting or playing World of Warcraft.Īfter being frustrated by crashes for a few days, I completely reinstalled my OS. I hadn't installed any new software or hardware. The first time it happened, it was out of the blue. Endpoint Detection & Response for Serversīeen getting BSOD with same error (listed in title) for a while now.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |