Advertisement
Guest User

Untitled

a guest
Nov 17th, 2019
147
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.65 KB | None | 0 0
  1. On Sat 16.11.2019 08:41:09 your computer crashed or a problem was reported
  2. crash dump file: C:\WINDOWS\Minidump\111619-5781-01.dmp
  3. This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
  4. Bugcheck code: 0xA (0x15004100, 0xD, 0x0, 0xFFFFF8075A0073D2)
  5. Error: IRQL_NOT_LESS_OR_EQUAL
  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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
  11. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
  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 Sat 16.11.2019 08:41:09 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!setjmpex+0x8149)
  19. Bugcheck code: 0xA (0x15004100, 0xD, 0x0, 0xFFFFF8075A0073D2)
  20. Error: IRQL_NOT_LESS_OR_EQUAL
  21. Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
  22. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
  23. 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