IRQL_NOT_LESS_OR_EQUAL BSOD [Pleas Help/Dump File Included]

[starshield10]

I have been getting many bsods recently, and the main one is IRQL_NOT_LESS_OR_EQUAL. I don't always get it immediately upon booting up, most of the time its during the playing of a game. I have ran memtest and my results came back within an hour saying no errors. All of my drivers have been updated. Here is what the dump file says:


Microsoft (R) Windows Debugger Version 10.0.10586.567 X86
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\Minidump\032016-4296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available




************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff802`bbe7b000 PsLoadedModuleList = 0xfffff802`bc159cd0
Debug session time: Sun Mar 20 13:42:04.598 2016 (UTC - 7:00)
System Uptime: 0 days 0:43:18.226
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck A, {88, ff, 0, fffff802bbecf95e}


Probably caused by : ntkrnlmp.exe ( nt!KiEndThreadAccountingPeriod+5e )


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


4: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000088, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, 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: fffff802bbecf95e, address which referenced memory


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




DUMP_CLASS: 1


DUMP_QUALIFIER: 400


BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728


SYSTEM_MANUFACTURER: System manufacturer


SYSTEM_PRODUCT_NAME: System Product Name


SYSTEM_SKU: SKU


SYSTEM_VERSION: System Version


BIOS_VENDOR: American Megatrends Inc.


BIOS_VERSION: 1101


BIOS_DATE: 10/01/2015


BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.


BASEBOARD_PRODUCT: Z170-A


BASEBOARD_VERSION: Rev 1.xx


DUMP_TYPE: 2


BUGCHECK_P1: 88


BUGCHECK_P2: ff


BUGCHECK_P3: 0


BUGCHECK_P4: fffff802bbecf95e


READ_ADDRESS: fffff802bc1f9520: Unable to get MiVisibleState
0000000000000088


CURRENT_IRQL: d


FAULTING_IP:
nt!KiEndThreadAccountingPeriod+5e
fffff802`bbecf95e 488b9088000000 mov rdx,qword ptr [rax+88h]


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: 39'00000000 (cache) 39'00000000 (init)


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


BUGCHECK_STR: AV


PROCESS_NAME: System


ANALYSIS_SESSION_HOST: JOHN-PC


ANALYSIS_SESSION_TIME: 03-20-2016 14:08:08.0877


ANALYSIS_VERSION: 10.0.10586.567 x86fre


TRAP_FRAME: ffffd00130b9bdf0 -- (.trap 0xffffd00130b9bdf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff802bc20e200 rbx=0000000000000000 rcx=0000000000000010
rdx=ffffd00130b6acc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802bbecf95e rsp=ffffd00130b9bf80 rbp=00000000001ea2cd
r8=00000000001ea2cd r9=0000000000000000 r10=ffffd00130b64468
r11=000000000000022b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KiEndThreadAccountingPeriod+0x5e:
fffff802`bbecf95e 488b9088000000 mov rdx,qword ptr [rax+88h] ds:fffff802`bc20e288=00000000000000ff
Resetting default scope


LAST_CONTROL_TRANSFER: from fffff802bbfc82e9 to fffff802bbfbd760


STACK_TEXT:
ffffd001`30b9bca8 fffff802`bbfc82e9 : 00000000`0000000a 00000000`00000088 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffd001`30b9bcb0 fffff802`bbfc6ac7 : 00000002`5e1a57e1 ffffd001`30b5e180 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffffd001`30b9bdf0 fffff802`bbecf95e : ffffe2ed`842c27b6 00000000`00000000 00000002`5e328f5d ffffd001`30b74660 : nt!KiPageFault+0x247
ffffd001`30b9bf80 fffff802`bbfbeb60 : ffffe000`de4cd010 ffffd001`30b74660 ffffe000`dc0c9000 00000000`00000001 : nt!KiEndThreadAccountingPeriod+0x5e
ffffd001`30b9bfb0 fffff802`bbfbefb7 : 00000000`00140001 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xc0
ffffd001`30b745e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37




STACK_COMMAND: kb


THREAD_SHA1_HASH_MOD_FUNC: 1355271353bf64ae7d40cf74a6b4118c432449f6


THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a5c694cd299f150a0300f2308ee1af3d11b1bf55


THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693


FOLLOWUP_IP:
nt!KiEndThreadAccountingPeriod+5e
fffff802`bbecf95e 488b9088000000 mov rdx,qword ptr [rax+88h]


FAULT_INSTR_CODE: 88908b48


SYMBOL_STACK_INDEX: 3


SYMBOL_NAME: nt!KiEndThreadAccountingPeriod+5e


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4410


IMAGE_VERSION: 10.0.10586.162


BUCKET_ID_FUNC_OFFSET: 5e


FAILURE_BUCKET_ID: AV_nt!KiEndThreadAccountingPeriod


BUCKET_ID: AV_nt!KiEndThreadAccountingPeriod


PRIMARY_PROBLEM_CLASS: AV_nt!KiEndThreadAccountingPeriod


TARGET_TIME: 2016-03-20T20:42:04.000Z


OSBUILD: 10586


OSSERVICEPACK: 0


SERVICEPACK_NUMBER: 0


OS_REVISION: 0


SUITE_MASK: 784


PRODUCT_TYPE: 1


OSPLATFORM_TYPE: x64


OSNAME: Windows 10


OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal


OS_LOCALE:


USER_LCID: 0


OSBUILD_TIMESTAMP: 2016-02-23 21:48:00


BUILDDATESTAMP_STR: 160223-1728


BUILDLAB_STR: th2_release_sec


BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728


ANALYSIS_SESSION_ELAPSED_TIME: 484


ANALYSIS_SOURCE: KM


FAILURE_ID_HASH_STRING: km:av_nt!kiendthreadaccountingperiod


FAILURE_ID_HASH: {7a809042-ee97-4189-e45a-6c3a9015ffc5}


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

 

[rgd1101]

from your other threads, you oc your system did you try undo your oc?

 

[starshield10]

from your other threads, you oc your system did you try undo your oc?

I reseted my OS last night so all my programs were deleted including OC GURU II which is what I used to overclock my graphics card. I haven't reinstalled that yet, so we can rule that out as the problem. I still have my I7 oced to 4.5ghz with 1.345 volts (100 x 45). My memory isnt overclocked at all, and I ran memtest as well as sfc/ scannow and no issues were found on either of those.

 

[starshield10]

bump