locked
blue screen windows 7 Professional help required RRS feed

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: 995aed10, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 82ccccbc, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d85848
    Unable to read MiSystemVaType memory at 82d64e40
     995aed10 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+89
    82ccccbc 2110            and     dword ptr [eax],edx
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    TRAP_FRAME:  8d53fb84 -- (.trap 0xffffffff8d53fb84)
    ErrCode = 00000002
    eax=995aed10 ebx=00000100 ecx=00000000 edx=fffffffe esi=8869fa88 edi=88891000
    eip=82ccccbc esp=8d53fbf8 ebp=8d53fc28 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MiReleaseConfirmedPageFileSpace+0x89:
    82ccccbc 2110            and     dword ptr [eax],edx  ds:0023:995aed10=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 82ccccbc to 82c5d5db
    STACK_TEXT:  
    8d53fb84 82ccccbc badb0d00 fffffffe 0001a8da nt!KiTrap0E+0x2cf
    8d53fc28 82c7dadb 000000c0 868ee840 000c0000 nt!MiReleaseConfirmedPageFileSpace+0x89
    8d53fc9c 82e43f3a 868ee7f0 868ee7f0 868ee818 nt!MiDeleteSegmentPages+0x32e
    8d53fccc 82c7df04 868ee7f0 00000000 00000000 nt!MiSegmentDelete+0xec
    8d53fd28 82c7e225 855b2a60 00000000 00000000 nt!MiProcessDereferenceList+0xdb
    8d53fd50 82e24fda 00000000 abeea93d 00000000 nt!MiDereferenceSegmentThread+0xc5
    8d53fd90 82ccd1d9 82c7e15e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+89
    82ccccbc 2110            and     dword ptr [eax],edx
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+89
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+89
    BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+89
    Followup: MachineOwner
    ---------
    -----------------------------------------------------------------------------------------------
    Please start running memtest86+ and check if there is an error that was reported. If an error is reported then replace your faulty RAM or contact your manufacturer Technical support.
    If this does not help, consider proceeding like that:
    • Update all possible drivers
    • Uninstall all unused programs
    • Disable all security softwares
    • Run msconfig and disable startup items / services except Microsoft ones

    Once done, check results.

    You can also contact Microsoft CSS for assistance.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by zhen tan Wednesday, November 23, 2011 5:57 AM
    • Marked as answer by Arthur Xie Thursday, December 8, 2011 12:41 PM
    Sunday, November 20, 2011 6:34 PM

All replies

  • Hi, The bug code reported is IRQL_NOT_LESS_OR_EQUAL but the memory_corruption image name is more indicative of a memory issue. Please try running memtest86+ or windiag and see if there are any issues reported with the RAM,

    http://mikemstech.blogspot.com/2011/11/troubleshooting-memory-errors.html


    1: 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: 995aed10, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 82ccccbc, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d85848
    Unable to read MiSystemVaType memory at 82d64e40
     995aed10 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+89
    82ccccbc 2110            and     dword ptr [eax],edx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    TRAP_FRAME:  8d53fb84 -- (.trap 0xffffffff8d53fb84)
    ErrCode = 00000002
    eax=995aed10 ebx=00000100 ecx=00000000 edx=fffffffe esi=8869fa88 edi=88891000
    eip=82ccccbc esp=8d53fbf8 ebp=8d53fc28 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MiReleaseConfirmedPageFileSpace+0x89:
    82ccccbc 2110            and     dword ptr [eax],edx  ds:0023:995aed10=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82ccccbc to 82c5d5db
    
    STACK_TEXT:  
    8d53fb84 82ccccbc badb0d00 fffffffe 0001a8da nt!KiTrap0E+0x2cf
    8d53fc28 82c7dadb 000000c0 868ee840 000c0000 nt!MiReleaseConfirmedPageFileSpace+0x89
    8d53fc9c 82e43f3a 868ee7f0 868ee7f0 868ee818 nt!MiDeleteSegmentPages+0x32e
    8d53fccc 82c7df04 868ee7f0 00000000 00000000 nt!MiSegmentDelete+0xec
    8d53fd28 82c7e225 855b2a60 00000000 00000000 nt!MiProcessDereferenceList+0xdb
    8d53fd50 82e24fda 00000000 abeea93d 00000000 nt!MiDereferenceSegmentThread+0xc5
    8d53fd90 82ccd1d9 82c7e15e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+89
    82ccccbc 2110            and     dword ptr [eax],edx
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+89
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+89
    
    BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+89
    
    Followup: MachineOwner
    ---------
    
    

    -- Mike Burr
    Technology
    Sunday, November 20, 2011 4:46 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: 995aed10, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 82ccccbc, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d85848
    Unable to read MiSystemVaType memory at 82d64e40
     995aed10 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+89
    82ccccbc 2110            and     dword ptr [eax],edx
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    TRAP_FRAME:  8d53fb84 -- (.trap 0xffffffff8d53fb84)
    ErrCode = 00000002
    eax=995aed10 ebx=00000100 ecx=00000000 edx=fffffffe esi=8869fa88 edi=88891000
    eip=82ccccbc esp=8d53fbf8 ebp=8d53fc28 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MiReleaseConfirmedPageFileSpace+0x89:
    82ccccbc 2110            and     dword ptr [eax],edx  ds:0023:995aed10=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 82ccccbc to 82c5d5db
    STACK_TEXT:  
    8d53fb84 82ccccbc badb0d00 fffffffe 0001a8da nt!KiTrap0E+0x2cf
    8d53fc28 82c7dadb 000000c0 868ee840 000c0000 nt!MiReleaseConfirmedPageFileSpace+0x89
    8d53fc9c 82e43f3a 868ee7f0 868ee7f0 868ee818 nt!MiDeleteSegmentPages+0x32e
    8d53fccc 82c7df04 868ee7f0 00000000 00000000 nt!MiSegmentDelete+0xec
    8d53fd28 82c7e225 855b2a60 00000000 00000000 nt!MiProcessDereferenceList+0xdb
    8d53fd50 82e24fda 00000000 abeea93d 00000000 nt!MiDereferenceSegmentThread+0xc5
    8d53fd90 82ccd1d9 82c7e15e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+89
    82ccccbc 2110            and     dword ptr [eax],edx
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+89
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389
    IMAGE_NAME:  memory_corruption
    FAILURE_BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+89
    BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+89
    Followup: MachineOwner
    ---------
    -----------------------------------------------------------------------------------------------
    Please start running memtest86+ and check if there is an error that was reported. If an error is reported then replace your faulty RAM or contact your manufacturer Technical support.
    If this does not help, consider proceeding like that:
    • Update all possible drivers
    • Uninstall all unused programs
    • Disable all security softwares
    • Run msconfig and disable startup items / services except Microsoft ones

    Once done, check results.

    You can also contact Microsoft CSS for assistance.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by zhen tan Wednesday, November 23, 2011 5:57 AM
    • Marked as answer by Arthur Xie Thursday, December 8, 2011 12:41 PM
    Sunday, November 20, 2011 6:34 PM