Bsod, irql_not_less_or_equal

Running memtest for less then 8 passes isn't worth it, because the results aren't conclusive.
But why did you run memtest? Suspecting memory corruption?

If everything is fine yes.

axe0 said:

Running memtest for less then 8 passes isn't worth it, because the results aren't conclusive.
But why did you run memtest? Suspecting memory corruption?

If everything is fine yes.

will be that if you format windows solves the problems?

Hi good day, uninstalled avast, updated the killer network and so stopped receiving bsod for 18 hours, but now just received once again a bsod

you can check again for me, thanks

I still see the Intel Rapid Storage Technology flagged

Code:

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

but there is also

Code:

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: 0000000000000002, 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: fffff80278b2462c, address which referenced memory

This might have to do with bad memory

Diagnostic Test

 RAM TEST

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

   Note

MemTest86+ needs to be run for at least 8 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.

axe0 said:

I still see the Intel Rapid Storage Technology flagged

Code:

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

but there is also

Code:

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: 0000000000000002, 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: fffff80278b2462c, address which referenced memory

This might have to do with bad memory

Diagnostic Test

 RAM TEST

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

   Note

MemTest86+ needs to be run for at least 8 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.

acabeu to see now, came out a new killer driver today, I'm downloading and completely uninstalled now intel rapid storage (this makes me miss my performance ssd?

I'm sorry, I don't fully understand "(this makes me miss my performance ssd?"

axe0 said:

I'm sorry, I don't fully understand "(this makes me miss my performance ssd?"

intel rapid storage serves to improve performance ssd?

krustybbr said:

intel rapid storage serves to improve performance ssd?

Intel Rapid Storage is for the hard drives that are connected via the RAID technology.
If this is not the case, then you should disable it.

axe0 said:

Intel Rapid Storage is for the hard drives that are connected via the RAID technology.
If this is not the case, then you should disable it.

uninstalled this driver (Intel Rapid Storage Technology), I installed the killer driver who came out today as well. :)
I hope soon solve the problem, you recommend a clean install of windows before testing memory ram?

Thank you,
Leonardo

A clean install won't work when RAM is the problem.
So, it doesn't really matter, but I wouldn't.

When a new version of a driver comes it, it is smart to wait a few days before installing the new version because of some possible problems that are usually fixed within a few days.