Need help with Windows 7 BSOD on Lenovo T500

The presence of older drivers on a system doesn't mean that that driver is causing the problem. It's only an indication that the driver is old - which also means (IMO) that the package that was installed with it was old also.

In this instance, I suspect that an issue with the power management software was probably affecting your network card and causing the BSOD's. The updating of the power management software probably fixed this issue without updating the particular driver that was mentioned (it updated some other file that wasn't listed in the memory dump).

A memory dump is a "snapshot" of the system's state at a particular point in time.

For example: If your power management software placed information in an improper location in memory (that belongs to the networking software) and then exited - there'd be no evidence of this instruction in the stack text. Then later, when the network card went to look at that address, it'd crash because the data it expected to find wasn't there (was corrupted).

This memory dump blames Windows files.


I'd first suggest updating these older drivers:

Code:

MarvinBus64.sys Fri Sep 23 17:17:03 2005
mdmxsdk.sys  Mon Jun 19 17:27:26 2006
Tppwr64v.sys Wed Oct 18 04:40:21 2006
pnetmdm64.sys Wed Mar 07 13:13:19 2007
VMNET.SYS    Thu May 22 06:33:54 2008
vmnetbridge.sys Thu May 22 06:34:05 2008
psadd.sys    Thu Aug 14 04:55:22 2008
smiifx64.sys Mon May 12 05:01:13 2008
e1y60x64.sys Fri Aug 22 18:09:50 2008
vstor2-ws60.sys Mon Dec 01 14:26:32 2008

I would suggest running Driver Verifier on all 3rd party drivers. To do this, please stop any running instances of Driver Verifier. To do this go to an elevated (Run as administrator) Command Prompt and type in "verifier /reset" (without the quotes) and press Enter - then reboot the system.

Then follow these directions to run Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users