BSOD x101 and x124

[discourage123]

I've been getting BSOD over the past few weeks. Sometimes everyday, sometimes once a week. I've used bluescreenview to look at dmp its its saying its caused by driver ntoskrnl.exe which i think is memory. Wanted to know if anyone thinks the same. Here is the dmp from bluescreenview

Specs:
MSI z170a gaming m5
i7 6700k
pny ddr4-2132
nvidia geforce gtx 970
750w psu

Dump File: 121316-6973-01.dmp
Crash Time: 12/13/2016 7:36:35 PM
Bug Check Code: 0x00000101
Parameter 1: 00000000`00000019
Parameter 2: 00000000`00000000
Parameter 3:fffff880`03717180
Parameter 4:00000000`00000006
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+70400
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version:6.1.7601.23572 (win7sp1_ldr.161011-0600)
Processor: x64
Crash Address: ntoskrnl.exe+70400
Full Path: C:\Windows\Minidump\121316-6973-01.dmp
Processors Count: 8
Major Version: 15
Minor Version: 7601
Dump File Size: 354,764
Dumpe File Time: 12/13/2016 7:37:41 PM

Dump File: 121816-6052-01 - Copy.dmp
Crash Time: 12/18/2016 9:06:34 PM
Bug Check Code: 0x00000124
Parameter 1: 00000000`00000000
Parameter 2: fffffa80`0eb3e028
Parameter 3:00000000`be000000
Parameter 4:00000000`00800400
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+70400
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 6.1.7601.23572 (win7sp1_ldr.161011-0600)
Processor: x64
Crash Address: ntoskrnl.exe+70400
Full Path: C:\Windows\Minidump\121816-6052-01 - Copy.dmp
Processors Count: 8
Major Version: 15
Minor Version: 7601
Dump File Size: 354,893
Dumpe File Time: 12/18/2016 9:07:43 PM

EDIT: I've ran a full memtest and prime95 test with no issues.

 

[ICIT2LOL]

Hello and welcome discourage mate before we can help we need these to be done in this order

System Info - See Your System Specs

&

Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions

 

[torchwood]

And
this tool please


http://go.microsoft.com/fwlink/?LinkID=52012

Roy

 

[discourage123]

Hello and welcome discourage mate before we can help we need these to be done in this order

System Info - See Your System Specs

&

Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions

Done

 

[ICIT2LOL]

Ok mate and thanks now two things - one what memtest did you use because this is the only one we recommend and it has to be run for at least 8 passes any less and you may as well not bother RAM - Test with Memtest86+ I only ask because the Windows memtest feature if you used that is not really much good at all.

If you need to run the memtest I linked you can stop the run if errors come up before 8 passes and it is best left for an overnight run as it does take some time to complete.

Could you also send the temps on the machine please use this Speccy - Free Download - Piriform

 

[discourage123]

Ok mate and thanks now two things - one what memtest did you use because this is the only one we recommend and it has to be run for at least 8 passes any less and you may as well not bother RAM - Test with Memtest86+ I only ask because the Windows memtest feature if you used that is not really much good at all.

If you need to run the memtest I linked you can stop the run if errors come up before 8 passes and it is best left for an overnight run as it does take some time to complete.

Could you also send the temps on the machine please use this Speccy - Free Download - Piriform

I ran memtest86 overnight, by the time I woke up it was finished and had 0 errors.

 

[ICIT2LOL]

Ok then I will assume it ran for the 8 passes which is a little strange because every memtest I have ever done would have run forever if I had not stopped it after 8 passes - it is important that that happened.

now the temps mate please.

 

[discourage123]

Ok then I will assume it ran for the 8 passes which is a little strange because every memtest I have ever done would have run forever if I had not stopped it after 8 passes - it is important that that happened.

now the temps mate please.

I'm using CPUID HWMonitor for this, (I'm currently gaming) CPU around 56-60 and GPU 46

 

[ICIT2LOL]

Well the temps are ok if you are gaming if it is at idle they are a tad high for my liking.

 

[discourage123]

Well the temps are ok if you are gaming if it is at idle they are a tad high for my liking.

Both BSOD are telling me its caused by ntoskrnl.exe, when I google it, i'm seeing post about memory issues, memory leaks, high memory usage. I'm currently 12gb or the 16gb with 75% physical memory. When i'm running everything I usually run i've seen physical memory as high as 90%. Any ideas?

 

[ICIT2LOL]

Ok mate that dump file can mean anything it is not something that can be used for fixing your problem.

It is more likely to do with this

[COLOR="Red"]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
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: fffffa800eb3e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value

and this

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 9E'00000000 (cache) 9E'00000000 (init)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Wow-64.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-9I73FSG

ANALYSIS_SESSION_TIME:  12-20-2016 16:00:38.0008

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
fffff880`03791b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  [COLOR="red"]X64_0x124_GenuineIntel_PROCESSOR_MAE[/COLOR]

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS:  [COLOR="red"]X64_0x124_GenuineIntel_PROCESSOR_MAE[/COLOR]

TARGET_TIME:  2016-12-19T02:06:34.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-10-12 01:57:55

BUILDDATESTAMP_STR:  161011-0600

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.23572.amd64fre.win7sp1_ldr.161011-0600

ANALYSIS_SESSION_ELAPSED_TIME: 30d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  [COLOR="red"]km:x64_0x124_genuineintel_processor_mae[/COLOR]

FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

Followup:     MachineOwner

We shall ahve to go in and do some more research.