BSOD: driver irql not less or equal

overlordofdoom

Reputable
Apr 29, 2014
79
0
4,630
I don't know what's wrong with my pc, but every time I run unigine valley on my 980 ti get the bsod: driver_irql_not_less_or_equal. My 980ti isn't even overclocked

Here is the minidump, thanks in advance:

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


Loading Dump File [C:\Users\Dina killer\Desktop\091716-2937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.187.amd64fre.rs1_release_inmarket.160906-1818
Machine Name:
Kernel base = 0xfffff801`e9a10000 PsLoadedModuleList = 0xfffff801`e9d14080
Debug session time: Sat Sep 17 23:46:48.724 2016 (UTC + 1:00)
System Uptime: 0 days 0:13:55.432
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {b0, ff, 0, fffff801ea246627}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )

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

2: 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: 00000000000000b0, 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: fffff801ea246627, address which referenced memory

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.187 (rs1_release_inmarket.160906-1818)

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7A12

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.40

BIOS_DATE: 07/24/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z170A GAMING PRO CARBON (MS-7A12)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: b0

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801ea246627

READ_ADDRESS: fffff801e9db6338: Unable to get MiVisibleState
00000000000000b0

CURRENT_IRQL: d

FAULTING_IP:
hal!HalpApic1EndOfInterrupt+7
fffff801`ea246627 c781b000000000000000 mov dword ptr [rcx+0B0h],0

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: Valley.exe

ANALYSIS_SESSION_HOST: DESKTOP-UCGIJ06

ANALYSIS_SESSION_TIME: 09-18-2016 14:20:53.0575

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

TRAP_FRAME: ffffa6018b8b98e0 -- (.trap 0xffffa6018b8b98e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff801ea246620 rbx=0000000000000000 rcx=ffffffffffd0b000
rdx=0000027d00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801ea246627 rsp=ffffa6018b8b9a78 rbp=ffffa6018b8b9b00
r8=ffffa60186240180 r9=0000000000000001 r10=ffffa60186246444
r11=0000000000000100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na po nc
hal!HalpApic1EndOfInterrupt+0x7:
fffff801`ea246627 c781b000000000000000 mov dword ptr [rcx+0B0h],0 ds:ffffffff`ffd0b0b0=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801e9b65229 to fffff801e9b5a0b0

STACK_TEXT:
ffffa601`8b8b9798 fffff801`e9b65229 : 00000000`0000000a 00000000`000000b0 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffa601`8b8b97a0 fffff801`e9b63807 : 00000000`00000000 ffffcd05`3b4be970 00000000`00000001 fffff801`e9a410d3 : nt!KiBugCheckDispatch+0x69
ffffa601`8b8b98e0 fffff801`ea246627 : fffff801`e9b5bb84 ffffcd05`3aa1e080 00000000`00000000 ffffa601`8b8b9a58 : nt!KiPageFault+0x247
ffffa601`8b8b9a78 fffff801`e9b5bb84 : ffffcd05`3aa1e080 00000000`00000000 ffffa601`8b8b9a58 ffffcd05`3d7769d0 : hal!HalpApic1EndOfInterrupt+0x7
ffffa601`8b8b9a80 00000000`6f61e66f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x44
00000000`00f3c8f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6f61e66f


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 8c79e4caf92c2a02899c5f4d2e4b788a9c3c0e70

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9b761accf64b4a3802cf2093b4fa94ab61899d84

THREAD_SHA1_HASH_MOD: cf09eec938e77a8fcc1464cb4da938dd43c312bc

FOLLOWUP_IP:
nt!KiPageFault+247
fffff801`e9b63807 33c0 xor eax,eax

FAULT_INSTR_CODE: ffb0c033

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+247

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 57cf9a34

IMAGE_VERSION: 10.0.14393.187

BUCKET_ID_FUNC_OFFSET: 247

FAILURE_BUCKET_ID: AV_nt!KiPageFault

BUCKET_ID: AV_nt!KiPageFault

PRIMARY_PROBLEM_CLASS: AV_nt!KiPageFault

TARGET_TIME: 2016-09-17T22:46:48.000Z

OSBUILD: 14393

OSSERVICEPACK: 187

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-09-07 05:40:20

BUILDDATESTAMP_STR: 160906-1818

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.187

ANALYSIS_SESSION_ELAPSED_TIME: 2fa

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!kipagefault

FAILURE_ID_HASH: {ec3e2762-48ae-ffe9-5b16-fbcb853e8320}

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

Thanks.