IRQL_NOT_LESS_OR_EQUAL Memory Error

[usasma]

I'll start by suspecting your networking drivers.
The older driver list shows an outdated USB networking device.
The BSOD summary shows an error blamed on tcpip.sys (a Windows networking component).

Please download the latest drivers for your USB networking device from the manufacturer's website. Then uninstall the current drivers, then install the freshly downloaded one's. Monitor the system for further BSOD's - if you get them, post them here and we'll do it again!

A lot of older drivers on your system. Please update them as soon as you can get to it:

scmndisp.sys Wed Jan 17 02:48:03 2007
ASACPI.sys   Mon Oct 30 22:09:12 2006
AsIO.sys     Mon Dec 17 04:11:49 2007
wg111v2.sys  Tue Dec 25 21:46:26 2007

Summary of the BSOD's:

Built by: 6001.18295.amd64fre.vistasp1_gdr.090721-0152
Debug session time: Wed Oct 21 08:43:28.132 2009 (GMT-4)
System Uptime: 0 days 12:41:00.448
BugCheck 3B, {c000001d, fffffa6000a5ccad, fffffa60099d4c30, 0}
Probably caused by : hardware ( fileinfo!FIPostCreateCallback+211 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WG111v2.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18304.amd64fre.vistasp1_gdr.090805-0102
Debug session time: Fri Oct 23 06:36:44.757 2009 (GMT-4)
System Uptime: 0 days 0:24:36.884
BugCheck 3B, {c0000005, fffffa6000a56cbf, fffffa60089afc30, 0}
Probably caused by : fileinfo.sys ( fileinfo!FIPostCreateCallback+223 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  left4dead.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18304.amd64fre.vistasp1_gdr.090805-0102
Debug session time: Sat Oct 24 19:53:37.885 2009 (GMT-4)
System Uptime: 0 days 1:22:26.770
BugCheck D1, {bbe1aec3, 2, 0, fffffa6000e74bff}
Probably caused by : tcpip.sys ( tcpip!TcpTimerMppTimeoutHandler+2db )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Eufloria.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18304.amd64fre.vistasp1_gdr.090805-0102
Debug session time: Sat Oct 24 23:30:01.230 2009 (GMT-4)
System Uptime: 0 days 3:35:27.575
BugCheck 50, {ffffffffffffffb4, 1, fffffa6000a0e6df, 0}
Probably caused by : hardware ( fltmgr!FltpPassThrough+2cf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[Lucien]

Well I haven't had a BSOD in the past week so the computer seems fine, however when I do run the memetest I get on average 20-40 errors for each 1% i scan through. Is there some kind of stress test I can run to see how the computer will cope when put through more strenuous demands then I am currently performing? I just want to try to ensure that the problem will not crop up in the future...

Also I visited the manufacturers website to get new drivers for my USB networking device as usasma suggested, apparently its not out of date, however would it be worth looking into purchasing a new USB network device?

With the older drivers you pointed out that I should update, what are they part of and how do I update them? These are the ones you pointed out:
Code:
scmndisp.sys Wed Jan 17 02:48:03 2007
ASACPI.sys Mon Oct 30 22:09:12 2006
AsIO.sys Mon Dec 17 04:11:49 2007
wg111v2.sys Tue Dec 25 21:46:26 2007

 

[usasma]

If you are getting errors using the MemTest program, please follow the procedure in this link to test the individual sticks and slots (steps 7 to 10): Memory Diagnostics

If the sticks are bad, get new one's. If the slots are bad, you'll have to choose between a new motherboard or a new system. BUT - there have been issues with the memory voltage in the P5Q boards - so you may want to ask about that in the Hardware forums.

scmndisp.sys = Netgear Neutral Wireless Solution
ASACPI.sys = Asus AISuite ( ASUSTeK Computer Inc.-Support- download_item_mkt )
AsIO.sys= Asus AISuite ( ASUSTeK Computer Inc.-Support- download_item_mkt )
wg111v2.sys = NETGEAR WG111v2 54Mbps Wireless USB 2.0 Adapter NT Driver

If there's no BSOD's, there's no sense in messing with the system. Just leave everything alone. If you start getting BSOD's again, then you can start with updating those drivers (after the memory is fixed).

 

[Lucien]

Thanks for the prompt response, Il leave it for now in that case, however you wouldn't recommend stress testing?

 

[usasma]

I'm worried about the memory errors - and would suspect that stress testing would just expose them.

If you can afford to replace the memory, do it now. No sense in waiting for it to fail completely.

Beyond that, leave it be until it starts acting up on you.

Good luck!