Advertisement
Guest User

Untitled

a guest
Nov 12th, 2013
64
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.06 KB | None | 0 0
  1. Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
  2. Online Crash Dump Analysis Service
  3. See http://www.osronline.com for more information
  4. Windows 8 Kernel Version 9600 MP (8 procs) Free x64
  5. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  6. Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
  7. Machine Name:
  8. Kernel base = 0xfffff803`f8e70000 PsLoadedModuleList = 0xfffff803`f9134990
  9. Debug session time: Tue Nov 12 09:07:12.677 2013 (UTC - 5:00)
  10. System Uptime: 0 days 0:19:37.380
  11. *******************************************************************************
  12. * *
  13. * Bugcheck Analysis *
  14. * *
  15. *******************************************************************************
  16.  
  17. KMODE_EXCEPTION_NOT_HANDLED (1e)
  18. This is a very common bugcheck. Usually the exception address pinpoints
  19. the driver/function that caused the problem. Always note this address
  20. as well as the link date of the driver/image that contains this address.
  21. Arguments:
  22. Arg1: ffffffffc0000005, The exception code that was not handled
  23. Arg2: fffff803f8f98202, The address that the exception occurred at
  24. Arg3: 0000000000000000, Parameter 0 of the exception
  25. Arg4: ffffffffffffffff, Parameter 1 of the exception
  26.  
  27. Debugging Details:
  28. ------------------
  29.  
  30. TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
  31.  
  32. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
  33.  
  34. FAULTING_IP:
  35. nt!PpmCheckSnapAllUtility+296
  36. fffff803`f8f98202 894140 mov dword ptr [rcx+40h],eax
  37.  
  38. EXCEPTION_PARAMETER1: 0000000000000000
  39.  
  40. EXCEPTION_PARAMETER2: ffffffffffffffff
  41.  
  42. READ_ADDRESS: fffff803f9122340: Unable to get special pool info
  43. fffff803f9122340: Unable to get special pool info
  44. GetUlongFromAddress: unable to read from fffff803f91bd208
  45. ffffffffffffffff
  46.  
  47. ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
  48.  
  49. BUGCHECK_STR: 0x1e_c0000005
  50.  
  51. CUSTOMER_CRASH_COUNT: 1
  52.  
  53. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  54.  
  55. PROCESS_NAME: palemoon.exe
  56.  
  57. CURRENT_IRQL: 2
  58.  
  59. EXCEPTION_RECORD: 0000000000000003 -- (.exr 0x3)
  60. Cannot read Exception record @ 0000000000000003
  61.  
  62. LAST_CONTROL_TRANSFER: from fffff803f9043e4e to fffff803f8fbdca0
  63.  
  64. CONTEXT: 4c000055409f894c -- (.cxr 0x4c000055409f894c)
  65. Unable to read context, Win32 error 0n30
  66.  
  67. STACK_TEXT:
  68. fffff803`fa84e8c8 fffff803`f9043e4e : 00000000`0000001e ffffffff`c0000005 fffff803`f8f98202 00000000`00000000 : nt!KeBugCheckEx
  69. fffff803`fa84e8d0 fffff803`f8fc51ed : fffff803`f9173000 fffff803`f8e70000 0003ed6c`00781000 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
  70. fffff803`fa84e910 fffff803`f8f509a5 : 00000000`00000000 fffff803`fa84ea40 fffff803`fa84f868 ffffe000`040d76d0 : nt!RtlpExecuteHandlerForException+0xd
  71. fffff803`fa84e940 fffff803`f8f5186b : fffff803`fa84f868 fffff803`fa84f570 fffff803`fa84f868 ffffd000`20aa6180 : nt!RtlDispatchException+0x455
  72. fffff803`fa84f040 fffff803`f8fc98c2 : 00000000`00000003 00000000`de054380 00000000`00000000 ffffe000`002e7758 : nt!KiDispatchException+0x61f
  73. fffff803`fa84f730 fffff803`f8fc7dfe : 00000008`00000005 ffffd000`f7ed0cd0 ffff41cd`c0504e6c 00000000`00000008 : nt!KiExceptionDispatch+0xc2
  74. fffff803`fa84f910 fffff803`f8f98202 : 00000035`ca985177 00000000`00000000 fffff803`fa84fba0 00000000`00000007 : nt!KiGeneralProtectionFault+0xfe
  75. fffff803`fa84faa0 fffff803`f8ef2202 : 00000000`00000001 fffff803`f8faab30 ffffe000`02323430 fffff803`f914bc70 : nt!PpmCheckSnapAllUtility+0x296
  76. fffff803`fa84fc30 fffff803`f8f36596 : fffff803`fa84fce0 fffff803`fa84fe80 00000000`00000000 fffff803`f914bc70 : nt!PpmCheckRun+0xd2
  77. fffff803`fa84fc60 fffff803`f8eef840 : fffff803`f9160f00 fffff803`f914bc70 fffff803`f9115cc0 fffff803`f91622a0 : nt!PpmCheckStart+0x7e
  78. fffff803`fa84fcf0 fffff803`f8eef520 : ffffe000`02233880 fffff803`f915e180 00000000`0000002a 00000002`83bb0a3e : nt!KiExecuteAllDpcs+0x1b0
  79. fffff803`fa84fe40 fffff803`f8fc0dd5 : 00000000`00000000 fffff803`f915e180 ffffd000`23b52b00 fffff803`f8e54900 : nt!KiRetireDpcList+0xd0
  80. fffff803`fa84ffb0 fffff803`f8fc0bd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
  81. ffffd000`23b52a40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
  82.  
  83.  
  84. FOLLOWUP_IP:
  85. nt!PpmCheckSnapAllUtility+296
  86. fffff803`f8f98202 894140 mov dword ptr [rcx+40h],eax
  87.  
  88. SYMBOL_STACK_INDEX: 7
  89.  
  90. SYMBOL_NAME: nt!PpmCheckSnapAllUtility+296
  91.  
  92. FOLLOWUP_NAME: MachineOwner
  93.  
  94. MODULE_NAME: nt
  95.  
  96. IMAGE_NAME: ntkrnlmp.exe
  97.  
  98. DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4
  99.  
  100. STACK_COMMAND: .cxr 0x4c000055409f894c ; kb
  101.  
  102. FAILURE_BUCKET_ID: X64_0x1e_c0000005_nt!PpmCheckSnapAllUtility+296
  103.  
  104. BUCKET_ID: X64_0x1e_c0000005_nt!PpmCheckSnapAllUtility+296
  105.  
  106. Followup: MachineOwner
  107. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement