BSOD IRQL_NOT_LESS_OR_EQUAL 0xA

[MersauX]

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]

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

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.

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

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Best Regards,
Frederik.

 

[MersauX]

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]

Good call on the Prime test.

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

Best Regards,
Frederik.

 

[MersauX]

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]

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]

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]

@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:

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:

[B]ErrorSource[/B] 1    

[B]ApicId[/B] 0    

[B]MCABank[/B] 0    

[B]MciStat[/B] 0x9000004000010005    

[B]MciAddr[/B] 0x0    

[B]MciMisc[/B] 0x0    

[B]ErrorType[/B] 12    

[B]TransactionType[/B] 256    

[B]Participation[/B] 256    

[B]RequestType[/B] 256    

[B]MemorIO[/B] 256    

[B]MemHierarchyLvl[/B] 256    

[B]Timeout[/B] 256    

[B]OperationType[/B] 256    

[B]Channel[/B] 256    

[B]Length[/B] 864    

[B]RawData[/B] 435045521002FFFFFFFF03000200000002000000600300000A310D001D060C140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89025EA27FAE555CD0100000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002080000000000A70602000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000A7060200000810009FE3BA0DFFFBEBBF000000000000000000000000000000000000000000000000000000000000000001000000010000005A84FDF5FD55CD010000000000000000000000000000000000000000000000000500010040000090000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

 

[FredeGail]

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

Best Regards,
Frederik.

 

[MersauX]

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.

 

[FredeGail]

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.

Interesting, were you able to connect it so it wouldn't be loose?

Best Regards,
Frederik.

 

[MersauX]

Interesting, were you able to connect it so it wouldn't be loose?

Best Regards,
Frederik.

Yes, I just pushed it all the way in and it's good now. Yesterday I got just a few WHEA Logger 19 warnings, but this morning since I started work they've become quite a lot. The difference is that now I have many browser tabs open. Also when I use the Lenovo Energy Management sofware's "smart power-saving CPU" mode I get a lot of WHEA Logger 19 warnings.

 

[MersauX]

Here are a couple of new BSODs, the first one was caused my a missing driver, since I tried something by removing Lenovo Energy Management. The second one occured a few minutes after waking the laptop from sleep, it was sleeping for several hours, so there should be no thermal issues, also after that it continued working normally.

 

[FredeGail]

Hello MersauX,

As you didn't have any errors with Memtest86+, our next step would be testing your CPU. Being in the WHEA_UNCORRECTABLE_ERROR (124) as we are, we'd need to troubleshoot your hardware.

I'd suggest you to do a Stress Test using Prime. Details below.

http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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: fffffa8007dba038, 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.

Best Regards,
Frederik.

 

[MersauX]

Hello MersauX,

As you didn't have any errors with Memtest86+, our next step would be testing your CPU. Being in the WHEA_UNCORRECTABLE_ERROR (124) as we are, we'd need to troubleshoot your hardware.

I'd suggest you to do a Stress Test using Prime. Details below.

http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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: fffffa8007dba038, 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.

Best Regards,
Frederik.

Hi Frederik,

I will conduct a Prime95 test today and keep you posted.

 

[MersauX]

Hi again,

I left it testing with prime95 close to two hours, no errors and a curious thing, not a single WHEA Logger error during that time, although CPU was 100% busy all the time.

I've decided to install a Linux distribution just to test whether the system will crash.

 

[FredeGail]

Alright!

When you're ready to move on troubleshooting Windows, let's enable Driver Verifier for the time being.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

 

[MersauX]

Hi, I'm back. I tried Ubuntu and it didn't crash once, so it must be some sort of a driver problem.

I enabled verifier as per your instructions. What I did before that is: I installed Windows and installed only the Lenovo drivers and Synaptics driver for touchpad without access to the internet, I first want to exclude them, because just a few minutes ago I received a BSOD, here it is attached.

I'm suspecting Synaptics since it was the last one I installed and I did it today, while all the others I installed yesterday and it didn't crash once.

In the meantime I bought a new laptop, because I can't lose work because of this one that's crashing.

 

[FredeGail]

Hello again MersauX!

I'd probably be the Synaptic driver. Are you able to uninstall it? Go to Device Manager > Touchpad/Sysnaptics (something like that) > Right Click it, Properties > Driver Tab, Uninstall driver.

Your touchpad should work either way.

Best Regards,
Frederik.

 

[MersauX]

Hi,

I left the laptop on at home with the verifier turned on, so maybe it will catch something since the first time it crashed while idle.

I will remove the Synaptics driver when I get home and I'll keep you posted.

My next step is to connect to the internet and start installing Windows updates one by one. Hopefully, I'll get to the end of it soon.