BSOD IRQL_NOT_LESS_OR_EQUAL 0xA

MersauX · 27 Jun 2012

I had some issues with my laptop lately. Random BSODs, I figured they had something to do with the iastor.sys driver, so I changed my HDD to be in IDE not AHCI mode, and those BSODs ceased.

However, I just got a new one and it seems to be a driver issue, but I have no idea which driver it could be. Here are the dump files and my driver list. I noticed some Brother drivers, I don't know how and when they got installed to be honest.

I used the diagnostic tool to gather the info.

P. S. Unfortunately, I cleared my event log.

I hope you can help me.

FredeGail · 27 Jun 2012

Hello MersauX and welcome to Sevenforums.

BSOD Analyse

Your dump contains regular and common bugcheck codes that can be caused by almost everything. Therefore, I'll be looking at your Event containments as well as some driver outdates. First of all, your dumps carried the WHEA_UNCORRECTABLE_ERROR 0x124. This can of course, as many other bugchecks, be caused by hardware, drivers and so on and so forth. The most common hardware related BSODs, exists from bad memory sectors or sticks, or maybe even slots.

Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

BSODs Summary

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007f03038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
--------------------------------------------------------------------------------------------------------------
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: fffff800092c7760, memory referenced
Arg2: 000000000000000d, 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: fffff80002ca5afb, address which referenced memory

This is the first hardware diagnose we'll be going through.

Event Viewer

Unfortunately your zip did not contain a $sys file so we're able to see the hotfixes install, but if you haven't already - you should install the hotfix M935842. It'll fix one of your Event errors.

Code:

Event[6]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-06-25T00:02:29.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: 37L4247F27-25
  Description: 
Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available

SFC /scannow

We usually ask people to do this command to check if Windows is corrupted. Some of your dumps included kernel pointers, though, the Debugging Tool will point to a kernel, because it cannot find the right driver to blame. In some cases, the Windows files are actually broken. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

Best Regards,
Frederik.

MersauX · 29 Jun 2012

Hello again,

I did all the tests scf /scannnow and memtest for 7 passed on each module on each slot, so 14 passes in total per module, no errors. I also did some prime95 testing on the processor, it passed with flying colors, so I'm at a loss what could be the problem.

It all started a few days ago when I got a Page fault in a nonpaged area and since then it's been hell. I formated my computer three times in the meantime, changed from AHCI to IDE and formted again, it was working a bit slower but fine until these two BSODs.

In the event log there is also sometimes the WHEA Logger 19 error for Internal Parity Error.

FredeGail · 29 Jun 2012

Good call on the Prime test.

Could you upload the newest BSOD dumps you've been experiencing?

Best Regards,
Frederik.

MersauX · 29 Jun 2012

Hi, I haven't really used the laptop since the first post, it was running the memtest for the past 24+ hours with different modules and slots, before that I was running prime, so I did not do much work, to be honest.

I will see what happens over the weekend during my work hours, and I will keep you posted.

Thanks for your help!

P. S. I also experienced a couple of BSODs during restarts. When the Win7 logo appears the laptop restarts again and then it boots normally.

FredeGail · 29 Jun 2012

MersauX said:

Hi, I haven't really used the laptop since the first post, it was running the memtest for the past 24+ hours with different modules and slots, before that I was running prime, so I did not do much work, to be honest.

I will see what happens over the weekend during my work hours, and I will keep you posted.

Thanks for your help!

P. S. I also experienced a couple of BSODs during restarts. When the Win7 logo appears the laptop restarts again and then it boots normally.

Hello again MersauX!

Thank you very much for keeping me informed on stuff like this, it keeps me very motivated. Get a cup-of-something, take your time, and just upload any dump when you have one. :)

Best Regards,
Frederik.

baxterboy · 29 Jun 2012

Possible fix for you:

SYMPTOMS

You have a computer that is running Windows 7 or Windows Server 2008 R2. Occasionally, the computer crashes after it runs for some time. Additionally, you receive a Stop error message on a blue screen. The Stop error message resembles the following: STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)
IRQL_NOT_LESS_OR_EQUAL

CAUSE

This issue occurs because Power Manager opens an Advanced local procedure call (ALPC) port. However, Power Manager closes another port instead of closing the ALPC port. Every time that a power request is made, a memory leak occurs. When the leaked memory usage accumulates to a certain level, the computer crashes.

Quoted from Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A"

You can request a fix by submitting your email to Microsoft, however I have the file already which I have attached.
Registered just for this post so I hope it helps.

MersauX · 29 Jun 2012

@basterboy
I did download it, however it says the update is not applicable to my system, which is strange since I'm running Windows 7 Home Premium x64.

@FredeGail
Thank you for helping me, no BSODs so far, just a few of these in the event log:

Code:

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 0

The details view of this entry contains further information.

The details tab shows this info:

Code:

   
ErrorSource 1    

ApicId 0    

MCABank 0    

MciStat 0x9000004000010005    

MciAddr 0x0    

MciMisc 0x0    

ErrorType 12    

TransactionType 256    

Participation 256    

RequestType 256    

MemorIO 256    

MemHierarchyLvl 256    

Timeout 256    

OperationType 256    

Channel 256    

Length 864    

RawData 435045521002FFFFFFFF03000200000002000000600300000A310D001D060C140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89025EA27FAE555CD0100000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002080000000000A70602000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000A7060200000810009FE3BA0DFFFBEBBF000000000000000000000000000000000000000000000000000000000000000001000000010000005A84FDF5FD55CD010000000000000000000000000000000000000000000000000500010040000090000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

FredeGail · 29 Jun 2012

Meanwhile make sure your CPU fan is connected the right way, and all the way down in the pins.

Best Regards,
Frederik.

MersauX · 29 Jun 2012

FredeGail said:

Meanwhile make sure your CPU fan is connected the right way, and all the way down in the pins.

Best Regards,
Frederik.

Hi again,

I just disassembled my laptop and put it back together. I checked the fan, the connector was a bit loose, but I keep getting the WHEA Logger error mention before, although it does not impact the performance of my machine, nor does it cause any BSODs.