irql_not_less_or_equal BSOD, error 0x0000000A

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
    
    • Good and Free system security combination.
    • How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek
    
    
  
  

   Warning

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
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

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

• Disk Check

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

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

BSOD BUGCHECK ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        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:

Code:

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:

• Drivers - Clean Left over Files after Uninstalling

• AMD Driver Autodetect

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

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
• Screenshots and Files - Upload and Post in Seven Forums

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.

• RAM - Test with Memtest86+

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.

Does look like RAM needs to be tested.

Code:

*******************************************************************************
*                                                                             *
*                        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
---------

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.

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. Video Card - Stress Test with Furmark 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.

Video Card - Stress Test with Furmark

Real Temp - CPU temperature monitoring