BSOD during idle, error code 1E

Page 1 of 4 123 ... LastLast

  1. Posts : 28
    Windows 7 64 Bit
       #1

    BSOD during idle, error code 1E


    I'm getting a BSOD when I leave my computer for like half an hour.

    What should I do?

    Note: Some of the LOGS may refer to another BSOD that I had earlier this month which I have recently fixed. The most recent BSOD was today (3/7/2015)

    Thanks in advance!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi dakoslug.

    Dont use a BETA display driver.

    Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

    Let us know for any further BSOD after doing it. Because, some more steps may be needed depending on the resulting situation.
    ___________________________________________
    Code:
    BugCheck 7F, {8, 80050033, 406f8, fffff8800f13ee78}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+81e78 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff8800f13ee78
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  a
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800032d2469 to fffff800032d2ec0
    
    STACK_TEXT:  
    fffff800`00ba4d28 fffff800`032d2469 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`032d0932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff880`0f13ee78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0933bff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x81e78
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+81e78
    fffff880`0f13ee78 e8ebfbffff      call    atikmdag+0x81a68 (fffff880`0f13ea68)
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  atikmdag+81e78
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  546ea3c3
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_atikmdag+81e78
    
    BUCKET_ID:  X64_0x7f_8_atikmdag+81e78
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_atikmdag+81e78
    
    FAILURE_ID_HASH:  {93242815-fadd-5c51-751c-058b875fd641}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0bd000 fffff880`10341000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Nov 21 08:00:27 2014 (546EA3C3)
        CheckSum:         0121F198
        ImageSize:        01284000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 28
    Windows 7 64 Bit
    Thread Starter
       #3

    Arc said:
    Hi dakoslug.

    Dont use a BETA display driver.

    Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

    Let us know for any further BSOD after doing it. Because, some more steps may be needed depending on the resulting situation.
    ___________________________________________
    Code:
    BugCheck 7F, {8, 80050033, 406f8, fffff8800f13ee78}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+81e78 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff8800f13ee78
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  a
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800032d2469 to fffff800032d2ec0
    
    STACK_TEXT:  
    fffff800`00ba4d28 fffff800`032d2469 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`032d0932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff880`0f13ee78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0933bff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x81e78
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+81e78
    fffff880`0f13ee78 e8ebfbffff      call    atikmdag+0x81a68 (fffff880`0f13ea68)
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  atikmdag+81e78
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  546ea3c3
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_atikmdag+81e78
    
    BUCKET_ID:  X64_0x7f_8_atikmdag+81e78
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_atikmdag+81e78
    
    FAILURE_ID_HASH:  {93242815-fadd-5c51-751c-058b875fd641}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0bd000 fffff880`10341000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Nov 21 08:00:27 2014 (546EA3C3)
        CheckSum:         0121F198
        ImageSize:        01284000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Hi, thanks for the reply! I believe this is the bsod that was caused by atimdag was it not? I've already resolved that specific BSOD (i took out the GPU, currently using integrated right now). I'm trying to troubleshoot another bsod that is caused by 1E.

    Could you look over the recent minidump (March 7th) and tell me what the cause is?
    Unless you believe that the ATI drivers are still causing it?
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    If there are BSODs even after removing the ATI card, uninstall ESET.
    Code:
    fffff800`0482ef48  fffff880`014668abUnable to load image \SystemRoot\system32\DRIVERS\epfw.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for epfw.sys
    *** ERROR: Module load completed but symbols could not be loaded for epfw.sys
     epfw+0x208ab
    Driver Reference Table - epfw.sys

    Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

    Also, there is failure from the part of intel HD graphics.
    Code:
    fffff800`0482db38  fffff880`048e01a8Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
     igdkmd64+0xbc1a8
    As random things are crashing, it would be better to Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    If memtest86+ is free from errors, we will try to concentrate on the intel graphics failure.
      My Computer


  5. Posts : 28
    Windows 7 64 Bit
    Thread Starter
       #5

    Before I decide to uninstall ESET, I'm also having some sound issues that might be related to the BSOD.

    When I first start up, there are some random sound poppings and sound distortions. Then it disappears and then again later on in the day it starts up.

    Could this be related to a ram issue or is it possible that it's part of ESET? I did install ESET recently but I don't think it started causing BSOD right away.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    OK, test the RAM first.

    The sound during startup comes from the HDDs sometimes, when the start spinning.
      My Computer


  7. Posts : 28
    Windows 7 64 Bit
    Thread Starter
       #7

    Sorry for the late reply. I have some time today so I'll be running the memtest right now.

    Edit: 3 pass, 0 errors.
    Last edited by dakoslug; 10 Mar 2015 at 16:01.
      My Computer


  8. Posts : 28
    Windows 7 64 Bit
    Thread Starter
       #8

    Ok I let it run through 4 passes, and still no error. I know you told me to wait atleast until 8 so I will do it again overnight but it ran for almost 5 hours and no errors.

    Do you still suspect that it might be a ram issue? Or should I continue with your other advice?
    Last edited by dakoslug; 10 Mar 2015 at 22:02.
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    How are you testing the RAM? Are you typing those from another computer?
      My Computer


  10. Posts : 28
    Windows 7 64 Bit
    Thread Starter
       #10

    I'm posting on my phone. Anyways I've left MemTest on overnight, 8 pass 0 errors


    Total Runtime: 10 hours and 20 mins
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 17:37.
Find Us