Advertisement
JonathanGiunta

BSODs

Jun 4th, 2018
157
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.55 KB | None | 0 0
  1. On Mon 04/06/2018 22:09:03 your computer crashed or a problem was reported
  2. crash dump file: C:\Windows\Minidump\060418-14024-01.dmp
  3. This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
  4. Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x1593000, 0x374)
  5. Error: REGISTRY_ERROR
  6. file path: C:\Windows\system32\ntoskrnl.exe
  7. product: Microsoft® Windows® Operating System
  8. company: Microsoft Corporation
  9. description: NT Kernel & System
  10. Bug check description: This indicates that a severe registry error has occurred.
  11. This bug check indicates there is a problem related to your registry.
  12. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  13.  
  14.  
  15.  
  16. On Mon 04/06/2018 22:09:03 your computer crashed or a problem was reported
  17. crash dump file: C:\Windows\MEMORY.DMP
  18. This was probably caused by the following module: ntkrnlmp.exe (nt!IoRegisterFsRegistrationChangeMountAwareEx+0x123DA)
  19. Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x1593000, 0x374)
  20. Error: REGISTRY_ERROR
  21. Bug check description: This indicates that a severe registry error has occurred.
  22. This bug check indicates there is a problem related to your registry.
  23. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  24.  
  25.  
  26.  
  27. On Mon 04/06/2018 21:15:28 your computer crashed or a problem was reported
  28. crash dump file: C:\Windows\Minidump\060418-13634-01.dmp
  29. This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
  30. Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x1593000, 0x374)
  31. Error: REGISTRY_ERROR
  32. file path: C:\Windows\system32\ntoskrnl.exe
  33. product: Microsoft® Windows® Operating System
  34. company: Microsoft Corporation
  35. description: NT Kernel & System
  36. Bug check description: This indicates that a severe registry error has occurred.
  37. This bug check indicates there is a problem related to your registry.
  38. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  39.  
  40.  
  41.  
  42. On Mon 04/06/2018 21:00:40 your computer crashed or a problem was reported
  43. crash dump file: C:\Windows\Minidump\060418-13150-01.dmp
  44. This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
  45. Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x1593000, 0x374)
  46. Error: REGISTRY_ERROR
  47. file path: C:\Windows\system32\ntoskrnl.exe
  48. product: Microsoft® Windows® Operating System
  49. company: Microsoft Corporation
  50. description: NT Kernel & System
  51. Bug check description: This indicates that a severe registry error has occurred.
  52. This bug check indicates there is a problem related to your registry.
  53. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  54.  
  55.  
  56.  
  57. On Mon 04/06/2018 20:57:55 your computer crashed or a problem was reported
  58. crash dump file: C:\Windows\Minidump\060418-21356-01.dmp
  59. This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
  60. Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x1593000, 0x374)
  61. Error: REGISTRY_ERROR
  62. file path: C:\Windows\system32\ntoskrnl.exe
  63. product: Microsoft® Windows® Operating System
  64. company: Microsoft Corporation
  65. description: NT Kernel & System
  66. Bug check description: This indicates that a severe registry error has occurred.
  67. This bug check indicates there is a problem related to your registry.
  68. 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