Jump to content

Arijit

Members
  • Posts

    9
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As you correctly said, I too have seen Malwarebytes working [perfectly in windows 2003, 2008, 2012, R2, 2016, 2019 all servers. So I have had a perfect experience till April 22. In fact in my other installations of windows 2012 R2 and windows 2008 R2 they are working fine. So unless it is violation of license agreements or something I am happy with what I am getting Now, as I said since this is 'server' is not being used as a 'desktop workstation', is web protection really necessary at this stage when issues are there Which one is better - 1) Go back to previous version with web protection on (even through I am not using any browsers on the machine) 2) Stay updated with current stable version, web protection off 3) Beta with web-protection off
  2. I was checking other posts in the forum on BSOD relating to mwac.sys to find if I have any similar situation, I read 9 pages of this link below but couldn't relate any link. - I am not running ad blocking software - Just the normal windows Firewall = Default Windows Filtering Platform is on and working - This is in fact a remote server where nobody sits and so not in use. I manage it and didn't have to look at the screen for days, and now I am logging in every hour
  3. No, it was OK for a few hours then bad again. MWB last updated to 1.0.23000 I signed up for Beta 21:46 PM after that had crashes on 01:06 AM, 3.34 AM, 5.52 AM Had very less sleep last night. A completely perfect running server of over 3 years now getting rendered useless by this issue. 1) Disabling web protection now 2) Will uninstall if problem still persists 3) Is there a way I can downgrade to a previous all working'version?
  4. No, it was OK for a few hours then bad again. MWB last updated to 1.0.23000 I signed up for Beta 21:46 PM after that had crashes on 01:06 AM, 3.34 AM, 5.52 AM Had very less sleep last night. A completely perfect running server of over 3 years now getting rendered useless by this issue. 1) Disabling web protection now 2) Will uninstall if problem still persists 3) Is there a way I can downgrade to a previous all working'version?
  5. OK, I signed up for Beta and MalwareBytes updated and enabled web Protection back on. Now lets see
  6. I did not sign up for Beta but the software updated to 1.0.22990 and crashed immediately! I will now try disabling web-protection ------------------ Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042620-18171-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location OK c:\mysymbols Deferred cache*c:\symbolcache Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: c:\mysymbols;cache*c:\symbolcache;SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 8 Kernel Version 9600 MP (4 procs) Free x64 Product: Server, suite: TerminalServer SingleUserTS Built by: 9600.19678.amd64fre.winblue_ltsb_escrow.200330-1737 Machine Name: Kernel base = 0xfffff800`d4e84000 PsLoadedModuleList = 0xfffff800`d51495f0 Debug session time: Sun Apr 26 21:44:12.159 2020 (UTC + 5:30) System Uptime: 0 days 2:08:03.797 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by : mwac.sys ( mwac+122a6 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: 0000000000000000 Debugging Details: ------------------ DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER BUGCHECK_STR: 0x133 PROCESS_NAME: System CURRENT_IRQL: d ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from fffff800d4fde86a to fffff800d4fc44c0 STACK_TEXT: ffffd001`8122bc88 fffff800`d4fde86a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffd001`8122bc90 fffff800`d4eb2fd1 : 00000000`00000000 00000000`000780f3 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x563a ffffd001`8122bd20 fffff800`d4e1cac5 : ffffd001`7ddc97a0 00000000`00000001 ffffd001`8121a480 ffffd001`7d9e0180 : nt!KeClockInterruptNotify+0x91 ffffd001`8122bf40 fffff800`d4f38943 : ffffafdd`6c51ec0b 00000000`00000000 ffffe000`86df2010 ffffd001`8121a838 : hal!HalpTimerClockIpiRoutine+0x15 ffffd001`8122bf70 fffff800`d4fc59ca : ffffe000`868eb1e0 ffffd001`8121a480 ffffe000`877eed20 ffffd001`8121a838 : nt!KiCallInterruptServiceRoutine+0xa3 ffffd001`8122bfb0 fffff800`d4fc5e77 : ffffd001`8121ae50 00000000`00000000 fffff800`95e4d4c0 ffffd001`8121a2c0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea ffffd001`8121a2a0 fffff800`d4f07073 : ffffe000`877eed20 ffffd001`8121ae50 ffffe000`86df2010 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffd001`8121a430 fffff800`95e492a6 : ffffe000`8ef1fc30 00000000`00000001 ffffd001`8121a628 fffff800`00000000 : nt!KxWaitForLockOwnerShip+0x27 ffffd001`8121a460 ffffe000`8ef1fc30 : 00000000`00000001 ffffd001`8121a628 fffff800`00000000 ffffd001`83216590 : mwac+0x122a6 ffffd001`8121a468 00000000`00000001 : ffffd001`8121a628 fffff800`00000000 ffffd001`83216590 fffff800`95e51b11 : 0xffffe000`8ef1fc30 ffffd001`8121a470 ffffd001`8121a628 : fffff800`00000000 ffffd001`83216590 fffff800`95e51b11 ffffe000`86df2002 : 0x1 ffffd001`8121a478 fffff800`00000000 : ffffd001`83216590 fffff800`95e51b11 ffffe000`86df2002 00000000`00000000 : 0xffffd001`8121a628 ffffd001`8121a480 ffffd001`83216590 : fffff800`95e51b11 ffffe000`86df2002 00000000`00000000 00000000`00000000 : 0xfffff800`00000000 ffffd001`8121a488 fffff800`95e51b11 : ffffe000`86df2002 00000000`00000000 00000000`00000000 fffff800`95e3da0b : 0xffffd001`83216590 ffffd001`8121a490 ffffe000`86df2002 : 00000000`00000000 00000000`00000000 fffff800`95e3da0b 00000000`00000000 : mwac+0x1ab11 ffffd001`8121a498 00000000`00000000 : 00000000`00000000 fffff800`95e3da0b 00000000`00000000 ffffe000`877eed20 : 0xffffe000`86df2002 STACK_COMMAND: kb FOLLOWUP_IP: mwac+122a6 fffff800`95e492a6 ?? ??? SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: mwac+122a6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: mwac IMAGE_NAME: mwac.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5e84a7fa FAILURE_BUCKET_ID: 0x133_DPC_mwac+122a6 BUCKET_ID: 0x133_DPC_mwac+122a6 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x133_dpc_mwac+122a6 FAILURE_ID_HASH: {5fb89f40-2c9e-f340-840d-969068313f39} Followup: MachineOwner ---------
  7. The disclaimer given on the Beta programme is quite fearsome! I am not very keen to crash my live production server more often it is doing now.
  8. Since April 22 I am having BSOD after every 2-3 hours. I am running latest version see screenshot. I did the following till now 1) did a WindBG on minidump and main dump, all of the results point to mwac.sys 2) I uninstalled - rebooted - reinstalled , still same 3) Downloaded latest support tool, opened a ticket Support Ticket 3008946 and submitted logs, still restart going on! Never had problems in free version for last 3 years. Did I do in any wrong in paying up? Thanks Arijit 042620-19015-01.dmp winDBG.txt -------------- Use !analyze -v to get detailed debugging information. BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by : mwac.sys ( mwac+122a6 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: 0000000000000000
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.