BSOD on system restart or shutdown, W7 X64 ERROR: 0x000001E

[DocMercy]

Around the same time this started occurring there was both a lightning storm and then my network adapter essentially vanished from my system records.

 

[YoYo155]

Welcome to 7F DocMercy .
Unfortunately files are missing, so I'm not getting the full picture.
Please run the SFDT again and let it run its course it can take 15min at times to collect all the data necessary.
:ar:There should be eight files generated not including the dumps.

Five out of the seven uploaded bug checks blame an outdated driver, while the other two are a TDR.

BugCheck 1E, {ffffffffc0000005, fffff80003dba0ca, 0, 4e}

*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )

lmvm AppleCharger
start             end                 module name
fffff880`0402f000 fffff880`04037000   AppleCharger T (no symbols)           
    Loaded symbol image file: AppleCharger.sys
    Image path: \SystemRoot\system32\DRIVERS\AppleCharger.sys
    Image name: AppleCharger.sys
    Timestamp:        [COLOR=Red][U]Thu Apr 22 10:05:49 2010[/U][/COLOR]

• Driver Reference Table - AppleCharger.sys

:arlease remove any of Gigabyte's Utilities.




A TDR (Timeout Detection Recovery) is not a bugcheck in the true sense in that something
has went terribly wrong in the kernel which forced the machine to crash.

"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

• Read the full post.

What is the Make, Model and age of your PSU?
Do you suspect it was damaged during the lightning storm?

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

:ar:When done with the testing procedure take a picture and upload it here.


Test for thermals and stability:

• Download HWinfo and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).