API tools faq
paste
Advertisement
Guest User

MY LIFEE

a guest
Aug 30th, 2016
123
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.09 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 Tue 8/30/2016 5:03:08 PM GMT your computer crashed
  9. crash dump file: C:\WINDOWS\Minidump\083016-21296-01.dmp
  10. This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x6B27D)
  11. Bugcheck code: 0xC2 (0xB, 0xFFFFE001B34A2000, 0x570000, 0xFFFFE001B34A2580)
  12. Error: BAD_POOL_CALLER
  13. file path: C:\WINDOWS\system32\drivers\bcmwl664.sys
  14. product: Broadcom 802.11 Network Adapter wireless driver
  15. company: Broadcom Corporation
  16. description: Broadcom 802.11 Network Adapter wireless driver
  17. Bug check description: This indicates that the current thread is making a bad pool request.
  18. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
  20. Google query: Broadcom Corporation BAD_POOL_CALLER
  21.  
  22.  
  23.  
  24. On Tue 8/30/2016 5:03:08 PM GMT your computer crashed
  25. crash dump file: C:\WINDOWS\memory.dmp
  26. This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x1CA5A)
  27. Bugcheck code: 0xC2 (0xB, 0xFFFFE001B34A2000, 0x570000, 0xFFFFE001B34A2580)
  28. Error: BAD_POOL_CALLER
  29. file path: C:\WINDOWS\system32\drivers\bcmwl664.sys
  30. product: Broadcom 802.11 Network Adapter wireless driver
  31. company: Broadcom Corporation
  32. description: Broadcom 802.11 Network Adapter wireless driver
  33. Bug check description: This indicates that the current thread is making a bad pool request.
  34. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
  36. Google query: Broadcom Corporation BAD_POOL_CALLER
  37.  
  38.  
  39.  
  40. On Tue 8/30/2016 4:55:43 PM GMT your computer crashed
  41. crash dump file: C:\WINDOWS\Minidump\083016-20437-01.dmp
  42. This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x686EC)
  43. Bugcheck code: 0xC2 (0x10, 0xFFFFE00205F205E0, 0x205000E, 0xFFFFE00205F205F0)
  44. Error: BAD_POOL_CALLER
  45. file path: C:\WINDOWS\system32\drivers\bcmwl664.sys
  46. product: Broadcom 802.11 Network Adapter wireless driver
  47. company: Broadcom Corporation
  48. description: Broadcom 802.11 Network Adapter wireless driver
  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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
  52. Google query: Broadcom Corporation BAD_POOL_CALLER
  53.  
  54.  
  55.  
  56. On Tue 8/30/2016 4:52:23 PM GMT your computer crashed
  57. crash dump file: C:\WINDOWS\Minidump\083016-20625-01.dmp
  58. This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
  59. Bugcheck code: 0xC2 (0xB, 0xFFFFE000C7510F00, 0x30007, 0xFFFFE000C7510F40)
  60. Error: BAD_POOL_CALLER
  61. file path: C:\WINDOWS\system32\ntoskrnl.exe
  62. product: Microsoft® Windows® Operating System
  63. company: Microsoft Corporation
  64. description: NT Kernel & System
  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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  68.  
  69.  
  70.  
  71. On Tue 8/30/2016 6:39:06 AM GMT your computer crashed
  72. crash dump file: C:\WINDOWS\Minidump\083016-22046-01.dmp
  73. This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
  74. Bugcheck code: 0x19 (0xE, 0xFFFFF8004AB27D70, 0xFFFFE0013411D520, 0x5B199EB21FA0375)
  75. Error: BAD_POOL_HEADER
  76. file path: C:\WINDOWS\system32\ntoskrnl.exe
  77. product: Microsoft® Windows® Operating System
  78. company: Microsoft Corporation
  79. description: NT Kernel & System
  80. Bug check description: This indicates that a pool header is corrupt.
  81. 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. This problem might also be caused because of overheating (thermal issue).
  82. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  83.  
  84.  
  85.  
  86. On Tue 8/30/2016 5:24:50 AM GMT your computer crashed
  87. crash dump file: C:\WINDOWS\Minidump\083016-19843-01.dmp
  88. This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x686EC)
  89. Bugcheck code: 0xC2 (0x7, 0x126C, 0x40D0000, 0xFFFFE000A3527010)
  90. Error: BAD_POOL_CALLER
  91. file path: C:\WINDOWS\system32\drivers\bcmwl664.sys
  92. product: Broadcom 802.11 Network Adapter wireless driver
  93. company: Broadcom Corporation
  94. description: Broadcom 802.11 Network Adapter wireless driver
  95. Bug check description: This indicates that the current thread is making a bad pool request.
  96. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  97. 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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
  98. Google query: Broadcom Corporation BAD_POOL_CALLER
  99.  
  100.  
  101.  
  102. On Tue 8/30/2016 5:20:06 AM GMT your computer crashed
  103. crash dump file: C:\WINDOWS\Minidump\083016-20250-01.dmp
  104. This was probably caused by the following module: ntoskrnl.exe (nt+0x148127)
  105. Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80322348127, 0xFFFFD000DDDE2458, 0xFFFFD000DDDE1C70)
  106. Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  107. file path: C:\WINDOWS\system32\ntoskrnl.exe
  108. product: Microsoft® Windows® Operating System
  109. company: Microsoft Corporation
  110. description: NT Kernel & System
  111. Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
  112. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  113. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  114.  
  115.  
  116.  
  117. On Tue 8/30/2016 4:34:34 AM GMT your computer crashed
  118. crash dump file: C:\WINDOWS\Minidump\083016-20046-02.dmp
  119. This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
  120. Bugcheck code: 0x7F (0x8, 0xFFFFD00173B48C30, 0x880101000000, 0xFFFFF80103F62F15)
  121. Error: UNEXPECTED_KERNEL_MODE_TRAP
  122. file path: C:\WINDOWS\system32\ntoskrnl.exe
  123. product: Microsoft® Windows® Operating System
  124. company: Microsoft Corporation
  125. description: NT Kernel & System
  126. Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
  127. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  128.  
  129.  
  130.  
  131. On Tue 8/30/2016 4:13:34 AM GMT your computer crashed
  132. crash dump file: C:\WINDOWS\Minidump\083016-20046-01.dmp
  133. This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x686EC)
  134. Bugcheck code: 0xC2 (0xB, 0xFFFFE000C6C2E4C0, 0x30014, 0xFFFFE000C6C2E500)
  135. Error: BAD_POOL_CALLER
  136. file path: C:\WINDOWS\system32\drivers\bcmwl664.sys
  137. product: Broadcom 802.11 Network Adapter wireless driver
  138. company: Broadcom Corporation
  139. description: Broadcom 802.11 Network Adapter wireless driver
  140. Bug check description: This indicates that the current thread is making a bad pool request.
  141. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  142. 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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
  143. Google query: Broadcom Corporation BAD_POOL_CALLER
  144.  
  145.  
  146.  
  147. On Tue 8/30/2016 3:10:02 AM GMT your computer crashed
  148. crash dump file: C:\WINDOWS\Minidump\082916-20953-01.dmp
  149. This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
  150. Bugcheck code: 0xC2 (0x7, 0x126C, 0x40D000C, 0xFFFFE00113C9C590)
  151. Error: BAD_POOL_CALLER
  152. file path: C:\WINDOWS\system32\ntoskrnl.exe
  153. product: Microsoft® Windows® Operating System
  154. company: Microsoft Corporation
  155. description: NT Kernel & System
  156. Bug check description: This indicates that the current thread is making a bad pool request.
  157. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  158. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  159.  
  160.  
  161.  
  162.  
  163.  
  164. --------------------------------------------------------------------------------
  165. Conclusion
  166. --------------------------------------------------------------------------------
  167.  
  168. 51 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
  169.  
  170. bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
  171.  
  172. 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.
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!