BSOD doing regular tasks within Windows 7, IRQL_NOT_LESS_THAN_OR_EQUAL

Usually I get the IRQL_NOT_LESS_THAN_OR_EQUAL and sometimes I get a PFN_LIST_CORRUPT BSOD error message, it happens when doing just about anything from playing a simple game to browsing the internet to just browsing through folders.

-Windows 7 x64 Professional
-It is the original OS on the system
-Full Retail Version from MSDNAA
-System hardware is brand new
-OS is brand new and yes have tried re-installing it

I have attached the zip file including the latest minidump, the perfmon report and the documents folder that is required. Any help would be greatly appreciated, thank you!

masterlegit said:

Usually I get the IRQL_NOT_LESS_THAN_OR_EQUAL and sometimes I get a PFN_LIST_CORRUPT BSOD error message, it happens when doing just about anything from playing a simple game to browsing the internet to just browsing through folders.

-Windows 7 x64 Professional
-It is the original OS on the system
-Full Retail Version from MSDNAA
-System hardware is brand new
-OS is brand new and yes have tried re-installing it

I have attached the zip file including the latest minidump, the perfmon report and the documents folder that is required. Any help would be greatly appreciated, thank you!

These crashes were caused by memory corruption (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!!!


1-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.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

Driver Verifier - Enable and Disable


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

Alright I have followed your instructions, the sticks weren't the problem so I'm guessing its the drivers, here is a picture of the error I get when I try to run windows now...

masterlegit said:

Alright I have followed your instructions, the sticks weren't the problem so I'm guessing its the drivers, here is a picture of the error I get when I try to run windows now...

No DMP files included in upload please try this method

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Alright it took me a bit to get these cause I had some trouble even with booting in safe mode but here are the DMP files that were in the minidump folder after the lastest BSODs

masterlegit said:

Alright it took me a bit to get these cause I had some trouble even with booting in safe mode but here are the DMP files that were in the minidump folder after the lastest BSODs

Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. It is a known cause of BSOD'S and should be removed.

I tried just deleting the software and that took care of the dtsoftbus01 issue but i was still getting a ntoskrnl.exe error so I reformatted my computer completely and now I'm still getting the same error with different address codes from ntoskrnl

I have posted the two latest minidump files from the crashes, thank you for any help you can provide

Bump

i have that prob also! but i stoped using the USB3.0 and that IRQ prob stopped mostly BSOD on USB3 with USB soundcards and the G19 keyboard! and the 0X0f4 BSOD (Swapfile) for me is the ALL the SSDs but the Intel one so im waiting to replace motherboard and cpu with AMD PhenomFX X8 4.4ghz and top range motherboard its a common prob with intels On cpu SATA chipset with Sandforce 3 SSDs AKA OCZ/Kingston/Corsair but mostly with OCZ due to them running the SSDs memory layout in a different way! I reduced BSOD on that par by putting swap table on a normal HDD (to note i tried the SSDs on an older pc Q6600 P45 all worked fine)

PC
Core i7 2600K 3.8ghz Corsair WaterCooler
GA-Z68XP-UD3R (PCIE 3.0)
32GB DDR3 1866mhz Corsair Vengance RED
2x Radeon 6990 + Geforce GTX560TI
Soundblaster Xfi Fatality PCIE1X
4x 120GB SSDs OCZ/kingston/Corsair 2x SATA3.0 OCZ drives RAID
5x 3TB WD Black SATA3 @ SATA2 Storage
Antec 1300W PSU HC
HAFX Case