BSOD playing Overwatch. APC_INDEX_MISMATCH and IRQL_NOT_LESS_OR_EQUAL.

Natural · 30 May 2017

System Specs:

PC/Desktop

Custom Built

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1

Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz

Gigabyte Technology Co., Ltd. Z97-HD3

16.00 GB

(1) NVIDIA GeForce GTX 970 (2) Intel(R) HD Graphics 4600

(1) USB Audio Device (2) NVIDIA High Definition Audio (3
Monitor(s) DisplaysEdit Value

35" Predator Z25

2560 x 1080 x 32 bits (4294967296 colors) @ 59 Hz

(1) Samsung 250 GB SSD (2) Western Digital 1 TB Hard Drive

evga supernova nex 750w

corsair k95 rgb

logitech g502

ESET NOD32

Google Chrome

Hi, For the past month now, I have been having BSODs. I usually have them randomly while using my computer but I also have them in Overwatch. The name of the BSOD is either APC_INDEX_MISMATCH or IRQL_NOT_LESS_OR_EQUAL. While in Blue Screen Viewer, I can that the File/Driver that is causing it is my ntoskrnl.exe.

I have tried reinstalling Windows 7 but that has not worked and I am wondering if anyone can find the problem exactly.

If any additional info is needed, don't hesitate to ask.

Thanks for your time.

**axe0** · 03 Jun 2017

Warning

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 4, please remove them as it may cause trouble.

An easy way to get remove these drivers is by using a restore point prior the installation.

Natural · 10 Jun 2017

axe0 said:

Warning

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 4, please remove them as it may cause trouble.

An easy way to get remove these drivers is by using a restore point prior the installation.

I have tried to remove all of the drivers installed by this. I have still been getting crashes and BSODs. Also want to mention that I have been receiving BSODs long before Driver Booster 4.

**axe0** · 10 Jun 2017

Driver update utilities are known to affect troubleshooting and stability, also when used after the first time issues occured.

Removal of the utility wasn't a suggestion to fix the BSOD, rather to prevent issues with troubleshooting.

If you want to post about BSOD issues, please follow the BSOD Posting Instructions. Without logs I cannot help.

Natural · 10 Jun 2017

axe0 said:

Driver update utilities are known to affect troubleshooting and stability, also when used after the first time issues occured.

Removal of the utility wasn't a suggestion to fix the BSOD, rather to prevent issues with troubleshooting.

If you want to post about BSOD issues, please follow the BSOD Posting Instructions. Without logs I cannot help.

Here are my most recent BSODs. Thank you for the help :)

**axe0** · 11 Jun 2017

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning

If you're overclocking your system, revert back to stock clocks now.

Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

CPU TEST

Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

TWO

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it please.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Diagnostics Test

HDD TEST

Note

Please run HDTune first, in the order posted!

Run HDTune to

check the health,
scan for errors, no quick scan but full scan
run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

the health,
the error scan,
the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log :arrow: Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

FOUR

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

Natural · 12 Jun 2017

Here are the HDTune Tests.
I will be uploading the others shortly.

Natural · 12 Jun 2017

Here are the CPU and GPU Stress Tests

Natural · 16 Jun 2017

Sorry for the delay, but here is the last test results , MemTest.
Again thanks for all the help.

**axe0** · 17 Jun 2017

Next step, BIOS and drivers :)

Check for BIOS updates and reset the BIOS to default settings.

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.