API tools faq
paste
Advertisement
Guest User

MWB

a guest
Apr 15th, 2016
200
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.69 KB | None | 0 0
raw download clone embed print report
  1. Crash Dump Analysis
  2. --------------------------------------------------------------------------------
  3.  
  4. Crash dump directory: C:\WINDOWS\Minidump
  5.  
  6. Crash dumps are enabled on your computer.
  7.  
  8. On Fri 2016-04-15 06:52:46 GMT your computer crashed
  9. crash dump file: C:\WINDOWS\Minidump\041516-15656-01.dmp
  10. This was probably caused by the following module: mwac.sys (mwac+0x6135)
  11. Bugcheck code: 0x19 (0x20, 0xFFFFE0004025E740, 0xFFFFE0004025E760, 0x402000C)
  12. Error: BAD_POOL_HEADER
  13. file path: C:\WINDOWS\system32\drivers\mwac.sys
  14. product: Malwarebytes Web Access Control
  15. company: Malwarebytes Corporation
  16. description: Malwarebytes Web Access Control
  17. Bug check description: This indicates that a pool header is corrupt.
  18. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  19. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
  20. Google query: Malwarebytes Corporation BAD_POOL_HEADER
  21.  
  22.  
  23.  
  24. On Fri 2016-04-15 06:52:46 GMT your computer crashed
  25. crash dump file: C:\WINDOWS\memory.dmp
  26. This was probably caused by the following module: mwac.sys (mwac+0x6135)
  27. Bugcheck code: 0x19 (0x20, 0xFFFFE0004025E740, 0xFFFFE0004025E760, 0x402000C)
  28. Error: BAD_POOL_HEADER
  29. file path: C:\WINDOWS\system32\drivers\mwac.sys
  30. product: Malwarebytes Web Access Control
  31. company: Malwarebytes Corporation
  32. description: Malwarebytes Web Access Control
  33. Bug check description: This indicates that a pool header is corrupt.
  34. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  35. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
  36. Google query: Malwarebytes Corporation BAD_POOL_HEADER
  37.  
  38.  
  39.  
  40. On Sun 2016-04-03 11:55:44 GMT your computer crashed
  41. crash dump file: C:\WINDOWS\Minidump\040316-28703-01.dmp
  42. This was probably caused by the following module: mwac.sys (mwac+0x90BF)
  43. Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE001BA4EC658)
  44. Error: BAD_POOL_CALLER
  45. file path: C:\WINDOWS\system32\drivers\mwac.sys
  46. product: Malwarebytes Web Access Control
  47. company: Malwarebytes Corporation
  48. description: Malwarebytes Web Access Control
  49. Bug check description: This indicates that the current thread is making a bad pool request.
  50. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  51. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
  52. Google query: Malwarebytes Corporation BAD_POOL_CALLER
  53.  
  54.  
  55.  
  56. On Sun 2016-04-03 09:07:49 GMT your computer crashed
  57. crash dump file: C:\WINDOWS\Minidump\040316-15671-01.dmp
  58. This was probably caused by the following module: mwac.sys (mwac+0x90BF)
  59. Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE000CB917C98)
  60. Error: BAD_POOL_CALLER
  61. file path: C:\WINDOWS\system32\drivers\mwac.sys
  62. product: Malwarebytes Web Access Control
  63. company: Malwarebytes Corporation
  64. description: Malwarebytes Web Access Control
  65. Bug check description: This indicates that the current thread is making a bad pool request.
  66. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  67. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
  68. Google query: Malwarebytes Corporation BAD_POOL_CALLER
  69.  
  70.  
  71.  
  72. On Fri 2016-04-01 19:35:19 GMT your computer crashed
  73. crash dump file: C:\WINDOWS\Minidump\040116-16031-01.dmp
  74. This was probably caused by the following module: mwac.sys (mwac+0x6135)
  75. Bugcheck code: 0x19 (0x20, 0xFFFFE00171F524F0, 0xFFFFE00171F52510, 0x402000C)
  76. Error: BAD_POOL_HEADER
  77. file path: C:\WINDOWS\system32\drivers\mwac.sys
  78. product: Malwarebytes Web Access Control
  79. company: Malwarebytes Corporation
  80. description: Malwarebytes Web Access Control
  81. Bug check description: This indicates that a pool header is corrupt.
  82. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
  83. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
  84. Google query: Malwarebytes Corporation BAD_POOL_HEADER
  85.  
  86.  
  87.  
  88.  
  89.  
  90. --------------------------------------------------------------------------------
  91. Conclusion
  92. --------------------------------------------------------------------------------
  93.  
  94. 5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
  95.  
  96. mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation)
  97.  
  98. If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
  99.  
  100.  
  101. Read the topic general suggestions for troubleshooting system crashes for more information.
  102.  
  103. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!