Random reboot (BSOD) - tech support no help

I have Lenovo with about 2 weeks of warranty left. I religiously run all Windows and Lenovo updates, unless the drivers are not indicated to provide any changes to my model. This laptop occasionally re-boots itself, always away from home such as in a hotel or public place, regardless of battery or A/C power. It can happen while I read e-mail, use IE, or if it just sits idle. It happens with wireless and network connection - but never when connected to a single router in a home setting. I called Lenovo support and all they suggested was to update BIOS and a driver, which was already done. One problem I have is that I can not fond the error messages associated with this. When it starts again I get a "Windows has recovered from an unexpected shutdown" message. I have tried to note the location of helpful files, and I can find the minidump files. Unfortunately, I cannot open or use these. The other location "C:\Users\Merlin666\AppData\Local\Temp\xxxx.sysdata.xml" does not exist, i.e. there is no Temp folder in the Local area.

The computer is less than one year old, with no modification to OEM OS or other.


Is there anything that can be done to fix this?
Just noticed that some other have attached dump files, so here we go hope this helps.

I noticed that the perfmon file (included in the zip) indicated no antivirus - but I am running Zonelarm.
Thanks for your help.

Remove ZoneAlarm (the symptoms suggest that this may be an issue)
Then use this free tool to remove any remnants (direct download link): http://download.zonealarm.com/bin/fr...cpes_clean.exe
Then try and force a crash - maybe by using a local wifi hotspot?

More to follow.....

It is possible that the following older drivers may be causing your problems.
Please either REMOVE or Update the older drivers listed below.

HOW TO FIND DRIVERS:
DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

The most common drivers are located on this page: Driver Reference
If you can't find the driver, post back and we'll see what we can find.

Here's the older drivers that were found in the memory dump files:

Code:

Tppwr64v.sys Wed Oct 18 04:40:21 2006 (4535E875)
 - ThinkPad Pwr Mgmt Port
 - Driver Reference

StarPortLite.sys Wed Jan 16 06:08:05 2008 (478DE595)
 - StarPort Storage Controller iSCSI, FCoE (FibreChannel-over-Ethernet) and AoE (ATA-over-Ethernet) Initiator; DVD-ROM, RAM disk and encrypted virtual hard disk emulator byRocket Division Software 
 - Driver Reference

smiifx64.sys Mon May 12 05:01:13 2008 (48280759)
 - SMI Driver for Lenovo system
 - Driver Reference

pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
 - low level access layer for CD devices (A part of many different CD/DVD burning   programs)
 - Driver Reference

e1y60x64.sys Fri Aug 22 18:09:50 2008 (48AF392E)
 - Intel(R) 82567LM Gigabit Network Connection
 - Driver Reference

adfs.SYS     Mon Nov 03 11:48:14 2008 (490F2B4E)
 - Adobe File System Filter driver
 - Driver Reference

mdmxsdk.sys  Mon Jun 19 17:27:26 2006 (449716BE)
 - Conexant Modem Diagnostic Interface x86 Driver
 - Driver Reference

If this doesn't fix the issues, please run Driver Verifier according to these directions:

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 23:18:33.590 2010 (UTC - 5:00)
System Uptime: 0 days 0:11:14.711
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`02c51ec0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 19 23:06:33.961 2010 (UTC - 5:00)
System Uptime: 0 days 0:10:45.222
Probably caused by : ntkrnlmp.exe ( nt!KiIdleLoop+d2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`02e09c58 00000000`00000002 00000000`00000001 fffff800`02c89f62
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 06:22:45.991 2010 (UTC - 5:00)
System Uptime: 0 days 0:28:50.770
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`02c53ec0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 05:52:47.174 2010 (UTC - 5:00)
System Uptime: 0 days 0:38:30.953
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`02c38ec0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov  3 16:23:41.615 2010 (UTC - 5:00)
System Uptime: 0 days 21:21:41.394
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchDdiNotifyInterruptWorker+198 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff880`05d6c120
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 19:00:49.286 2010 (UTC - 5:00)
System Uptime: 0 days 22:30:46.065
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : atipmdag.sys ( atipmdag+29eaf3 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff880`04afbaf3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 22 16:55:26.520 2010 (UTC - 5:00)
System Uptime: 0 days 2:07:01.299
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`02c90ec0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

merlin666 said:

Thanks for the response. It seems I will have some work to do.
How do I interpret the bugcheck - is that the result from minidump?

Yes, the bugcheck is from the mini dump.

It seems there are two issues identified - atipmdag.sys which may be related to graphics drivers, and ntkrnlmp.exe wchich I have no idea what it may mean.

It could be a graphics card issue; it is just as possible that outdated drivers were conflicting and causing corruption. In other words, it may may not have been the video card causing the crash. ntkrnlmp.exe is the Windows system core and very unlikely to be the real cause. It just got blamed because the dump has to blame something.

Since the last crashI also have updated the BIOS, and I have no idea how to replicate the issue, maybe try to connect to one of the networks that are around.

I have about 2 weeks of warranty left and am not sure if these errors point to an issue that may be covered by warranty, or if I should purchase extension of warranty.

It is too soon to tell if there is an underlying hardware problem. Run your system for a few days and see how it does. This is assuming you have taken care of those obsolete drivers.

2 weeks left on the warranty?

Run these free hardware diagnostics. The first 2 are purely hardware tests - if they fail, it's a hardware problem. The others would require some interpretation. Prime95 primarily identifies hardware issues also - but it's not 100% certain.:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.