Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD during idle, error code 1E

07 Mar 2015   #1
dakoslug

Windows 7 64 Bit
 
 
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 System SpecsSystem Spec
.
07 Mar 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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 System SpecsSystem Spec
07 Mar 2015   #3
dakoslug

Windows 7 64 Bit
 
 

Quote   Quote: Originally Posted by Arc View Post
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 System SpecsSystem Spec
.

08 Mar 2015   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
How to Test and Diagnose RAM Issues with Memtest86+
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 System SpecsSystem Spec
08 Mar 2015   #5
dakoslug

Windows 7 64 Bit
 
 

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 System SpecsSystem Spec
08 Mar 2015   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

OK, test the RAM first.

The sound during startup comes from the HDDs sometimes, when the start spinning.
My System SpecsSystem Spec
10 Mar 2015   #7
dakoslug

Windows 7 64 Bit
 
 

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

Edit: 3 pass, 0 errors.
My System SpecsSystem Spec
10 Mar 2015   #8
dakoslug

Windows 7 64 Bit
 
 

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?
My System SpecsSystem Spec
11 Mar 2015   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

How are you testing the RAM? Are you typing those from another computer?
My System SpecsSystem Spec
11 Mar 2015   #10
dakoslug

Windows 7 64 Bit
 
 

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 System SpecsSystem Spec
Reply

 BSOD during idle, error code 1E




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Error code 116, Playing games/Idle, random times
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1039 Additional information about the problem: BCCode: 116 BCP1: FFFFFA80089B44E0 BCP2: FFFFF880107EB6AC BCP3: FFFFFFFFC000009A
BSOD Help and Support
BSOD PLaying League of Legends error code 0x0000001e a common code
Hello and good morning, I having problems with bsod mostly while playing league of legends but can occur randomly at other times. I have done memtest86, scanned the hard drive, and even took it to pcdirect where there installed a new motherboard but the problem has persisted. Thank you very much...
BSOD Help and Support
BSOD when left idle, STOP code 0x0000007A
Basically as titled. When left idle for any extended period of time (sometimes after 30 minutes, sometimes it's gone as long as about 30 hours), I come back to a BSOD, either a crucial process or thread has stopped or a kernel inpage error. Started roughly a month ago... today's the first time...
BSOD Help and Support
BSOD when computer was idle, BC Code 9f, BCP1:0000000000000003
My laptop continues to blue screen and it is usually when it's been idle/hibernated. I'm not sure if it's an issue with it overheating or the fan not getting enough air/circulation as the fan seems to run/make noticeable noise all the time. It is always the same error message:...
BSOD Help and Support
Multiple code errors, BSOD while gaming/netflix/idle...
This has been happening for the past four months now to no avail. I get BSOD about every 1-4 days, often with different messages, but the average as of right now is 1e. Built this system in October 2010. I've always had BSOD problems, but with work getting in the way and not really using my...
BSOD Help and Support
BSOD while idle, error 09f
I have Windows Home Premium x64. It is the original version installed on my computer, and it is OEM. My hardware and OS are around a year old. While idling or trying to shut down my system encounters this error. I've never had the error while actively using my system.
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 19:49.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App