+/- monthly BSOD & boottime BSOD with verifier on

michielm · 02 Jun 2012

Hi all,
Over the past months I have encountered a BSOD roughly every month and I want to get rid of it. The BSOD happens at random (at least as far as I know), not with specific tasks.

This morning I started looking for the error and found that turning verifier ON might help in identification. I did this and rebooted a couple of times, every time with the same BSOD occuring during the boot stating something about dne64x.sys

I've turned verifier OFF again (otherwise I wouldn't be typing this).

I have attached all the data to my post. Could someone have a look and, hopefully, tell me what is wrong and how to fix it?!

Thanks!

Michiel

System specs:
--
Windows 7 Professional x64 full retail version
+/- 8 months old system, OS age is the same

usasma · 02 Jun 2012

The purpose of Driver Verifier is to generate BSOD's - but it's only useful as a troubleshooting tool when looking for solutions to specific issues (issues that the tool checks for). Please leave it off unless we suggest that you run it in a specific way.

perfmon /report shows your Cisco VPN adapter as being disabled. Please reenable it and uninstall it. Should you want to keep this device, feel free to reinstall it after the system is made stable again. Additionally, since Driver Verifier blames it (the dne64x.sys driver) - and it dates from 2008, it's most likely the cause of your problems.

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): Crystal Dew World
- 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 - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
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.

You have a 100 mHz overclock on your system. Please remove this and revert the system back to stock values while we're troubleshooting. Feel free to resume the oveclock once the system is stable again.

MSINFO32 shows a hardware problem with one of your disks back in September of 2011 - was this a different disk, or do you still have the same hard drive (this can be the SSD or any other hard drive attached to your system). In the event that the disk is still attached, please run the hard drive diagnostics suggested here: Hard Drive Diagnostic Procedure

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:


LMouFilt.Sys  Fri Sep 02 02:23:15 2011 (4E607653)
LHidFilt.Sys  Fri Sep 02 02:23:09 2011 (4E60764D)
mvs91xx.sys   Thu Jun 16 05:54:52 2011 (4DF9D2EC)
iaStor.sys    Tue Nov 29 22:39:19 2011 (4ED5A567)
mvxxmm.sys    Thu Jun 16 05:54:34 2011 (4DF9D2DA)
amdxata.sys   Fri Mar 19 12:18:18 2010 (4BA3A3CA)
LUsbFilt.Sys  Fri Sep 02 02:23:19 2011 (4E607657)
avkmgr.sys    Thu Sep 15 09:36:11 2011 (4E71FF4B)
avipbb.sys    Thu Apr 26 06:12:40 2012 (4F991F98)
AsUpIO.sys    Mon Aug 02 22:47:59 2010 (4C57835F)
AsIO.sys      Mon Aug 23 21:53:02 2010 (4C7325FE)
HECIx64.sys   Tue Oct 19 19:33:43 2010 (4CBE2AD7)
rtl8192Ce.sys Thu Oct 06 03:47:16 2011 (4E8D5D04)
Rt64win7.sys  Thu Feb 16 00:39:50 2012 (4F3C96A6)
asmtxhci.sys  Wed Jun 01 22:27:46 2011 (4DE6F522)
dne64x.sys    Mon Nov 10 20:01:24 2008 (4918D964)
nvhda64v.sys  Wed Apr 18 13:07:54 2012 (4F8EF4EA)
asmthub3.sys  Wed Jun 01 22:27:58 2011 (4DE6F52E)
RtsUStor.sys  Wed Oct 27 04:25:40 2010 (4CC7E204)
avgntflt.sys  Tue Apr 24 02:14:35 2012 (4F9644CB)
nvlddmkm.sys  Tue May 15 03:35:36 2012 (4FB20748)
nvBridge.kmd  Fri May 20 23:58:23 2011 (4DD7385F)
CVPNDRVA.sys  Tue Mar 23 15:16:37 2010 (4BA91395)
avipbb.sys    Wed Jan 18 08:21:12 2012 (4F16C748)
avgntflt.sys  Thu Sep 15 10:23:26 2011 (4E720A5E)
nvhda64v.sys  Tue Jan 17 07:45:46 2012 (4F156D7A)
nvlddmkm.sys  Wed Feb 29 13:04:52 2012 (4F4E68C4)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060212-9032-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun  2 03:30:35.028 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:12.871
*** WARNING: Unable to verify timestamp for dne64x.sys
*** ERROR: Module load completed but symbols could not be loaded for dne64x.sys
Probably caused by : dne64x.sys ( dne64x+ff50 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_dne64x+ff50
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`00000094 fffffa80`0b06cb30 fffff880`05d6cf50
BiosVersion = 1104
BiosReleaseDate = 10/27/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060212-7768-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun  2 03:18:43.701 2012 (UTC - 4:00)
System Uptime: 0 days 0:58:59.529
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+464cd )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+464cd
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0000405c 00004055`000080aa
BiosVersion = 1104
BiosReleaseDate = 10/27/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051312-8517-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 13 15:01:18.808 2012 (UTC - 4:00)
System Uptime: 0 days 2:37:27.637
Probably caused by : win32k.sys ( win32k!LFONTOBJ::ppfeMapFont+137 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  MATLAB.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!LFONTOBJ::ppfeMapFont+137
Bugcheck code 00000050
Arguments fffff900`c3d8c020 00000000`00000000 fffff960`0013a3db 00000000`00000000
BiosVersion = 1104
BiosReleaseDate = 10/27/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

michielm · 03 Jun 2012

Dear usasma,
Thanks for the extensive feedback!
I have re-enabed and uninstalled the vpn adapter (and client) and dialed back my CPU speed. The dne64x.sys file is still there in the system32/drivers folder, should I remove it or can I just leave it there?

The harddisk from september 2011 is still there, but at the time Windows was installed on it and at the moment I have Windows installed on my SSD and the harddisk is only for extra storage capacity. I will run a diagnostics on it today.

Since my operating system is installed on the SSD I cannot easily test whether it is causing problems. So I'll leave this for now and first check the other potential sources.

Is there any way I can test now whether the vpn adapter was indeed the issue? Or should I just wait for my next BSOD (which might take another month)

usasma · 03 Jun 2012

Leave the driver for now - we don't know if it's an incompatibility, a corruption, or merely a symptom of another problem. If it pops up again in the errors we'll take a closer look at it.

As for the Hard Drive - check all of the hard drives (with the exception of the SSD). If one has issues it can affect the rest of the system.

The test for a BSOD is waiting. In general I use this criteria:
- if the BSOD doesn't come back in a week, it's probably fixed.
- if it doesn't come back in 2 weeks, it's most likely fixed.
- if it doesn't come back in a month, it's fixed.
But this depends on the type of error and the frequency of crashes that you've experienced.
If you post back with a month gap between BSOD's, I'll only run those that happened after the month gap.
It's an arbitrary criteria that I use, but it seems to suit the conditions that we see.

michielm · 05 Jun 2012

I ran the Extended test on my HDD and it passed so that seems to be okay.

I'll post back if I run into any new BSODs. Thanks again for the extensive help!