IRQl_NOT_LESS_OR_EQUAL Random BSOD While playing Tera, Error 0xA

Verenios · 21 May 2012

Hello,

I just brought a brand new custom built desktop computer 3 weeks ago which basically has all the lastest hardware inside of it and it runs perfectly with no problems but least once or twice i have had a BSOD while on Mozilla Firefox while streaming but i looked at its AddOns and some said best to turn off as it couldn't find updates so i did that and for now haven't had anymore BSOD but now when i play Tera Online every now and then maybe once or twice a day sometimes never i get a BSOD while playing, The computer was setup and ready for me to do what ever from day one from the computer store i got it from just now and then i have installed driver updates from the manufacturers websites to keep up to date thats all i have pretty much done from now i downloaded WhoCrashed as i saw in one topic someone said to download and it comes up with...

On Mon 21/05/2012 3:06:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052212-19546-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x282E0)
Bugcheck code: 0xA (0xFFFFF8800C85E000, 0xD, 0x1, 0xFFFFF800030A5A50)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Mon 21/05/2012 3:06:26 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF8800C85E000, 0xD, 0x1, 0xFFFFF800030A5A50)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Thats basically the results it gives me but i have looked all over and updated all my drivers well the ones i know of to see if that fixes it but still i get the BSOD...

Anyways i have Windows Home Premium 64bit and have attached the dump files and health report down below, I really hope i can get this resolved! Thank you in advance.

usasma · 22 May 2012

Only one memory dump in the enclosed reports. If you are using a disk cleanup utility, please don't use it while we're troubleshooting.

You have a TP-LINK 150Mbps Wireless N Adapter. Win7 doesn't like these devices, and if you're using a Vista-era driver with it it's sure to start spitting out BSOD's. Here's my rant about these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

SSD's must have the latest firmware installed, and you must have the latest controller drivers (for your motherboard) from the manufacturer of the controller that's on you motherboard (not from the motherboard manufacturer).
Here's my rant on these devices:
We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

These 2 devices are disabled:

Bluetooth PAN Network Adapter ROOT\NET\0000 This device is disabled.

Realtek PCIe GBE Family Controller PCI\VEN_10EC&DEV_8168&SUBSYS_81681849&REV_06\4&9B80F17&0&00AB This device is disabled.

These devices must either be:
- be uninstalled and then removed from the system
- or re-enabled, drivers updated, and then disable them again

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download and install a fresh copy of the ATI drivers from http://www.ati.com (in the upper right corner of the page)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC). This is a separate issue and isn't required for the AMD OverDrive removal.

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Some free alternatives (I don't use them, so I can't comment on them)
KernSafe iSCSI initiator, Virtual CD/DVD-RW Emulator, Virtual Encryption Disk and Virtual CD/DVD-ROM Emulator All-in-One free software.
MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

MSI Afterburner (along with Riva Tuner and EVGA Precision are known to cause BSOD's on Win7 systems. Please uninstall it immediately.

I have seen problems recently with XFast USB, but not enough to ask you to uninstall it. Please keep an eye on this in case the BSOD's continue.

Older Western Digital software is known to have problems with some Win7 systems. Please uninstall it from your system.

These older drivers need updating or should be removed from your system (click on the links for more info about what program the driver belongs to):
000.fcl Fri Sep 26 09:11:22 2008 (48DCDF7A)
http://www.carrona.org/drivers/driver.php?id=000.fcl

BTHidMgr.sys Mon Mar 05 07:17:15 2007 (45EC0A4B)
http://www.carrona.org/drivers/driver.php?id=BTHidMgr.sys

BlueletSCOAudio.sys Mon Mar 05 07:16:23 2007 (45EC0A17)
http://www.carrona.org/drivers/driver.php?id=BlueletSCOAudio.sys

FNETURPX.SYS Fri Oct 03 22:27:02 2008 (48E6D476)
http://www.carrona.org/drivers/driver.php?id=FNETURPX.SYS

MTiCtwl.sys Tue Nov 04 02:40:50 2008 (490FFC82)
http://www.carrona.org/drivers/driver.php?id=MTiCtwl.sys

VComm.sys Mon Mar 05 07:17:28 2007 (45EC0A58)
http://www.carrona.org/drivers/driver.php?id=VComm.sys

VcommMgr.sys Mon Mar 05 07:17:48 2007 (45EC0A6C)
http://www.carrona.org/drivers/driver.php?id=VcommMgr.sys

blueletaudio.sys Mon Mar 05 07:16:09 2007 (45EC0A09)
http://www.carrona.org/drivers/driver.php?id=blueletaudio.sys

btnetdrv.sys Mon Mar 05 07:18:08 2007 (45EC0A80)
http://www.carrona.org/drivers/driver.php?id=btnetdrv.sys

pnarp.sys Tue Oct 28 01:57:00 2008 (4906A9AC)
http://www.carrona.org/drivers/driver.php?id=pnarp.sys

purendis.sys Tue Oct 28 00:31:28 2008 (490695A0)
http://www.carrona.org/drivers/driver.php?id=purendis.sys

vbtenum.sys Mon Mar 05 07:17:00 2007 (45EC0A3C)
http://www.carrona.org/drivers/driver.php?id=vbtenum.sys

wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


000.fcl             Fri Sep 26 09:11:22 2008 (48DCDF7A)

ALSysIO64.sys       Sat Jul 09 20:27:45 2011 (4E18F201)

AODDriver2.sys      Tue Mar 06 04:55:00 2012 (4F55DEF4)

AmdLLD64.sys        Wed Apr 22 15:32:17 2009 (49EF70C1)

AsrAppCharger.sys   Tue May 10 04:28:46 2011 (4DC8F73E)

AsrRamDisk.sys      Thu Jan 12 23:52:38 2012 (4F0FB896)

AsrVDrive.sys       Wed Jan 26 04:11:02 2011 (4D3FE526)

AtihdW76.sys        Thu Feb 23 07:30:12 2012 (4F463154)

BTHidMgr.sys        Mon Mar 05 07:17:15 2007 (45EC0A4B)

BlueletSCOAudio.sys Mon Mar 05 07:16:23 2007 (45EC0A17)

CLBStor.sys         Thu Jul 15 06:05:41 2010 (4C3EDD75)

CLBUDF.SYS          Thu Jul 15 06:05:36 2010 (4C3EDD70)

FNETTBOH_305.SYS    Fri May 13 01:09:28 2011 (4DCCBD08)

FNETURPX.SYS        Fri Oct 03 22:27:02 2008 (48E6D476)

L8042Kbd.sys        Fri Sep 02 02:24:42 2011 (4E6076AA)

L8042mou.Sys        Fri Sep 02 02:24:39 2011 (4E6076A7)

LHidFilt.Sys        Fri Sep 02 02:23:09 2011 (4E60764D)

LMouFilt.Sys        Fri Sep 02 02:23:15 2011 (4E607653)

LMouKE.Sys          Fri Sep 02 02:24:28 2011 (4E60769C)

MBfilt64.sys        Thu Jul 30 23:40:32 2009 (4A7267B0)

MTiCtwl.sys         Tue Nov 04 02:40:50 2008 (490FFC82)

RTCore64.sys        Tue Sep 06 08:24:50 2011 (4E661112)

RTKVHD64.sys        Tue Mar 27 05:01:50 2012 (4F7181FE)

Rt64win7.sys        Thu Feb 16 00:39:50 2012 (4F3C96A6)

VComm.sys           Mon Mar 05 07:17:28 2007 (45EC0A58)

VcommMgr.sys        Mon Mar 05 07:17:48 2007 (45EC0A6C)

WmBEnum.sys         Tue Apr 27 16:10:19 2010 (4BD744AB)

WmFilter.sys        Tue Apr 27 16:10:19 2010 (4BD744AB)

WmXlCore.sys        Tue Apr 27 16:09:26 2010 (4BD74476)

actg707k.SYS        Tue Dec 27 17:30:45 2011 (4EFA4715)

amdiox64.sys        Thu Feb 18 10:17:53 2010 (4B7D5A21)

amdsata.sys         Wed Oct 07 16:13:09 2009 (4ACCF655)

amdxata.sys         Wed Oct 07 16:13:10 2009 (4ACCF656)

asmthub3.sys        Fri Mar 04 02:55:10 2011 (4D709ADE)

asmtxhci.sys        Fri Mar 04 02:54:59 2011 (4D709AD3)

athrx.sys           Fri Nov 06 15:56:02 2009 (4AF48D62)

atikmdag.sys        Thu Apr 05 21:48:25 2012 (4F7E4B69)

atikmpag.sys        Thu Apr 05 21:10:44 2012 (4F7E4294)

blueletaudio.sys    Mon Mar 05 07:16:09 2007 (45EC0A09)

btnetdrv.sys        Mon Mar 05 07:18:08 2007 (45EC0A80)

cfosspeed6.sys      Mon Jul 04 09:18:51 2011 (4E11BDBB)

kl1.sys             Fri Mar 04 04:20:03 2011 (4D70AEC3)

kl2.sys             Fri Mar 04 04:17:31 2011 (4D70AE2B)

klif.sys            Wed Apr 20 06:34:31 2011 (4DAEB6B7)

klim6.sys           Thu Mar 10 09:36:02 2011 (4D78E1D2)

klmouflt.sys        Mon Nov 02 11:26:06 2009 (4AEF081E)

lvrs64.sys          Thu Dec 15 00:13:30 2011 (4EE981FA)

lvuvc64.sys         Thu Dec 15 00:14:00 2011 (4EE98218)

pnarp.sys           Tue Oct 28 01:57:00 2008 (4906A9AC)

purendis.sys        Tue Oct 28 00:31:28 2008 (490695A0)

rikvm_90970B6B.sys  Wed Apr 28 22:26:32 2010 (4BD8EE58)

sptd.sys            Sat Mar 03 11:45:52 2012 (4F524AC0)

usbfilter.sys       Wed Oct 07 03:44:08 2009 (4ACC46C8)

vbtenum.sys         Mon Mar 05 07:17:00 2007 (45EC0A3C)

wdcsam64.sys        Wed Apr 16 04:39:08 2008 (4805BB2C)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052212-19546-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 21 11:06:26.076 2012 (UTC - 4:00)
System Uptime: 0 days 8:47:23.185
BugCheck A, {fffff8800c85e000, d, 1, fffff800030a5a50}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+691a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!_??_::FNODOBFM::_string_+691a
Bugcheck code 0000000A
Arguments fffff880`0c85e000 00000000`0000000d 00000000`00000001 fffff800`030a5a50
BiosVersion = P1.70
BiosReleaseDate = 03/27/2012
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Verenios · 23 May 2012

Thank you very much for your reply i have stopped using CCleaner for now for cleaning my computer while i get to the bottom of these BSOD's.

Now the TP-LINK 150Mbps Wireless N Adapter is directly plugged into the motherboard through PCI-e and i have gone to the manufacturers website and downloaded the latest driver for it.

As for my SSD i have also go to the manufacturers and downloaded the latest firmware for this but there were no downloads for Update chipset and storage controller drivers that i could find as i don't know much about this stuff but i have gone to the motherboards website and downloaded all of there latest drivers and installed them in the machine.

Now the 2 disabled devices have been re-enabled again and updates there drivers to the latest.

AMD Overdrive i have now uninstalled from my machine but the ATI VISION Engine Control Center i kind of need for some games as they intend to have some flickering bugs now and then and it was suggested i change the settings around within this application until ATI releases more drivers to fix these bugs so hopefully i wont have to remove this feature as my laptop seems to run this just fine.

I have also now removed Daemon Tools along with the sptd driver.

I have removed MSI Afterburner.

XFast USB Utility was installed along with all my drivers from my motherboards CD ROM but i will keep a eye on this as suggested.

Western Digital software that was installed when i plugged in my portable HDD and i have it updated to the most latest software, I haven't had problems with this on my laptop so i hope it wont affect my desktop so i will keep a eye on this.

I have downloaded all the latest drivers that are highlighted in red except for...

000.fcl Fri Sep 26 09:11:22 2008 (48DCDF7A)
http://www.carrona.org/drivers/driver.php?id=000.fcl

&

wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

The fci one from cyberlink don't seem to provide driver updates unless you update there software so i tried that but i have cyberlink media suite 9 and they now have media suite 10 put but want me to pay again for it so i hope i can bypass this but will keep a eye.

The wdcsam64 i don't know why this is outdated as the WD Software Updater also updates the driver but just incase i uninstalled the program and reinstalled it and hope that the driver is updated along with it.

I will keep in touch if i get another BSOD i will post a new dmp file for you here and again thank you very much for your reply and help.

Also while im here in my device manager my driver TP-LINK 150Mbps Wireless N Adapter used to be called TP-LINK 150Mbps Wireless N Adapter but now its called TP-LINK 150Mbps Wireless N Adapter #4 is there anyway i can make it back to TP-LINK 150Mbps Wireless N Adapter again? sorry im a lil OCD when it comes to this stuff, Thank you in advance.

usasma · 23 May 2012

I've never found a way, but I haven't looked for a long while (since I was using Windows 2000).
It has to involve removing all the traces of the old devices and then reinstalling the new drivers again - but I have no idea of the details required. Try posting over in the General forums for more expert assistance.

Verenios · 23 May 2012

Okay as of far i have had the computer on for 16hrs straight and not even one BSOD and thats with doing my usual daily activities which is MSN, SKype, Ventrilo, & Playing Games all at the same time as well as watching videos on Mozilla, Usually after 3-4hrs of gameplay it hits a BSOD but i was able to play for 7hrs with no problems, So i will keep you posted in case of another BSOD.

I was thinking of keeping a eye on the machine for 7 days and after that i can say for 100% problem solved! So yet again thank you very much usasma for your help with this problem!

usasma · 23 May 2012

Sounds like one of the things that you did solved it!
Thanks for letting us know!
Good Luck!

Verenios · 02 Jun 2012

Ok so its been a little over 7 days now and only have had 1 BSOD which i found out was due to ATI Vision Center had its own AMD Overdrive feature and it was turned on, So once i turned this off it was bye bye BSOD after that.. I think why i was getting BSOD was cause of that cause since my motherboard is a ASRock 970 Extreme4 with a AMD processor it has a feature to enable turbo mode which activates all 8 cores and boosts my Ghz from 3.6 to 4.2 and i heard turbo mixed with overdrive or any type of overclocking your graphics can cause that as its too much stress so yeah thank you so much usasma for all your help :)

I still couldn't find away to get the fci.sys updated nor the wdcsam64.sys but like i said no BSOD so seems windows is ok with them.

usasma · 02 Jun 2012

Updating the FCL is difficult - but it doesn't usually cause problems so it's usually not a concern.

If you're having difficulties updating the wdcsam64.sys - then I'd suggest uninstalling the Western Digital software in order to remove it from your system.