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 After Waking From Sleep


11 Jun 2013   #1

Windows 7 Pro x64
 
 
BSOD After Waking From Sleep

Hi,

I have been having several crashes when waking from sleep. I got the latest drivers for all my kit when I did a fresh install last week and the firmware on the SSDs is the latest available. The problem occurs when I move my mouse to wake the PC, it thinks about it then crashes and restarts.

I'd be grateful if anyone could look at the attached zip file and tell me what's wrong.

Thanks.


My System SpecsSystem Spec
.

11 Jun 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

There are no dumps in the zip uploaded.

Configure dumps

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.
Dump Files - Configure Windows to Create on BSOD
Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

Hard Drive/Storage

Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition
  • For how to upload a screenshot or file, read here
Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

Disk Check

For errors on your Hard drive(s): How to Run Disk Check in Windows 7

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 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. How to Test and Diagnose RAM Issues with Memtest86+

Note   Note
Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

Tip   Tip
Do this test overnight.
My System SpecsSystem Spec
13 Jun 2013   #3

Windows 7 Pro x64
 
 

I've ran all the tests and they came back ok but just had another BSOD but this time it was whilst I was playing a game. There are dump files this time so grateful if you could take a look at them.
My System SpecsSystem Spec
.


13 Jun 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Some input form a senior analyst on SSD's
Quote   Quote: Originally Posted by usasma View Post
We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: Solved Win8 x64 PC reboots when waking from sleep
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
And this one seems to be a hardware error:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88003165180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  TombRaider.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0ada64c8 fffff800`02cd1a3a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03165180 : nt!KeBugCheckEx
fffff880`0ada64d0 fffff800`02c846e7 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffff880`04bbd17e : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0ada6560 fffff800`031f5895 : fffff800`0321b460 fffff880`0ada6710 fffff800`0321b460 fffff700`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0ada6660 fffff800`02c77153 : 00000000`8e70568b fffff800`02df5e80 fffff800`02df5e80 fffff680`00043ff8 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0ada6690 fffff800`02cac1f7 : fffff800`02df5e80 fffffa80`00000000 00000000`00000001 fffff880`0ada68e8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0ada6820 fffff800`02c673ff : fffffa80`00000000 00000000`08830fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x7f6
fffff880`0ada69e0 fffff800`02c79e93 : ffffffff`ffffffff 00000000`09cde430 00000000`09cde428 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0ada6ae0 00000000`779414fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`09cde3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779414fa


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
REad the instructions on this thread: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
My System SpecsSystem Spec
23 Jun 2013   #5

Windows 7 Pro x64
 
 

I'm still having major problems with restarts and just had another BSOD so I've attached the latest dump files. All my SSD's have the latest firmware and (as far as I know) I have the latest drivers installed. I'd be very grateful if someone could look at the latest dump files and possibly see what's going wrong with my system.

Thanks
My System SpecsSystem Spec
23 Jun 2013   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Welcome to the forums zom414,

Code:
BugCheck 101, {19, 0, fffff88003365180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Code:
Usual causes:  Device driver, BIOS bug, hardware defect
This troubleshooting guide may be of use to you - STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Code:
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04c94000 fffff880`05775000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun May 12 20:09:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
The only driver I was able to find from the raw stack from the nVidia graphics card driver, since you have the latest version then, let's begin with testing the graphics card with - Video Card - Stress Test with Furmark

You can monitor your GPU temperature with GPU-Z Video card GPU Information Utility, don't let the temperature exceed 80*C.

Stop 0x101's can only be truly analysed throughly with a Kernel Memory dump, to investigate the other threads call stacks. Please configure a Kernel Memory Dump upon BSOD with Dump Files - Configure Windows to Create on BSOD, and then upload this file to a free file sharing site such as DropBox or Skydrive. Post the link to the file in your next post.
My System SpecsSystem Spec
23 Aug 2013   #7

Windows 7 Pro x64
 
 

Well, I finally solved this problem so just thought I'd share the solution in case anyone else comes across this problem.

It was in fact nothing to do with drivers etc but a setting in my BIOS. I stumbled on the fix by accident when I was looking for something else. I have an Asus board and apparently it's a common problem with their boards. You have to disable the Internal PLL Voltage setting in the BIOS, it messes with the sleep function somehow. I did this 4 days ago and have not had any restarts/BSOD when waking from sleep since then.

I've spent hours trying to find a solution so I hope this post saves someone with an Asus board some time if they have the same problem.
My System SpecsSystem Spec
23 Aug 2013   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Glad you were able to solve your problem, and thanks for posting your solution
My System SpecsSystem Spec
Reply

 BSOD After Waking From Sleep




Thread Tools



Similar help and support threads for2: BSOD After Waking From Sleep
Thread Forum
Solved BSOD from waking up from sleep BSOD Help and Support
BSOD after waking up from sleep Win 7 x64 BSOD Help and Support
BSOD after waking up from sleep BSOD Help and Support
BSOD waking from sleep BSOD Help and Support
BSOD after waking from S3 sleep BSOD Help and Support
Win 7 BSOD after waking from sleep 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 11:51 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33