BSOD again!

[rosahas]

My last one was on March 30th and then things seemed to be working. Most of my BSODs were if I left my machine running overnight. I haven't had a need to do that since March 30th.

But, today, I had back to back BSODs while just normal use.. just browsing!

I have downloaded WinDbg and tried to download all the Symbol files. I was able to read most of my dumps until I started getting this error message:
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Now, I can't tell what's causing the problems when I try to read my dmp files.

Can someone please tell me what my problem might be and how I could resolve this error in WinDbg around Symbols? I have tried to download the sybmbols from the Microsoft server as well, with no luck of fixing this error above.

Thanks,

RoSahas.

 

[usasma]

There was an issue with the Microsoft Symbol Server recently where this error message would be given even though the ntoskrnl.exe file was valid. This has been reported to Microsoft and may have already been fixed.

In the case of the memory dumps that you uploaded here - the symbols are being read correctly on my system. So, if you're still experiencing symbol errors - it's likely that the symbol path on your system isn't correct. Please use this for the symbol path on your system:

[B][COLOR=#000000][FONT=Times New Roman][LEFT][COLOR=#333333][FONT=georgia][B]SRV*c:\symbols*http://msdl.microsoft.com/download/symbols[/B][/FONT][/COLOR][/LEFT][/FONT][/COLOR][/B]

That being said, the memory dumps that you've uploaded don't contain a lot of useful information. So let's try this:

Please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find 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: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

ext2fs.sys   Thu Sep 25 11:38:43 2008 - Ext2fs File System Driver - http://www.carrona.org/dvrref.html#ext2fs.sys
ifsmount.sys Thu Aug 28 16:48:59 2008 - Ext2fs File System Driver - http://www.carrona.org/dvrref.html#ifsmount.sys
mdmxsdk.sys  Mon Jun 19 17:27:26 2006 - Diagnostic Interface x86 Driver by Conexant (www.conexant.com) (most   likely a modem) - http://www.carrona.org/dvrref.html#mdmxsdk.sys
psadd.sys    Mon Feb 19 13:56:37 2007 - Lenovo Parties Service Access  Device Driver (SMBIOS) - http://www.carrona.org/dvrref.html#psadd.sys
SI3132.sys   Wed Oct 03 14:39:29 2007 -    Silicon Image (SiS) driver - http://www.carrona.org/dvrref.html#SI3132.sys
SiRemFil.sys Wed Jun 20 15:42:10 2007 -    Silicon Image (SiS) driver  - http://www.carrona.org/dvrref.html#SiRemFil.sys
SiWinAcc.sys Thu Jun 14 20:02:02 2007 - Silicon Image (SiS) driver - http://www.carrona.org/dvrref.html#SiWinAcc.sys
smiifx64.sys Mon May 12 05:01:13 2008 - SMI Driver for Lenovo system - http://www.carrona.org/dvrref.html#smiifx64.sys

Then, if the BSOD's still don't stop, 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"
- 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

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Apr 10 16:07:04.343 2010 (GMT-4)
System Uptime: 0 days 3:29:11.495
BugCheck D1, {22, 2, 8, 22}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Apr 10 12:36:43.973 2010 (GMT-4)
System Uptime: 1 days 2:47:21.250
BugCheck D1, {0, 8, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar 30 02:51:53.598 2010 (GMT-4)
System Uptime: 0 days 3:39:19.392
BugCheck 7F, {8, 80050031, 6f8, 610f121f}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  SmcGui.exe

 

[rosahas]

Thanks for those pointers. I am going through those tips now.

Don't think that Symbols error has been fixed yet, I still get it even after getting the latest files from the server.

 

[usasma]

I didn't get symbol errors when running your files - so I suspect that there's an issue with your settings for the Symbol Server. Please follow the directions in Step E at this link: WinDbg Analysis Report

 

[rosahas]

Symbols are fixed now, I just uninsulated all the Symbols I had from Microsoft site. Then added the path to retrieve them from the website. It seems to work now.

I was wondering, how did you retrieve the list of those drivers from the minidumps? I am trying to figure out if I should just disable those drivers and see what happens. It's consistently going BSOD. These are not newly installed. The only thing I can think of is that I enabled Hardware level virtualization to use the Windows XP mode as per instructions. I might disable that and see if the BSODs stop.

 

[usasma]

Open up the memory dump file in the debugger.
Then, at the very bottom of the window there will be a small rectangular area the width of the window.

Type the following in there and then press Enter:

lmtsmn

That will list the drivers in alphabetical order.