BSOD when running laptop off battery power

[Reverend Truth]

About 4 months ago I performed a number of upgrades to my 4 year old Lenovo SL400 laptop.

I upgraded to a Seagate Momentus hybrid drive, upgraded my CPU, installed new RAM, purchased a new 9-cell battery and performed a clean intstall of Windows 7 Home Premium 64-bit (the computer came with Vista - Windows 7 was a retail upgrade).

I had several BSOD crashes which only happened when running on battery power. I was sure the battery was the culprit and RMA'd to the vendor for a replacement. I still have the issue with the replacement.

I notice a screen flicker a second or two before the crash. About half the time the computer recovers without crashing.

I've attached the dump files and system health report.

Any help would be greatly appreciated.

Thanks.

 

[Reverend Truth]

I saw the ThinkPad Display error in the 7-17 performance report so I uninstalled and reinstalled the driver for my display and I no longer have that error. I've attached an updated report.

Anyone have an idea what is causing my crashes? I'd love to be able to use this machine without being tethered to the plug.

 

[Reverend Truth]

I ran sfc /scannow and there were no integrity violations.

Can anyone point me in the right direction?

 

[Reverend Truth]

I just ran prime 95 for nearly 7 hours without a problem.

 

[z3r010]

I'm not expert an bsod analysis (I'm not even an amateur) but I've looked at the dumps and igdkmd64.sys and athrx.sys are mentioned as possible cause.

igdkmd64.sys - Intel Graphics driver
athrx.sys - Atheros Network Driver

Have a look and see if you can find updated versions of the above drivers and see if it helps while you are waiting for somebody that understand this stuff to come along lol

 

[Reverend Truth]

I actually did update the Atheros driver about a week ago. The Lenovo site gave me a 2 year old athrx.sys driver but I was able to find one on the Atheros site from 2/23/12. I still get dumps pointing to that though. I'll see what I can find on the other. Thanks.

 

[gregrocker]

Did you check optional Windows Updates for newer drivers after your Clean Reinstall - Factory OEM Windows 7?

You may need to enable to Automatically get recommended drivers and updates for your hardware .

The reason I ask is that Win7 is nearly driver complete in the installer and then quickly updated via optional Updates. Only if these driver cause issues should drivers be changed with the latest from the OEM's Support Downloads webpage.

Looking at the Lenovo webpage for the SL400 model you list, it shows Realtek Ethernet and Intel Wireless drivers, no Atheros. So unless you've listed the wrong model I would double check the exact model against the drivers posted online for SL400 at Lenovo Support - Download Drivers and Software (US)

There are also several video drivers for that model listed, so I'd use the autodetect feature Lenovo offers to determine your drivers from it's tab on Lenovo Support - Download Drivers and Software (US)

If there is any question remaining, determine the exact hardware device using Hardware Identification.

 

[Reverend Truth]

Yes - I have Windows update set to retrieve drivers and icons for me. I did visit Intel's page and used their automatic driver update tool after installing the operating system. I only started hunting drivers as a way to solve my blue screen problem.

The Lenovo site shows Intel Wireless LAN and a couple of nameless wireless LANs.

I've attached a screen grab that shows my network adapters (including the Atheros wireless LAN).

 

[gregrocker]

Did you use the auto detect feature on the Lenovo page I linked above?

You want to try the Lenovo drivers first as they may have modified them. But there are a lot of drivers dumped in the Downloads webpage for the SL400 so you need to either refine the model number or use the autodetect so it will bring up your exact wireless and display driver.

If not trace the exact device used on your laptop using Hardware Identification

 

[Reverend Truth]

I don't see the autodetect feature on the Lenovo support page. I do have Lenovo Thinkvantage system update installed which I run periodically.

I'd gone into my device manager already and my wireless adapter is identified there as 11 b/g Wireless LAN Mini PCI Express Adapter III, Manufacturer: Qualcom Atheros Communications Inc. I used that info to select the driver from their website.

 

[Reverend Truth]

I found the autodetect on the Levovo site. I had to "clear my selection" for it to come up.

Here's a screen grab of the selection I'm offered.

 

[gregrocker]

The problem is that the wrong driver might be installed which is forcing device to be named incorrectly as well. That's why I'd use autodetect or (even better) Hardware Identification to see what wireless device is actually installed on the laptop.

Is the model listed in Specs your actual model? Again, Lenovo's driver downloads webpage doesn't list Atheros as a wireless driver associated with that model. So either it's an anomaly or it might have had the wrong driver installed and is even listing the wrong device as a result.

I would trust the autodetect to provide the drivers for wireless and Video. If it still BSOD's then I'd run Hardware ID to determine with certainty the device makes/models.

 

[Reverend Truth]

OK - using hardware detect for 168C shows me Atheros as the vendor: PCI Vendor and Device Lists

These are the values for my hardware IDs:

 

[writhziden]

Software Concerns:

I note you have a driver updating utility. It is best to get your driver updates from the manufacturer of the hardware or from Lenovo. 3rd party driver updates are unreliable because they can update drivers that are not intended to be updated for notebook systems and their special power plan designs. That may be what happened to your wireless driver...
Automated driver update software can also install buggy drivers from time to time (any updated driver has the potential to be buggy), and updating multiple drivers at once increases the chances that one might be buggy.
​

Analysis:

The following is for information purposes only.

--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\062212-12355-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 2:33:04.270

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]athrx.sys[/COLOR][/B]

*** ERROR: Module load completed but symbols could not be loaded for [B][COLOR="Red"]athrx.sys[/COLOR][/B]

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : [B][COLOR="Red"]athrx.sys[/COLOR][/B] ( athrx+2e902 )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9b368 fffff800`02cccbbe : 00000000`00000001 fffff880`00000001 fffff800`00b9bae0 fffff800`02d00160 : nt!KeBugCheck

fffff800`00b9b368 fffff800`02cccbbe : 00000000`00000001 fffff880`00000001 fffff800`00b9bae0 fffff800`02d00160 : nt!KeBugCheck
fffff800`00b9b370 fffff800`02cffe2d : fffff800`02edb770 fffff800`02e182f0 fffff800`02c56000 fffff800`00b9c288 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b3a0 fffff800`02cfec05 : fffff800`02e1bfac fffff800`00b9b418 fffff800`00b9c288 fffff800`02c56000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b3d0 fffff800`02d0fb81 : fffff800`00b9c288 fffff800`00b9bae0 fffff800`00000000 fffffa80`07847a00 : nt!RtlDispatchException+0x415
fffff800`00b9bab0 fffff800`02cd4842 : fffff800`00b9c288 fffffa80`05ca21a0 fffff800`00b9c330 fffffa80`05d90020 : nt!KiDispatchException+0x135
fffff800`00b9c150 fffff800`02cd314a : ffffffff`ff609894 fffff800`02e47e80 fffff880`019994f0 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c330 fffff880`04085902 : fffff880`019994e8 fffffa80`000200ff fffff880`01999848 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c4c0 fffff880`019994e8 : fffffa80`000200ff fffff880`01999848 00000000`00000000 00000000`00000000 : athrx+0x2e902
fffff800`00b9c4c8 fffffa80`000200ff : fffff880`01999848 00000000`00000000 00000000`00000000 00fffa80`06823690 : tcpip!endpointLruContext+0x468
fffff800`00b9c4d0 fffff880`01999848 : 00000000`00000000 00000000`00000000 00fffa80`06823690 00000000`008c2406 : 0xfffffa80`000200ff
fffff800`00b9c4d8 00000000`00000000 : 00000000`00000000 00fffa80`06823690 00000000`008c2406 fffffa00`00000000 : tcpip!endpointLruContext+0x7c8


FAILURE_BUCKET_ID:  X64_0x1e_0_athrx+2e902

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\062212-12604-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 1:12:58.511

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff88001216518, 2, 1, fffff80002c8eaf2}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+f2 )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`041bc958 fffff800`02c83769 : 00000000`0000000a fffff880`01216518 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff800`041bc958 fffff800`02c83769 : 00000000`0000000a fffff880`01216518 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`041bc960 fffff800`02c823e0 : fffff800`02df6e80 fffff780`00000320 00000000`0004485f 0000000a`31cbc465 : nt!KiBugCheckDispatch+0x69

fffff800`041bc960 fffff800`02c823e0 : fffff800`02df6e80 fffff780`00000320 00000000`0004485f 0000000a`31cbc465 : nt!KiBugCheckDispatch+0x69
fffff800`041bcaa0 fffff800`02c8eaf2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00da7a64 : nt!KiPageFault+0x260
fffff800`041bcc30 fffff800`02c8e9a7 : 00000002`c7ec66c4 00000002`0004485f 00000002`c7ec661f 00000000`0000005f : nt!KiTimerExpiration+0xf2
fffff800`041bccd0 fffff800`02c7beca : fffff800`02df6e80 fffff800`02e04cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`041bcd80 00000000`00000000 : fffff800`041bd000 fffff800`041b7000 fffff800`041bcd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\062912-14024-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 12:16:36.005

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002ce0f90}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b0 )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`0311b288 fffff800`02cd8769 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff880`0311b288 fffff800`02cd8769 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0311b290 fffff800`02cd73e0 : fffffa80`0675e030 fffffa80`0686ce30 fffff880`00000001 fffffa80`03dcf978 : nt!KiBugCheckDispatch+0x69

fffff880`0311b290 fffff800`02cd73e0 : fffffa80`0675e030 fffffa80`0686ce30 fffff880`00000001 fffffa80`03dcf978 : nt!KiBugCheckDispatch+0x69
fffff880`0311b3d0 fffff800`02ce0f90 : fffff800`02e4be80 fffffa80`0a4bf6b0 00000000`00000000 fffffa80`07a4b5f0 : nt!KiPageFault+0x260
fffff880`0311b560 fffff800`02ce3c7d : fffffa80`03dcf970 fffffa80`0a5c5900 fffffa80`0a5c5938 fffff880`06ded1ac : nt!KiTimerWaitTest+0x2b0
fffff880`0311b5e0 fffff800`02ce3bbe : 00000066`e6df4b02 fffff880`0311bc58 00000000`002b3aa3 fffff880`009ea9e8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`0311bc30 fffff800`02ce39a7 : 0000001c`115237c6 0000001c`002b3aa3 0000001c`115237ad 00000000`000000a3 : nt!KiTimerExpiration+0x1be
fffff880`0311bcd0 fffff800`02cd0eca : fffff880`009e7180 fffff880`009f1f40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`0311bd80 00000000`00000000 : fffff880`0311c000 fffff880`03116000 fffff880`0311bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+2b0

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\063012-13447-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 0:56:40.271

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000a3bb8, fffff880026d5c60, 0}

Probably caused by : win32k.sys ( win32k!xxxInterSendMsgEx+fcb )

SYSTEM_SERVICE_EXCEPTION (3b)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

STACK_TEXT:  
fffff880`026d6640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxInterSendMsgEx+0xfcb


FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxInterSendMsgEx+fcb

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\070212-12776-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 0:12:14.252

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002c7366c, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!RtlFindSetBits+128 )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  BrStsW64.exe

STACK_TEXT:  
fffff880`095cdb58 fffff800`02d1cd88 : 00000000`0000001e ffffffff`c0000005 fffff800`02c7366c 00000000`00000000 : nt!KeBugCheckEx

fffff880`095cdb58 fffff800`02d1cd88 : 00000000`0000001e ffffffff`c0000005 fffff800`02c7366c 00000000`00000000 : nt!KeBugCheckEx
fffff880`095cdb60 fffff800`02cd1842 : fffff880`095ce338 fffff8a0`00000000 fffff880`095ce3e0 fffffa80`043d1060 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`095ce200 fffff800`02cd014a : 00000000`00000000 fffff880`03d75b50 fffff880`095ce660 fffffa80`043d6b60 : nt!KiExceptionDispatch+0xc2
fffff880`095ce3e0 fffff800`02c7366c : e56c6946`02cdde48 fffff880`095ce600 fffffa80`05db9010 fffff8a0`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`095ce578 e56c6946`02cdde48 : fffff880`095ce600 fffffa80`05db9010 fffff8a0`00000000 fffff880`00000016 : nt!RtlFindSetBits+0x128
fffff880`095ce580 fffff880`095ce600 : fffffa80`05db9010 fffff8a0`00000000 fffff880`00000016 00000000`00000001 : 0xe56c6946`02cdde48
fffff880`095ce588 fffffa80`05db9010 : fffff8a0`00000000 fffff880`00000016 00000000`00000001 00000000`00000000 : 0xfffff880`095ce600
fffff880`095ce590 fffff8a0`00000000 : fffff880`00000016 00000000`00000001 00000000`00000000 00000000`00000001 : 0xfffffa80`05db9010
fffff880`095ce598 fffff880`00000016 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffff8a0`00000000
fffff880`095ce5a0 00000000`00000001 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffff880`00000016
fffff880`095ce5a8 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`095bd000 : 0x1


FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!RtlFindSetBits+128

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\070312-13119-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 1:06:16.659

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff8800311b100, 0, 0, fffff880040967c6}

*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]athrx.sys[/COLOR][/B]

*** ERROR: Module load completed but symbols could not be loaded for [B][COLOR="Red"]athrx.sys[/COLOR][/B]

*** WARNING: Unable to verify timestamp for igdkmd64.sys

*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : [B][COLOR="Red"]athrx.sys[/COLOR][/B] ( athrx+227c6 )

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`0311bae0 fffffa80`00000000 : fffffa80`03d14270 fffff880`0311bc60 fffff880`04a80b80 00000000`00000002 : athrx+0x227c6
fffff880`0311bae8 fffffa80`03d14270 : fffff880`0311bc60 fffff880`04a80b80 00000000`00000002 fffffa80`0647e5d0 : 0xfffffa80`00000000
fffff880`0311baf0 fffff880`0311bc60 : fffff880`04a80b80 00000000`00000002 fffffa80`0647e5d0 fffffa80`0656a800 : 0xfffffa80`03d14270
fffff880`0311baf8 fffff880`04a80b80 : 00000000`00000002 fffffa80`0647e5d0 fffffa80`0656a800 fffff880`0407572c : 0xfffff880`0311bc60
fffff880`0311bb00 00000000`00000002 : fffffa80`0647e5d0 fffffa80`0656a800 fffff880`0407572c fffffa80`05bd4030 : igdkmd64+0x66b80
fffff880`0311bb08 fffffa80`0647e5d0 : fffffa80`0656a800 fffff880`0407572c fffffa80`05bd4030 fffff880`0311bba8 : 0x2
fffff880`0311bb10 fffffa80`0656a800 : fffff880`0407572c fffffa80`05bd4030 fffff880`0311bba8 fffffa80`06366000 : 0xfffffa80`0647e5d0
fffff880`0311bb18 fffff880`0407572c : fffffa80`05bd4030 fffff880`0311bba8 fffffa80`06366000 fffffa80`00000001 : 0xfffffa80`0656a800
fffff880`0311bb20 fffffa80`05bd4030 : fffff880`0311bba8 fffffa80`06366000 fffffa80`00000001 fffff880`0311bb00 : athrx+0x172c
fffff880`0311bb28 fffff880`0311bba8 : fffffa80`06366000 fffffa80`00000001 fffff880`0311bb00 fffffa80`067ad040 : 0xfffffa80`05bd4030
fffff880`0311bb30 fffffa80`06366000 : fffffa80`00000001 fffff880`0311bb00 fffffa80`067ad040 fffffa80`06366000 : 0xfffff880`0311bba8
fffff880`0311bb38 fffffa80`00000001 : fffff880`0311bb00 fffffa80`067ad040 fffffa80`06366000 fffff880`0174acdc : 0xfffffa80`06366000
fffff880`0311bb40 fffff880`0311bb00 : fffffa80`067ad040 fffffa80`06366000 fffff880`0174acdc fffffa80`067ad040 : 0xfffffa80`00000001
fffff880`0311bb48 fffffa80`067ad040 : fffffa80`06366000 fffff880`0174acdc fffffa80`067ad040 fffff880`0311bba8 : 0xfffff880`0311bb00
fffff880`0311bb50 fffffa80`06366000 : fffff880`0174acdc fffffa80`067ad040 fffff880`0311bba8 fffff880`0311bbb0 : 0xfffffa80`067ad040
fffff880`0311bb58 fffff880`0174acdc : fffffa80`067ad040 fffff880`0311bba8 fffff880`0311bbb0 00000000`00000000 : 0xfffffa80`06366000
fffff880`0311bb60 fffff800`02ccde19 : fffff880`0311bc70 00000000`00000000 fffffa80`00000000 fffff800`02cdd798 : ndis!ndisMiniportIsr+0x4c
fffff880`0311bba0 fffff800`02ccdbf8 : fffff880`009e7180 fffff880`0311bc70 fffff880`009ead80 00000000`00000007 : nt!KiScanInterruptObjectList+0x69
fffff880`0311bbf0 fffff800`02cc9ea2 : fffff880`009e7180 fffff880`00000002 00000000`00000002 fffff880`00000000 : nt!KiChainedDispatch+0x128
fffff880`0311bd80 00000000`00000000 : fffff880`0311c000 fffff880`03116000 fffff880`0311bd40 00000000`00000000 : nt!KiIdleLoop+0x32


FAILURE_BUCKET_ID:  X64_0x3D_athrx+227c6

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\071212-13228-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 0:02:58.896

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002cd011e}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : hardware ( nt!KiGeneralProtectionFault+de )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9c0f8 fffff800`02cd1769 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff800`00b9c0f8 fffff800`02cd1769 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c100 fffff800`02cd03e0 : fffff880`047f3098 fffff880`047f30ae fffff880`047f30b9 fffffa80`076d0c68 : nt!KiBugCheckDispatch+0x69

fffff800`00b9c100 fffff800`02cd03e0 : fffff880`047f3098 fffff880`047f30ae fffff880`047f30b9 fffffa80`076d0c68 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c240 fffff800`02cd011e : fffff800`00b9cc58 fffff800`02d82aa9 fffff800`00b9c600 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c3d0 fffff800`02cd9f90 : ffffffff`fffdb610 fffff800`02cdce3c 00000000`00000000 fffffa80`00000000 : nt!KiGeneralProtectionFault+0xde
fffff800`00b9c560 fffff800`02cdcc7d : fffffa80`076d0c60 fffff880`0399eb80 00000000`00000000 00000000`00000102 : nt!KiTimerWaitTest+0x2b0
fffff800`00b9c5e0 fffff800`02cdcbbe : 00000000`6aa18204 fffff800`00b9cc58 00000000`00002ccb fffff800`02e48be8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9cc30 fffff800`02cdc9a7 : 00000000`1d27fec5 00000000`00002ccb 00000000`1d27fef0 00000000`000000cb : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cc9eca : fffff800`02e44e80 fffff800`02e52cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\071612-13306-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 0:19:08.977

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff80003982bab, 2, 0, fffff80002cefd13}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )

IRQL_NOT_LESS_OR_EQUAL (a)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`0311b308 fffff800`02ce4769 : 00000000`0000000a fffff800`03982bab 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`0311b308 fffff800`02ce4769 : 00000000`0000000a fffff800`03982bab 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0311b310 fffff800`02ce33e0 : 00000000`00000000 fffffa80`07bdbbb0 fffffa80`07bdbbb6 fffff800`03982b80 : nt!KiBugCheckDispatch+0x69

fffff880`0311b310 fffff800`02ce33e0 : 00000000`00000000 fffffa80`07bdbbb0 fffffa80`07bdbbb6 fffff800`03982b80 : nt!KiBugCheckDispatch+0x69
fffff880`0311b450 fffff800`02cefd13 : fffffa80`0778b5f0 fffffa80`075c0a40 fffffa80`075c0a40 fffffa80`04b800e0 : nt!KiPageFault+0x260
fffff880`0311b5e0 fffff800`02cefbbe : 00000002`acd80f01 fffff880`0311bc58 00000000`00011fb3 fffff880`009eabe8 : nt!KiProcessExpiredTimerList+0x103
fffff880`0311bc30 fffff800`02cef9a7 : 00000000`badf6ec2 00000000`00011fb3 00000000`badf6e41 00000000`000000b3 : nt!KiTimerExpiration+0x1be
fffff880`0311bcd0 fffff800`02cdceca : fffff880`009e7180 fffff880`009f1f40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`0311bd80 00000000`00000000 : fffff880`0311c000 fffff880`03116000 fffff880`0311bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+103

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\071612-12838-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 2:43:57.092

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff80001609090, 2, 8, fffff80001609090}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9c288 fffff800`02c88769 : 00000000`0000000a fffff800`01609090 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx

fffff800`00b9c288 fffff800`02c88769 : 00000000`0000000a fffff800`01609090 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`00b9c290 fffff800`02c873e0 : fffff800`00b9cc58 fffff800`02d39aa9 fffff800`00b9c618 fffff800`00b9c600 : nt!KiBugCheckDispatch+0x69

fffff800`00b9c290 fffff800`02c873e0 : fffff800`00b9cc58 fffff800`02d39aa9 fffff800`00b9c618 fffff800`00b9c600 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c3d0 fffff800`01609090 : fffff800`02c93e3c fffff800`00b9c678 fffff880`00000000 00000001`40330a00 : nt!KiPageFault+0x260
fffff800`00b9c568 fffff800`02c93e3c : fffff800`00b9c678 fffff880`00000000 00000001`40330a00 00000000`00000002 : 0xfffff800`01609090
fffff800`00b9c570 fffff800`02c93cd6 : fffff880`0399eb80 fffff880`0399eb80 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`02c93bbe : 00000016`e75d2b52 fffff800`00b9cc58 00000000`00099f32 fffff800`02dfe8c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02c939a7 : 00000006`3f57bac4 00000006`00099f32 00000006`3f57baa1 00000000`00000032 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02c80eca : fffff800`02dfbe80 fffff800`02e09cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\071612-10701-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 0:08:26.083

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff880044850fd}

*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]athrx.sys[/COLOR][/B]

*** ERROR: Module load completed but symbols could not be loaded for [B][COLOR="Red"]athrx.sys[/COLOR][/B]

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : [B][COLOR="Red"]athrx.sys[/COLOR][/B] ( athrx+4f0fd )

UNEXPECTED_KERNEL_MODE_TRAP (7f)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02c9a769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx

fffff800`00ba4d28 fffff800`02c9a769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02c98c32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff800`00ba4d30 fffff800`02c98c32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`044850fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`34b9c420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : athrx+0x4f0fd


FAILURE_BUCKET_ID:  X64_0x7f_8_athrx+4f0fd

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [F:\Kingston\BSODDmpFiles\Reverend Truth\071612-10311-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

System Uptime: 0 days 0:13:19.554

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`00b9b408 fffff800`02cc0bbe : 00000000`00000000 00000000`00b9b7b0 fffff800`00b9bb80 fffff800`02cf4160 : nt!KeBugCheck

fffff800`00b9b408 fffff800`02cc0bbe : 00000000`00000000 00000000`00b9b7b0 fffff800`00b9bb80 fffff800`02cf4160 : nt!KeBugCheck
fffff800`00b9b410 fffff800`02cf3e2d : fffff800`02ecf770 fffff800`02e0c2f0 fffff800`02c4a000 fffff800`00b9c328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b440 fffff800`02cf2c05 : fffff800`02e0ffac fffff800`00b9b4b8 fffff800`00b9c328 fffff800`02c4a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b470 fffff800`02d03b81 : fffff800`00b9c328 fffff800`00b9bb80 fffff800`00000000 fffffa80`07f19c10 : nt!RtlDispatchException+0x415
fffff800`00b9bb50 fffff800`02cc8842 : fffff800`00b9c328 fffffa80`07f19c18 fffff800`00b9c3d0 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c1f0 fffff800`02cc714a : fffff880`009e7180 fffff880`009e9300 fffff800`00b9c600 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c3d0 fffff800`02cd0ec2 : ffffffff`fffe7960 fffff800`02cd3e3c 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c560 fffff800`02cd3c7d : fffffa80`07f19c10 fffff880`03974b00 fffff880`03974b80 00000000`00000102 : nt!KiTimerWaitTest+0x1e2
fffff800`00b9c5e0 fffff800`02cd3bbe : 00000001`dc92484b fffff800`00b9cc58 00000000`0000c835 fffff800`02e3e928 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9cc30 fffff800`02cd39a7 : 00000000`820fe0c7 00000000`0000c835 00000000`820fe06e 00000000`00000035 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cc0eca : fffff800`02e3be80 fffff800`02e49cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FAILURE_BUCKET_ID:  X64_0x1e_0_nt!KiKernelCalloutExceptionHandler+e

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793

--------------------------------------------
---------------------END--------------------
--------------------------------------------

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

PxHlpa64.sys Fri Feb 2 14:24:22 2007 (45C3AC06)
ASMMAP64.sys Sun Feb 4 12:52:56 2007 (45C63998)
ibmpmdrv.sys Wed May 14 03:15:52 2008 (482AADC8)
VSTCNXT6.SYS Wed Oct 15 18:52:22 2008 (48F69046)
VSTAZL6.SYS Wed Oct 15 18:53:42 2008 (48F69096)
VSTDPV6.SYS Wed Oct 15 18:57:45 2008 (48F69189)
GEARAspiWDM.sys Mon May 18 06:17:04 2009 (4A1151C0)
PuAcpi64.sys Thu Jun 4 08:40:26 2009 (4A27DCDA)
intelppm.sys Mon Jul 13 17:19:25 2009 (4A5BC0FD)
rimmpx64.sys Thu Sep 3 04:37:00 2009 (4A9F9C4C)
rimspx64.sys Thu Sep 3 04:59:25 2009 (4A9FA18D)
rixdpx64.sys Thu Sep 3 05:14:28 2009 (4A9FA514)
IntcHdmi.sys Mon Mar 15 09:45:27 2010 (4B9E5617)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
SynTP.sys Thu Apr 22 17:11:30 2010 (4BD0D7A2)
smiifx64.sys Mon Sep 6 22:38:27 2010 (4C85C1C3)
ApsHM64.sys Tue Mar 29 03:55:16 2011 (4D91AC84)
Apsx64.sys Tue Mar 29 03:58:36 2011 (4D91AD4C)
SYMDS64.SYS Mon May 16 16:15:03 2011 (4DD1A1E7)
Rt64win7.sys Fri Jun 10 00:33:15 2011 (4DF1BAAB)
igdkmd64.sys Thu Oct 13 13:05:43 2011 (4E973687)
ccSetx64.sys Fri Nov 4 16:05:25 2011 (4EB461A5)
ccSetx64.sys Fri Nov 4 16:05:25 2011 (4EB461A5)
SYMNETS.SYS Sat Nov 12 14:11:53 2011 (4EBEE119)
Ironx64.SYS Mon Nov 14 19:00:53 2011 (4EC1C7D5)
SYMEVENT64x86.SYS Tue Nov 22 11:30:48 2011 (4ECBEA58)
SYMEFA64.SYS Tue Nov 22 17:49:28 2011 (4ECC4318)
psadd.sys Mon Dec 26 18:09:28 2011 (4EF91AC8)
athrx.sys Fri Feb 24 00:55:06 2012 (4F47425A)
SRTSP64.SYS Thu Mar 15 12:09:13 2012 (4F623049)
SRTSPX64.SYS Thu Mar 15 12:09:21 2012 (4F623051)
EX64.SYS Wed Apr 25 03:27:28 2012 (4F97C380)
ENG64.SYS Wed Apr 25 03:29:25 2012 (4F97C3F5)
EraserUtilRebootDrv.sys Tue May 15 18:36:03 2012 (4FB2F673)
eeCtrl64.sys Tue May 15 18:36:03 2012 (4FB2F673)
BHDrvx64.sys Wed May 16 20:16:36 2012 (4FB45F84)
IDSvia64.sys Thu May 24 18:08:33 2012 (4FBECD81)

PxHlpa64.sys
ASMMAP64.sys
ibmpmdrv.sys
VSTCNXT6.SYS
VSTAZL6.SYS
VSTDPV6.SYS
GEARAspiWDM.sys
PuAcpi64.sys
intelppm.sys
rimmpx64.sys
rimspx64.sys
rixdpx64.sys
IntcHdmi.sys
amdxata.sys
SynTP.sys
smiifx64.sys
ApsHM64.sys
Apsx64.sys
SYMDS64.SYS
Rt64win7.sys
igdkmd64.sys
ccSetx64.sys
ccSetx64.sys
SYMNETS.SYS
Ironx64.SYS
SYMEVENT64x86.SYS
SYMEFA64.SYS
psadd.sys
athrx.sys
SRTSP64.SYS
SRTSPX64.SYS
EX64.SYS
ENG64.SYS
EraserUtilRebootDrv.sys
eeCtrl64.sys
BHDrvx64.sys
IDSvia64.sys
​

Recommendations:

Try installing Wireless LAN ThinkPad 11abg, abgn, bg, bgn for Windows Vista (32-bit, 64-bit) - ThinkPad using the steps for installing a Vista driver on Windows 7:

http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html​

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

1. First, download the driver specified. Then do the next steps.
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 Network adapters
7. Right click the wireless network 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 only if Windows asks you to.
11. Install the downloaded driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the driver specified. Then do the next steps.
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 Network adapters
8. Right click the wireless network device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the downloaded driver for the device.

​

 

[gregrocker]

I found the autodetect on the Levovo site. I had to "clear my selection" for it to come up.

Here's a screen grab of the selection I'm offered.

It appears Lenovo has indeed modified the driver and you would use the next to last one in your screenshot, as confirmed by writhziden.

 

[Reverend Truth]

I followed your instructions and installed the driver from the Lenovo site that you recommended.

I've been running on battery power for over an hour now and so far, so good - No crashes.

That's a long time for this machine but not unprecedented. I'll have to test it for a few days to be sure.

If there are no further issues, I'll report back and mark the thread as solved.

I can't thank you enough for your help and for your extremely clear instructions.

Assuming that driver was the culprit, I wonder why it was only an issue on battery power.

 

[gregrocker]

Have you also updated the Display driver from the Lenovo site?

You should not have Standard VGA driver.

 

[Reverend Truth]

I downloaded what I believe was the correct driver from the Lenovo site.

Windows asked me to restart after I uninstalled the existing driver and then automatically installed another driver upon restart. When I tried to update to the downloaded driver I got a message saying that windows had determined that the driver was up to date. I then ran windows update and it gave me an updated for that driver which I let it install.

It is a different driver than what I found on the lenovo site but is also different than what was there earlier.

Should I leave this driver or uninstal it and go with the one from Lenovo?

 

[writhziden]

How is the display currently? Is the resolution what you remember? Are your window sizes as you remember them? If everything looks fine to you and your programs all run fine, then you probably have nothing to worry about with the display drivers.

 

[Reverend Truth]

Everything looks good.

Problem is, I just had another BSOD while running on battery power.

I've attached the mini dump.