IRQL_NOT_LESS_OR_EQUAL Windows 7 64-bit

Hi,
I have recently installed new hardware on my PC. I added a new motherboard, processor, graphics card, and network adapter, and removed a 500GB harddrive from my 1TB. After formatting my hard drive, I then installed a new copy of Windows 7 Ultimate 64-bit. Ever since, I have had BSOD occuring at random. One of the problems I found to be Norton Antivirus 2009. I then removed that properly and replaced it with Symantec Endpoint version 12.0.122.192. Still, however, BSOD occurs at random, but gives me the infamous IRQL_NOT_LESS_OR_EQUAL error. I did some research on this and found that improper drivers could be the culprit. I updated all of my drivers (to my knowledge), ran Windows Memory Diagnostic (which said my RAM was fine), and ran a virus scan with Endpoint (which detected nothing). I do not know how to proceed with this, except ask for some assistance. Perhaps somebody could help me out? I am running Windows 7 Ultimate 64-bit. Attatched are my minidumps.

Thanks in advance,
qotsa

Hi,

There are several issues with all of the crash that you've mentioned. Let's eliminate every potential cause.
I'm sorry to say this but Symantec are causing some of these crashes and you need to remove it completely from your system
http://www.symantec.com/norton/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN&ln=en_US

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
I suspect the graphic card as well. First thing to try is to re-install it. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Test your Ram please: Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Window Memory diagnostic (built in), I don't trust that, please use memtestx86 to test it.

BUGCHECK SUMMARY:

Code:

BugCheck A, {28, 2, 0, fffff800030b7518}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
---------
BugCheck D1, {fffff8800ae5a898, 7, 0, fffff880012950be}

Unable to load image \SystemRoot\system32\DRIVERS\mv91xx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : mv91xx.sys ( mv91xx+280be )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff88004a55cee, fffff880027cf6a8, fffff880027cef10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )

Followup: MachineOwner
---------
BugCheck 50, {fffff8800b635d70, 0, fffff88001384150, 2}

Unable to load image \SystemRoot\system32\drivers\NISx64\1107000.00C\SYMEFA64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS

Could not read faulting driver name
Probably caused by : SYMEFA64.SYS ( SYMEFA64+3150 )

Followup: MachineOwner
---------

BugCheck 50, {fffff8800e63e0f0, 0, fffff88004c20ce5, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )

Followup: MachineOwner
---------
BugCheck F4, {3, fffffa800e761b30, fffffa800e761e10, fffff80003381540}

Probably caused by : wininit.exe

Followup: MachineOwner
---------
BugCheck F4, {3, fffffa800e761b30, fffffa800e761e10, fffff80003381540}

Probably caused by : wininit.exe

Followup: MachineOwner
---------
BugCheck 109, {a3a039d8a1d4ea1b, 0, d66b36638eef180f, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
BugCheck 50, {fffff8800a25a7c8, 0, fffff800030a23a5, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerFileObjectContext+a5 )

Followup: MachineOwner
---------

Update the directx as well:
Download details: DirectX End-User Runtime

Regard,

Tuan

Lets address the RAM first. If Memtest showed errors, you have defective RAM or a defective motherboard slot. Remove all of your RAM except one stick. Run Memtest on that one stick. If it passes, repeat until you have tested each stick separately. If you do not find a bad stick, test each slot with a good stick. If that testing does not show an error, you may a compatibility problem. I know this is time consuming; but I do not know any other way to do it.

Regarding sptd.sys, you can rename it to sptd.bak and it will not load.

You most definitely need to download Microsoft Security Essentials, completely uninstall Symantec, and install MSE for the purposes of trouble shooting. Do this ASAP. The idea is to eliminate known causes of crashes. Use this removal tool to uninstall Symantec - Info > Tool. Your version of Symantec has an obsolete driver which alone can cause memory corruption. Post back when you have done this.

You have other obsolete drivers on your system. Generally speaking, Windows 7 does not like drivers dated prior to July 13, 2009. Obsolete drivers can and do cause memory corruption.

e1y60x64.sys Mon Aug 18 17:45:05 2008
Lycosa.sys Fri Jan 18 03:51:42 2008
SYMEVENT64x86.SYS Wed May 28 20:35:19 2008 (Symantec)
teefer2.sys Tue Oct 14 15:24:10 2008 (Symantec)
wpsdrvnt.sys Wed Apr 22 18:07:15 2009 (Symantec)

Update these drivers (except the Symantec drivers) from the manufacturers' sites rather than through Windows Update or Device Manger.

If you need help with these, please post.

Here is some help for the drivers you need to update.

e1y60x64.sys - Ethernet driver (Intel PRO/1000 LAN adapter software), Gigabit Ethernet. Update this driver. It you can't you should upgrade your network adapter card.

Lycosa.sys - Razer Tarantula Keyboard Driver - Razer Tarantula - Razer USA Ltd. Update this driver. If there is no update for it, you need consider a new keyboard.

CarlTR6,

Thanks for going that extra mile to retrieve the drivers' information, but I beat you to it :). I renamed sptd.sys to sptd.bak, updated all of the drivers you listed except for the Symantec ones from the manufacturers' sites, and completely removed Symantec Endpoint using the Norton Removal Tool, along with installing, updating, and scanning with Microsoft Security Essentials.

I had not known the effects of obsolete drivers, so thanks for bringing that to my attention, and I will be sure to be more on top of that in the future.

Appears as if my RAM is not the problem. I tested every RAM stick individually, and each showed no errors while running Memtest86+ for about 3 Passes each. From here I can only assume it is a RAM slot on my new motherboard, which is thankfully still under warranty if I need to replace it, but it is 3:00am, and I will test the slots tomorrow. You were right about it being time consuming, because it took the whole day and then some.

In the meantime, however, I still have a few questions:
-Is Daemon Tools completely unreliable? If so, can I use an alternate drive virtualization program, or should I just keep burning DVDs/CDs?
-Is Microsoft Security Essentials a program I can use on its own, or does it need another antivirus along with it? If so, can you recommend me an antivirus? Preferably one I get the most bang for my buck with, because my budget is very limited.

Thanks again, and I will post back once my RAM slots have been tested.

Regards,
qotsa

P.S.: I apologize; I am new to forums. I do not know how to PM or the like, could you tell me how to do that, too?

qotsa1911 said:

CarlTR6,

Thanks for going that extra mile to retrieve the drivers' information, but I beat you to it :). I renamed sptd.sys to sptd.bak, updated all of the drivers you listed except for the Symantec ones from the manufacturers' sites, and completely removed Symantec Endpoint using the Norton Removal Tool, along with installing, updating, and scanning with Microsoft Security Essentials.

I had not known the effects of obsolete drivers, so thanks for bringing that to my attention, and I will be sure to be more on top of that in the future.

You are very welcome. That is what we are here for and I am glad to be able to help. :)

Appears as if my RAM is not the problem. I tested every RAM stick individually, and each showed no errors while running Memtest86+ for about 3 Passes each. From here I can only assume it is a RAM slot on my new motherboard, which is thankfully still under warranty if I need to replace it, but it is 3:00am, and I will test the slots tomorrow. You were right about it being time consuming, because it took the whole day and then some.

Just a note of caution, three passes may not be enough. We had a BSOD yesterday or the day before where RAM errors did not show up until the 5th pass and did so consistently. That is why we recommend at least five passes.

If you are under warranty, I urge you to get your computer checked out by a tech while you can.

In the meantime, however, I still have a few questions:
-Is Daemon Tools completely unreliable? If so, can I use an alternate drive virtualization program, or should I just keep burning DVDs/CDs?

Yes there are virtualization programs that do not use the stpt driver and they work well with Windows. I do not know the name of them; but some on the team do. I will find out for you.

-Is Microsoft Security Essentials a program I can use on its own, or does it need another antivirus along with it? If so, can you recommend me an antivirus? Preferably one I get the most bang for my buck with, because my budget is very limited.

Thanks again, and I will post back once my RAM slots have been tested.

Regards,
qotsa

MSE is fine on its own and offers solid protection. Avast (free) runs well with Windows also. In fact, MSE and Avast can run simultaneously with no conflicts. This is an exception to the rule of not running two antivirus programs. For added protection, I suggest you download Malwarebytes (free) and run it on demand - once a day, once a week, whatever you are comfortable with. It runs fine with Win 7.

P.S.: I apologize; I am new to forums. I do not know how to PM or the like, could you tell me how to do that, too?

To PM someone, go to their profile by clicking on their name. In the profile in the upper left, click on send message.

Let us know how the RAM slots are. :)

Thanks for the update.

That is certainly evidence that there is something wrong. Since you have a warranty, you don't have to pinpoint the cause. You can stop the testing. I suggest that you take it in to the shop. Tell them what you problems are and the steps you have taken so far. Be sure to tell them what Memtest showed. Keep us posted. Let us know what the do and what they find.

Go ahead and install MSE. I have not gotten the name of a CD virtualization program yet; but I will do so shortly. I will post it here.

Edited to add: MagicDisc is a free alternative virtualization program that does not use SPTD.