BSOD Windows 10, (IRQL_NOT_LESS_OR_EQUAL and KERNEL_SECURITY_CHECK_FALIURE)

antoniopoopstfn

Prominent
Sep 10, 2017
17
0
510
0
BSOD Windows 10, (IRQL_NOT_LESS_OR_EQUAL and KERNEL_SECURITY_CHECK_FALIURE)
I cannot think of anything I've done different to randomly start bluescreening over and over, I think it's happened close to 10 times now, thinking of just having a professional check up on it, I have 4 minidump files and I'll post the most recent one, if anyone can help me, please do.

If needed just ask for another dump file

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 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`86895000 PsLoadedModuleList = 0xfffff803`86be15c0
Debug session time: Sun Sep 10 16:28:20.658 2017 (UTC - 4:00)
System Uptime: 0 days 0:07:06.369
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000100000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803868e5c94, address which referenced memory

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

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

WRITE_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
0000100000000000

CURRENT_IRQL: 2

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: AV

PROCESS_NAME: WerFault.exe

BAD_PAGES_DETECTED: 66fa

TRAP_FRAME: ffffde800461e250 -- (.trap 0xffffde800461e250)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffde800461e478
rdx=0000100000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803868e5c94 rsp=ffffde800461e3e0 rbp=ffffde800461e4b8
r8=fffff80386bff708 r9=0000000000000000 r10=0000000000000000
r11=ffffd50000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KxWaitForLockOwnerShip+0x14:
fffff803`868e5c94 48890a mov qword ptr [rdx],rcx ds:00001000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80386a0c8a9 to fffff80386a01560

STACK_TEXT:
ffffde80`0461e108 fffff803`86a0c8a9 : 00000000`0000000a 00001000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffde80`0461e110 fffff803`86a0ae7d : ffffbf0b`25e83860 ffffbf0b`28ec8c30 ffffbf0b`272b7180 ffffbf0b`2711c040 : nt!KiBugCheckDispatch+0x69
ffffde80`0461e250 fffff803`868e5c94 : ffffbf0b`264220a0 00000000`00000000 00000000`00000000 ffffa881`716ee600 : nt!KiPageFault+0x23d
ffffde80`0461e3e0 fffff803`868e1605 : ffffd500`022953c0 fffff803`86c14bc8 ffffbf0b`29ec4000 ffffbf0b`28ec8900 : nt!KxWaitForLockOwnerShip+0x14
ffffde80`0461e410 fffff803`86a3a8f0 : 00000000`00000001 00000000`00000000 ffffd500`022953c0 ffffbf0b`26421000 : nt!KxAcquireQueuedSpinLock+0x25
ffffde80`0461e440 fffff803`86a3aca7 : ffffd7ff`00000000 fffff803`00000004 fffff803`00000000 00000000`00000000 : nt!MiInsertPageInList+0x10e610
ffffde80`0461e4e0 fffff803`8693436b : ffffde80`0461e6c8 ffffde80`0461e690 7fffffff`00000010 ffffbf0b`26424011 : nt!MiInsertAndUnlockStandbyPages+0x10da87
ffffde80`0461e5b0 fffff803`86934f74 : ffffbf0b`28ec0870 ffffbf0b`00000009 ffffbf0b`272ba900 fffff809`c8ad3400 : nt!MiFinishHardFault+0x98b
ffffde80`0461e770 fffff803`86952f3e : ffffde80`0461ec38 00000000`00000000 00000000`00000000 ffffa881`00000000 : nt!MiWaitForInPageComplete+0x264
ffffde80`0461e870 fffff803`86952ebe : 00000000`00000000 ffffbf0b`2a77a040 00000000`00000000 ffffa881`00000001 : nt!MiPfCompleteInPageSupport+0x3a
ffffde80`0461e8b0 fffff803`86d6dff7 : ffffbf0b`2578c6e8 ffffbf0b`2578c6b0 ffffde80`ffffffff 00000000`00000000 : nt!MiPfCompletePrefetchIos+0x4e
ffffde80`0461e8e0 fffff803`86d72b00 : ffffbf0b`00000008 00000000`00000000 ffffde80`0461ec38 00000000`00000008 : nt!MmPrefetchPagesEx+0x1e7
ffffde80`0461e950 fffff803`86d74998 : ffffa881`00000007 ffffbf0b`2ad13840 ffffde80`0461ebd0 00000000`00000003 : nt!PfSnPrefetchSections+0x200
ffffde80`0461eb60 fffff803`86d74779 : 00000000`00000001 00000000`00000002 00000000`00000178 ffffa881`72bf0e88 : nt!PfSnAsyncPrefetchStep+0x3c
ffffde80`0461eba0 fffff803`868d2ca8 : 00000000`00000200 ffffbf0b`2a77a040 ffffbf0b`2ad13840 fffff803`86c8d380 : nt!PfSnAsyncPrefetchWorker+0x1b9
ffffde80`0461ecc0 fffff803`86971ac7 : ffffde80`0071d180 00000000`00000080 ffffbf0b`24ac4680 ffffbf0b`2a77a040 : nt!ExpWorkerThread+0xd8
ffffde80`0461ed50 fffff803`86a069e6 : ffffde80`0071d180 ffffbf0b`2a77a040 fffff803`86971a80 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffde80`0461eda0 00000000`00000000 : ffffde80`0461f000 ffffde80`04619000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

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

axe0axe0

Notable
Jun 5, 2017
760
0
1,160
96
Follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, don't run the stress tests, upload the zip to a 3rd party uploader and post a share link.
 

adamstobbzy16

Prominent
Sep 22, 2017
11
0
520
1
Something very similar like this happened to me only a week ago and I fixed it.
If you got a Disk that came in the box with your GPU and you installed that disk, uninstall it immediantly. Then navigate to the files in your documents with the name of the GPU software. Mine was GPUTweaII so I had to navigate to C:\Program Files (x86)\ASUS\GPU TweakII Once you have found this location delete any files inside of this folder. Restart your PC to make sure they are gone. Next go onto google and type in your GPU software that you unistalled and re-install a newer version. Also make sure that you get the latest drivers from Nvidia website. Once downloaded the newer version of your GPU Software and the latest Nvidia drivers, restart your pc!
Hope this helps!
 

Similar threads