Windows 10: BSOD error, please help

Hello all,


Occasionaly I receive a BSOD with 90% with the same error code, if someone can help me with this


Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\gebruiker\Downloads\070519-6609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`0809d000 PsLoadedModuleList = 0xfffff802`0844a170
Debug session time: Fri Jul 5 22:00:59.312 2019 (UTC + 2:00)
System Uptime: 0 days 4:20:11.988
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`08247ab0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffb502`7df91880=000000000000001e
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8020824f777, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 6

Key : Analysis.Elapsed.Sec
Value: 15

Key : Analysis.Memory.CommitPeak.Mb
Value: 67


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7A78

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.A0

BIOS_DATE: 07/03/2018

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z270 GAMING M5 (MS-7A78)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8020824f777

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff802084e9388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%p verwijst naar geheugen op 0x%p. Het geheugen kan niet worden %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff802`0824f777 498b08 mov rcx,qword ptr [r8]

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: RuneLite.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: GEBRUIKER-PC

ANALYSIS_SESSION_TIME: 07-05-2019 22:02:50.0094

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

TRAP_FRAME: ffffa50000007000 -- (.trap 0xffffa50000007000)
Unable to read trap frame at ffffa500`00007000

LAST_CONTROL_TRANSFER: from fffff80208159fbd to fffff80208247ab0

STACK_TEXT:
ffffb502`7df91878 fffff802`08159fbd : 00000000`0000001e ffffffff`c0000005 fffff802`0824f777 00000000`00000000 : nt!KeBugCheckEx
ffffb502`7df91880 fffff802`08258742 : fffff802`0846bf28 00000000`00000e00 ffffa500`00007000 fffff802`0846b780 : nt!KiDispatchException+0x58d
ffffb502`7df91f30 fffff802`08254e9c : 00000001`00000000 fffff802`082434aa 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffb502`7df92110 fffff802`0824f777 : 00000000`00000000 fffff802`0817c20a 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x2dc
ffffb502`7df922a0 fffff802`0817c20a : 00000000`00000000 00000000`00000000 fffff802`083957d0 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffb502`7df922b0 fffff802`0817b888 : fffff802`0846af00 00000000`000000bc ffffdf8c`00000002 ffffdf8c`00000000 : nt!MiGetPage+0x50a
ffffb502`7df92380 fffff802`080cbf36 : 8a000004`3bbbb867 ffffb502`7df928c0 00000000`00000000 00000234`46798000 : nt!MiGetPageChain+0x178
ffffb502`7df924b0 fffff802`0817d477 : ffffb502`7df925e0 ffffb502`7df925c0 00000000`00000002 ffffdf8c`00000001 : nt!MiCreateSharedZeroPages+0x2f6
ffffb502`7df92580 fffff802`08179b3b : ffffb90e`00000111 00000000`00000000 ffffa200`06767940 00000000`00000002 : nt!MiResolveDemandZeroFault+0x287
ffffb502`7df92670 fffff802`08181ae8 : ffffb502`7df928c0 00000000`00000002 ffffb502`7df927c0 fffff802`0818062b : nt!MiResolveProtoPteFault+0xe1b
ffffb502`7df92740 fffff802`0817f03e : ffffb502`7df928c0 00000000`00000001 00000000`c0000016 ffffb502`00000000 : nt!MiDispatchFault+0xd48
ffffb502`7df92890 fffff802`082551da : ffffdf8c`5ff99700 00000000`00000000 00000234`45a92040 00000234`3fdf0000 : nt!MmAccessFault+0x21e
ffffb502`7df92a00 00000000`70fbd973 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x31a
000000d3`3624ee50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x70fbd973


THREAD_SHA1_HASH_MOD_FUNC: e1910c6d210718f3130c2603b666c100f76f6414

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 21cd9103054d520e9f80aa6035fd2321c21e57a1

THREAD_SHA1_HASH_MOD: fe34192f63d13620a8987d294372ee74d699cfee

FOLLOWUP_IP:
nt!KiDispatchException+58d
fffff802`08159fbd 90 nop

FAULT_INSTR_CODE: cccccc90

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiDispatchException+58d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5cf9f460

IMAGE_VERSION: 10.0.17134.829

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 58d

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiDispatchException

BUCKET_ID: 0x1E_c0000005_R_nt!KiDispatchException

PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nt!KiDispatchException

TARGET_TIME: 2019-07-05T20:00:59.000Z

OSBUILD: 17134

OSSERVICEPACK: 829

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: 2019-06-07 07:21:36

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 3ca6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!kidispatchexception

FAILURE_ID_HASH: {8cda4994-5937-8d70-909d-3f5236ba02c6}

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



:)

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

Just got a BSOD with error driver irql_not_less_or_equal (nwifi.sys)

Hi Willy,

Welcome to Microsoft Community.

I understand your concerned. Let me help you to fix the issue.

To assist you better, please provide us more information.

• 
  What is the make and model of the computer?
  
• When exactly do you get this error message BSOD?

Meanwhile, let’s try simple steps and check if this helps in resolving the issue. I would suggest you to go to the below link and try the steps.

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Also, I suggest you to remove all the connected external hardware device and check.

Hope this helps. If you need further assistance with Windows, let us know and will be glad to help you.