Advertisement
Guest User

Untitled

a guest
Jan 21st, 2018
135
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.05 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 (6 procs) Free x64
  5. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  6. Built by: 9600.18895.amd64fre.winblue_ltsb.180101-1800
  7. Machine Name:
  8. Kernel base = 0xfffff800`e4c8a000 PsLoadedModuleList = 0xfffff800`e4f576d0
  9. Debug session time: Sun Jan 21 15:05:19.999 2018 (UTC - 5:00)
  10. System Uptime: 0 days 9:05:59.704
  11. *******************************************************************************
  12. * *
  13. * Bugcheck Analysis *
  14. * *
  15. *******************************************************************************
  16.  
  17. DPC_WATCHDOG_VIOLATION (133)
  18. The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
  19. or above.
  20. Arguments:
  21. Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
  22. component can usually be identified with a stack trace.
  23. Arg2: 0000000000000501, The DPC time count (in ticks).
  24. Arg3: 0000000000000500, The DPC time allotment (in ticks).
  25. Arg4: 0000000000000000
  26.  
  27. Debugging Details:
  28. ------------------
  29.  
  30. TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
  31.  
  32. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  33.  
  34. BUGCHECK_STR: 0x133
  35.  
  36. PROCESS_NAME: System
  37.  
  38. CURRENT_IRQL: d
  39.  
  40. LAST_CONTROL_TRANSFER: from fffff800e4e14e3c to fffff800e4ddeea0
  41.  
  42. STACK_TEXT:
  43. fffff800`e6853c88 fffff800`e4e14e3c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
  44. fffff800`e6853c90 fffff800`e4d39de7 : 00000000`00000000 00000000`00000000 00000000`00000001 ffffe001`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ee6c
  45. fffff800`e6853d20 fffff800`e4c22b4f : 00000000`000000ff ffffe001`6fb6f8e0 fffff800`e4c6e910 00000000`00000000 : nt!KeClockInterruptNotify+0x787
  46. fffff800`e6853f40 fffff800`e4d56bb3 : fffff800`e4c6e870 fffff800`e4d7faf7 fffff800`65a0ff70 fffff800`e68448b0 : hal!HalpTimerClockInterrupt+0x4f
  47. fffff800`e6853f70 fffff800`e4de03da : fffff800`e4c6e870 ffffe001`6f7bff40 fffff800`e68448b0 fffff800`e68448b0 : nt!KiCallInterruptServiceRoutine+0xa3
  48. fffff800`e6853fb0 fffff800`e4de08a7 : 00000000`0000000a fffff800`e4f73180 fffff800`e6844618 fffff800`e4d02c64 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
  49. fffff800`e6844580 fffff800`e4d0b62b : 00000000`00000021 00000000`00da7a64 00000000`00000000 00000000`0000003f : nt!KiInterruptDispatchNoLockNoEtw+0x37
  50. fffff800`e6844710 fffff800`e4ddfc46 : ffffe001`6dbf3190 fffff800`e4c216b5 ffffe001`6d966620 00000000`00000002 : nt!KxWaitForSpinLockAndAcquire+0x1f
  51. fffff800`e6844740 fffff800`64ed8a2f : ffffe001`6bf2df00 fffff800`65a0ff70 fffff800`e68448b0 ffffe001`6d715080 : nt!KeSynchronizeExecution+0x36
  52. fffff800`e6844780 fffff800`659c5e78 : 00000000`00000000 fffff800`e68448a0 ffffe001`6dbf3040 00000000`00000000 : dxgkrnl!DpSynchronizeExecution+0xaf
  53. fffff800`e68447d0 00000000`00000000 : fffff800`e68448a0 ffffe001`6dbf3040 00000000`00000000 fffff800`e68448a0 : nvlddmkm+0xc8e78
  54.  
  55.  
  56. STACK_COMMAND: kb
  57.  
  58. FOLLOWUP_IP:
  59. dxgkrnl!DpSynchronizeExecution+af
  60. fffff800`64ed8a2f 8806 mov byte ptr [rsi],al
  61.  
  62. SYMBOL_STACK_INDEX: 9
  63.  
  64. SYMBOL_NAME: dxgkrnl!DpSynchronizeExecution+af
  65.  
  66. FOLLOWUP_NAME: MachineOwner
  67.  
  68. MODULE_NAME: dxgkrnl
  69.  
  70. IMAGE_NAME: dxgkrnl.sys
  71.  
  72. DEBUG_FLR_IMAGE_TIMESTAMP: 59e1c8f5
  73.  
  74. FAILURE_BUCKET_ID: X64_0x133_dxgkrnl!DpSynchronizeExecution+af
  75.  
  76. BUCKET_ID: X64_0x133_dxgkrnl!DpSynchronizeExecution+af
  77.  
  78. Followup: MachineOwner
  79. ---------
  80.  
  81.  
  82. This free analysis is provided by OSR Open Systems Resources, Inc.
  83. Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
  84. Show DivCrash Code Links
  85. Show DivLoaded Module List
  86. Show DivRaw Stack Contents
  87. Show DivDump Header Information
  88. Show DivStrings
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement