BSOD: ntoskrnl.exe and more

axe0 · 13 Apr 2016

If the crashes persist, simply try to update the BIOS again for now :)

EUWDIAMOND · 13 Apr 2016

Doesn't help unfortunately :s

Here is the log. Is there anything you can derive from it?

axe0 · 13 Apr 2016

simply try to update the BIOS again for now :)

.

EUWDIAMOND · 13 Apr 2016

Will do it right now. Anything else?

EUWDIAMOND · 13 Apr 2016

Happened again, bios update did not fix the problem.

Can you please tell me what causes my PC to crash? We still have no clue whether drivers or hardware causes the issues and I'd like to actively change things and swap things out whatever needs to be done but I have no clue what the root of the problem is, please help me :)

I can also do it myself if you tell me how to analyze such a report and where I get the information on what caused the pc to stop.

axe0 · 14 Apr 2016

The BIOS isn't updated?

Code:

BiosMajorRelease = 5
BiosMinorRelease = 11
BiosVendor = American Megatrends Inc.
BiosVersion = P1.90
BiosReleaseDate = 09/03/2015

Btw, I'm thinking that we need to test your memory a bit more.
Below is a bit similar to another thread where I said that RAM was faulty.
Thread: Solved Daily BSOD - Windows 10 Forums

Code:

1: kd> !pte 0000000000041284
                                           VA 0000000000041284
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000208
contains 030000011C790867  contains 0000000000000000
pfn 11c790    ---DA--UWEV  not valid

Analyzing dumps isn't always as easy as some may think or as others may let it look like (thanks to there amount of experience), let me show you the output of the last dump without the usual stuff I normally load too.
Please don't get me wrong, I'd love to explain it, but it just isn't something that can be understand easily without looking at it numerous of times and researching what it means.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 213cca36000, 73c6, fffff58010804000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+15f0f )

Followup:     MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000213cca36000
Arg3: 00000000000073c6
Arg4: fffff58010804000

Debugging Details:
------------------


SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_DATE:  09/03/2015

BASEBOARD_PRODUCT:  Z170 Pro4S

BASEBOARD_VERSION:                        

BUGCHECK_P1: 41284

BUGCHECK_P2: 213cca36000

BUGCHECK_P3: 73c6

BUGCHECK_P4: fffff58010804000

BUGCHECK_STR:  0x1a_41284

CPU_COUNT: 4

CPU_MHZ: c78

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80102ff100f to fffff80102fcc760

STACK_TEXT:  
ffffd002`002b27a8 fffff801`02ff100f : 00000000`0000001a 00000000`00041284 00000213`cca36000 00000000`000073c6 : nt!KeBugCheckEx
ffffd002`002b27b0 fffff801`02f1ecb8 : ffffd002`002b2a80 fffff681`09e651b0 00000000`0000000e ffffe001`20cdb080 : nt! ?? ::FNODOBFM::`string'+0x15f0f
ffffd002`002b2810 fffff801`02fd6fa3 : ffffe001`20cdb080 0000009c`00000000 ffffe001`1bb42e80 ffffe001`1bb42e80 : nt!NtUnlockVirtualMemory+0x2b8
ffffd002`002b2a00 00007ffc`fd6886e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000009c`cbefe328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`fd6886e4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+15f0f
fffff801`02ff100f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+15f0f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  56fa1e56

IMAGE_VERSION:  10.0.10586.212

BUCKET_ID_FUNC_OFFSET:  15f0f

FAILURE_BUCKET_ID:  0x1a_41284_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x1a_41284_nt!_??_::FNODOBFM::_string_

PRIMARY_PROBLEM_CLASS:  0x1a_41284_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41284_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {c39d115f-eaa3-aeb6-09bd-1a63e83e1077}

Followup:     MachineOwner
---------

EUWDIAMOND · 14 Apr 2016

Thank you vey much. I will read the other thread and swap out modules again.

The bios is updated, 1.90 is the one you recommemded me to download. Look at the link, plenty of versions appear, from 1.90 ul to 3.xx. You told me to download the one that *imprpves shstem stability*, which is 1.90. Do i need to download a different one?

axe0 · 14 Apr 2016

simply try to update the BIOS again for now

With this I meant to try a newer version of the BIOS.

EUWDIAMOND · 30 Apr 2016

Good morning,

I can proudly say that this issue is FINALLY solved! I updated the BIOS to the latest version and took out on RAM Module, no bsods for the past 2 / 3 weeks :)!!! Thank you so so much for your help, you truly made my life better, you can be proud of yourself.

I am not sure whether my ram is faulty, I might even be able to put the other stick back in again, but as long as it runs with 1 stick I won't change anything. Updating the BIOS to the most recent version is what fixed it :)

axe0 · 30 Apr 2016

Glad to hear that :)