BSOD when its in sleep state. is that even possible?

[robins6876]

Dear great helper people,

Have you ever seen this? I put my computer to sleep and then sometime along the way it will crash and then shuts itself down. Only when I restart it do I find out there was a crash. But now its been doing it so often that I need help. It seems to always crash if its been sitting in sleep mode for several hours. Maybe its crashing as I put it to sleep? who knows...

I've attached my perfmon and Windows_NT6_BSOD_jcgriff2 dump.

Microsoft Windows 7 Professional 32-bit 7601 Multiprocessor Free Service Pack 1
(windows 7 was purchased and installed, computer originally had XP installed)
- Full Retail
- computer is from 2006
- windows 7 was installed 2009

thanks!
-rich

 

[zigzag3143]

Dear great helper people,

Have you ever seen this? I put my computer to sleep and then sometime along the way it will crash and then shuts itself down. Only when I restart it do I find out there was a crash. But now its been doing it so often that I need help. It seems to always crash if its been sitting in sleep mode for several hours. Maybe its crashing as I put it to sleep? who knows...

I've attached my perfmon and Windows_NT6_BSOD_jcgriff2 dump.

Microsoft Windows 7 Professional 32-bit 7601 Multiprocessor Free Service Pack 1
(windows 7 was purchased and installed, computer originally had XP installed)
- Full Retail
- computer is from 2006
- windows 7 was installed 2009

thanks!
-rich

Hi Rich and welcome


Two issues

1-dirvers from as far back as 2005.

mdmxsdk.sys    6/19/2006 5:26:59 PM        0xa65cd000    0xa65d0180    0x00003180    0x449716a3                        
xaudio.sys    11/28/2006 8:44:50 PM        0xac0f5000    0xac0fd000    0x00008000    0x456cd802                        
HSX_CNXT.sys    12/22/2006 3:48:52 PM        0x8290a000    0x829be000    0x000b4000    0x458c36a4                        
HSXHWAZL.sys    12/22/2006 3:49:02 PM        0x82733000    0x82770000    0x0003d000    0x458c36ae                        
HSX_DPV.sys    12/22/2006 3:50:21 PM        0x82807000    0x8290a000    0x00103000    0x458c36fd                        
SWNC5E01.sys    1/12/2007 5:26:41 PM        0x82770000    0x82788f00    0x00018f00    0x45a7fd11                        
psadd.sys    2/19/2007 2:56:45 PM        0x9e9ec000    0x9e9f1380    0x00005380    0x45d9f2ed                        
swmx01.sys    2/22/2007 8:26:46 PM        0x829e9000    0x829fa600    0x00011600    0x45de34c6                        
nscirda.sys    1/19/2008 1:55:24 AM        0x9e90a000    0x9e911800    0x00007800    0x479190cc                        
Tppwr32v.sys    6/12/2008 10:27:57 PM        0x9a09f000    0x9a0a6000    0x00007000    0x4851db2d                        
atikmdag.sys    12/1/2008 5:01:46 PM        0x9d016000    0x9d5fe000    0x005e8000    0x493450ba                        
ADIHdAud.sys    5/18/2009 1:32:57 PM        0x82688000    0x826eb000    0x00063000    0x4a119bc9

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



Second Your 3 year old Symantec. I would remove and replace it Microsoft Security Essentials

ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials

 

[robins6876]

Thank you zigzag3143

The problem seems to be with the video driver. I have an ATI Mobility Radeon X1400 on my lenovo T60. I've gotten several debug clues and windows recovery errors that point to the video driver as the problem (For instance, this morning it crashed and this is the message: "ATI Graphics Driver has stopped working properly"). The problem is the ATI (AMD) does not have drivers for this old laptop for windows 7. Here is what AMD told me:

=============
Unfortunately there are no drivers from AMD for your Lenovo laptop and its proprietary mobility X1400 chipset, the drivers for this card come from Lenovo. If Lenovo does not offer Windows 7 drivers, running Windows 7 on the unit would not be a good idea.

You should be able to manually install the Vista drivers from Lenovo support for the laptops mobility chipset thorough the Windows Device Manager.

There are 3rd party drivers and utilities available on line. They are not recommended or supported by AMD Global Customer Care, they are popular with laptop users.

If you search online for Omega Drivers or ATI Modder Utility you should be able to update drivers to more current ones than offered by your laptop manufacturer.

OmegaDrivers.net | ATI/NVIDIA Omega Driver's Home, PC Gaming Drivers & News!

Mobility Modder - ATI Version, Install the Latest Drivers on your ATI laptop
============

So I am lost as what to do next.
Any ideas?

thanks
-rich
ps I updated some of the drivers you listed, but most I couldn't find even after hours and hours of searching.

 

[writhziden]

Can you upload your latest crash reports?

Also, there are warnings that running Windows 7 on an unsupported Lenovo laptop is not a good idea. However, if you really want to do so, you could try uninstalling all AMD drivers and letting Windows 7 install the proper display drivers for you. If it re-installs the same AMD drivers, let us know. We may have to try further steps to ensure that you only get the generic drivers. You won't get as much out of your graphics with this method, but it is likely the best option if you are set on running Windows 7.

The only other alternative I can see is to install Vista drivers on Windows 7, but this may not be stable.

 

[robins6876]

I am attaching the last crash report.
Lenovo believes that this computer can run Windows 7. I am attaching a pdf of their support that "shows" this is true.
But their driver on the site for the video has only two choices, one is vista and the other is XP. The vista version is from 2007. For this last crash I had a 12/2008 version of the driver installed, either win 7 or SlimDrivers must have updated it. I just now rolled it back to the 2007 Vista driver version on the Lenovo website.

thanks for helping,
please let me know if you see anything obvious

 

[writhziden]

I would recommend that you see how things go with the driver from the Lenovo website. Also, if you are using third party software to find drivers, this can cause conflicts on the system. These programs often install driver "updates" that are for different hardware than what is on the system being updated. We see crashes caused through the use of such software a lot.

I would recommend sticking only to the drivers provided by Lenovo for your system. If you have other drivers that were updated with SlimDrivers, roll back to the Lenovo versions, or better yet, re-install them with the following method.


To fully re-install a driver, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

Problem Devices:

MpKsl0844a36f	ROOT\LEGACY_MPKSL0844A36F\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslb924e325	ROOT\LEGACY_MPKSLB924E325\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl4ec08c07	ROOT\LEGACY_MPKSL4EC08C07\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslba0d28c8	ROOT\LEGACY_MPKSLBA0D28C8\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl0f5b26af	ROOT\LEGACY_MPKSL0F5B26AF\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslbcdfc772	ROOT\LEGACY_MPKSLBCDFC772\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl93cd8aaa	ROOT\LEGACY_MPKSL93CD8AAA\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl214c8d1a	ROOT\LEGACY_MPKSL214C8D1A\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslc0735a4e	ROOT\LEGACY_MPKSLC0735A4E\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl96b5ad60	ROOT\LEGACY_MPKSL96B5AD60\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl599b471c	ROOT\LEGACY_MPKSL599B471C\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl5e7f3c22	ROOT\LEGACY_MPKSL5E7F3C22\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslc6bffffd	ROOT\LEGACY_MPKSLC6BFFFFD\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl65a75770	ROOT\LEGACY_MPKSL65A75770\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl32b84c06	ROOT\LEGACY_MPKSL32B84C06\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslc8aa4ed0	ROOT\LEGACY_MPKSLC8AA4ED0\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl6da41c33	ROOT\LEGACY_MPKSL6DA41C33\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl6de2871a	ROOT\LEGACY_MPKSL6DE2871A\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl3b5b2b72	ROOT\LEGACY_MPKSL3B5B2B72\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslcdde95a1	ROOT\LEGACY_MPKSLCDDE95A1\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslac6dd888	ROOT\LEGACY_MPKSLAC6DD888\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl3e29f3c3	ROOT\LEGACY_MPKSL3E29F3C3\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl3e995875	ROOT\LEGACY_MPKSL3E995875\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsldeb96c6c	ROOT\LEGACY_MPKSLDEB96C6C\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslb03d1528	ROOT\LEGACY_MPKSLB03D1528\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl445953a8	ROOT\LEGACY_MPKSL445953A8\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl0344c4e4	ROOT\LEGACY_MPKSL0344C4E4\0000	This device is not present, is not working properly, or does not have all its drivers installed.
IBM ThinkPad Fast Infrared Port	ACPI\IBM0071\4&290E2D73&0	This device is disabled.
MpKsldf8a742f	ROOT\LEGACY_MPKSLDF8A742F\0000	This device is not present, is not working properly, or does not have all its drivers installed.
MpKslb47cd729	ROOT\LEGACY_MPKSLB47CD729\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Antivirus Software:

rtvscan.exe	c:\program files\symantec\symantec endpoint protection\rtvscan.exe	2936	8	200	1380	3/10/2012 2:18 PM	11.0.6070.422	1.75 MB (1,831,024 bytes)	5/31/2010 6:54 PM
smc.exe	c:\program files\symantec\symantec endpoint protection\smc.exe	1488	8	200	1380	3/10/2012 2:18 PM	11.0.6005.440	1.79 MB (1,881,368 bytes)	5/31/2010 6:54 PM
smcgui.exe	c:\program files\symantec\symantec endpoint protection\smcgui.exe	3676	8	200	1380	3/10/2012 2:19 PM	11.0.6005.440	1.39 MB (1,459,528 bytes)	5/31/2010 6:54 PM

Possible out of date drivers:

mdmxsdk	ab7b3000	ab7b6180	Mon Jun 19 15:26:59 2006 (449716a3)	0000c5ae		mdmxsdk.sys
xaudio	b2ad7000	b2adf000	Tue Nov 28 17:44:50 2006 (456cd802)	0000f70b		xaudio.sys
HSX_CNXT	a1c27000	a1cdb000	Fri Dec 22 12:48:52 2006 (458c36a4)	000a6afd		HSX_CNXT.sys
HSXHWAZL	a1864000	a18a1000	Fri Dec 22 12:49:02 2006 (458c36ae)	0004107d		HSXHWAZL.sys
HSX_DPV	a18a1000	a19a4000	Fri Dec 22 12:50:21 2006 (458c36fd)	000ff744		HSX_DPV.sys
SWNC5E01	a1d18000	a1d30f00	Fri Jan 12 14:26:41 2007 (45a7fd11)	0001efab		SWNC5E01.sys
psadd	a0018000	a001d380	Mon Feb 19 11:56:45 2007 (45d9f2ed)	00007612		psadd.sys
swmx01	a1d06000	a1d17b80	Tue Apr 10 12:03:45 2007 (461bd181)	00017a8e		swmx01.sys
atikmdag	9e204000	9e7ec000	Mon Dec 01 14:01:46 2008 (493450ba)	00409b06		atikmdag.sys
smihlp	a1df9000	a1dfa700	Fri Mar 13 06:47:23 2009 (49ba55db)	000120cc		smihlp.sys
GEARAspiWDM	a018e000	a0193280	Mon May 18 06:16:53 2009 (4a1151b5)	00008fb0		GEARAspiWDM.sys
ADIHdAud	9eb7c000	9ebdf000	Mon May 18 11:32:57 2009 (4a119bc9)	0006636d		ADIHdAud.sys
SYMTDI	915b9000	915e5480	Wed Jun 17 15:11:02 2009 (4a395be6)	00038832		SYMTDI.SYS
SYMREDRV	b2b81000	b2b85d00	Wed Jun 17 15:11:33 2009 (4a395c05)	0000bd74		SYMREDRV.SYS
SYMEVENT	92190000	921b5000	Wed Jun 24 14:14:58 2009 (4a428942)	00024d55		SYMEVENT.SYS

mdmxsdk.sys
xaudio.sys
HSX_CNXT.sys
HSXHWAZL.sys
HSX_DPV.sys
SWNC5E01.sys
psadd.sys
swmx01.sys
atikmdag.sys
smihlp.sys
GEARAspiWDM.sys
ADIHdAud.sys
SYMTDI.SYS
SYMREDRV.SYS
SYMEVENT.SYS

The things that concern me most of the above are the number of problem devices and the fact that your antivirus software is out of date... The problems are you are experiencing are likely due to one of these two issues or perhaps both.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\robins6876\Windows_NT6_BSOD_jcgriff2\031012-90246-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8300a000 PsLoadedModuleList = 0x831534d0
Debug session time: Sat Mar 10 10:05:51.997 2012 (UTC - 6:00)
System Uptime: 3 days 23:40:49.150
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................................................
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8651f020, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 00000000, Pointer to offending driver name.
Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

FAULTING_THREAD:  8651f020

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9ea321f7 to 830e8ef4

STACK_TEXT:  
b7b4c9a4 9ea321f7 000000ea 8651f020 00000000 nt!KeBugCheckEx+0x1e
b7b4c9e8 9ea2abc0 b7b4ca34 00000000 9ea2d51e dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x2c
b7b4ca10 9e228052 b7b4ca34 00000000 00000000 dxgkrnl!TdrTimedOperationDelay+0xc9
WARNING: Stack unwind information not available. Following frames may be wrong.
b7b4ca60 9e225a9c 9e377260 b7b4cafc ffffffff atikmdag+0x24052
b7b4ca7c 9e376d86 88be2000 b7b4ca98 1fff1fff atikmdag+0x21a9c
b7b4cad8 9e3773dd 8a7dd004 9e377260 b7b4cafc atikmdag+0x172d86
b7b4cb14 9e3a9905 85bac000 ffffffff 00000000 atikmdag+0x1733dd
b7b4cb28 9e41f5d1 85bac0ea ffffffff 00000000 atikmdag+0x1a5905
b7b4cb40 9e41d9a9 85bb32b0 00003219 88e730d8 atikmdag+0x21b5d1
b7b4cb58 9e376f9a c8b58510 85bc8718 b7b4cb7c atikmdag+0x2199a9
b7b4cb68 9e21cd42 c8b584c8 00000000 8adbbde0 atikmdag+0x172f9a
b7b4cb7c 9e225c07 8adbbde0 00000000 a92415e0 atikmdag+0x18d42
b7b4cb90 9eab98dc 88d0df80 8adbbde0 00000000 atikmdag+0x21c07
b7b4cba4 9eab7616 88d0df80 9e225be4 8adbbde0 dxgkrnl!DpiDxgkDdiProtectedCallback+0x2a
b7b4cce8 8321e4e6 88e73020 a92415e0 89181930 dxgkrnl!DpiFdoExcludeAdapterAccess+0x1d3
b7b4cd00 83087a6b 89181930 00000000 8651f020 nt!IopProcessWorkItem+0x2d
b7b4cd50 83212fda 80000001 9a7d80df 00000000 nt!ExpWorkerThread+0x10d
b7b4cd90 830bb1f9 8308795e 80000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .thread 0xffffffff8651f020 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c
9ea321f7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78ffe

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

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

Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest Lenovo Vista drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest Lenovo Vista driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest Lenovo Vista drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest Lenovo Vista drivers for the display cards once Windows starts