locked
Blue Screen Errors - Please Help RRS feed

  • Question

  • Can someone please analyze these mini dump files? I have been getting blue screen errors for quite a while now. They always seem to be different. I get Memory Management, IRQL Less Than or Equal, among others. They usually occur within just a few minutes of an initial boot or resume from sleep. I have updated drivers, ran the Windows Memory diagnostic overnight, etc without any errors. I am using EasyTether (an Android Market app) to access the Internet. I initially was using Klink, when the errors began. I have since switched to EasyTether but the errors continue. I think it may have to do with the driver for my Evo 4g as the errors seemed to coincide with the initial load. I have also reinstalled Windows 7 with no luck.

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="165px" height="128px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=6DA23F27343C9D1F&resid=6DA23F27343C9D1F%21118&authkey=ACnDBSD0izIvmNU"></iframe>

    Thanks in advance.

    Wednesday, December 21, 2011 2:38 AM

Answers

  • Hi,

     

    122011-20732-01.dmp

    12/20/2011 18:27

    IRQL_NOT_LESS_OR_EQUAL

    0x0000000a

    121911-16707-01.dmp

    12/20/2011 18:23

    KMODE_EXCEPTION_NOT_HANDLED

    0x0000001e

    122011-18642-01.dmp

    12/20/2011 18:21

    MEMORY_MANAGEMENT

    0x0000001a

     

    According these dump file, this problem could be a memory related issue. Please upgrade all the driver on your machine and check the issue in Clean Boot to determine whether this problem is caused by third party software.

    http://support.microsoft.com/kb/929135

     

    Note: Clean Boot is a step of troubleshooting, we can go back to normal by running MSCONIFG.

     

    Also you could use Windows Memory Diagnostic to check memory. And let me know the result.

    1.       Click Start button, type “Windows Memory Diagnostic” then press Enter.

    2.       Click Restart now and check for problem.

     

    Hope that helps


    William Tan

    TechNet Community Support

    • Marked as answer by Arthur Xie Wednesday, December 28, 2011 4:55 AM
    Friday, December 23, 2011 8:19 AM
  • *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000000, 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: fffff80002e8718c, address which referenced memory
    Debugging Details:
    ------------------
    OVERLAPPED_MODULE: Address regions for 'CLASSPNP' and 'Unknown_Module_00ffffff`00ffffff' overlap
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b40e0
     0000000000000000 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`02e8718c 4c8938          mov     qword ptr [rax],r15
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff88002f549a0 -- (.trap 0xfffff88002f549a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004ccc0c8
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e8718c rsp=fffff88002f54b30 rbp=0000000000000000
     r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
    r11=fffff80002ff6e80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KeWaitForSingleObject+0x17c:
    fffff800`02e8718c 4c8938          mov     qword ptr [rax],r15 ds:00000000`00000000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e7d469 to fffff80002e7df00
    STACK_TEXT:  
    fffff880`02f54858 fffff800`02e7d469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`02f54860 fffff800`02e7c0e0 : fffffa80`029d9810 00000000`00000000 00000000`00000000 fffff800`0311dfd4 : nt!KiBugCheckDispatch+0x69
    fffff880`02f549a0 fffff800`02e8718c : fffffa80`021dfb60 fffff800`02ff6e80 fffffa80`021dfc20 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`02f54b30 fffff800`02e3fa6e : 00000000`00000000 fffff800`00000022 00000000`00000000 fffffa80`021dfb00 : nt!KeWaitForSingleObject+0x17c
    fffff880`02f54bd0 fffff800`030cd783 : 00000000`00000001 fffff880`02f54cc0 00000000`00000000 fffff800`0311faf7 : nt!KiAcquireFastMutex+0x4e
    fffff880`02f54c10 fffff800`0310cead : 00000000`00000000 fffff880`02f54cb8 fffff800`0310ce00 fffffa80`0384e740 : nt! ?? ::NNGAKEGL::`string'+0x1f901
    fffff880`02f54c70 fffff800`02e8b161 : fffff800`0310ce08 fffff800`03177500 fffffa80`00000148 fffff800`030215f8 : nt!CmpLazyFlushWorker+0xa5
    fffff880`02f54cb0 fffff800`03121166 : ffffffff`ffffffbf fffffa80`021dfb60 00000000`00000080 fffffa80`02151990 : nt!ExpWorkerThread+0x111
    fffff880`02f54d40 fffff800`02e5c486 : fffff800`02ff6e80 fffffa80`021dfb60 fffffa80`021df040 11011130`11001200 : nt!PspSystemThreadStartup+0x5a
    fffff880`02f54d80 00000000`00000000 : fffff880`02f55000 fffff880`02f4f000 fffff880`02f53a50 00000000`00000000 : nt!KxStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`02e8718c 4c8938          mov     qword ptr [rax],r15
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KeWaitForSingleObject+17c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    FAILURE_BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    Followup: MachineOwner
    ----------------------------------------------------------------------------------------------------------------------------------------------------------

    The following actions might prevent an error like this from happening again:

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

     

    Regards,

     


    MCP ✦ MCTS ✦ MCITP
    • Marked as answer by Arthur Xie Wednesday, December 28, 2011 4:55 AM
    Friday, December 23, 2011 1:04 PM

All replies

  • This is usually hardware related.

    Clean out your PC Hardware (Dust, Fragments)

    Push in all connectors on the board (Especially Memory usually accounts for IRQs)

     

    This should resolve it, or buy some new memory.


    Professional In Computing - Please Contact for Help. Please remember to click “Mark as Answer” on the post that helps you This can be beneficial to other community members reading the thread.
    Wednesday, December 21, 2011 3:43 AM
  • Thanks. I have previously reseated the memory, and made sure all my connections were snug. This machine is just over a year old so there wasnt much dust. Although I did clean it up. No change...
    Wednesday, December 21, 2011 4:03 AM
  • Hi,

     

    122011-20732-01.dmp

    12/20/2011 18:27

    IRQL_NOT_LESS_OR_EQUAL

    0x0000000a

    121911-16707-01.dmp

    12/20/2011 18:23

    KMODE_EXCEPTION_NOT_HANDLED

    0x0000001e

    122011-18642-01.dmp

    12/20/2011 18:21

    MEMORY_MANAGEMENT

    0x0000001a

     

    According these dump file, this problem could be a memory related issue. Please upgrade all the driver on your machine and check the issue in Clean Boot to determine whether this problem is caused by third party software.

    http://support.microsoft.com/kb/929135

     

    Note: Clean Boot is a step of troubleshooting, we can go back to normal by running MSCONIFG.

     

    Also you could use Windows Memory Diagnostic to check memory. And let me know the result.

    1.       Click Start button, type “Windows Memory Diagnostic” then press Enter.

    2.       Click Restart now and check for problem.

     

    Hope that helps


    William Tan

    TechNet Community Support

    • Marked as answer by Arthur Xie Wednesday, December 28, 2011 4:55 AM
    Friday, December 23, 2011 8:19 AM
  • *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000000, 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: fffff80002e8718c, address which referenced memory
    Debugging Details:
    ------------------
    OVERLAPPED_MODULE: Address regions for 'CLASSPNP' and 'Unknown_Module_00ffffff`00ffffff' overlap
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b40e0
     0000000000000000 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`02e8718c 4c8938          mov     qword ptr [rax],r15
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff88002f549a0 -- (.trap 0xfffff88002f549a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004ccc0c8
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e8718c rsp=fffff88002f54b30 rbp=0000000000000000
     r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
    r11=fffff80002ff6e80 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KeWaitForSingleObject+0x17c:
    fffff800`02e8718c 4c8938          mov     qword ptr [rax],r15 ds:00000000`00000000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e7d469 to fffff80002e7df00
    STACK_TEXT:  
    fffff880`02f54858 fffff800`02e7d469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`02f54860 fffff800`02e7c0e0 : fffffa80`029d9810 00000000`00000000 00000000`00000000 fffff800`0311dfd4 : nt!KiBugCheckDispatch+0x69
    fffff880`02f549a0 fffff800`02e8718c : fffffa80`021dfb60 fffff800`02ff6e80 fffffa80`021dfc20 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`02f54b30 fffff800`02e3fa6e : 00000000`00000000 fffff800`00000022 00000000`00000000 fffffa80`021dfb00 : nt!KeWaitForSingleObject+0x17c
    fffff880`02f54bd0 fffff800`030cd783 : 00000000`00000001 fffff880`02f54cc0 00000000`00000000 fffff800`0311faf7 : nt!KiAcquireFastMutex+0x4e
    fffff880`02f54c10 fffff800`0310cead : 00000000`00000000 fffff880`02f54cb8 fffff800`0310ce00 fffffa80`0384e740 : nt! ?? ::NNGAKEGL::`string'+0x1f901
    fffff880`02f54c70 fffff800`02e8b161 : fffff800`0310ce08 fffff800`03177500 fffffa80`00000148 fffff800`030215f8 : nt!CmpLazyFlushWorker+0xa5
    fffff880`02f54cb0 fffff800`03121166 : ffffffff`ffffffbf fffffa80`021dfb60 00000000`00000080 fffffa80`02151990 : nt!ExpWorkerThread+0x111
    fffff880`02f54d40 fffff800`02e5c486 : fffff800`02ff6e80 fffffa80`021dfb60 fffffa80`021df040 11011130`11001200 : nt!PspSystemThreadStartup+0x5a
    fffff880`02f54d80 00000000`00000000 : fffff880`02f55000 fffff880`02f4f000 fffff880`02f53a50 00000000`00000000 : nt!KxStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KeWaitForSingleObject+17c
    fffff800`02e8718c 4c8938          mov     qword ptr [rax],r15
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KeWaitForSingleObject+17c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    FAILURE_BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    BUCKET_ID:  X64_0xA_nt!KeWaitForSingleObject+17c
    Followup: MachineOwner
    ----------------------------------------------------------------------------------------------------------------------------------------------------------

    The following actions might prevent an error like this from happening again:

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

     

    Regards,

     


    MCP ✦ MCTS ✦ MCITP
    • Marked as answer by Arthur Xie Wednesday, December 28, 2011 4:55 AM
    Friday, December 23, 2011 1:04 PM