locked
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000080, 0x0000000000000002, 0x0000000000000001, 0xfffff80002adf63f). A dump was saved in: C:\Windows\Minidump\122311-12121-01.dmp. Report Id: 122311-12121-01. RRS feed

Answers

All replies

  • *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000080, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002adf63f, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d060e8
     0000000000000080 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!KeAcquireInStackQueuedSpinLock+5f
    fffff800`02adf63f 488717          xchg    rdx,qword ptr [rdi]
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000
    STACK_TEXT:  
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nt!KeAcquireInStackQueuedSpinLock+5f
    fffff800`02adf63f 488717          xchg    rdx,qword ptr [rdi]
    SYMBOL_NAME:  nt!KeAcquireInStackQueuedSpinLock+5f
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    BUCKET_ID:  INVALID_KERNEL_CONTEXT
    MODULE_NAME: Unknown_Module
    Followup: MachineOwner
    ---------
    ----------------------------------------------------------------------
    Please start by that:
    • Update all possible drivers especially your graphic card one
    • Uninstall all unused programs
    • Run msconfig and disable startup items / services except Microsoft ones
    • Update BIOS

    Once done, check results.

    If BSODs occurs again then update new dumps.

    You can also contact Microsoft CSS.



    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 Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Saturday, December 24, 2011 12:20 PM
  • thx a lot will do it, but if i get error will upload more dumps, thx a lot!!!
    Saturday, December 24, 2011 7:17 PM
  • This error was fairly nonspecific (no faulting module found with the
    dump), 0xa IRQL_NOT_LESS_OR_EQUAL generally follows this line,
     
     
    Please enable driver verifier and upload any dumps after the system
    crashes with verifier enabled
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Niki Han Tuesday, January 3, 2012 1:55 AM
    Monday, December 26, 2011 2:03 AM
  • thanks a lot, gonna try it, one thing i noticed, i used memtest86+ to test my memory after 6 pass i got 1 failing address error. so i started checking each ram module seperately for a few days but none of the individual ram got any error, i added both memory module again and did a test, and after 11 passes i still didnt get any error, that weird, but thanks a lo, any more prob will keep u updated
    Monday, December 26, 2011 5:40 AM