Windows 7 - BSOD "driver_irql_not_less_or_equal" and "irql_not_less_or_equal"

voxivoid · 02-12-2012

Windows 7 32 bit
My pc has 5 months which specs (it was built home):

ASUS P8H61 PLUS REV 3.0
INTEL CORE i3 2120 (3.3GHZ) SKT 1155
NOX URANO 600W 12CM SLI
NOX COOLBAY BLACK (WINDOW)
CORSAIR 2GB DDR3 1333MHZ XMS3 (CL9)
ASUS GT520 SILENT 1GB DDR3 PCI-E
REVOLTEC 3 PIN Y CABLE
SEAGATE 500GB SATA III 16MB (the one who as the OS installed)
Old HITACHI hdd

I've formated it yesterday and the error persisted. I'm not pretty sure when it occurs but usually happens when I'm using firefox (but mainly randomly). And I've also the latest BIOS installed (and drivers, I think). If anyone could help I appreciate it

usasma · 02-12-2012

SP1 isn't installed, please do the following:

Quote:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates

Windows 7 doesn't like wireless USB devices. You have Adaptador de Rede USB Sem Fios Linksys RangePlus

Quote:

I do not recommend using wireless USB devices. Especially in Windows 7 systems.
These wireless USB devices have many issues with Windows 7 - 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 Windows 7 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.

I've got to wonder about your Comodo Internet Security due to the involvement of the networking drivers. Please do the following:

Quote:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the antivirus software from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of the antivirus software using one of these free tools: Antivirus Uninstallers
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.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
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
inspect.sys  Mon Dec 19 13:43:35 2011 (4EEF85D7)
cmdguard.sys Tue Jan 17 14:49:31 2012 (4F15D0CB)
cmdhlp.sys   Mon Dec 19 13:43:37 2011 (4EEF85D9)
nvlddmkm.sys Sat Oct 15 02:34:27 2011 (4E992973)
HECI.sys     Wed Nov 09 19:52:00 2011 (4EBB2030)
nvhda32v.sys Thu Jul 07 12:20:54 2011 (4E15DCE6)
RTKVHDA.sys  Tue Dec 13 05:23:47 2011 (4EE727B3)
netr28u.sys  Wed Feb 25 21:42:42 2009 (49A601A2)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021212-16863-01.dmp]
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Debug session time: Sun Feb 12 16:11:22.780 2012 (UTC - 5:00)
System Uptime: 0 days 0:45:25.200
BugCheck D1, {1, 2, 0, 88c2d029}
Probably caused by : NETIO.SYS ( NETIO!WfpStartTimer+92 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xD1_NETIO!WfpStartTimer+92
Bugcheck code 000000D1
Arguments 00000001 00000002 00000000 88c2d029
BiosVersion = 0604
BiosReleaseDate = 09/28/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3291
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021212-18002-01.dmp]
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Debug session time: Sun Feb 12 09:12:17.602 2012 (UTC - 5:00)
System Uptime: 0 days 1:48:14.046
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+238 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_nt!MiInsertPageInFreeOrZeroedList+238
Bugcheck code 0000000A
Arguments 87a8bc00 00000002 00000001 82ce3d0e
BiosVersion = 0604
BiosReleaseDate = 09/28/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3291
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

voxivoid · 02-13-2012

I've uninstalled Comodo Firewall and installed MSE and service pack 1 and untill now everything's fine. I'll post if some error apear again. Thanks!

voxivoid · 02-14-2012

new error, now memory management

voxivoid · 02-14-2012

==================================================
Dump File : 021412-45427-01.dmp
Crash Time : 14-02-2012 20:41:47
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000008
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x82adaf1b
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+415fb
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415fb
Stack Address 1 : ntkrnlpa.exe+98f1b
Stack Address 2 : ntkrnlpa.exe+92b4d
Stack Address 3 : ntkrnlpa.exe+9e0d9
Computer Name :
Full Path : C:\Windows\Minidump\021412-45427-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 154.720
==================================================

==================================================
Dump File : 021412-17877-01.dmp
Crash Time : 14-02-2012 14:52:06
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00000403
Parameter 2 : 0xc004ac50
Parameter 3 : 0x525b786f
Parameter 4 : 0xc024ac50
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+a10a6
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+a10a6
Stack Address 1 : ntkrnlpa.exe+9fcb1
Stack Address 2 : ntkrnlpa.exe+baacb
Stack Address 3 : ntkrnlpa.exe+3e21a
Computer Name :
Full Path : C:\Windows\Minidump\021412-17877-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 158.328
==================================================

that's BlueScreenView info, it keeps happening

usasma · 02-14-2012

While I admire Nir Sofer's work, BlueScreenView doesn't always point out the correct things.
I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps - so please zip up the memory dumps and upload them for us to have a look at (we don't need the full jcgriff2 report each time).

This one (the one from post 4) is the 2nd one in post 5 also. It's a memory managment error - and there doesn't seem to be any troublesome remnants - so that suggests that it's hardware or Windows.

Please start out with these free diagnostics: Hardware Diags Start with the Memory Test and Prime95.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.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
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


MpFilter.sys  Wed Apr 06 14:25:55 2011 (4D9CB033)
vmbus.sys     Sat Nov 20 04:14:58 2010 (4CE79192)
winhv.sys     Sat Nov 20 03:38:15 2010 (4CE788F7)
amdxata.sys   Fri Mar 19 12:19:01 2010 (4BA3A3F5)
nvhda32v.sys  Thu Jul 07 12:20:54 2011 (4E15DCE6)
nvlddmkm.sys  Sat Oct 15 02:34:27 2011 (4E992973)
netr28u.sys   Wed Feb 25 21:42:42 2009 (49A601A2)
RTKVHDA.sys   Tue Dec 13 05:23:47 2011 (4EE727B3)
NisDrvWFP.sys Wed Apr 06 14:26:30 2011 (4D9CB056)
MpNWMon.sys   Wed Apr 06 14:25:54 2011 (4D9CB032)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021412-17877-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Tue Feb 14 09:50:39.978 2012 (UTC - 5:00)
System Uptime: 0 days 0:41:07.024
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+46
Bugcheck code 0000001A
Arguments 00000403 c004ac50 525b786f c024ac50
BiosVersion = 0604
BiosReleaseDate = 09/28/2011
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3291
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

voxivoid · 02-14-2012

What memory test should I use? Memory diag?

usasma · 02-14-2012

Yep, this one: Hardware Diags

voxivoid · 02-15-2012

MemTest didn't find any error
http://img802.imageshack.us/img802/1520/sdc14669.jpg

Prime95 found an error
[Wed Feb 15 17:14:52 2012]
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
Self-test 512K passed!
[Wed Feb 15 17:31:24 2012]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Wed Feb 15 17:46:31 2012]
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
Self-test 576K passed!
[Wed Feb 15 18:02:37 2012]
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
[Wed Feb 15 18:17:49 2012]
Self-test 672K passed!
Self-test 672K passed!
Self-test 672K passed!
Self-test 672K passed!
[Wed Feb 15 18:33:05 2012]
Self-test 20K passed!
Self-test 20K passed!
Self-test 20K passed!
Self-test 20K passed!
[Wed Feb 15 18:49:09 2012]
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
Self-test 800K passed!
[Wed Feb 15 19:05:32 2012]
Self-test 28K passed!
Self-test 28K passed!
FATAL ERROR: Rounding was 0.49609375, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Self-test 28K passed!
[Wed Feb 15 19:20:59 2012]
Self-test 960K passed!
Self-test 960K passed!
Self-test 960K passed!
[Wed Feb 15 19:37:11 2012]
Self-test 40K passed!
Self-test 40K passed!
Self-test 40K passed!
[Wed Feb 15 19:53:34 2012]
Self-test 1120K passed!
Self-test 1120K passed!
Self-test 1120K passed!

usasma · 02-15-2012

Quote:

FATAL ERROR: Rounding was 0.49609375, expected less than 0.4
Hardware failure detected, consult stress.txt file.

This is an error.
Now, run the following 3 Prime95 tests:
- Blend
- Large FFT's
- Small FFT's

Time how long it takes for an error to appear (for each test).
Crashes count as an error
Let us know the results and we'll figure out if it's - CPU cache, memory controller (on CPU), or RAM

Windows 7 - BSOD "driver_irql_not_less_or_equal" and "irql_not_less_or_equal"

BSOD "driver_irql_not_less_or_equal" and "irql_not_less_or_equal" problems?