I keep getting BSODs when using this computer. Often it would crash right after logging into windows and this is fairly consistent. Othertimes, it would crash while using windows. I am using an SSD with a HDD as a mass storage.
x64 Professional Full Retail, nearly fresh installation
i5 2500k stock
2x4Gb DDR3
560 ti
My notes about SSD's:
Perfmon reports that the drivers for your Galaxy S2 aren't installed. I'd suggest uninstalling any software and removing the phone from your system while we're troubleshooting.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
- 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)
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to swtich 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
Perfmon also reports that the drivers for your USB controller aren't installed. Please update your chipset drivers (from the PC Manufacturer's website) in order to update the USB 1.1 and 2.0 controller. To update any USB 3.0 controllers you'll have to look at the PC Manufacturer's website to see if they're available.
You only have 51 updates installed after SP1. Most systems have 60-70 or more. Please visit Windows Update and get all available updates.
Please uninstall MSI Afterburner, it is known to cause BSOD's on Win7 systems (the same components are also in Riva Tuner and EVGA Precision). FYI - the driver dates from 2005 so this is most likely the source of your problems.
Please update your Creative audio drivers as some of them date from 2008.
BSOD BUGCHECK SUMMARY
Code:Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-7753-01.dmp] Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Debug session time: Sun Jan 8 03:15:38.408 2012 (UTC - 5:00) System Uptime: 0 days 0:02:17.282 Probably caused by : hardware BUGCHECK_STR: 0x124_GenuineIntel DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE Bugcheck code 00000124 Arguments 00000000`00000000 fffffa80`07e1d028 00000000`be000000 00000000`00800400 BiosVersion = V1.12B6 BiosReleaseDate = 07/13/2011 CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz" MaxSpeed: 3300 CurrentSpeed: 3306 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-6942-01.dmp] Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Debug session time: Sun Jan 8 03:00:27.576 2012 (UTC - 5:00) System Uptime: 0 days 0:00:18.825 Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+165 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x3B_nt!KiCommitThreadWait+165 Bugcheck code 0000003B Arguments 00000000`c000001d fffff800`030dfec5 fffff880`07d22c80 00000000`00000000 BiosVersion = V1.12B6 BiosReleaseDate = 07/13/2011 CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz" MaxSpeed: 3300 CurrentSpeed: 3306 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121011-28392-01.dmp] Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Debug session time: Sat Dec 10 20:29:19.389 2011 (UTC - 5:00) System Uptime: 0 days 0:01:05.638 Probably caused by : win32k.sys ( win32k!RawInputThread+6ed ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x3B_win32k!RawInputThread+6ed Bugcheck code 0000003B Arguments 00000000`c000001d fffff800`0309bec5 fffff880`03a85c80 00000000`00000000 BiosVersion = V1.12B6 BiosReleaseDate = 07/13/2011 CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz" MaxSpeed: 3300 CurrentSpeed: 3306 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
I have uninstalled afterburner and updated practically all of the windows updates. The sound card was also removed and the driver for it uninstalled. I also installed the newest Nvidia drivers and it crashed earlier with the same problem. The system was just idling and it randomly BSOD. I would like to say that it's crashing a lot less frequently now that I have done all those steps but I think the crash dump still points to the same problem.
Using a Corsair Force 3 90Gb SSD as the OS boot drive on a MSI P67a G43 Mobo. When I installed windows, I changed some of the disk settings on the computer to optimize it for an SSD as the boot drive. Could this have affected it? I'm not sure exactly what changes I did anymore. The HDD that I'm using as the storage used to be my main and only drive and everything worked fine back then.
I also included the newest crash dump as an attachment. Thanks for helping.
Reset the settings in your BIOS to default.
Try the storage hard drive as the boot hard drive (you don't need to register/activate Windows) to see if it stops the errors.
USB controller and Galaxy S2 still showing up in the perfmon report
Memory dump doesn't blame anything in particular
BSOD BUGCHECK SUMMARY
Code:Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010912-7425-01.dmp] Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Debug session time: Mon Jan 9 20:30:33.844 2012 (UTC - 5:00) System Uptime: 0 days 15:57:02.718 Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+165 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x3B_nt!KiCommitThreadWait+165 Bugcheck code 0000003B Arguments 00000000`c000001d fffff800`03081ec5 fffff880`0c30d620 00000000`00000000 BiosVersion = V1.12B6 BiosReleaseDate = 07/13/2011 CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz" MaxSpeed: 3300 CurrentSpeed: 3306 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
I decided to do a fresh install on the SSD through Parted Magic and everything seems to be running stable. I disabled the pagefile on the SSD drive and the system blue screened after a reboot. However, I reenabled it and now its been running fine so far. Thanks for the help.
If you have any more crashes, the Corsair Force 3 series SSDs have a known BSoD issue. Corsair is trying to fix it, check for firmware updates, install the latest.
It is the Sandforce controller that is being blamed on most sites.
Agree with usasma's idea, for testing, install Windows 7 on a HDD partition.
If everything is stable, RMA/send for refund, your Corsair Force 3 SSD.
Edit: Just checked your link usasma, that is the issue I'm referring to.
[SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
Thanks Dave76! I haven't ventured into the land of the SSD because of the number of problems that I've seen.
It's nice to get confirmation from someone who knows about this problem!
Your welcome.
SSDs, as with any new hardware, need a little time to get established.
I've had no real issues with mine, just tweaking settings to get max performance, which isn't much these days.
They all seem to have firmware issues at some point, most resolved fairly quickly.
The performance is amazing.
I appear to have spoken too soon. The bsod is back with the same problem with a bug code of B3. Got a WHEA bsod also with a code of 124 while watching a movie which I'm going to temporarily blame on the Turbo Boost on my 2500k since I lowered the voltage to the minimum required.
Also, when I installed Windows on the SSD, I did some registry changes so that the document files and stuff are switched over to the mechanical drive. Would some of these changes perhaps be part of the problem? I also disabled hybernation, superfetch, shadowcopy, and indexing.
I figured third gen SSDs were more stable so I purchased it, kind of regretting it now.
We're still seeing issues with SSD's, so I'm not quite ready to switch over myself.
As for disabling stuff, I can't see that impacting the SSD so badly that it causes BSOD's.
I prefer not to make registry changes - and would recommend that you make the changes moving the different user folders using the interface built into Windows. Can you reverse them and then use the built in way (some of these are system files)?
Please disable all sleep/hibernate/power state/overclock/underclock settings in the BIOS. If you are using custom memory settings, please only use the settings that your memory manufacturer suggests. If overclocking, please return the system to stock values while we're troubleshooting. We are seeing an increasing number of problems with these settings and I'd wonder if they are a part of the problem here.
Was the error a B3 or a 3B? Please zip up and upload the more recent BSOD's so we can have a look at them.
Quote