BSOD in Windows 7 Home Premium 32 bit

[Yunshou]

Completely unexpected, while reading mail or surfing on the internet, playing a game like Unreal Tournament or making a document, my pc ends with a BSOD with the message:
IRQ_LESS_OR_EQUAL.

I also have seen other ERROR messages but not sure what they exactly said thats why i post the most common one.

I have it already for a long time, hope that somebody can help to get rid of it.

In the attachment the required files.

 

[JMH]

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have Raid > update its Driver.


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Yunshou]

JMH, i have ran the MEM test and no errors found after 8 passes. I will now work on the driver verifier part .

 

[JMH]

Good news thus far.

 

[Yunshou]

Another BSOD this morning

JMH:
Hi i am back again, i did what you said in the Verifier part, left my pc running from the moment i posted my last note and used it normally. This morning i had the BSOD again with the IRQ_NOT_LESS_OR _EQUAL ( i forgot the word NOT in my first post). So i ran the jcgriff program again and i put the file here again... Hope it gives info to solve it now...
Thanks so far

 

[JMH]

> Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

> Also do a SFC {Option 2}
This may have to be run 3 times.

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

 

[Yunshou]

Update after running Malwarebytes scan

I run the scan and it found two items which i put as a screenshot in a worddoc.
I wait for you to reply befor i do anything, just doing it step by step.

 

[zigzag3143]

I run the scan and it found two items which i put as a screenshot in a worddoc.
I wait for you to reply befor i do anything, just doing it step by step.

There are two items that malwarebytes considers malware. Please check them and mark either quarantine or delete.

 

[JMH]

Have you run SFC as requested?
​

 

[Yunshou]

SFC scannow

I run the scannow but i only see quickly a dos screen pop op and disappearing again, how do i know it has run properly?

 

[zigzag3143]

I run the scannow but i only see quickly a dos screen pop op and disappearing again, how do i know it has run properly?

You need to go to start>search>type cmd> in the dos window tpye SFC /scannow

You may need to run it as admin

 

[Yunshou]

Oh sorry, i did not mention that, i did run it as admin as i am administrator and it still said i have to run it as admin :-(.

 

[zigzag3143]

Oh sorry, i did not mention that, i did run it as admin as i am administrator and it still said i have to run it as admin :-(.

See pix. It has to say Administrator in the top line. Does yours?

 

[Yunshou]

It does not say that, but there is no other admin account... now what or what do i do wrong?

 

[zigzag3143]

It does not say that, but there is no other admin account... now what or what do i do wrong?

Knew it. Go to tutorial section here http://www.sevenforums.com/tutorial...dd-remove-context-menu-windows-7-a.html?ltr=R Download it and run. There will be a new context menu item saying run ad administrator

 

[Yunshou]

Update SFC /scannow

Hello,

don't know what happened to my earlier post, i have it in my mail but don't see it here anymore.
Anyways i ran it twice and post the log here.

 

[Yunshou]

Update

Still having blue screens, i made a pic of it and put it here, is there any solution? Since my last post i did not see any reactions.

 

[zigzag3143]

Still having blue screens, i made a pic of it and put it here, is there any solution? Since my last post i did not see any reactions.

We Still need the new DMP files

 

[Yunshou]

Ok, here they are .

 

[zigzag3143]

Ok, here they are .

The apparent causes are all over the map.



Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.