Advertisement
Guest User

Untitled

a guest
Aug 10th, 2013
314
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.64 KB | None | 0 0
  1. Great, thanks.
  2.  
  3. All of the attached DMP files are of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.
  4.  
  5. A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).
  6.  
  7. If we run an !errrec on the address of the WER structure (2nd parameter), we get the following:
  8.  
  9.  
  10. ===============================================================================
  11. Section 2 : x86/x64 MCA
  12. -------------------------------------------------------------------------------
  13. Descriptor @ fffffa80086f9138
  14. Section @ fffffa80086f92c0
  15. Offset : 664
  16. Length : 264
  17. Flags : 0x00000000
  18. Severity : Fatal
  19.  
  20. Error : DCACHEL1_DRD_ERR (Proc 3 Bank 0)
  21. Status : 0xb669c00000000135
  22. Address : 0x000000011cd32c50
  23. Misc. : 0x0000000000000000
  24.  
  25. DCACHEL1_DRD_ERR = L1 Cache Data Read Error.
  26.  
  27. All of the dumps are consistent with the same processor and bank (0). Likely a faulty CPU.
  28.  
  29. Normally I would also assume possible motherboard software conflicts (motherboard utilities that communicate directly between the OS and the BIOS are known to cause issues 0x124 bugchecks at times).
  30.  
  31. HOWEVER -
  32.  
  33. MODULE_NAME: hardware
  34.  
  35. IMAGE_NAME: hardware
  36.  
  37. DEBUG_FLR_IMAGE_TIMESTAMP: 0
  38.  
  39. FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
  40.  
  41. BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
  42.  
  43. Due to the module / image name being 'hardware', this implies it is not driver or software related, but the processor itself.
  44.  
  45. As your temperatures appear to be within standard via the Speccy screenshot, your CPU itself is faulty and needs to be replaced.
  46.  
  47. Regards,
  48.  
  49. Patrick
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement