Random BSOD - IRQL_NOT_LESS_OR_EQUAL

Hi dazuara.

Can you install this driver? Intel® Iris™ and HD graphics Driver for Windows* 7/8/8.1 64-bit

Let us know the situation after this update.
__________________________________________

Code:

BugCheck A, {91c7ab8, 2, 0, fffff80002c89321}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchWaitForEvents+f5 )

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

Code:

fffff880`091c7a70 fffff880`0420b2aa dxgmms1!VidSchWaitForCompletionEvent+0x139
fffff880`091c7ab0 fffff880`04237ff6 dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`091c7bc0 fffff800`02f2273a dxgmms1!VidSchiWorkerThread+0xba

Code:

fffff880`091c7388  fffff880`054fcdb3Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xebdb3

Code:

    Image name: igdkmd64.sys
    Timestamp:        Fri Jul 04 20:20:47 2014 (53B6BF47)

I see that the driver is updated.

But this time the BSOD is not showing any finite probable cause.

Code:

BugCheck 1A, {31, fffffa8008a1a3a0, fffff8800a155000, fffff8a00614f4e2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+71b1 )

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. Will decide the next step after knowing the result.

dazuara said:

Im running memtest right now and i already got 9 errors , im at pass 5

Stop testing now.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.

It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.

It is a motherboard issue. The particular slot is bad.

It may take a time, but will give you the accurate result. Let us know it accordingly.