Advertisement
Guest User

27440

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