Repeated BSOD's - about once a day

mochaultimate · Jul 5, 2012

Hi,

I need help with debugging the BSOD's I've started to receive on my system for the past 2 weeks. They have been on the following dates:

24th June, 1st July, 4th July, and 5th July (today) and thus have started to come with increasing regularity.

The OS on my system is the preloaded Windows 7 from Lenovo, which I started using on the 11th of June.

Here are my system specifications:

· OS - Vista/ Windows 7 ? - Windows 7
· x86 (32-bit) or x64 ? - x64
· What was original installed OS on system? Windows 7 Professional x64 (this is the original preload)
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM version
· Age of system (hardware) - less than a month
· Age of OS installation - have you re-installed the OS? - no I have not reinstalled the OS, this is the OEM preload

· CPU - Core i7-2760M
· Video Card - Nvidia Quadro 1000m
· MotherBoard - Lenovo W520
· Power Supply - brand & wattage - this is a laptop

· System Manufacturer - Lenovo
· Exact model number (if laptop, check label on bottom) - Lenovo W520 42763KU

View attachment bsod.rar

I've attached the perfmon report, and the 'Windows7_Vista_jcgriff2' report as instructed in the stickied post.

Please help!

usasma · Jul 5, 2012

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): http://crystalmark.info/?lang=en
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - http://www.techsupportforum.com/forums/f299/cant-find-the-cause-of-bsod-f4-613075.html#post3537179
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

All errors are STOP 0xD1, but each blames a different cause. More about this later (I'll suggest running Driver Verifier if the BSOD's continue after updating the stuff that I saw.)

Modem drivers date from 2006 and later, please update to the latest available version.

Fingerprint driver dates from 2009, please update to the latest available verision.

Then, if this doesn't fix things, I'd suggest running Driver Verifier according to these instructions: http://www.carrona.org/verifier.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
5U877.sys       Fri Mar 04 04:18:41 2011 (4D70AE71)
CAXHWAZL.sys    Tue Jun 30 16:01:14 2009 (4A4A6F0A)
CAX_CNXT.sys    Tue Jun 30 15:59:52 2009 (4A4A6EB8)
CAX_DPV.sys     Tue Jun 30 16:05:11 2009 (4A4A6FF7)
CHDRT64.sys     Mon Oct 03 15:46:36 2011 (4E8A111C)
DzHDD64.sys     Mon Oct 24 06:10:13 2011 (4EA53985)
DzHDD64.sys     Thu Oct 14 20:32:33 2010 (4CB7A121)
ElbyCDIO.sys    Thu Dec 16 17:58:13 2010 (4D0A9985)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
MpFilter.sys    Fri Mar 09 06:05:26 2012 (4F59E3F6)
NETwNs64.sys    Mon Oct 31 18:57:43 2011 (4EAF27E7)
NETwNs64.sys    Wed Aug 03 20:28:26 2011 (4E39E7AA)
NisDrvWFP.sys   Fri Mar 09 06:05:35 2012 (4F59E3FF)
PHCORE64.SYS    Fri Jul 08 02:02:21 2011 (4E169D6D)
SynTP.sys       Thu Apr 05 22:13:02 2012 (4F7E512E)
SynTP.sys       Thu May 19 23:02:08 2011 (4DD5D9B0)
Tppwr64v.sys    Mon Nov 28 23:08:06 2011 (4ED45AA6)
Tppwr64v.sys    Thu Nov 18 22:36:29 2010 (4CE5F0BD)
Tvti2c.sys      Sun May 29 21:36:58 2011 (4DE2F4BA)
VClone.sys      Sat Jan 15 11:21:04 2011 (4D31C970)
XAudio64.sys    Wed Apr 29 14:21:07 2009 (49F89A93)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dump_iaStor.sys Sat Nov 06 03:44:52 2010 (4CD50774)
dump_iaStor.sys Wed May 30 16:40:40 2012 (4FC685C8)
e1c62x64.sys    Tue Dec 21 04:30:56 2010 (4D1073D0)
e1c62x64.sys    Wed Jan 11 15:30:54 2012 (4F0DF17E)
iaStor.sys      Sat Nov 06 03:44:52 2010 (4CD50774)
iaStor.sys      Wed May 30 16:40:40 2012 (4FC685C8)
ibmpmdrv.sys    Fri Nov 12 04:41:49 2010 (4CDD0BDD)
ibmpmdrv.sys    Wed Feb 29 01:01:34 2012 (4F4DBF3E)
igdkmd64.sys    Mon Sep 26 05:40:22 2011 (4E804886)
mdmxsdk.sys     Mon Jun 19 17:27:26 2006 (449716BE)
nusb3hub.sys    Thu Dec 09 23:50:35 2010 (4D01B19B)
nusb3xhc.sys    Thu Dec 09 23:50:35 2010 (4D01B19B)
nvBridge.kmd    Wed May 25 18:37:29 2011 (4DDD84A9)
nvlddmkm.sys    Sun Mar 04 14:39:24 2012 (4F53C4EC)
nvpciflt.sys    Sun Mar 04 14:40:11 2012 (4F53C51B)
psadd.sys       Mon Dec 26 20:09:28 2011 (4EF91AC8)
psadd.sys       Tue Jul 26 02:56:31 2011 (4E2E651F)
risdxc64.sys    Wed May 25 04:23:28 2011 (4DDCBC80)
smihlp.sys      Fri Mar 13 08:47:32 2009 (49BA55E4)
smihlp.sys      Mon May 30 12:21:37 2011 (4DE3C411)
smiifx64.sys    Tue Sep 07 00:38:27 2010 (4C85C1C3)
snapman.sys     Wed Mar 09 08:22:38 2011 (4D777F1E)
tap0901.sys     Thu Aug 19 18:07:59 2010 (4C6DAB3F)
timntr.sys      Thu Jul 29 13:29:24 2010 (4C51BA74)
tpm.sys         Mon Jul 13 19:21:48 2009 (4A5BC18C)
vididr.sys      Tue Apr 12 07:31:24 2011 (4DA4380C)
vsflt53.sys     Tue Apr 12 07:31:35 2011 (4DA43817)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062412-8236-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jun 24 05:08:22.434 2012 (UTC - 4:00)
System Uptime: 1 days 16:53:58.127
BugCheck D1, {4c, 2, 0, fffff88004adbb28}
Probably caused by : usbehci.sys ( usbehci!EHCI_MapAsyncTransferToTd+284 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  ASProxy.exe
FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_MapAsyncTransferToTd+284
Bugcheck code 000000D1
Arguments 00000000`0000004c 00000000`00000002 00000000`00000000 fffff880`04adbb28
BiosVersion = 8BET55WW (1.35 )
BiosReleaseDate = 12/06/2011
SystemManufacturer = LENOVO
SystemProductName = 42763KU
CPUID:        "Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\070112-7113-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 30 16:38:41.494 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:04.446
BugCheck D1, {41, a, 1, fffff88004575699}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessIsrCompletedPacket+219 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessIsrCompletedPacket+219
Bugcheck code 000000D1
Arguments 00000000`00000041 00000000`0000000a 00000000`00000001 fffff880`04575699
BiosVersion = 8BET55WW (1.35 )
BiosReleaseDate = 12/06/2011
SystemManufacturer = LENOVO
SystemProductName = 42763KU
CPUID:        "Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\070412-8736-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul  4 02:41:37.102 2012 (UTC - 4:00)
System Uptime: 0 days 5:18:10.039
BugCheck D1, {f, 9, 0, fffff88005e42318}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+20e318 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0xD1_igdkmd64+20e318
Bugcheck code 000000D1
Arguments 00000000`0000000f 00000000`00000009 00000000`00000000 fffff880`05e42318
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\070512-8985-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul  5 05:42:33.692 2012 (UTC - 4:00)
System Uptime: 0 days 22:22:58.629
BugCheck D1, {ffffffffffffff89, 2, 0, fffff880054086b8}
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+54 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0xD1_nwifi!Pt6RepackRecvNBL+54
Bugcheck code 000000D1
Arguments ffffffff`ffffff89 00000000`00000002 00000000`00000000 fffff880`054086b8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

usasma · Jul 5, 2012

NOTE: Both Intel and nVidia graphics drivers are listed in the memory dumps.
I don't trust these new-fangled video contraptions - and we've had a few issues with them in the past (particularly with VIRTU software).
I'd suggest ensuring that you have the latest video drivers from Intel and nVidia - along with the latest switching software (something similar to VIRTU I'd presume).

mochaultimate · Jul 5, 2012

Hello usasma,

Thank you for the prompt and detailed response.

On your advice I've done the following:

1) Update fingerprint software with latest version from Lenovo;
2) Update modem drivers with latest version from Lenovo;
3) Disabled Nvidia Optimus (their automatic switchable graphics solution) and running exclusively on the dedicated graphics card.

I went about 2 weeks without a BSOD on the system, and my previous laptop (a T420) had an SSD without any bluescreen issues. Going back to a platter drive isn't something I'm willing to do yet at this point.

In addition, I've also removed the extra memory modules (the system came with 1; I added another 2) leaving 4Gb in the laptop.

Is there any way I can test this setup's stability? The BSOD's do come a minimum of a day apart, and running for a few hours with no problems really doesn't tell me anything at this point.

If there are any further steps I need to take I'd appreciate any guidance as well - thanks again in advance.

Vir Gnarus · Jul 5, 2012

If you haven't already, you will still need to update the SSD's firmware. Don't assume that because an SSD worked on one computer that it'll work on another, or that because one SSD works all SSDs will be fine. There's always potential for SSD failure early in its life, and there's also the problem of incompatibility and bug issues involved in an SSD's firmware, which is quite frequent. Updating the SSD firmware has resolved issues with a lot of people owning SSD drives, so it'd be wise to do so at earliest convenience.

Follow the rest of the instructions usasma gave, especially those involving Driver Verifier, for improved data collection.

mochaultimate · Jul 5, 2012

Hello Vir,

Thanks for the response. I'm using an Intel 520 SSD, which I believe only comes with 1 version of firmware (the release version).

I'm looking into Driver Verifier right now, but am getting cold feet from reports of others not being able to boot into their systems after running it. My data is mission-critical and I don't want to run any risks of losing it. I'll post back later with any further findings.

Your help is very much appreciated.

Vir Gnarus · Jul 5, 2012

If DV finds a bad driver at startup, it'll BSOD the system, causing a boot loop. You can simply enter Safe Mode through F8 and then turn DV off from there. Make sure when you set up DV to only select 3rd-party drivers, and do not select Force Pending I/O Requests, IRP Logging or Low Resource Sim checks, as they'll cause false positives. All other checks will do.

mochaultimate · Jul 5, 2012

Hello (posting from another PC atm),

I ran Driver Verifier using the instructions posted on Carrona's website. The system now hangs DURING the Windows 7 logo at the start, with a blue screen that's too quick for me to see what the stated issue is.

Pressing F8 doesn't give me an option for Safe Mode - just Startup Repair, and Start Windows normally (which leads to the boot loop as you mentioned).

I don't have a Windows DVD, only a USB drive, and when I boot off it, it doesn't seem to see my Windows install.

Please guide me on what further step to take - thank you.

mochaultimate · Jul 5, 2012

Hi,

I'm probably at this step atm:

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 to stop Driver Verifier from loading (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

However, I can't seem to boot into Windows - how would I edit the registry to allow me to boot into the system?

Thank you in advance.

usasma · Jul 5, 2012

The Driver Verifier instructions include the necessary steps to recover from a BSOD that results in the system becoming non-bootable:

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).

I'm also adding System Repair Disc instructions and "Disable Automatic restart on System Failure" instructions to the Verifier webpage for additional assurances.

We fix these kind of BSOD's in one of several ways:
- Safe Mode (you can turn off Driver Verifier there)
- Repair Discs (Start...All Programs...Maintenenance...Create a System Repair Disc) - using System Restore
- Repair Discs - using Startup Repair
- remote mounting of the registry hives and editing them

Additionally, depending on the cause, we can also start/stop the loading of some drivers through the Repair Disc or remote mounting of the Registry.

Then the only requirements are:
1) that you make a System Repair disc if you don't have a full installation DVD
2) that you make a System Restore point before starting.
3) that you have access to another computer so you can get back in touch with us should that happen.

mochaultimate · Jul 5, 2012

Hi usasma,

Yes, I did make a System Restore point before I ran Driver Verifier.

I'll look into creating a Repair Disc on this other PC I have here (also ensured I had another running PC available before I ran DV).

I'm missing (1) out of the 3 requisites and am working on fixing that (good thing this PC runs Win 7 as well). I'll post back on any developments, meantime the PC in question refuses to boot and looks like a dead end there. Booting from my USB Win 7 drive allows me to see my hard drives, but doesn't seem to allow me to do anything with them.

Vir Gnarus · Jul 5, 2012

You may not be pressing F8 early enough. If you're doing it when the Windows logo has popped up, it's too late. It's best to just continuously tap it in rapid succession during boot-up to get to the bootup menu. It's more difficult to reach that sweet spot when it'll trigger the menu on an SSD than an HD because of SSDs loading faster.

mochaultimate · Jul 5, 2012

Vir Gnarus,

You're a genius. That just worked, I'll go back to my main PC and upload the bluescreen dumps.

I can't thank you guys enough.

usasma · Jul 5, 2012

Just FYI - if you have issues with System Repair discs, I can assist (I have ISO's :0)

mochaultimate · Jul 5, 2012

Hi all,

I'm now able to boot back into my main PC. Unfortunately it appears that no dumps were generated, and the only information I gleaned from Driver Verifier is that the crash occured almost immediately; during the Windows logo swirling animation.

Please let me know what the next step is, thanks!

to usasma: I'm good on the System Repair disc I think - it IS the same across all versions of Win7, correct? My entertainment PC runs Home Premium while my work laptop runs Professional.

mochaultimate · Jul 5, 2012

I'm a little stumped, and since I don't have Bionic eyes, I'm going to take a video of the bluescreen process and hope to catch the offending driver name on-screen.

I'll post back later with my findings.

usasma · Jul 5, 2012

The only difference is between 32 and 64 bit versions.

Do the Driver Verifier thing again and see if you can get this info:
When booting, get to the Safe Mode menu and scroll down to "Disable automatic restart on system failure" - select it by pressing Enter
Then, when the system BSOD's it'll stop at this screen (Get the info in RED):

That may help us to ID the issue further. Right now we're pretty certain that this is either a system-start or a boot-start driver, and that it's a 3rd party driver (not a driver from the Windows operating system). It should be fairly easy to pin it down despite the missing memory dump(s).

BTW - check the date/time stamp on this file: C:\Windows\MEMORY.dmp
If it's around the time of the last Driver Verifier crash, then that's most likely it.

Vir Gnarus · Jul 5, 2012

What you can do is set it up so it doesn't restart at BSOD. Type "view advanced system settings" in Start Menu, then click Settings button under Startup and Recovery, and uncheck "Automatically restart". You may need to set "Small memory dump" if it already isn't set to such. You can also give us a JCGriff Report, as it should at least produce an event in the syslog of the occurrence if the crashdump did not produce.

Usasma's method works too.

mochaultimate · Jul 5, 2012

Hello all,

I've managed to get a clear look at the BSOD (took videos with my iPhone the wonders of technology!) and here are the pertinent parts as usasma requested:

Technical information:

***STOP: 0x000000D1 (with a bunch of other numbers behind)

*** iastor.sys - Address (long list of other numbers behind as well)

The main error is DRIVER_IRQL_NOT_LESS_OR_EQUAL

I'm not sure if the rest of the BSOD is relevant so I've uploaded a screenshot below. I repeated the bluescreen twice so I'm fairly confident it's consistent.

Please let me know what's next.

Vir Gnarus · Jul 5, 2012

It pointed at your iaStor driver, which would explain why crashdumps wouldn't be generated (iaStor is your Intel storage driver). The bugcheck itself is generic, but it also does show that either Driver Verifier wasn't on at the time, or this was a crash not triggered by DV. If you can assure us that DV was on, then we are certainly dealing with a faulting drive.

Given that this system is so young and it's an OEM, it's best you put your fresh warranty to use. If you wish, you may still try and install any update for your BIOS and your storage drivers (it may be called Intel Matrix Storage), but I don't believe they're at fault here. It's not unusual to get a laptop from an OEM that craps out on ya early, so run through the procedure on getting a free replacement/repair by Lenovo.

Repeated BSOD's - about once a day

Member

Retired Admin

Retired Admin

Member

BSOD Kernel Dump Expert

Member

BSOD Kernel Dump Expert

Member

Member

Retired Admin

Member

BSOD Kernel Dump Expert

Member

Retired Admin

Member

Member

Retired Admin

BSOD Kernel Dump Expert

Member

Attachments

BSOD Kernel Dump Expert