Advertisement
Guest User

27674

a guest
Jan 10th, 2015
9
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.04 KB | None | 0 0
  1. Loading Dump File [K:\Windows Assessment and Deployment Kit\Debuggers\Dumps Jan 5 2015\010515-27674-01.dmp]
  2. Mini Kernel Dump File: Only registers and stack trace are available
  3.  
  4.  
  5. ************* Symbol Path validation summary **************
  6. Response Time (ms) Location
  7. OK C:\Windows
  8.  
  9. ************* Symbol Path validation summary **************
  10. Response Time (ms) Location
  11. Deferred http://msdl.microsoft.com/download/symbols
  12. Symbol search path is: http://msdl.microsoft.com/download/symbols
  13. Executable search path is: C:\Windows
  14. Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
  15. Product: WinNt, suite: TerminalServer SingleUserTS
  16. Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
  17. Machine Name:
  18. Kernel base = 0xfffff800`03650000 PsLoadedModuleList = 0xfffff800`03893890
  19. Debug session time: Mon Jan 5 21:43:14.790 2015 (UTC - 8:00)
  20. System Uptime: 0 days 3:22:23.742
  21. Loading Kernel Symbols
  22. .
  23.  
  24. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
  25. Run !sym noisy before .reload to track down problems loading symbols.
  26.  
  27. ..............................................................
  28. ................................................................
  29. ..............................................................
  30. Loading User Symbols
  31. Loading unloaded module list
  32. .......
  33. *******************************************************************************
  34. * *
  35. * Bugcheck Analysis *
  36. * *
  37. *******************************************************************************
  38.  
  39. Use !analyze -v to get detailed debugging information.
  40.  
  41. BugCheck 124, {0, fffffa8018875028, fa000000, 400405}
  42.  
  43. Probably caused by : GenuineIntel
  44.  
  45. Followup: MachineOwner
  46. ---------
  47.  
  48. 2: kd> !analyze -v
  49. *******************************************************************************
  50. * *
  51. * Bugcheck Analysis *
  52. * *
  53. *******************************************************************************
  54.  
  55. WHEA_UNCORRECTABLE_ERROR (124)
  56. A fatal hardware error has occurred. Parameter 1 identifies the type of error
  57. source that reported the error. Parameter 2 holds the address of the
  58. WHEA_ERROR_RECORD structure that describes the error conditon.
  59. Arguments:
  60. Arg1: 0000000000000000, Machine Check Exception
  61. Arg2: fffffa8018875028, Address of the WHEA_ERROR_RECORD structure.
  62. Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
  63. Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
  64.  
  65. Debugging Details:
  66. ------------------
  67.  
  68.  
  69. BUGCHECK_STR: 0x124_GenuineIntel
  70.  
  71. CUSTOMER_CRASH_COUNT: 1
  72.  
  73. DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  74.  
  75. PROCESS_NAME: FarCry4.exe
  76.  
  77. CURRENT_IRQL: f
  78.  
  79. ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
  80.  
  81. STACK_TEXT:
  82. fffff880`0396cb58 fffff800`03619a3b : 00000000`00000124 00000000`00000000 fffffa80`18875028 00000000`fa000000 : nt!KeBugCheckEx
  83. fffff880`0396cb60 fffff800`037dc463 : 00000000`00000001 fffffa80`187484a0 00000000`00000000 fffffa80`187484f0 : hal!HalBugCheckSystem+0x1e3
  84. fffff880`0396cba0 fffff800`03619700 : 00000000`00000728 fffffa80`187484a0 fffff880`0396cf30 fffff880`0396cf00 : nt!WheaReportHwError+0x263
  85. fffff880`0396cc00 fffff800`03619052 : fffffa80`187484a0 fffff880`0396cf30 fffffa80`187484a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
  86. fffff880`0396cd50 fffff800`03618f0d : 00000000`00000008 00000000`00000001 fffff880`0396cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
  87. fffff880`0396cd90 fffff800`0360ce88 : 00000000`00268e76 00000000`00268e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
  88. fffff880`0396cdc0 fffff800`036c44ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
  89. fffff880`0396cdf0 fffff800`036c4313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
  90. fffff880`0396cf30 00000000`6368c1cb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
  91. 00000000`15389588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6368c1cb
  92.  
  93.  
  94. STACK_COMMAND: kb
  95.  
  96. FOLLOWUP_NAME: MachineOwner
  97.  
  98. MODULE_NAME: GenuineIntel
  99.  
  100. IMAGE_NAME: GenuineIntel
  101.  
  102. DEBUG_FLR_IMAGE_TIMESTAMP: 0
  103.  
  104. IMAGE_VERSION:
  105.  
  106. FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
  107.  
  108. BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
  109.  
  110. ANALYSIS_SOURCE: KM
  111.  
  112. FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
  113.  
  114. FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
  115.  
  116. Followup: MachineOwner
  117. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement