locked
IRQL_NOT_LESS_OR_EQUAL BSOD with 0x0000000A stop code RRS feed

  • Question

  • Hi all,

    Six months ago, I built an HTPC using a Gigabyte motherboard with integrated ATI 3200 graphics. I'm using an AMD Phenom 9750 quad core CPU and 4GB 1066 RAM. During system burn-in I ran MemCheck for a few days with no reported issues.

    Vista 64 Ultimate has been running fine for 6 months now - NO ISSUES. Yesterday, I couldn't get the screen to come on, and noticed my VFD was frozen. I figured it locked up on me, so I switched off and hard-booted. Several seconds after login, the screen flaked out and I got a BSOD with IRQL_NOT_LESS_OR_EQUAL and a stop code of 0x0000000A. I tried this several times with the same result every time.

    I booted back up to safe mode (with networking). Came up and ran just fine for at least 20 minutes. So I shut down and tried booting back up to normal mode - same BSOD again.

    What can be the problem with this system? It's not an installation issue - it's run clean for 6 months now. Then all of a sudden, it starts to BSOD? What's with that?

    Any ideas would be much appreciated.

    John


    John Calcote, Sr. Software Engineer, Novell
    Thursday, January 29, 2009 5:02 PM

Answers

  •  

    Hi John,

     

    Please understand that to troubleshoot the blue screen issues, we usually need to perform debugging. However, in this forum, we do not provide debugging support. If you would like to perform debugging, please contact Microsoft Customer Support Service (CSS).

     

    To obtain the phone numbers for specific technology request, please refer to the website listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US,  please refer to http://support.microsoft.com for regional support phone numbers.

     

    Having said that, I'd still like to provide the following general troubleshooting steps to see if we can eliminate this problem:

     

    Note: Please perform a complete system backup first. If any unexpected issue occurs, we can quickly restore the system to the current status.

     

    1.   Update the drivers for the motherboard and video card.

     

    2.   Scan your system to make sure that the system is virus free. If you have recently installed any software, hardware or drivers, please remove them.

     

    3.   Ensure all the hardware devices, installed device drivers, and installed applications are all compatible with Windows Vista.

     

    4.   For Compatibility information, please refer to Windows Vista Hardware Compatibility List:

     

    http://winqual.microsoft.com/hcl/

     

    5.   Disable all the third party startup programs and services by using the MSConfig.exe utility shipped with Windows Vista. To use this tool, you can refer to the following Microsoft Knowledge Base article:

     

    (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135

     

    If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit.

     

    However, if the issue still persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon. Thanks!

     

    Tim Quan - MSFT

    Friday, January 30, 2009 9:19 AM
    Moderator

All replies

  • Hello John,

    I am experiencing a very similar problem on my asus striker extreme motherboard (680i) with 4gb 800mhz ram and Q6600. In my case, however, the issue arose on vista ultimate 32bit (SP1). Furthermore, the problem occurs when I set up my ram in dual channel only. See if this happens in your case too.

    I am very tempted to reinstall the OS (maybe even rollback to xp but I'm a gamer and I'll miss DX10).

    Let me post my kernel debug, is yours similar?

     


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x81c34000 PsLoadedModuleList = 0x81d41930
    Debug session time: Thu Jan 29 20:44:42.154 2009 (GMT+0)
    System Uptime: 0 days 0:00:09.883
    Loading Kernel Symbols
    ...............................................................
    ...............................................
    Loading User Symbols

    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {72cffff6, 2, 0, 81caa4c5}

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

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

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 72cffff6, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 81caa4c5, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS:  72cffff6

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MiUnlinkFreeOrZeroedPage+15
    81caa4c5 0fb6460e        movzx   eax,byte ptr [esi+0Eh]

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  8d717bf0 -- (.trap 0xffffffff8d717bf0)
    ErrCode = 00000002
    eax=80cf3000 ebx=92081000 ecx=00000400 edx=00000000 esi=80cf2000 edi=92081000
    eip=81c9dd13 esp=8d717c64 ebp=8d717c6c iopl=0         nv up ei pl nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210212
    nt!memcpy+0x33:
    81c9dd13 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 81caa4c5 to 81c8ec84

    STACK_TEXT: 
    8d7179d0 81caa4c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
    8d717a54 81caafc6 ff55ffff 000002ec 81d42220 nt!MiUnlinkFreeOrZeroedPage+0x15
    8d717a84 81cbe74c 000002ec 86a14030 c0248204 nt!MiRemoveAnyPage+0xa9
    8d717abc 81caf62e 00000001 92081000 c0248204 nt!MiResolveDemandZeroFault+0x411
    8d717b68 81ca580e 92081000 00000000 00000000 nt!MiDispatchFault+0x9a6
    8d717bd8 81c8eab4 00000001 92081000 00000000 nt!MmAccessFault+0xdca
    8d717bd8 81c9dd13 00000001 92081000 00000000 nt!KiTrap0E+0xdc
    8d717c6c 81d7b586 92081000 80cf2000 00001000 nt!memcpy+0x33
    8d717c94 81d7bb70 8b026008 00000000 86a14030 nt!HvpDropPagedBins+0x86
    8d717d7c 81ddc6d5 00000003 76d12ede 00000000 nt!CmpLoadHiveThread+0x351
    8d717dc0 81cc36de 81d7b81e 00000003 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiUnlinkFreeOrZeroedPage+15
    81caa4c5 0fb6460e        movzx   eax,byte ptr [esi+0Eh]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+15

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  48d1b7e8

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MiUnlinkFreeOrZeroedPage+15

    BUCKET_ID:  0xA_nt!MiUnlinkFreeOrZeroedPage+15

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

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 72cffff6, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 81caa4c5, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS:  72cffff6

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MiUnlinkFreeOrZeroedPage+15
    81caa4c5 0fb6460e        movzx   eax,byte ptr [esi+0Eh]

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  8d717bf0 -- (.trap 0xffffffff8d717bf0)
    ErrCode = 00000002
    eax=80cf3000 ebx=92081000 ecx=00000400 edx=00000000 esi=80cf2000 edi=92081000
    eip=81c9dd13 esp=8d717c64 ebp=8d717c6c iopl=0         nv up ei pl nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210212
    nt!memcpy+0x33:
    81c9dd13 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 81caa4c5 to 81c8ec84

    STACK_TEXT: 
    8d7179d0 81caa4c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
    8d717a54 81caafc6 ff55ffff 000002ec 81d42220 nt!MiUnlinkFreeOrZeroedPage+0x15
    8d717a84 81cbe74c 000002ec 86a14030 c0248204 nt!MiRemoveAnyPage+0xa9
    8d717abc 81caf62e 00000001 92081000 c0248204 nt!MiResolveDemandZeroFault+0x411
    8d717b68 81ca580e 92081000 00000000 00000000 nt!MiDispatchFault+0x9a6
    8d717bd8 81c8eab4 00000001 92081000 00000000 nt!MmAccessFault+0xdca
    8d717bd8 81c9dd13 00000001 92081000 00000000 nt!KiTrap0E+0xdc
    8d717c6c 81d7b586 92081000 80cf2000 00001000 nt!memcpy+0x33
    8d717c94 81d7bb70 8b026008 00000000 86a14030 nt!HvpDropPagedBins+0x86
    8d717d7c 81ddc6d5 00000003 76d12ede 00000000 nt!CmpLoadHiveThread+0x351
    8d717dc0 81cc36de 81d7b81e 00000003 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiUnlinkFreeOrZeroedPage+15
    81caa4c5 0fb6460e        movzx   eax,byte ptr [esi+0Eh]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+15

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  48d1b7e8

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MiUnlinkFreeOrZeroedPage+15

    BUCKET_ID:  0xA_nt!MiUnlinkFreeOrZeroedPage+15

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

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 72cffff6, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 81caa4c5, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS:  72cffff6

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MiUnlinkFreeOrZeroedPage+15
    81caa4c5 0fb6460e        movzx   eax,byte ptr [esi+0Eh]

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  8d717bf0 -- (.trap 0xffffffff8d717bf0)
    ErrCode = 00000002
    eax=80cf3000 ebx=92081000 ecx=00000400 edx=00000000 esi=80cf2000 edi=92081000
    eip=81c9dd13 esp=8d717c64 ebp=8d717c6c iopl=0         nv up ei pl nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210212
    nt!memcpy+0x33:
    81c9dd13 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 81caa4c5 to 81c8ec84

    STACK_TEXT: 
    8d7179d0 81caa4c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
    8d717a54 81caafc6 ff55ffff 000002ec 81d42220 nt!MiUnlinkFreeOrZeroedPage+0x15
    8d717a84 81cbe74c 000002ec 86a14030 c0248204 nt!MiRemoveAnyPage+0xa9
    8d717abc 81caf62e 00000001 92081000 c0248204 nt!MiResolveDemandZeroFault+0x411
    8d717b68 81ca580e 92081000 00000000 00000000 nt!MiDispatchFault+0x9a6
    8d717bd8 81c8eab4 00000001 92081000 00000000 nt!MmAccessFault+0xdca
    8d717bd8 81c9dd13 00000001 92081000 00000000 nt!KiTrap0E+0xdc
    8d717c6c 81d7b586 92081000 80cf2000 00001000 nt!memcpy+0x33
    8d717c94 81d7bb70 8b026008 00000000 86a14030 nt!HvpDropPagedBins+0x86
    8d717d7c 81ddc6d5 00000003 76d12ede 00000000 nt!CmpLoadHiveThread+0x351
    8d717dc0 81cc36de 81d7b81e 00000003 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiUnlinkFreeOrZeroedPage+15
    81caa4c5 0fb6460e        movzx   eax,byte ptr [esi+0Eh]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+15

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  48d1b7e8

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0xA_nt!MiUnlinkFreeOrZeroedPage+15

    BUCKET_ID:  0xA_nt!MiUnlinkFreeOrZeroedPage+15

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


    Thursday, January 29, 2009 9:11 PM
  • Hi,

    I'm sorry to say that our problems look a bit different on closer inspection. You're experiencing a very different sort of fault, albeit the same Stop code (IRQL_NOT_..., or 0xA). Both are faulting on the thread-scheduler software interrupt, but you're performing a read operation on 32-bit memory address 0x72cffff6, whereas my system is trying to write to the null pointer (0x0).

    Here's my problem report summary:

    Product
    Windows

    Problem
    Shut down unexpectedly

    Date
    1/28/2009 9:18 PM

    Status
    Report Sent

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.0.6001.2.1.0.256.1
    Locale ID:    1033

    Files that help describe the problem (some files may no longer be available)
    Mini012809-02.dmp
    sysdata.xml
    Version.txt

    Extra information about the problem
    BCCode:    a
    BCP1:    0000000000000000
    BCP2:    0000000000000002
    BCP3:    0000000000000001
    BCP4:    FFFFF80001E9E660
    OS Version:    6_0_6001
    Service Pack:    1_0
    Product:    256_1
    Server information:    7613ebb0-1259-49d1-a6d9-2158906efa86

    John


    John Calcote, Sr. Software Engineer, Novell
    Friday, January 30, 2009 4:46 AM
  • I've discovered a partial work-around to my problem: I ran msconfig and basically disabled everything in my startup list, and many things in my services list. This seemed to make the problem go away. On a hunch, I enabled the symantec end point protection program (anti-virus software), and rebooted. Sure enough - another BSOD. So I disabled the symantec stuff and re-enabled everything else. No BSOD this time.

    Now, I don't believe it's the anti-virus program that's causing the problem. I think the AV program was triggering the problem. I believe that over time, I'll continue to experience this problem on an intermittent basis, and I think it may be OS-related. I believe this because the problem is being caused by the thread-scheduler software interrupt level (IRQL 2).

    The reason I believe this is because it's already happened a couple of times when I've tried to run various programs - such as firefox 3.0.5 (the first time).

    Please advise MS Techs.

    --john


    John Calcote, Sr. Software Engineer, Novell
    Friday, January 30, 2009 4:51 AM
  •  

    Hi John,

     

    Please understand that to troubleshoot the blue screen issues, we usually need to perform debugging. However, in this forum, we do not provide debugging support. If you would like to perform debugging, please contact Microsoft Customer Support Service (CSS).

     

    To obtain the phone numbers for specific technology request, please refer to the website listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US,  please refer to http://support.microsoft.com for regional support phone numbers.

     

    Having said that, I'd still like to provide the following general troubleshooting steps to see if we can eliminate this problem:

     

    Note: Please perform a complete system backup first. If any unexpected issue occurs, we can quickly restore the system to the current status.

     

    1.   Update the drivers for the motherboard and video card.

     

    2.   Scan your system to make sure that the system is virus free. If you have recently installed any software, hardware or drivers, please remove them.

     

    3.   Ensure all the hardware devices, installed device drivers, and installed applications are all compatible with Windows Vista.

     

    4.   For Compatibility information, please refer to Windows Vista Hardware Compatibility List:

     

    http://winqual.microsoft.com/hcl/

     

    5.   Disable all the third party startup programs and services by using the MSConfig.exe utility shipped with Windows Vista. To use this tool, you can refer to the following Microsoft Knowledge Base article:

     

    (KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135

     

    If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit.

     

    However, if the issue still persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon. Thanks!

     

    Tim Quan - MSFT

    Friday, January 30, 2009 9:19 AM
    Moderator