Lenovo T510 - Daily BSOD mess

[philnicholas]

I have a Lenovo T510 (purchased 5/8/10), running the factory-installed Win7 64-bit OS, with all hardware and software drivers/patches up to date. Yet I continue to receive intermittent, unpredictable BSOD's -- about daily, sometimes more. I'm posting this crash dump in hopes of definitively nailing down the cause. This crash came just 4 minutes after the previous BSOD.

System: Lenovo T510-4313CTO (i.e., configured to order)
OS: Windows 7 64-bit Ultimate; all drivers up to date from Lenovo.
CPU: Core i7-620
Memory: 8GB (4x4GB G.Skill memory; test and passed the Thinkvantage Tools memory test)
Video: Nvidia NVS 3100M

 

[ttran]

Stop code 124 is usually hardware related. Please read this article to know what it is and what to try:
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

BUGCHECK SUMMARY:

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.277\072410-15334-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`0328ce50
Debug session time: Sat Jul 24 16:10:51.628 2010 (UTC + 7:00)
System Uptime: 0 days 0:02:45.173
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009e02028, b2000000, 30005}

Probably caused by : hardware

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

 

[Tews]

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009e02028, b2000000, 30005}

Probably caused by : hardware

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

The following drivers are outdated and should be updated

fffff880`01a0b000 fffff880`01a12000  smiifx64.sys Mon May 12 05:01:13 2008 (48280759) SMI Driver for Lenovo system 
fffff880`040b9000 fffff880`040bf000  Tppwr64v.sys Wed Oct 18 04:40:21 2006 (4535E875) ThinkPad Pwr Mgmt Port -

 

[ickymay]

this shows as WHEA_UNCORRECTABLE_ERROR (124) which is a hardware error, I suggest firstly get the latest drivers for your system and these show in the crash dump on your system as

mdmxsdk.sys fffff880`03bb1000 fffff880`03bb5280 0x00004280 0x449716be 19/06/2006 22:27:26
Tppwr64v.sys fffff880`040b9000 fffff880`040bf000 0x00006000 0x4535e875 18/10/2006 09:40:21
smiifx64.sys fffff880`01a0b000 fffff880`01a12000 0x00007000 0x48280759 12/05/2008 10:01:13
XAudio64.sys fffff880`0937f000 fffff880`09387000 0x00008000 0x49f89a93 29/04/2009 19:21:07

the ones from 2006 pre-date windows 7 release even development so i suggest you really need to update or unninstall/disable them

mdmxsdk.sys - Conexant Modem Diagnostic Interface DRIVER
Tppwr64v.sys is the ThinkPad Pwr Mgmt Port and can be found at Driver Reference*
smiifx64.sys is the SMI Driver for Lenovo system found at Driver Reference*
xaudio64.sys is your Conexant Modem Audio

also please tell us what antivirus and or third party firewall you are using ?

do you have the latest bios for your laptop ?

*driver links compliments to Usasma.

 

[philnicholas]

ickymay: Thank you for the fast and helpful response

ickymay, thank you for your quick response.

this shows as WHEA_UNCORRECTABLE_ERROR (124) which is a hardware error, I suggest firstly get the latest drivers for your system

I did that already; both through Lenovo and Microsoft.

also please tell us what antivirus and or third party firewall you are using ?

This time around I didn't install anti-virus or a firewall (other than the OS-based one), though I am behind a hardware firewall. Note that this problem occurred with the original system image, shipped from Lenovo in May. So a few weeks ago I restored the hard drive (from the recovery partition) to if that might help. Still, the problem continues. From what you've posted, I can now see why.

do you have the latest bios for your laptop ?

Yes. I've gone to the ThinkVantage updater built into the system and made sure that I have the latest hardware and software updates (as noted in my original post).

It seems from what you've posted that at least those four drivers are seriously out of date -- 2006 to 2008! -- and not Win7 compliant, even though they were install on my system through Lenovo!! I'm very disappointed in Lenovo for pushing such out-of-date drivers to my system. That means there are many thousands of owners with T410/T510 series systems that are also getting the same bad updates.

Thank you, again, for your quick response!

 

[philnicholas]

Tews: thank you for the reply

The following drivers are outdated and should be updated

fffff880`01a0b000 fffff880`01a12000  smiifx64.sys Mon May 12 05:01:13 2008 (48280759) SMI Driver for Lenovo system 
fffff880`040b9000 fffff880`040bf000  Tppwr64v.sys Wed Oct 18 04:40:21 2006 (4535E875) ThinkPad Pwr Mgmt Port -

Thank you for posting this. From your post and ickymay's reply, I now see that the "updates" that Lenovo is sending out are not up to date at all. It's really frustrating to have the system updater say that there are "no available updates" and yet in reality the drivers on my system are completely out of date.

I can only wonder how many thousand of other Lenovo T410/T510 owners are running Win7 and facing this same driver mess but don't know why.

 

[philnicholas]

Stop code 124 is usually hardware related.

ttran, thank you for the fast response. As you can see from the two other replies, it looks like my system has horribly out of date drivers.

 

[jmwiles3]

Welcome to the world of Lenovo. They do this across the board. When I origianlly complained about systems shipping out with bios versions at least 5 versions behind current, and about BSOD's right out of the box, I was told "no sense in beating a dead horse."

Nice, makes me glad my personal equipment isn't any of their products.

 

[philnicholas]

Question on driver dates and troubleshooting

ickymay ,

I hope this thread is still open for questions. I did some research on my system and I have a question about what you wrote about these drivers (found in my BSOD dump file):

mdmxsdk.sys fffff880`03bb1000 fffff880`03bb5280 0x00004280 0x449716be 19/06/2006 22:27:26
Tppwr64v.sys fffff880`040b9000 fffff880`040bf000 0x00006000 0x4535e875 18/10/2006 09:40:21
smiifx64.sys fffff880`01a0b000 fffff880`01a12000 0x00007000 0x48280759 12/05/2008 10:01:13
XAudio64.sys fffff880`0937f000 fffff880`09387000 0x00008000 0x49f89a93 29/04/2009 19:21:07

First, I found those on my system and the dates indicated above are the dates for their "digital signature". I don't know if that's necessarily their release dates.

Second, is there an easy way to disable those specific drivers in hopes of narrowing it down? Are any of those four critical to system operations? Obviously I don't want to render my system un-bootable


Thanks!

 

[philnicholas]

Welcome to the world of Lenovo. They do this across the board. When I origianlly complained about systems shipping out with bios versions at least 5 versions behind current, and about BSOD's right out of the box, I was told "no sense in beating a dead horse."

Nice, makes me glad my personal equipment isn't any of their products.

Google T510 or T410 and "blue screen" or BSOD. I'm one of many. I used to be a huge Thinkpad advocate; recommending them and even buying them for friends for school. But if this continues, Lenovo will ZOOM right past Dell to the top of my personal Do Not Buy list. I will also weigh my legal options, as I'm unwilling to just let this be a $2,000 mistake.

One more thing: The system has an Nvidia NVS3100 video card. Get this: it's not compatible with HDMI-based monitors such as my two gorgeous LG246WP LCDs! Nvidia apparently knows about the 59Hz HDMI timing bug and simply will not fix it.

 

[ttran]

ickymay ,

I hope this thread is still open for questions. I did some research on my system and I have a question about what you wrote about these drivers (found in my BSOD dump file):

mdmxsdk.sys fffff880`03bb1000 fffff880`03bb5280 0x00004280 0x449716be 19/06/2006 22:27:26
Tppwr64v.sys fffff880`040b9000 fffff880`040bf000 0x00006000 0x4535e875 18/10/2006 09:40:21
smiifx64.sys fffff880`01a0b000 fffff880`01a12000 0x00007000 0x48280759 12/05/2008 10:01:13
XAudio64.sys fffff880`0937f000 fffff880`09387000 0x00008000 0x49f89a93 29/04/2009 19:21:07

First, I found those on my system and the dates indicated above are the dates for their "digital signature". I don't know if that's necessarily their release dates.

Second, is there an easy way to disable those specific drivers in hopes of narrowing it down? Are any of those four critical to system operations? Obviously I don't want to render my system un-bootable


Thanks!

Hi,
At this point I want to jump in. I'm using Lenovo thinkpad too, and I can say for sure that all of those driver are all important for your computer. I believe that the first one, which is mdmxsdk.sys, date from 2006 is the newest one, because the one in my system is 2006 too. But you can always update the first one and last one, which is xaudio.sys by updating audio driver, I believe xaudio.sys date 2009 is the newest one, not 2006.
Secondly, I belive that Tppwr64v.sys that date from 2006 is the cause for your BSODs. I think Lenovo should fix this issue as soon as possible. It belong to power manager driver, which is very important. I remember that I use to have a BSODs related to intel wifi card driver, but original problem is due to power manager driver because It could not wake my computer up from hibernating. Please update the power manager driver right away (not the utility but the driver, look up carefully).

smiifx64.sys is SMI Driver for Lenovo system, I've never seen this driver, but update it as well.
Lenovo Support & downloads - Home page

Regard,

Tuan

 

[ickymay]

thanks for that Ttran and to clarify for philnicholas unfortunately this sort of driver issue is why windows gets such bad press for it's failures and crashes , because when windows versions come out there are always many manufacturers who are slow to react or have simply not rewritten their drivers to work properly on the windows Operating system

apple avoids this by building a limited range of systems with specified hardware and drivers all written in house or at least close collaboration

It is important to remember that any hardware device can take months or a year or more from build to actually reaching a customer so it's very common to receive a system that's got out of date drivers :huh:

fortunately you have brought your problem to a forum where others may be able to help so for now maybe we should check and double check you do have the latest bios and drivers for your system ?

please can you download and run CPU-Z select the mainboard tab and tell us the date and version number of your BIOS ?

also go to the lenovo support site and download and install the "power management driver" which has a date of 10 Jun 2010 ?

the audio driver is also there with a date of 25 May 2010 ?

bookmark that drivers page for now and please provide the .dmp file and let us know if you have a new bluescreen

 

[philnicholas]

Thanks, Tuan

Secondly, I belive that Tppwr64v.sys that date from 2006 is the cause for your BSODs. I think Lenovo should fix this issue as soon as possible. It belong to power manager driver, which is very important. I remember that I use to have a BSODs related to intel wifi card driver, but original problem is due to power manager driver because It could not wake my computer up from hibernating. Please update the power manager driver right away (not the utility but the driver, look up carefully).

Tuan,

Thank you for jumping in. I don't know how else to say that I have the latest drivers here... or else the System Update really has me fooled.

Since you mentioned the "Tppwr64v.sys" driver, I can already confirm that I went to Lenovo's support page for the T510/T410 http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-74582and manually downloaded the latest "ThinkPad Power Management driver" (Version: 1.60, Release Date: 2009/12/11) at [FONT=&quot]http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4GXPEG[/FONT]

Yet even still my C:\Windows\System32\driver\Tppwr64v.sys file has a "Date modified" of 5/12/2010. The digital signature (Properties -> Digital Signatures -> Details) is dated "‎Wednesday, ‎October ‎18, ‎2006 7:11:27 PM". That's the date you were seeing in the dump that posted before. So whatever files the Lenovo Power Manager Update is installing is not updating or affecting the "Tppwr64v.sys" file. It's almost like "Tppwr64v.sys" is an orphan; forever to remain non-updated or something.


Just so you see what I've got, went to the diagnostics (ThinkVantage Toolbox -> Diagnostics -> System Information -> Advanced) and saved the complete specs to PDF file... see attached. As you can see, I am using BIOS v.1.24 (the latest). If you see anything out of spec or otherwise problematic, please let me know.

 

[philnicholas]

apple avoids this by building a limited range of systems with specified hardware and drivers all written in house or at least close collaboration

I know this all too well. I worked support at Apple in '95 and was a hardware manager (glorified title if there ever was one) in '97. I worked the original G3 "gossamer" project.

please can you download and run CPU-Z select the mainboard tab and tell us the date and version number of your BIOS ?

See my reply to Tuan (above). I'm running v.1.24 of the BIOS, which Lenovo's site shows as the latest.

also go to the lenovo support site and download and install the "power management driver" which has a date of 10 Jun 2010 ?

Yes. See my reply to Tuan. It doesn't affect the driver with the questionable date.

the audio driver is also there with a date of 25 May 2010 ?

Yes. And for the note, even though I re-downloaded and re-installed the audio drivers, the System Information printout still shows a variety of dates that pre-date the May 25 2010 revision date shown on the Lenovo site.... tho the version number (4.95.43.52) matches. Go figure.

 

[jmwiles3]

I seem to have more problems with their desktops than I do their laptops. The work laptop I have is a w700 that hasn't had any issues at all with xp/vista/7. I may have just jinxed myself.

One more thing, we're contracted to buy all our systems from IBM/Lenovo so I don't have the option to switch to anything else except Apple.

 

[philnicholas]

...and please provide the .dmp file and let us know if you have a new bluescreen

I've continued to have occasional BSODs. See attached. I'm really at my ends on this one.

 

[Jonathan_King]

Still points to hardware. Please read this article: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Test your CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Test hard drive: http://www.carrona.org/hddiag.html

Test your temps: SpeedFan - Access temperature sensor in your computer

I see nvcplui.exe was running at the time of the crash. Due to the nature of the program, I would uninstall the nVidia Controll application. Do not overclock and hardware, especially video card in this case.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 30 00:38:25.971 2010 (UTC - 4:00)
System Uptime: 1 days 14:38:46.860
BugCheck 124, {0, fffffa8009ace028, b2000000, 30005}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  nvcplui.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[cluberti]

And the worst part about the hardware errors is that it's Proc 0, but the WHEA error is listed as "unknown". Very odd.

 

[ickymay]

...and please provide the .dmp file and let us know if you have a new bluescreen

I've continued to have occasional BSODs. See attached. I'm really at my ends on this one.

this still shows as a WHEA_UNCORRECTABLE_ERROR (124) which is a hardware error, to eliminate the potential software causes you must remove these drivers which are still showing in the .dmp

mdmxsdk.sys fffff880`03bb1000 fffff880`03bb5280 0x00004280 0x449716be 19/06/2006 22:27:26
Tppwr64v.sys fffff880`040b9000 fffff880`040bf000 0x00006000 0x4535e875 18/10/2006 09:40:21
smiifx64.sys fffff880`01a0b000 fffff880`01a12000 0x00007000 0x48280759 12/05/2008 10:01:13
XAudio64.sys fffff880`0937f000 fffff880`09387000 0x00008000 0x49f89a93 29/04/2009 19:21:07

the ones from 2006 pre-date windows 7 release even development so i suggest you really need to update or unninstall/disable them

mdmxsdk.sys - Conexant Modem Diagnostic Interface DRIVER
xaudio64.sys is your Conexant Modem Audio

you are not using your modem so please go into your device manager and unninstall it then reboot and go straight into your bios and turn off the device which will stop windows trying to reinstall it ?

I would say let's try getting rid of the modem drivers then you can concentrate on the last two old drivers below if you are still getting problems ?

Tppwr64v.sys is the ThinkPad Pwr Mgmt Port and can be found at Driver Reference
smiifx64.sys is the SMI Driver for Lenovo system found at Driver Reference

as Jonathan King has suggested unninstall the Nvidia control panel application

other things to try are turn off your laptop carefully hold your fans static and blow through with air to clear any dust and also remove your battery and then remove your ram then replace to make sure the sticks are properly seated ( do not do this if it might void any warranty ?)

It may or may not be significant that your windows build string is .gdr which means it has windows intermediary patches for hardware compatibility issues and to quote digital life "The fact that Microsoft adds GDR into build string of OS kerner (ntoskrnl.exe) of Windows 7 RTM may signifies that the reliability and stability can still be improved considerably."

as a long shot can you please run the windows 7 upgrade advisor to check your hardware compatibility

did you say your bios is up to date ?

I would be starting a conversation with lenovo support about your bluescreens too ?


let us know how it goes