BSOD, IRQL_NOT_LESS_OR_EQUAL, Windows 7 64-bit
- Thread starter G30
- Start date
Route44
Posts: 12,015 +82
All three minidump files report the same thing that your issue is with memory corruption. Therefore you’ll need to run Memtest on your RAM.
1. Go to www.memtest.org and download the latest ISO version which is 4.20. It is free and perfectly safe.
2. Burn ISO to a CD.
3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.
There is a Tutorial: How to use Memtest in our Guides and Tutorials forum; follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.
Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes (not hours; this test is not measured by hours); the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.
There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.
If you have errors you have corrupted memory and it needs to be replaced.
Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
* Get back to us with the results.
1. Go to www.memtest.org and download the latest ISO version which is 4.20. It is free and perfectly safe.
2. Burn ISO to a CD.
3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.
There is a Tutorial: How to use Memtest in our Guides and Tutorials forum; follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.
Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes (not hours; this test is not measured by hours); the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.
There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.
If you have errors you have corrupted memory and it needs to be replaced.
Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
* Get back to us with the results.
Route44
Posts: 12,015 +82
Both dumps didn't cite anything specific but...
0x109: CRITICAL_STRUCTURE_CORRUPTION
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data.
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
* Through research failing RAM appears to be the main cause for many people. The other error is...
0x1E: KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors.
0xA errors are caused by either hardware (of which bad RAM can generate this error code) or faulty drivers attempting to address a higher IRQ Level than it is designed for resulting in system crashes.
I have seen 1E errors generated by corrupted memory as well.
0x109: CRITICAL_STRUCTURE_CORRUPTION
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data.
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
* Through research failing RAM appears to be the main cause for many people. The other error is...
0x1E: KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors.
0xA errors are caused by either hardware (of which bad RAM can generate this error code) or faulty drivers attempting to address a higher IRQ Level than it is designed for resulting in system crashes.
I have seen 1E errors generated by corrupted memory as well.
