Bsod irql_not_less_or_equal

[freesix]

Hi, I'm getting a BSOD and tried couple of things I read from various website but still persists.

Please can you help?

I attached the zip file generated by your utility.

 

[ICIT2LOL]

Hello and welcome freesix now mate can you please follow this as the bugchecks are pointing toward a hardware problem.
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
*(pretyped to save time)

[COLOR="Red"]BugCheck 1000000A,[/COLOR]

and this

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: 00000016, [COLOR="red"]memory referenced[/COLOR]
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82e815f1, address which referenced memory

So as if it is hardware based then we have a bit to do and I think in light of the memory being refrenced until we get the specs back you should try a memtest see this
Now to make absolutely we are on the same page the memtest linked here is the only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+
(This is pretyped to save time)

Remember 8 passes no less please because otherwise it is wasting time and effort unless errors come up fairly quickly..

 

[freesix]

Thanks, will try it.

I run the system under Safe Mode, now 3 hours on there's no BSOD.


The BSOD only rises in Normal Windows mode, but anyway will try Memory Check.

 

[freesix]

I also ran Windows Memory Diagnostic (this / that) and the report came "No Error Found"

 

[axe0]

This looks like a known bug with Avast.
In Avast, check manually for updates, the cause is a virus definition update of yesterday morning. Yesterday evening they released a virus definition update that should fix the issue.

Same instruction execution and stack calls as other users who experienced the same issue.

FAULTING_IP: 
nt!KiSignalNotificationObject+13
82e495f1 807f1601        cmp     byte ptr [edi+16h],1


ChildEBP RetAddr  Args to Child              
9b457a34 82e78a1d 8d700120 00000000 85c569f0 nt!KiSignalNotificationObject+0x13
9b457a5c 82e826f8 9b457678 00000000 00000000 nt!KeSetEvent+0x98
9b457aac 82eb2a86 00c56a30 9b457ad8 00000000 nt!IopCompleteRequest+0x23b
9b457afc 82e29b48 00000000 00000000 00000000 nt!KiDeliverApc+0x111
9b457b10 8304904c 00000000 00000000 bea3c3b0 nt!KiCheckForKernelApcDelivery+0x24
9b457b58 83049097 85cef938 9b457be4 00000000 nt!MiMapViewOfSection+0x2d3
9b457b88 830497f6 bea3c3b0 85cef938 9b457be4 nt!MmMapViewOfSection+0x2a
9b457c04 82e3f8c6 00000014 ffffffff 001eee10 nt!NtMapViewOfSection+0x204
9b457c04 776c70f4 00000014 ffffffff 001eee10 nt!KiSystemServicePostCall (FPO: [0,3] TrapFrame @ 9b457c34)
WARNING: Frame IP not in any known module. Following frames may be wrong.
001eed7c 00000000 00000000 00000000 00000000 0x776c70f4

 

[freesix]

Thanks,

I went through couple of Avast Forum that mention that too; and did as you requested.

So now just waiting to see if it's fixed !


If I don't come back to post here it means it solved !!

Thanks !!!