Lenovo X61S Crashing Often After Win 7 Install

gjpundsack · 01 Feb 2011

Didn't happen before. I have downloaded all Lenovo updates and MS updates I have been able to find for Windows 7.Suspect it may have something to do with the fact that under "ThinkVantage Tool Box>Diagnostics>DXevice Manager Alerts, I have a message that says "Driver not installed on PCI memory conroller" and another message that says "Driver problem on Intel PCIC Compatiable PMCIA Controller". Both give me click options for reinstalling the drivers, but when I do that for the PCI Memor Controller, I get a dialogue box that says the manufacturer of the device is unknown and a message that says: "The drivers for this device are not installed. (Code 28). There is no driver selected for the device information set or element. To find a driver for this device, click Update Driver". Then, I cannot click on the update driver tab and get anything. On the PMCIA Controller, the dialogue box says the location of the device is unknown and the message says: "his device cannot start. (Code 10)".

What to do?

CarlTR6 · 01 Feb 2011

Hi and welcome to the forum. Can you boot sometimes in the normal mode? Can you boot in the safe mode? Were you ever able to boot into Windows successfully? Can you use your CD to do a repair install? Repair Install

gjpundsack · 01 Feb 2011

Thanks for responding. Yes, I can boot in all modes. Everything works fine up to the point of freezing. I will try the reinstall procedure you graciously provided me. I will post my results. Thanks again.

CarlTR6 · 01 Feb 2011

You are most welcome. If you are getting BSOD's, read this tutorial, follow the instructions and upload the files: https://www.sevenforums.com/crashes-d...tructions.html

gjpundsack · 01 Feb 2011

Still having problems. See Zip file attached as instructed. Thanks for your help. Software is Windows 7 Professional version acquired from a retailer. Its installed on a 2-year old Lenovo X61S laptop. It was reinstalled today.

CarlTR6 · 03 Feb 2011

I looked through the files you uploaded. Here are the problem devices. This is not necessarily bad unless one of them is critical to the running of your system. It just means those devices will not work.

MpKsl84e84e85 ROOT\LEGACY_MPKSL84E84E85\0000 This device is not present, is not working properly, or does not have all its drivers installed.
PCI Memory Controller PCI\VEN_8086&DEV_444E&SUBSYS_444E8086&REV_01\4&F588BB4&0&00E0 The drivers for this device are not installed.
MpKsl179d3752 ROOT\LEGACY_MPKSL179D3752\0000 This device is not present, is not working properly, or does not have all its drivers installed.
MpKsl209a1df3 ROOT\LEGACY_MPKSL209A1DF3\0000 This device is not present, is not working properly, or does not have all its drivers installed.

I see some outdated drivers loading on your system. Some of these can easily be contributing to the freezes. Some are quite outdated and are XP drivers. Software and hardware designed for XP and not upgraded for Win 7 are not going to run properly on a Win 7 system. Win 7 is a totally new OS and is not an evolution from XP. It is different even from Vista. Update the following drivers.

ADIHdAud.sys 5/18/2009 - SoundMAX Digital HD Audio Driver. OEM - none at Analog Devices | Mixed-signal and Digital Signal Processing ICs. See if you can update this through the Lenovo website.

e1e6032.sys 3/24/2009 - Intel PRO/1000 Adapter NDIS 6 deserialized driver (LAN adapter). http://downloadcenter.intel.com/Default.aspx. First try to updated this from Lnovo and then try the Intel site.

HSX_CNXT.sys 12/22/2006 - SoftK56 Modem Driver by Conexant Systems. Conexant: Support.

HSX_DPV.sys 12/22/2006 - SoftK56 Modem Driver by Conexant Systems. Conexant: Support.

HSXHWAZL.sys 12/22/2006 - SoftK56 Modem Driver by Conexant Systems. Conexant: Support.

ibmpmdrv.sys 5/31/2007 - ThinkPad Power Management Driver Lenovo Support - Home page.

mdmxsdk.sys 6/19/2006 - Conexant Modem Diagnostic Interface x86 Driver. Conexant: Support.

netw5v32.sys 3/26/2009 - Intel Wireless WiFi Link Driver. http://downloadcenter.intel.com/Default.aspx.

TVicPort.sys 3/30/2005 - TVicPort Generic Device. EnTech Taiwan | Support.

xaudio.sys 11/28/2006 - Conexant modem audio driver. Conexant: Support.

How to find drivers -

- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those 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 manufacturer links are on this page: Drivers and Downloads

If you need help with the drivers, please post.

gjpundsack · 04 Feb 2011

New zip file attached [dated 02.04.11]. After seeing your advice about updating everything through Lenovo, I found a single point on Lenovo's website that had me enter all my machine ID numbers and than it updated everything in one fell swoop re Windows 7. The zip file contains a Lenovo generated report showing everything passed. Freezes continued. So, after one of the freezes, I saved the Windows error message and it can be found in the zip file. The remaining items in the zip file are updated reports that are asked for in the BSOD posting instructions.
Now what to do?

CarlTR6 · 04 Feb 2011

I see that you had three BSOD's today. All of the are Bugcheck 124, WHEA_UNCORRECTABLE_ERROR. This is usually caused by hardware and sometimes by drivers. All of your drivers, at least those that got loaded, are up to date. Your uptimes in all three dumps are 9 seconds or less. Many times crashes during the boot process indicate a power supply problem. Were you on battery or plugged in when these crashes occurred? If plugged in, do you get the same results when on just the battery? Do you get BSOD's booting in the Safe mode?

Bugcheck 124 is a general hardware error and it is fundamentally different from many other types of BSOD's because it stems from a hardware complaint. Bugcheck 124 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: [2-Int] Stop 0x124 - what it means and what to try

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c0e000 PsLoadedModuleList = 0x82d56810
Debug session time: Fri Feb  4 09:01:09.941 2011 (GMT-5)
System Uptime: 0 days 0:00:08.985
Loading Kernel Symbols
........................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 862848fc, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 862848fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8d51bcc4 82cdcfc5 862848e0 82d75c28 82d75c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8d51bce4 82cdddef 82d75c20 862848e0 82d75c50 nt!WheapProcessWorkQueueItem+0x56
8d51bd00 82c7bf3b 82d75c20 00000000 855e8a70 nt!WheapWorkQueueWorkerRoutine+0x1f
8d51bd50 82e1c6d3 00000001 aff0b664 00000000 nt!ExpWorkerThread+0x10d
8d51bd90 82cce0f9 82c7be2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

1: kd> lmtsmn
start    end        module name
8b0af000 8b0f7000   ACPI     ACPI.sys     Tue Dec 01 01:56:47 2009 (4B14BE2F)
8b34d000 8b356000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8b800000 8b809000   ApsHM86  ApsHM86.sys  Sun Jun 13 22:19:32 2010 (4C1591B4)
8b811000 8b831000   Apsx86   Apsx86.sys   Sun Jun 13 22:38:32 2010 (4C159628)
8b317000 8b320000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b320000 8b343000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8b156000 8b161000   BATTC    BATTC.SYS    Mon Jul 13 19:19:15 2009 (4A5BC0F3)
832a1000 832a9000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
832eb000 83396000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8b7c9000 8b7ee000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
832a9000 832eb000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8b580000 8b5dd000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8b14e000 8b156000   compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6)
8b7ee000 8b7fb000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b7b8000 8b7c9000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8b5eb000 8b5ef480   DozeHDD  DozeHDD.sys  Tue Nov 10 08:47:43 2009 (4AF96EFF)
90f19000 90f2a000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
90e18000 90f19000   dump_iaStor dump_iaStor.sys Sat Nov 06 03:37:33 2010 (4CD505BD)
8b38a000 8b39b000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8b356000 8b38a000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8b5f0000 8b5f9000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8b786000 8b7b8000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8b980000 8b9b1000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8301e000 83055000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8b77e000 8b786000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
8b216000 8b317000   iaStor   iaStor.sys   Sat Nov 06 03:37:33 2010 (4CD505BD)
8b1bc000 8b1c3000   intelide intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
80bad000 80bb5000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8b56d000 8b580000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8b71c000 8b741000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
83218000 83290000   mcupdate mcupdate.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
8b000000 8b016000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8b343000 8b34d000   msahci   msahci.sys   Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b100000 8b108000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8b542000 8b56d000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8b76e000 8b77e000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8b627000 8b6de000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8b6de000 8b71c000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
82c0e000 8301e000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
8b413000 8b542000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8b13d000 8b14e000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8b108000 8b132000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8b1c3000 8b1d1000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b1d1000 8b1ff000   pcmcia   pcmcia.sys   Mon Jul 13 19:19:29 2009 (4A5BC101)
8b5dd000 8b5eb000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
83290000 832a1000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8b741000 8b76e000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8b809000 8b811000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8b837000 8b980000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
8b132000 8b13d000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8b9b1000 8b9b9380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8b161000 8b171000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8b171000 8b1bc000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8b9ba000 8b9f9000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8b030000 8b0a1000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8b0a1000 8b0af000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8b0f7000 8b100000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
Mini Kernel Dump does not contain unloaded driver list

gjpundsack · 06 Feb 2011

Still having the problem. But...your questions about the battery has me wondering. My battery is worn out and I only use the laptop on AC with the battery installed in the machine. Relative to the problem? I can start in safe mode, but have not chosen to do so because I don't know what to do when I am there. Attached are a couple of crash dump reports--maybe they will help?

gjpundsack · 07 Feb 2011

Today, after the first freeze, I removed the dead battery and re-booted the machine in normal mode to see if the battery was the problem. Guess not, it froze again.