Windows 7 BSOD keeps on coming

[oyb]

Hey,

Built a new computer about a year ago, and quickly found out that something was wrong with the new HDD I had installed, so I returned it to manufacurer and the BSODs stopped.

But then in January(meaning you might wanna disregard the previous dump files), the BSods started up again. Can't think of any new software that should cause the problem.

Can anyone help me out?
Link Removed

 

[usasma]

I just ran the 4 memory dumps from February.

Only 109 Windows Updates installed. Most systems have at 130/140 or even more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

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.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

This device is having problems:

SBRE ROOT\LEGACY_SBRE\0000 This device is not present, is not working properly, or does not have all its drivers installed.

This likely belongs to a Viper antivirus program. Check for it in Device Manager (maybe in Hidden devices?) and right click on it to uninstall it.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I strongly suspect that this hold true for Win8 systems also.

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's on some Windows systems. Please uninstall it immediately.

Also, if overclocking, please stop while we are troubleshooting. Feel free to resume the overclock once the system has been stabilized.

All memory dumps seem to point at your Marvell storage controller on the motherboard (note the comments above related to NOT using this with an SSD). Please:
- download a fresh copy of the latest Win7 compatible drivers
- uninstall the current drivers
- install the freshly downloaded drivers
- monitor for further BSOD's

HotSpot Shield is known to cause BSOD's on some Win7 systems. Please uninstall it immediately.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

LHidFilt.Sys Wed Jun 17 12:49:39 2009 (4A391EA3)
Logitech SetPoint HID Filter Driver
Link Removed

LMouFilt.Sys Wed Jun 17 12:49:43 2009 (4A391EA7)
Logitech SetPoint HID Filter Driver
Link Removed

LEqdUsb.Sys Wed Jun 17 12:49:54 2009 (4A391EB2)
Logitech SetPoint Unifying KMDF USB Filter
Link Removed

LHidEqd.Sys Wed Jun 17 12:49:56 2009 (4A391EB4)
Logitech SetPoint Unifying KMDF HID Filter
Link Removed




Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Wed Feb  6 12:36:44.064 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020613-9110-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:01:51.923[/B]
Probably caused by :[B]mv91xx.sys ( mv91xx+3178e )[/B]
BugCheck [B]3D, {fffff8800ccc2fa0, 0, 0, fffff8800111978e}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff8800ccc2fa0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800111978e
BUGCHECK_STR:  0x3D
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: [B]X64_0x3D_mv91xx+3178e[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3310[/B]
  BIOS Version                  3202
  BIOS Release Date             02/17/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb  6 12:34:02.083 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020613-8626-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 8:50:56.332[/B]
Probably caused by :[B]mv91xx.sys ( mv91xx+3178e )[/B]
BugCheck [B]3D, {fffff80000b9bf60, 0, 0, fffff8800144978e}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff80000b9bf60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800144978e
BUGCHECK_STR:  0x3D
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x3D_mv91xx+3178e[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3310[/B]
  BIOS Version                  3202
  BIOS Release Date             02/17/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  2 12:30:55.786 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-8377-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:01:00.035[/B]
Probably caused by :[B]mv91xx.sys ( mv91xx+3178e )[/B]
BugCheck [B]3D, {fffff80000b9bf60, 0, 0, fffff8800109078e}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff80000b9bf60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800109078e
BUGCHECK_STR:  0x3D
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x3D_mv91xx+3178e[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3310[/B]
  BIOS Version                  3202
  BIOS Release Date             02/17/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb  2 12:24:21.670 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-18174-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 6:46:23.919[/B]
Probably caused by :[B]mv91xx.sys ( mv91xx+3178e )[/B]
BugCheck [B]3D, {fffff80004c7bf60, 0, 0, fffff8800151978e}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff80004c7bf60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800151978e
BUGCHECK_STR:  0x3D
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x3D_mv91xx+3178e[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3310[/B]
  BIOS Version                  3202
  BIOS Release Date             02/17/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Wed Feb  6 12:36:44.064 2013 (UTC - 5:00)**************************
[COLOR=RED][B]LHidFilt.Sys                Wed Jun 17 12:49:39 2009 (4A391EA3)[/B][/COLOR]
[COLOR=RED][B]LMouFilt.Sys                Wed Jun 17 12:49:43 2009 (4A391EA7)[/B][/COLOR]
[COLOR=RED][B]LEqdUsb.Sys                 Wed Jun 17 12:49:54 2009 (4A391EB2)[/B][/COLOR]
[COLOR=RED][B]LHidEqd.Sys                 Wed Jun 17 12:49:56 2009 (4A391EB4)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]taphss.sys                  Tue Sep 15 15:58:23 2009 (4AAFF1DF)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
btath_rcp.sys               Thu Jun 24 02:17:21 2010 (4C22F871)
btath_flt.sys               Thu Jun 24 02:17:38 2010 (4C22F882)
btath_bus.sys               Thu Jun 24 02:17:43 2010 (4C22F887)
btath_hcrp.sys              Tue Jun 29 05:30:43 2010 (4C29BD43)
jraid.sys                   Tue Aug 10 05:28:44 2010 (4C611BCC)
mvxxmm.sys                  Fri Aug 27 05:49:03 2010 (4C778A0F)
mv91xx.sys                  Fri Aug 27 05:49:22 2010 (4C778A22)
psi_mf.sys                  Wed Sep  1 03:53:14 2010 (4C7E066A)
btath_lwflt.sys             Mon Sep 13 04:26:54 2010 (4C8DE04E)
e1c62x64.sys                Tue Sep 21 17:34:15 2010 (4C9924D7)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
RTKVHD64.sys                Tue Nov 23 05:14:08 2010 (4CEB93F0)
btath_a2dp.sys              Mon Feb 14 20:47:47 2011 (4D59DB43)
btfilter.sys                Tue Mar  8 01:15:22 2011 (4D75C97A)
iaStor.sys                  Fri May 20 12:52:24 2011 (4DD69C48)
asmtxhci.sys                Wed Sep 14 03:36:09 2011 (4E705969)
asmthub3.sys                Wed Sep 14 03:36:19 2011 (4E705973)
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
[COLOR=RED][B]hssdrv6.sys                 Mon May 14 19:06:22 2012 (4FB18FEE)[/B][/COLOR]
nvhda64v.sys                Mon May 21 09:10:39 2012 (4FBA3ECF)
nvlddmkm.sys                Thu Jun 28 18:58:00 2012 (4FECE178)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[oyb]

Thanks for the help, I'll give it a go with all the new drivers