Advertisement
Guest User

Untitled

a guest
Apr 1st, 2015
285
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.11 KB | None | 0 0
  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 13/02/2015 20:26:03 GMT your computer crashed
  9. crash dump file: C:\Windows\Minidump\021315-62088-01.dmp
  10. This was probably caused by the following module: ntoskrnl.exe (nt+0x7769A)
  11. Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8006701B50, 0xFFFFF80003C073D0)
  12. Error: CUSTOM_ERROR
  13. file path: C:\Windows\system32\ntoskrnl.exe
  14. product: Microsoft® Windows® Operating System
  15. company: Microsoft Corporation
  16. description: NT Kernel & System
  17. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  18.  
  19.  
  20.  
  21. On Fri 13/02/2015 20:26:03 GMT your computer crashed
  22. crash dump file: C:\Windows\memory.dmp
  23. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
  24. Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA8006701B50, 0xFFFFF80003C073D0)
  25. Error: DRIVER_POWER_STATE_FAILURE
  26. Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
  27. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  28. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  29.  
  30.  
  31.  
  32. On Mon 11/08/2014 18:14:29 GMT your computer crashed
  33. crash dump file: C:\Windows\Minidump\081114-20857-01.dmp
  34. This was probably caused by the following module: athrx.sys (athrx+0x1D0469)
  35. Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007E94469, 0xFFFFF8800393F708, 0xFFFFF8800393EF60)
  36. Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  37. file path: C:\Windows\system32\drivers\athrx.sys
  38. product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
  39. company: Qualcomm Atheros Communications, Inc.
  40. description: Qualcomm Atheros Extensible Wireless LAN device driver
  41. Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
  42. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  43. 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: athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
  44. Google query: Qualcomm Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  45.  
  46.  
  47.  
  48.  
  49.  
  50. --------------------------------------------------------------------------------
  51. Conclusion
  52. --------------------------------------------------------------------------------
  53.  
  54. 3 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:
  55.  
  56. athrx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
  57.  
  58. If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
  59.  
  60.  
  61. Read the topic general suggestions for troubleshooting system crashes for more information.
  62.  
  63. 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