BSOD IRQL_NOT_LESS_OR_EQUAL caused by driver ntoskrnl.exe


Joined
Oct 29, 2016
Messages
1
Reaction score
0
Hey guys,

I've got the following problem: I've upgraded my PC about two weeks ago. Back then everything was fine. But for about 1,5 weeks now, my PC crashes everytime when I play Battlefield 4 for about 5 to 10 minutes. Everything's fine with other games or graphics-intensive programs. The crash comes with the "IRQL_NOT_LESS_OR_EQUAL" error message.

I ran the bluescreen viewer, which states that the BSOD is related to the driver ntoskrnl.exe.

To fix this checked my RAM on several occasions for errors, updated my drivers and also resetted my PC to the point where everything was finde - without any improvements.

I'll upload the minidump files.

I'd like to thank you very much in advance for your help and support!

P.S.: I've seen in another post here that the problem was solved by uninstalling two programs, but I haven't installed those, but maybe there are other ones which cause the BSOD.
 

Attachments

  • Minidump.zip
    268.9 KB · Views: 400
Ad

Advertisements

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
13,417
Reaction score
2,320
Hello and welcome to the forum.
All three of your dump files appear to be nearly identical.
BugCheck A, {28, 2, 0, fffff802acbfd57d}
Probably caused by : memory_corruption
Followup: memory_corruption
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.
The only "driver" I see, in a cursory inspection is
ffffcb82`9a69f108 fffff80a`80bb4399*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
avipbb
+0x4399
Which is apparently related to Avira.
My suggestion would be to uninstall it
https://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/88
Following up with their manual uninstall instructions, also linked on that page.

The only other driver I see, which troubles me, although not mentioned at all in the dump files is
IOMap64.sys 10/22/2014
That's an ASUS kernel mode driver which has a bit of a bad history / reputation with some BSOD issues. Normally associated with
Asus Smart Doctor and or Asus GPU Tweak and GPU Tweak Streaming
Since all three dump files make mention of issues with Virtual Memory and Page Faults, I would certainly seriously consider getting rid of that as well.
STACK_TEXT:
ffffcb82`9a69efb8 fffff803`37166429 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffcb82`9a69efc0 fffff803`37164a07 : 00000000`00002e01 fffff80a`80bb4399 00000000`6c46624f fffff803`3725c34b : nt!KiBugCheckDispatch+0x69
ffffcb82`9a69f100 fffff803`3717d57d : ffffcb82`9a69f3c0 fffff803`3746e25a 00000000`00000040 fffff803`373583b8 : nt!KiPageFault+0x247
ffffcb82`9a69f290 fffff803`3704d76a : 00000000`00000011 ffff9180`002c5fa8 ffffcb82`9a69f680 00000000`58bf5000 : nt! ?? ::FNODOBFM::`string'+0x130ed
ffffcb82`9a69f390 fffff803`374b9224 : 00000000`00000003 00000000`00000001 00000000`00001000 00000000`00001000 : nt!MmProbeAndLockPages+0x25a
ffffcb82`9a69f4a0 fffff803`374b8e4f : 00000000`00000000 00000000`00000010 ffffb68e`3f277f20 ffffcb82`9a69fa01 : nt!MmCopyVirtualMemory+0x364
ffffcb82`9a69f950 fffff803`374b8ceb : ffffb68e`4641e080 00000000`0145f598 ffffcb82`9a69fa28 00000000`00000000 : nt!MiReadWriteVirtualMemory+0x15f
ffffcb82`9a69f9d0 fffff803`37165f93 : 00000000`0000082f 00000000`00000000 00000000`0145f490 00000000`00000000 : nt!NtReadVirtualMemory+0x1b
ffffcb82`9a69fa10 00007ffa`515a5634 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0145f578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`515a5634
All three clearly mention BF4
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: AV
PROCESS_NAME: bf4.exe
AND the bottom line
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top