Advertisement
Guest User

Untitled

a guest
Aug 9th, 2013
94
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.61 KB | None | 0 0
  1. On Wed 8/7/2013 5:22:59 AM GMT your computer crashed
  2. crash dump file: C:\Windows\Minidump\080613-18907-01.dmp
  3. This was probably caused by the following module: hal.dll (hal+0x2D965)
  4. Bugcheck code: 0x124 (0x0, 0xFFFFFA80086F9028, 0xB669C000, 0x135)
  5. Error: WHEA_UNCORRECTABLE_ERROR
  6. file path: C:\Windows\system32\hal.dll
  7. product: Microsoft® Windows® Operating System
  8. company: Microsoft Corporation
  9. description: Hardware Abstraction Layer DLL
  10. Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
  11. This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
  12. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  13.  
  14.  
  15.  
  16. On Wed 8/7/2013 5:22:59 AM GMT your computer crashed
  17. crash dump file: C:\Windows\memory.dmp
  18. This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xF9)
  19. Bugcheck code: 0x124 (0x0, 0xFFFFFA80086F9028, 0xB669C000, 0x135)
  20. Error: WHEA_UNCORRECTABLE_ERROR
  21. file path: C:\Windows\system32\hal.dll
  22. product: Microsoft® Windows® Operating System
  23. company: Microsoft Corporation
  24. description: Hardware Abstraction Layer DLL
  25. Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
  26. This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
  27. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  28.  
  29.  
  30.  
  31. On Wed 8/7/2013 5:03:53 AM GMT your computer crashed
  32. crash dump file: C:\Windows\Minidump\080613-19219-01.dmp
  33. This was probably caused by the following module: ntoskrnl.exe (nt+0x52A451)
  34. Bugcheck code: 0x124 (0x0, 0xFFFFFA80090878F8, 0x0, 0x0)
  35. Error: WHEA_UNCORRECTABLE_ERROR
  36. file path: C:\Windows\system32\ntoskrnl.exe
  37. product: Microsoft® Windows® Operating System
  38. company: Microsoft Corporation
  39. description: NT Kernel & System
  40. Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
  41. This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
  42. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  43.  
  44.  
  45.  
  46. On Sun 8/4/2013 7:14:58 AM GMT your computer crashed
  47. crash dump file: C:\Windows\Minidump\080413-25927-01.dmp
  48. This was probably caused by the following module: ntoskrnl.exe (nt+0x52A451)
  49. Bugcheck code: 0x124 (0x0, 0xFFFFFA8008FFE038, 0x0, 0x0)
  50. Error: WHEA_UNCORRECTABLE_ERROR
  51. file path: C:\Windows\system32\ntoskrnl.exe
  52. product: Microsoft® Windows® Operating System
  53. company: Microsoft Corporation
  54. description: NT Kernel & System
  55. Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
  56. This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
  57. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement