BSOD with driver_irql_not_less_or_equal message


  1. Posts : 3
    Windows 7 Home Premium x64
       #1

    BSOD with driver_irql_not_less_or_equal message


    Built a new computer over the holidays and keep encountering a blue screen with this message on it after a few hours of use. The screen disappears before I can get the detailed error codes, but I was however to find this data as soon as my computer restarted
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: d1
    BCP1: 0000000000000028
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88001237245
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    System Specs:
    Windows 7 Home Premium x64
    Full Retail
    AMD FX 6100 6 core CPU
    ATI HD 5670 (Visiontek)
    4GB RAM
    Gigabyte motherboard
    All the detailed specs can be found on my profile such as motherboard model number, ect.
    The Windows 7 installation is new, and the hardware is brand new.

    Any help would be appreciated, and I apologize ahead of time if I failed to follow the posting format for this type of thread, I am new here and I'm here because I want to solve this issue.
    Happy Holidays.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Taking a look... Will post back in 10-20 minutes with steps to take. Welcome to SevenForums. :)
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\WickedRaptor\Windows_NT6_BSOD_jcgriff2\123111-17721-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
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03251670
    Debug session time: Sat Dec 31 05:39:37.951 2011 (GMT-7)
    System Uptime: 0 days 11:52:25.091
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {28, 2, 0, fffff88001237245}
    
    Probably caused by : tdx.sys ( tdx!TdxEventReceiveMessagesTransportAddress+235 )
    
    Followup: MachineOwner
    ---------
    
    3: 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: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001237245, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bb100
     0000000000000028 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    tdx!TdxEventReceiveMessagesTransportAddress+235
    fffff880`01237245 8b4628          mov     eax,dword ptr [rsi+28h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880085945f0 -- (.trap 0xfffff880085945f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88008594898 rbx=0000000000000000 rcx=fffff880085948a6
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001237245 rsp=fffff88008594780 rbp=fffffa8004479100
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000002
    r11=fffff88008594898 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    tdx!TdxEventReceiveMessagesTransportAddress+0x235:
    fffff880`01237245 8b4628          mov     eax,dword ptr [rsi+28h] ds:9de1:00000000`00000028=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030881e9 to fffff80003088c40
    
    STACK_TEXT:  
    fffff880`085944a8 fffff800`030881e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`085944b0 fffff800`03086e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07090290 : nt!KiBugCheckDispatch+0x69
    fffff880`085945f0 fffff880`01237245 : fffffa80`07090290 fffff880`05ad779a fffff880`085949e8 fffffa80`073d45d0 : nt!KiPageFault+0x260
    fffff880`08594780 fffff880`016aec75 : fffffa80`073d45d0 00000000`00000000 fffffa80`073d45d0 fffffa80`073d45d0 : tdx!TdxEventReceiveMessagesTransportAddress+0x235
    fffff880`08594970 fffff880`016a884d : fffffa80`00000000 fffffa80`073d45d0 fffffa80`00000000 fffff880`05ad77a2 : tcpip!UdpDeliverDatagrams+0x155
    fffff880`08594b00 fffff880`01687227 : fffffa80`0483c840 fffffa80`055c61a0 00000000`00000002 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x1ed
    fffff880`08594c10 fffff880`01686d3a : 00000000`00000000 fffff880`017a69a0 fffff880`08594dd0 fffffa80`05840760 : tcpip!IppDeliverListToProtocol+0xf7
    fffff880`08594cd0 fffff880`01686339 : fffff880`017a69a0 fffffa80`05841aa0 00000000`00000011 fffff880`08594dc0 : tcpip!IppProcessDeliverList+0x5a
    fffff880`08594d70 fffff880`016840af : 00000000`00000000 fffffa80`04972000 fffff880`017a69a0 00000000`0587fb01 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`08594e50 fffff880`016836a2 : fffffa80`03a683c0 00000000`00000000 fffffa80`0587fb01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`08595050 fffff880`01682b3a : fffffa80`0587fba0 fffff880`08595180 fffffa80`0587fba0 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`08595130 fffff800`03095618 : fffffa80`05841970 00000000`00004800 fffffa80`05f99450 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`08595180 fffff880`01683202 : fffff880`01682a60 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`08595260 fffff880`015330eb : fffffa80`0587b740 00000000`00000000 fffffa80`055c61a0 fffff880`042fa13f : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`085952d0 fffff880`014fcad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`08595340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tdx!TdxEventReceiveMessagesTransportAddress+235
    fffff880`01237245 8b4628          mov     eax,dword ptr [rsi+28h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  tdx!TdxEventReceiveMessagesTransportAddress+235
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tdx
    
    IMAGE_NAME:  tdx.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79332
    
    FAILURE_BUCKET_ID:  X64_0xD1_tdx!TdxEventReceiveMessagesTransportAddress+235
    
    BUCKET_ID:  X64_0xD1_tdx!TdxEventReceiveMessagesTransportAddress+235
    
    Followup: MachineOwner
    ---------
    The problem was caused by a system file. This usually happens if you have corrupt system files, a hardware issue, or an underlying driver that is incompatible with Windows 7. For testing purposes, please uninstall Avast as it is known to cause blue screen errors in some systems. To uninstall, use the steps in avast! Uninstall Utility and install Microsoft Security Essentials - Free Antivirus for Windows in its place to run alongside Windows Firewall.
      My Computer


  4. Posts : 3
    Windows 7 Home Premium x64
    Thread Starter
       #4

    Thank you for your help :) I will take a look at that AV and see if my computer improves (no crashing or anything) One thing i should have noted before is that the blue screen would happen anywhere from 5-12 hours of computer use (leaving the computer running ect. ect.)
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    WickedRaptor said:
    Thank you for your help :) I will take a look at that AV and see if my computer improves (no crashing or anything) One thing i should have noted before is that the blue screen would happen anywhere from 5-12 hours of computer use (leaving the computer running ect. ect.)
    It may be an overheating issue or bad RAM, but we should do one step at a time to determine what fixes the problem. Take care of AV, and then we'll proceed with further steps if needed.
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #6

    Have you had any crashes since replacing AVAST with MSE? Let us know if you still need help.
      My Computer


  7. Posts : 3
    Windows 7 Home Premium x64
    Thread Starter
       #7

    Upate: Since this was almost a year ago, this isn't probably going to be seen unless it is searched directly; however replacing avast with MSE worked wonders. Never was able to give proper thanks to this forum until now.
      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 09:17.
Find Us