Bsod driver_irql_not_less_or_equal


  1. Posts : 3
    Win7 32b
       #1

    Bsod driver_irql_not_less_or_equal


    Hy all,

    I just buy a new laptop Sony Vaio VPCEB3L1E, even from the first with the preinstaled windows(win7 Hom Premium 64b) I receive BSOD. I just ignore it and install a fresh Win 7 Ultimate 32b. I still receive BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL.
    What to do?
    I use as antivirus Kaspersky Pure, perfmon /report did not fint any AV installed...
    Also see attachment!
    Thank`s
    Last edited by Jacota; 06 Nov 2010 at 04:18.
      My Computer


  2. Posts : 507
    Windows 7 Ultimate x64 SP1
       #2

    So the memory test indicated error during 3 passes?
    Why dont you RMA the laptop because a good RAM won't show error just for 3 rounds.
    RAM - Test with Memtest86+
      My Computer


  3. Posts : 3
    Win7 32b
    Thread Starter
       #3

    Thank`s for your reply. Unfortunately I can`t RMA the laptop.
    If I`ll replace the RAM the problem should be solved right?
      My Computer


  4. Posts : 507
    Windows 7 Ultimate x64 SP1
       #4

    Yes, it should solve your problem.
    Error that show in memtest indicated hardware problem not software/driver problem.
    In other hand, if you have replaced and have good RAM but still get BSOD problem so it might be software/driver problem.
    At that time you may post the data again here :)
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    Jacota said:
    Hy all,

    I just buy a new laptop Sony Vaio VPCEB3L1E, even from the first with the preinstaled windows(win7 Hom Premium 64b) I receive BSOD. I just ignore it and install a fresh Win 7 Ultimate 32b. I still receive BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL.
    What to do?
    I use as antivirus Kaspersky Pure, perfmon /report did not fint any AV installed...
    Also see attachment!
    Thank`s

    More from DMP

    This one was caused by your athr.sys, driver. It should be updated and re-installed.



    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\110510-24414-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82c4c000 PsLoadedModuleList = 0x82d94810
    Debug session time: Fri Nov  5 06:09:06.162 2010 (GMT-4)
    System Uptime: 0 days 0:00:56.224
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, 2, 8, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\athr.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athr.sys
    *** ERROR: Module load completed but symbols could not be loaded for athr.sys
    Probably caused by : athr.sys ( athr+7b1e3 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82db4718
    Unable to read MiSystemVaType memory at 82d94160
     00000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +5fb0952f03e7dd40
    00000000 ??              ???
    
    PROCESS_NAME:  System
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    TRAP_FRAME:  82d72a88 -- (.trap 0xffffffff82d72a88)
    ErrCode = 00000010
    eax=00000000 ebx=878b0008 ecx=878118a0 edx=00000000 esi=868860e0 edi=82d5be2a
    eip=00000000 esp=82d72afc ebp=82d72b08 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    00000000 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 00000000 to 82c9282b
    
    FAILED_INSTRUCTION_ADDRESS: 
    +5fb0952f03e7dd40
    00000000 ??              ???
    
    STACK_TEXT:  
    82d72a88 00000000 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    82d72af8 924b21e3 00000000 878118a0 82d72b38 0x0
    82d72b08 8c616774 00000000 878118a0 00000000 athr+0x7b1e3
    82d72b38 82cb604d 878b0040 008b0008 7aded880 ndis!ndisMTimerObjectDpc+0xbc
    82d72b7c 82cb5ff1 82d75d20 82d72ca8 00000003 nt!KiProcessTimerDpcTable+0x50
    82d72c68 82cb5eae 82d75d20 82d72ca8 00000000 nt!KiProcessExpiredTimerList+0x101
    82d72cdc 82cb420e 00000e14 875f37b8 82d7f280 nt!KiTimerExpiration+0x25c
    82d72d20 82cb4038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
    82d72d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    athr+7b1e3
    924b21e3 ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  athr+7b1e3
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: athr
    
    IMAGE_NAME:  athr.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4acea1f4
    
    FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_athr+7b1e3
    
    BUCKET_ID:  0xD1_CODE_AV_NULL_IP_athr+7b1e3
    
    Followup: MachineOwner
    ---------
    You have a few old drivers
    Code:
    SFEP.sys        0x92418480    0x00002480    8/3/2007 01:36:08            0x46b2bec8    0x92416000                
    teamviewervpn.sys        0x909a5200    0x00006200    11/29/2007 04:27:19            0x474e77e7    0x9099f000
      My Computer


  6. Posts : 12
    Windows 7 Ultimate 32bit
       #6

    Sorry for your problem.
    My advice is:
    1st try zigzag3143 advice and update or reinstall athr.sys
    2nd try to take one memory mod out from laptop and start application that was crashing.If you get BSOD again or application crush take out other mod and back first in and do same thing.That will show you if one of your mem mod don't work good or mem slots are bad.

    I hope that you resolve problem with this.
    If not post BSODs again.
    GL
      My Computer


  7. Posts : 3
    Win7 32b
    Thread Starter
       #7

    I test each memory on each slot, 20 Pass each test. No errors found.
    Also both modules togheter and no error found (9 pass test).
    Driver for wi.fi removed and reinstalled.
    New BOSD attached.
    Curious that on first memtest with both modules 1 error was foundet, bur last tests are ok, it is possible?
      My Computer


  8. Posts : 507
    Windows 7 Ultimate x64 SP1
       #8

    Hi,
    Your atheros driver was blamed again as the cause, so follow zigzag3143 advice to update it.

    Then for troubleshooting your problem, uninstall Kaspersky and replace it with MSE.
    You may go back to Kaspersky a week after your windows running better and free from BSOD.
    http://www.microsoft.com/security_essentials/

    Also uninstall Tuneup Utilities because it use 2009 driver.

    These drivers need to be update:
    Code:
    teamviewervpn.sys Thu Nov 29 00:27:19 2007 --> TeamViewerVPN Network Adapter
    SFEP.sys     Thu Aug 02 22:36:08 2007 -->    Sony Firmware Extension Parser driver
    athr.sys Tue Jun 09 11:04:52 2009 --> Atheros Extensible Wireless LAN  driver for CB42/CB43/MB42/MB43 Network Adapte
    Log
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {30, 2, 0, 8f0488a5}
    
    Unable to load image \SystemRoot\system32\DRIVERS\athr.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athr.sys
    *** ERROR: Module load completed but symbols could not be loaded for athr.sys
    Probably caused by : athr.sys ( athr+428a5 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000030, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8f0488a5, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82dbb718
    Unable to read MiSystemVaType memory at 82d9b160
     00000030 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    athr+428a5
    8f0488a5 8b5130          mov     edx,dword ptr [ecx+30h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  8ad1c894 -- (.trap 0xffffffff8ad1c894)
    ErrCode = 00000000
    eax=0000001a ebx=87e3e258 ecx=00000000 edx=00000088 esi=00000000 edi=00000000
    eip=8f0488a5 esp=8ad1c908 ebp=8ad1c90c iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    athr+0x428a5:
    8f0488a5 8b5130          mov     edx,dword ptr [ecx+30h] ds:0023:00000030=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 8f0488a5 to 82c9982b
    
    STACK_TEXT:  
    8ad1c894 8f0488a5 badb0d00 00000088 00000001 nt!KiTrap0E+0x2cf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8ad1c90c 8f048647 00000000 c64a83cc ada5c490 athr+0x428a5
    8ad1c944 8f047c52 885f6108 87bcdda8 00000000 athr+0x42647
    8ad1c96c 8f06efc0 885f6028 87bcdda8 00000018 athr+0x41c52
    8ad1c9c0 8f06f8c7 8792b020 87bcdda8 00000000 athr+0x68fc0
    8ad1cb14 8f020cfe 87bcdda8 8ad1cb30 8f01dd2f athr+0x698c7
    8ad1cb20 8f01dd2f 87bcdda8 879ff5f8 8ad1cb40 athr+0x1acfe
    8ad1cb30 8f0659c7 879ff5f8 87bcdda8 8ad1cb68 athr+0x17d2f
    8ad1cb40 8f0656b7 87b59628 87bcdda8 00000000 athr+0x5f9c7
    8ad1cb68 8f01962a 87b59628 87bcdda8 00000000 athr+0x5f6b7
    8ad1cb94 8f019414 879ff8c0 87bcdd20 87e3e258 athr+0x1362a
    8ad1cbac 8f01a499 879ff8c0 883d6828 c642c0f0 athr+0x13414
    8ad1cbc4 8f01a525 879ff8c0 8ad1cbdc 8f077554 athr+0x14499
    8ad1cbd0 8f077554 879ff8c0 8ad1cbf8 8f07c1ff athr+0x14525
    8ad1cbdc 8f07c1ff 87b56020 87e30022 8ad01a54 athr+0x71554
    8ad1cbf8 8f020abd 87b56020 8ad1cc14 8f007761 athr+0x761ff
    8ad1cc04 8f007761 8792b020 879ff8c0 8ad1cc50 athr+0x1aabd
    8ad1cc14 88e7c309 879ff8c0 00000000 8ad1cc40 athr+0x1761
    8ad1cc50 88e279f4 87e3e26c 00e3e258 00000000 ndis!ndisMiniportDpc+0xe2
    8ad1cc78 82cbb3b5 87e3e26c 87e3e258 00000000 ndis!ndisInterruptDpc+0xaf
    8ad1ccd4 82cbb218 8ad00120 8ad05800 00000000 nt!KiExecuteAllDpcs+0xf9
    8ad1cd20 82cbb038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
    8ad1cd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    athr+428a5
    8f0488a5 8b5130          mov     edx,dword ptr [ecx+30h]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  athr+428a5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: athr
    
    IMAGE_NAME:  athr.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea444
    
    FAILURE_BUCKET_ID:  0xD1_athr+428a5
    
    BUCKET_ID:  0xD1_athr+428a5
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm athr
    start    end        module name
    8f006000 8f116000   athr     T (no symbols)           
        Loaded symbol image file: athr.sys
        Image path: \SystemRoot\system32\DRIVERS\athr.sys
        Image name: athr.sys
        Timestamp:        Tue Jun 09 11:04:52 2009 (4A2EA444)
        CheckSum:         0011A043
        ImageSize:        00110000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 13:05.
Find Us