Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Not sure where to go from here. (I have my MEMORY.DMP file)


  • Please log in to reply
8 replies to this topic

#1 G33kman

G33kman

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:25 PM

Posted 13 March 2017 - 08:55 PM

So over the last few days I have had random BSOD's and I have been trying to determine the root cause. I downloaded windbg and looked at my MEMORY.DMP file but I'm not too familiar with diagnosing blue screen problems. I have been a computer tech for 15 years and do have knowledge with a lot of computer issues but have never really looked into these types of problems. Now that it is happening on my computer I feel like it's time I really figure out how to diagnose these types of issues. So here's the output from my MEMORY.DMP file in windbg.

 

Anyone with some knowledge would be greatly appreciated.

Thanks!

Ryan

 

 

 
Microsoft ® Windows Debugger Version 10.0.14321.1024 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\tl2k5\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff803`40c11000 PsLoadedModuleList = 0xfffff803`40f16060
Debug session time: Mon Mar 13 20:35:22.575 2017 (UTC - 5:00)
System Uptime: 0 days 1:21:11.264
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00d3c018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 124, {0, ffff9d8757947028, bf800000, 124}
 
Page d2a1d not present in the dump file. Type ".hh dbgerr004" for details
Page d2a1d not present in the dump file. Type ".hh dbgerr004" for details
Page d36c1 not present in the dump file. Type ".hh dbgerr004" for details
Page d36c1 not present in the dump file. Type ".hh dbgerr004" for details
Page 4b2f not present in the dump file. Type ".hh dbgerr004" for details
Page 4b2f not present in the dump file. Type ".hh dbgerr004" for details
Page d2996 not present in the dump file. Type ".hh dbgerr004" for details
Page d2996 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : GenuineIntel
 
Followup:     MachineOwner
---------
 
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9d8757947028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  14393.693.amd64fre.rs1_release.161220-1747
 
SYSTEM_MANUFACTURER:  ASUS
 
SYSTEM_PRODUCT_NAME:  All Series
 
SYSTEM_SKU:  All
 
SYSTEM_VERSION:  System Version
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  2102
 
BIOS_DATE:  10/28/2014
 
BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
 
BASEBOARD_PRODUCT:  H87M-PRO
 
BASEBOARD_VERSION:  Rev X.0x
 
DUMP_TYPE:  1
 
BUGCHECK_P1: 0
 
BUGCHECK_P2: ffff9d8757947028
 
BUGCHECK_P3: bf800000
 
BUGCHECK_P4: 124
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CPU_COUNT: 8
 
CPU_MHZ: dac
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 3c
 
CPU_STEPPING: 3
 
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  DyingLightGame.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_SESSION_HOST:  DESKTOP-BG2L3PL
 
ANALYSIS_SESSION_TIME:  03-13-2017 20:54:18.0900
 
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
 
STACK_TEXT:  
ffffd481`fcd1f6f8 fffff803`4146727f : 00000000`00000124 00000000`00000000 ffff9d87`57947028 00000000`bf800000 : nt!KeBugCheckEx
ffffd481`fcd1f700 fffff803`40e3c34c : ffff9d87`57947028 ffff9d87`572d29a0 ffff9d87`572d29a0 ffff9d87`572d29a0 : hal!HalBugCheckSystem+0xcf
ffffd481`fcd1f740 fffff803`4146776c : 00000000`00000728 00000000`00000007 ffffd481`fcd1fb30 00000000`00000000 : nt!WheaReportHwError+0x258
ffffd481`fcd1f7a0 fffff803`41467ac4 : ffff9d87`00000010 ffff9d87`572d29a0 ffffd481`fcd1f948 ffff9d87`572d29a0 : hal!HalpMcaReportError+0x50
ffffd481`fcd1f8f0 fffff803`414679ae : ffff9d87`572d1ff0 00000000`00000001 00000000`00000007 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
ffffd481`fcd1f940 fffff803`41467bee : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffd481`fcd1f980 fffff803`41467d70 : ffff9d87`572d1ff0 ffffd481`fcd1fbb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd481`fcd1f9b0 fffff803`40d655fb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd481`fcd1f9e0 fffff803`40d65384 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd481`fcd1fb20 fffff803`40d660c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x184
00000000`00efe958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemCall64
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  7bc0173fbce53ba045942f43b572f7e8981c1861
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1976b94477f596af541106a3ba1b84fe6b50cad9
 
THREAD_SHA1_HASH_MOD:  bba6629b38ee48af58586b1285e003efb528212b
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: GenuineIntel
 
IMAGE_NAME:  GenuineIntel
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
 
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
 
PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_CACHE
 
TARGET_TIME:  2017-03-14T01:35:22.000Z
 
OSBUILD:  14393
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-12-21 00:50:57
 
BUILDDATESTAMP_STR:  161220-1747
 
BUILDLAB_STR:  rs1_release
 
BUILDOSVER_STR:  10.0.14393.693.amd64fre.rs1_release.161220-1747
 
ANALYSIS_SESSION_ELAPSED_TIME: 5fe
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache
 
FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
 
Followup:     MachineOwner
---------
 


BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:25 PM

Posted 13 March 2017 - 09:04 PM

Hi, Ryan,

Please follow these BSOD posting instructions and attach the requested files in your next reply.

Thanks.

Useful information!
Please only use the .ZIP compression format, do not use .7z, .rar, etc.!!!

 

P.S. If you don't mind too, can you zip up MEMORY.DMP and upload it to a trustworthy file-sharing service, e.g. OneDrive or DropBox, providing me with the URL in your next reply?


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 G33kman

G33kman
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:25 PM

Posted 13 March 2017 - 09:46 PM

Hey,

Thanks for your quick reply. My apologies for not reading that earlier I should have known better. Lol

Attached is the Sysnative output zip and I will provide a link below to the memory.dmp file.

Thanks for your assistance!

 

https://drive.google.com/open?id=0B_pT5uO6dOTVMzRfWDBuVURWZXc

Attached Files



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:25 PM

Posted 13 March 2017 - 10:15 PM

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR bugcheck:
2: kd> .bugcheck
Bugcheck code 00000124
Arguments 00000000`00000000 ffffe209`0e725028 00000000`bf800000 00000000`00000124
If we use the !errrec command on the second parameter of the bugcheck:
2: kd> !errrec ffffe2090e725028
===============================================================================
Common Platform Error Record @ ffffe2090e725028
-------------------------------------------------------------------------------
Record Id     : 01d29c4b205d5e3d
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/14/2017 0:13:20 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe2090e7250a8
Section       @ ffffe2090e725180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe2090e7250f0
Section       @ ffffe2090e725240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb da 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe2090e725240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe2090e725138
Section       @ ffffe2090e7252c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 2 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x00000007c142a180
  Misc.       : 0x0000000000000086
It indicates a Cache Error; the rest of the dumps indicate similar cache errors, but at different locations. Anyway... it's great you aren't overclocking:
2: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
What I find particularly interesting is that there are third-party Logitech drivers all over the place:
ffffd481`fca50848  fffff806`efd21c11*** ERROR: Module load completed but symbols could not be loaded for LEqdUsb.Sys LEqdUsb+0x1c11
ffffd481`fca504c0  fffff806`f02e8b69*** ERROR: Module load completed but symbols could not be loaded for LMouFilt.Sys LMouFilt+0x8b69
Here's some information about each driver:
2: kd> lmvm LEqdUsb
start             end                 module name
fffff803`bc320000 fffff803`bc337000   LEqdUsb    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\LEqdUsb.Sys
    Image name: LEqdUsb.Sys
    Timestamp:        Tue Jun 09 15:25:30 2015 (55773DAA)
    CheckSum:         00021EC5
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm LMouFilt
start             end                 module name
fffff803`bc8e0000 fffff803`bc8f4000   LMouFilt   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\LMouFilt.Sys
    Image name: LMouFilt.Sys
    Timestamp:        Tue Jun 09 15:25:39 2015 (55773DB3)
    CheckSum:         00018946
    ImageSize:        00014000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Additionally, there are NVIDIA drivers everywhere:
ffffd482`034fd680  fffff806`f049d54d nvlddmkm+0xfd54d
ffffd482`034fd2a8  fffff806`f04ee9f5 nvlddmkm+0x14e9f5ffffd482`034fd2b8  
fffff806`f04e86a4 nvlddmkm+0x1486a4ffffd482`034fd2d8  
fffff806`f04eb9e9 nvlddmkm+0x14b9e9
Here are the temps on the system:
1: kd> !tzinfo 0xffff9d87579a7950
ThermalInfo @ 0xffff9d87579a7950
  Stamp:         00000006  Constant1:  00000000  Constant2:   00000000
  Period:        00000000  ActiveCnt:  00000005  MinThrottle: 00000000
  Current Temperature:                 00000bc2 (301.0K)
  Passive TripPoint Temperature:       00000000 (0.0K)
  Active TripPoint Temperature 0:      00000dcc (353.2K)
  Active TripPoint Temperature 1:      00000cd2 (328.2K)
  Active TripPoint Temperature 2:      00000aac (273.2K)
  Active TripPoint Temperature 3:      00000aac (273.2K)
  Active TripPoint Temperature 4:      00000aac (273.2K)
  Critical TripPoint Temperature:      00000ec6 (378.2K)
  Hibernate TripPoint Temperature:     00000000 (0.0K)
303.0K is about 30°C... which is pretty good.

Typically, 0x124s are caused by hardware problems, but in this case I'm not sure. We definitely need many dumps to come up with a definite diagnosis. I'd start troubleshooting by reinstalling all Logitech drivers. Then, reinstall your NVIDIA graphics driver, using version 368.69, as it's pretty stable. But, please perform a Custom Installation and only install the Graphics Drivers and PhysX software. :exclame: DO NOT INSTALL ANY 3D DRIVERS!!!

Then run the Intel Processor Diagnostic Tool to check for any obvious CPU problems. Also, since you work in computer repair, how about swapping CPUs? :)

Edited by bwv848, 14 March 2017 - 02:46 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 G33kman

G33kman
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:25 PM

Posted 14 March 2017 - 11:59 AM

Hey that's definitely some good options for me to look into. I'm currently at work so I will be checking into these options when I get home tonight. I will update when I try these things to let you know how things went.



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:25 PM

Posted 14 March 2017 - 02:48 PM

Thanks for the update. :) I improved on my analysis to make it look better...

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 G33kman

G33kman
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:25 PM

Posted 21 March 2017 - 04:08 PM

Hey sorry it's taken me forever to reply I haven't had much time (or energy to work on my computer) since work has been crazy but I finally figured out the issue. I uninstalled and reinstalled the Logitech drivers and did the same with my Nvidia drivers with the version you listed. I ended up pulling my system apart to see if it was something physical and low and behold the heatsink had (somehow) popped off the board partially.

I reapplied new thermal paste and reinstalled everything and the system works great! I ran the IPDT and everything passed and haven't had a single issue since.

Thank you so much for your assistance with this issue and again sorry for the late reply.

Ryan



#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:10:25 PM

Posted 21 March 2017 - 04:43 PM

I'm glad to hear that, Ryan! :)

 

Regards,

bwv848


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#9 Nabctero

Nabctero

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:10:25 AM

Posted 21 March 2017 - 10:37 PM

Hey,

Thanks for your quick reply. My apologies for not reading that earlier I should have known better. Lol

Attached is the Sysnative output zip and I will provide a link below to the memory.dmp file.

Thanks for your assistance!

 

https://drive.google.com/open?id=0B_pT5uO6dOTVMzRfWDBuVURWZXc

Thanks for your answer ,






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users