Blue Screen Error

[ferhatbegovics]

My computer keeps getting these error messages:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and something with KMODE.


I’ve updated all my drivers and I don’t have a clue what the problem could be, I doubt it’s the hardware as nothing has been recently installed.

Can anyone help please?

 

[Colif]

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[ferhatbegovics]

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 16299 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`b7013000 PsLoadedModuleList = 0xfffff803`b7374ff0
Debug session time: Sun Dec 17 19:37:29.738 2017 (UTC - 5:00)
System Uptime: 0 days 0:38:00.379
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803b7055cd4, The address that the exception occurred at
Arg3: ffff84006b14d598, Exception Record Address
Arg4: ffff84006b14cde0, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!KxWaitForLockOwnerShip+14
fffff803`b7055cd4 48890a mov qword ptr [rdx],rcx

EXCEPTION_RECORD: ffff84006b14d598 -- (.exr 0xffff84006b14d598)
ExceptionAddress: fffff803b7055cd4 (nt!KxWaitForLockOwnerShip+0x0000000000000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffff84006b14cde0 -- (.cxr 0xffff84006b14cde0)
rax=fffff68000000000 rbx=0000000000000000 rcx=ffff84006b14d820
rdx=0001000000000000 rsi=000000000020f9b8 rdi=ffff84006b14d820
rip=fffff803b7055cd4 rsp=ffff84006b14d7d0 rbp=ffff84006b14d889
r8=0000000000000034 r9=0000000000000034 r10=fffff380053fa928
r11=fffff68000007000 r12=0000000000000034 r13=fffff803b7394e40
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!KxWaitForLockOwnerShip+0x14:
fffff803`b7055cd4 48890a mov qword ptr [rdx],rcx ds:002b:00010000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

BAD_PAGES_DETECTED: bbc6

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffffffffffff

FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+14
fffff803`b7055cd4 48890a mov qword ptr [rdx],rcx

BUGCHECK_STR: AV

EXCEPTION_STR: 0xbbc6

LAST_CONTROL_TRANSFER: from fffff803b709354a to fffff803b7055cd4

STACK_TEXT:
ffff8400`6b14d7d0 fffff803`b709354a : fffff380`053fa9c0 00000000`00000000 fffff380`053fa9c0 fffff380`053fa900 : nt!KxWaitForLockOwnerShip+0x14
ffff8400`6b14d800 fffff803`b709148f : 00000000`001bfe34 00000000`001bfe34 fffff803`00000000 ffffcb89`00000034 : nt!MiInsertPageInFreeOrZeroedList+0x76a
ffff8400`6b14d8f0 fffff803`b712ed7f : 00000000`00000004 00000000`00000034 00000000`00000034 ffffcb89`01243020 : nt!MiZeroPage+0x3ef
ffff8400`6b14daa0 fffff803`b703bf87 : fffff803`b7394e40 00000000`00000000 ffffcb89`01243020 00000000`00000000 : nt!MiZeroPageThread+0x3ef
ffff8400`6b14dc10 fffff803`b717c676 : ffffde01`bef05180 ffffcb89`01363040 fffff803`b703bf40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff8400`6b14dc60 00000000`00000000 : ffff8400`6b14e000 ffff8400`6b148000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xffff84006b14cde0 ; kb

BUCKET_ID: PAGE_NOT_ZERO

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

*** Memory manager detected 48070 instance(s) of page corruption, target is likely to have memory corruption.