SSD's have been problematic recently. We've seen numerous BSOD's due to them. Here's the info that I have 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!!!)
- 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
If you are overclocking, please stop while we're troubleshooting.
Only running the memory dumps from 2012 (9 of them).
perfmon reports a problem with your nVidia program. Please do the following:
- download a fresh copy of the latest Win7 x64 drivers from the nVidia site here:
Graphics Driver - GeForce 285.62 Driver - GeForce
- uninstall the nVidia stuff from your system
- install the freshly downloaded drivers
- monitor for further BSOD's
Many device drivers aren't installed on your system. Please visit the Asus support site for your mobo (
ASUSTeK Computer Inc. - Motherboards- ASUS P8Z68-V PRO ), enter your OS info (Windows 7 64bit) and download/install
ALL drivers/programs for your system.
SM Bus Controller PCI\VEN_8086&DEV_1C22&SUBSYS_844D1043&REV_05\3&11583659&0&FB The drivers for this device are not installed.
Universal Serial Bus (USB) Controller PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&108ABD8A&0&00E4 The drivers for this device are not installed.
Universal Serial Bus (USB) Controller PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&DDEC341&0&00E1 The drivers for this device are not installed.
PCI Simple Communications Controller PCI\VEN_8086&DEV_1C3A&SUBSYS_844D1043&REV_04\3&11583659&0&B0 The drivers for this device are not installed.
Not Available USB\VID_0CF3&PID_3000\6&DF2EE03&0&7 The drivers for this device are not installed.
This is most likely an Atheros AR3011 Bluetooth device
Ethernet Controller PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05\3&11583659&0&C8 The drivers for this device are not installed.
You do not have SP1 installed, please do this also:
Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update
ALL drivers.
DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1:
Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates
Haven't seen any issues with these in a long time - but the M-Audio USB devices were causing BSOD's a while back. Please ensure that your drivers are updated to the latest available, Win7 compatible version.
9 memory dumps since 05 Jan 2012
4 different BSOD error codes
7 different causes blamed
This is (IMO) most likely:
- a hardware problem
- a compatibility issue
- a low-level driver problem
- or malware
Your wacommousefilter.sys driver dates from 2007. Please either update the driver to a more recent, Win7 compatible version - or UNINSTALL the program from your system while we're testing.
Your CPU speeds are varying. Are you doing this (overclocking)? Or is there a program on your system (in the BIOS and/or in Windows) that's fiddling with your clock speeds(like an Automatic Turbo Mode)? If the latter is the case, please disable these programs as some of them have been known to cause BSOD issues.
If none of the above things stop the BSOD's, then please start out with
ALL of the free hardware diagnostics on this page:
Hardware Diags
Let us know the results and we'll move on from there.
BSOD BUGCHECK SUMMARY
Code:
[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011512-17019-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan 15 22:26:22.047 2012 (UTC - 5:00)
System Uptime: 0 days 0:07:23.031
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR: 0x19_3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`0667c290 fffffa80`0667c290 00fffa80`0667c290
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3300
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011512-20092-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan 15 22:17:43.117 2012 (UTC - 5:00)
System Uptime: 0 days 0:54:13.475
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+15d )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: dwm.exe
BUGCHECK_STR: 0x7E
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_PROCESS_HEAP::MapViewOfAllocation+15d
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`030e69e0 fffff880`058c4138 fffff880`058c39a0
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011512-19500-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sun Jan 15 18:55:05.450 2012 (UTC - 5:00)
System Uptime: 0 days 1:16:24.403
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectSafe+c )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!ObReferenceObjectSafe+c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030a31ec fffff880`06df8cb0 00000000`00000000
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011512-15693-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Jan 14 23:35:33.808 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:59.776
Probably caused by : hardware ( dxgmms1!VidSchiSubmitRenderCommand+5b9 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`041ef9d5 fffff880`05865868 fffff880`058650d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-19531-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Jan 14 23:25:42.408 2012 (UTC - 5:00)
System Uptime: 0 days 2:31:30.750
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck D1, {478, 2, 0, fffff88001853748}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
Bugcheck code 000000D1
Arguments 00000000`00000478 00000000`00000002 00000000`00000000 fffff880`01853748
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-16192-02.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Jan 14 17:00:43.579 2012 (UTC - 5:00)
System Uptime: 0 days 0:02:02.921
Probably caused by : nvlddmkm.sys ( nvlddmkm+128287 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+128287
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`1000c287 fffff880`0cef09d0 00000000`00000000
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-16192-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Jan 14 16:57:52.151 2012 (UTC - 5:00)
System Uptime: 0 days 0:04:04.103
Probably caused by : ntkrnlmp.exe ( nt!ExIsResourceAcquiredSharedLite+4 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!ExIsResourceAcquiredSharedLite+4
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0309ad24 fffff880`0929cde0 00000000`00000000
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3399
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-18220-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan 6 00:32:31.658 2012 (UTC - 5:00)
System Uptime: 0 days 3:10:01.001
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( Unknown_Module_fffffa80`07643950>+19cb240 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`033c3a3c fffff880`0af240e0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-22183-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jan 5 21:21:27.723 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:17.066
Probably caused by : fileinfo.sys ( fileinfo!FIStreamQueryWorker+9e )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
FAILURE_BUCKET_ID: X64_0x7E_fileinfo!FIStreamQueryWorker+9e
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`0304d357 fffff880`0379b248 fffff880`0379aab0
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]