irql_not_less_or_equal BSOD, error 0x0000000A

[traveler249]

I've been getting this stop error for a few months now at least, at first it would only happen occasionally (once every few weeks/month), but lately (the past month, give or take a week) it's happening a couple times a week on average. I haven't noticed any specific pattern as to when this error occurs. It seems to be more likely to crash the more programs I have running on my computer, but sometimes it'll crash with only one program running.

I've attached the dump files as per the posting instructions. Thanks in advance for any help you can give!

 

[koolkat77]

Welcome to SevenForums.

Norton tends to cause BSOD-s. I would recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials To Test. Please also remove Norton Back-up for the time being. You may install them back if it was not the cause of your blue screens.

• Norton Removal Tool

Make scans with the following:

-Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

-ESET online scanner

• Free Online Virus Scanner | ESET

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    • http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html
    • How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek

   Warning

:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.
Perform a System File Check:

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

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

Disk Check on your hard drive for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

BSOD BUGCHECK ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking 
failure, Installing a faulty or mismatched hardware (especially memory) or a failure 
after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates 
needed, Improperly seated cards, Incompatible storage devices, Overclocking, 
Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

BugCheck 7F, {8, 80050033, 6f8, fffff88000e1e2f1}

*** WARNING: Unable to verify timestamp for volmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgr.sys
Probably caused by : volmgr.sys ( volmgr+92f1 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, 
Backup tool, compatibility
BugCheck A, {0, 2, 0, fffff80002ca3df5}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
---------

Please update your video card drivers:

Driver	c:\windows\system32\drivers\atikmdag.sys (8.1.1.921, 5.76 MB (6,038,016 bytes), 8/4/2009 10:23 PM)
Driver	c:\windows\system32\drivers\stwrt64.sys (6.10.6276.0, 493.50 KB (505,344 bytes), 3/23/2010 2:53 PM)

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

• AMD Driver Autodetect

Let us know the results with further bsod reports if any.

 

[traveler249]

Thanks for the quick reply koolkat, wish I could've gotten back quicker but my internet speed isn't great so some of those downloads took a while.

So I used the Norton removal tool to uninstall Norton Internet Security. I didn't see a tool to remove the Online Backup on the provided link so I did it through the Add/Remove Programs tool. Not sure if that got rid of it completely, but I found another post that said that was just a prompt that asked you to install Norton products anyway.

Kaspersky TDSSKiller found no threats.

ESET scan found no threats.

Installed MSE for now. I was thinking of either switching to that or Avast once my Norton subscription ran out anyway since I've heard good things about both.

MSE scan found no threats.

MBAM scan found no threats.

Windows Resource Protection didn't find any integrity violations.

Disk check found no problems with the drive... I'm starting to wonder if it's a good thing that these scans aren't finding anything wrong, or if it's bad because the cause of the problems still isn't obvious, heh

My start-up programs are pretty bare-bones as it is but I was able to take a few more off the list like Quicktime and iTunes.

Got the new AMD driver installed through their site (weirdly enough the AutoDetect gave me a 404 error when I tried to download through that). Checked it in Device Manager though and it is installed.

Haven't had any BSODs since yesterday, so fingers are crossed that this was just a driver or Norton issue... it hasn't been that long though of course so I'll definitely reply again right away if I get one. If this didn't fix it, I imagine it'll probably happen again in the next couple of days.

On that note, if I do get another one, is it pretty safe to assume this is a hardware issue instead of a software problem? I've read on other people getting these IRQL errors and some of them mentioned they had faulty RAM. I haven't installed any new hardware on this computer since I've gotten it, but I'm wondering if ~3 years of wear and tear from regular use could cause that kind of error.

Oh and last, are there any other logs I should upload, or should I only do that if I get another BSOD?

 

[koolkat77]

You can make two hardware tests, Hard drive and RAM. If and when you have time of course.

Follow these quotes:

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS
• SeaTools for DOS tutorial

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

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

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[traveler249]

It happened again :[ The error code was different this time, I think it was 0x0000003B or something like that... but I imagine it might say in the logs. Had quite a few programs running... iTunes, messenger, a few browsers... I never had problems running that many programs until a few months ago when I started getting these blue screens.

I'll probably run those tests tonight, then. Probably start with the RAM one since I'm afraid that's what the problem is. If I'm understanding this right, testing the individual sticks is basically for finding out if there's a problem with one of the sticks or the motherboard? I don't really want to take the notebook apart myself so if that test does find an error I think I might just take it into Geek Squad or something... but I guess I'll see how it turns out first anyway.

Ran the diagnostic again and attached the file... I'll post again tomorrow after the memory and hard drive tests are finished.

 

[koolkat77]

Does look like RAM needs to be tested.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f04281, fffff88007f72120, 0}

Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )

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

 

[Britton30]

I can't find the manual for your netbook, not enough model number info.
Usually there is a panel on the bottom with 2 or 4 screws which allow access to the RAM. There will be a tiny clip on each side of the RAM modules that are gently pushed to the side and the RAM will pop up allowing you to pull it out.

 

[traveler249]

So I let memtest86+ run for 8 passes and... no errors. The hard drive passed any test I ran it through with SeaTools, too. No crashes since yesterday, so no new logs to post. I was really expecting memtest to find something... anything, really. Any other suggestions?

 

[Britton30]

Memory corruption may be RAM, CPU cache, or graphics memory too. It will take some more tests to try to pin it down. To test graphics follow this. http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html#post866972 Watch for any anomalies (artifacts) in the animation and keep an eye on the temp. Let it run for 30 minutes if temp stay below 70C-85C.

Also try Prime95 to test the CPU and monitor its temp with Real Temp. It should run several hours and watch to see it it reports a "Worker has stopped". The CPU should not go above 70C.

http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html#post866972

Real Temp - CPU temperature monitoring

 

[traveler249]

I might try Prime95 either before I go to bed tonight or tomorrow, but first, I'm running into a couple of weird things with FurMark...

First off, it doesn't seem to be recording the GPU temperature. I followed the instructions in the tutorial, I checked the box for Log GPU data (temperature, power, ...), but it just displayed the GPU temp at 0 C for the entire test (I ran it about ten minutes). I thought I might have forgotten to check the box for the first test but when I double-checked it and ran it again it still said 0 C. I uploaded a screencap of the start of the second attempt, but it didn't get any faster for the ~5 minutes I let it go before stopping.

Also, notice the framerate is abysmal. Most of the time it was only showing one frame every couple of seconds. I didn't see any artifacts, but with the framerate that low I don't even know if they would have a chance to appear.

I'm not really sure what to make of this, but I'm guessing it might be something significant.

 

[Britton30]

With the on-chip GPU I think your frame rate is ok for Furmark at least, it is stressful.

Hate to have you download yet another tool, but try Downloads | techPowerUp to see if it picks up the GPU temp, maybe it doesn't have a temp sensor built in.

Have you checked the HP support website to see if there is a newer BIOS for that machine?

 

[traveler249]

Oh okay I saw some people posting in the tutorial thread that had FPS from 7 to 15, so I wasn't sure if that was normal.

Yeah GPU-Z doesn't show the temperature either, just GPU Load, Core and Memory Clocks, and Memory Usage. I guess it probably doesn't have a built-in temperature sensor then.

RealTemp.exe and RealTempGT.exe won't run: they show an error message "The processor detected is not supported: AMD Turion(tm) II Dual-Core Mobile M520". Should I run Prime95 anyway even if I can't monitor the temperature?

I did get BIOS updated through HP's site. It's showing the updated version in System Information, so at least that went right, haha

 

[Britton30]

Sorry, I knew one of the temp programs won't work with AMD. Try Core Temp it should work. Also Speccy will too and has lots of other system info what can be handy to know. Speccy - System Information - Free Download

As with all downloads read the install windows carefully so you can opt out of crapware bundled in some.

 

[traveler249]

So right after starting the Small FFTS, Coretemp logged the CPU temp going up to 75 C pretty quickly. Only took a few more minutes of testing to get up to 85 C. It topped out at 88 before I stopped it. Didn't seem like a good idea to leave it running for hours at a temperature that high. I only ran it for about 10 minutes in total, so the test didn't show any errors, just the high temperature. If we need to see if the test finds any errors I could run it longer though.

Oh and also, completely separate problem that I've just noticed, but the battery is stuck in the "plugged in, not charging" state. I've fixed it before by uninstalling and reinstalling the ACPI-Compliant Control Method driver, but it didn't work this time. Think it might be because of the BIOS update, since I only noticed it after doing that. Can only seem to find the method I already tried when I google the problem, of course.

 

[Britton30]

Try using the Blend Test instead and see how the temp does.

If the lappy will run with no battery, try that then put the battery back in. How long will in run without the power cable plugged in?

 

[traveler249]

Pretty much the same result with the blend test, pretty quickly got up to 85 C and then rose slowly until I stopped it 10 minutes in... no errors, no warnings, just the high temp.

Haha oh wow that's embarrassing... I tried unplugging the battery before but didn't unplug the charger. It's charging up now. whoops haha

edit: Ah, it only said it was charging for like the 30 seconds it took to post this reply. Now it's back to not charging. Hmmm

edit 2 : It should show how much time is left in hours/minutes when you mouse over the icon in the system tray, yeah? It shows that there's 87% left in the battery, but not how much time that is

 

[Britton30]

Clean the vents out if you haven't yet, with a can of compressed air.
for the battery try this:

• Run on battery until it powers off due to running down.
• Plug in the power and charge it fully.
• Repeat

 

[traveler249]

Ohhhh no no no. Posting from my phone now. Hit the vents with some compressed air (they were a bit dusty), then tried to turn on the computer... And nothing. the caps and scroll lock lights flash, the power button lights up...... But the monitor is black. No HP splash screen, no cursor, nothing. It was fine just minutes before, then i shut it down to clean the vents and now this. It didn't crash either, just shut it down normally.

Didn't get around to draining the battery so that's not it. Any idea for a fix? I can hear the comp start up but then blackness. What the heck could i have done to even cause this?

Edit: a few more unsuccessful tries. Can't even access BIOS. I am at a complete loss.

 

[Britton30]

Ouch! It could be in moving it around to blow dust out you have dislodged the hard drive, battery, or something else.
I'll ask for some help with this.

 

[Arc]

So you cannot access even the BIOS? Is the PSU fan running when you power on? If yes, make it sure that all the hardware is seated properly, including all the cables.

If no, apply a different PSU.

Also, scan the system for possible virus infection with Windows Defender Offline.