0
I bought a Samsung 850 EVO 120GB SSD about a month ago. I installed Windows 8.1 x64 Pro on it, and since then my PC is almost useless because I get all sorts of BSODs (currently at 20) which weren't present with an HDD.
Specs:
- mobo: ASRock P55 pro (2.60 BIOS)
- CPU: Intel i5-650 (@BCLK 160 because of the RAMs)
- GPU: VTX3D HD6790 1GB
- RAM: Kingston HyperX Blue DDR3 1600 2x8GB
- HDD: Western Digital Caviar Green 2TB
- SSD: Samsung 850 EVO 120GB
- DVD: Asus SATA DVD-RW
- Tenda W322P+ PCI Wi-Fi adapter
The drive controller is set AHCI with Hot-Plug but I tried IDE with Enhanced setting but didn't made any difference. The VGA uses the latest AMD 14.12 Omega driver and the on board audio is using the latest hd audio driver from Realtek anything else is from Microsoft.
As you see there is an Overclock on the CPU but I tried with default clock and I still got BSODs.
I checked the temperatures, but everything is OK. CPU after 1 hour stress test was about 60° C. The VGA after 1 hour stress test was 75° C.
I run HHD sentinel tests on the WD HDD but that returned OK, the Samsung Magician shows that the SSD is Good and is using the latest firmware.
Today I got a BSOD while working and after reboot I got immediately a Critical Process Died BSOD. When I tried to set Windows back to an earlier date it told me that that the system protection must be enabled, but it was enabled for ALL partitions. I was able to set it back with a few tricks, but this is still annoying.
I tried to post my problem on the MS forum but the only answer I got was to uninstall Avast because one of the BSOD was connected to Avast. Anyway I tried uninstalling Avast, but it didn't made any difference.
Is there anything I can try to get rid of these BSODs?
A few of the BSODs are from the AMD VGA driver, so I installed the latest beta diver, but still I'm getting BSODs, but since then I'm not getting any VGA driver related BSODs.
here are the BSODs since I changed the VGA driver.
Laci K
Posted 2015-05-05T16:02:31.483
Reputation: 263
There are a few possible causes: 1) Not SSD related at all (which means the error would go away if you test or run a while with a HDD). 2) IO related (either problems with the SSD, the drivers, the chipset or the SATA cable). Quicket to test that with: Change cable and or try a different SATA port. – Hennes – 2015-05-05T16:05:59.217
We only need the .dmp files for the most recent crashes, after you solved the problems with your display driver and Avast. You say it made no difference but are you still getting BSOD indicating its caused by Avast. – Ramhound – 2015-05-05T16:06:11.663
The latest I'we checkd with the windbg showed Unable to verify timestamp for aswSP.sys but in analyse-v shows the process as csrss.exe so I don't know if its Avast related or not. – Laci K – 2015-05-05T16:14:17.550
1csrss.exe has nothing to do with Avast. My research indicates that aswSP.sys is the avast! self protection module which means you still are loading a Avast kernel level driver. So use Auotruns and configure your system NOT to load it. Simply keeping Avast and the OS updated would solve this problem more then likely. – Ramhound – 2015-05-05T16:20:18.767
Avast Uninstall Utilty – Ramhound – 2015-05-05T16:25:36.960
Thanks, I run the utility in safe mode, and cahnged my sata cable to a brand new one and changed the connection from sata0 to sata4 on the MB, now we will see if any of this helps. Oh I just saw you edited your comment, My system is up to date and I also kept Avast up to date. – Laci K – 2015-05-05T16:39:18.177
So it turns out that nothing is changed today I got a KMODE_EXCEPTION_NOT_HANDLED BSOD according to Windbg its probably caused by
hardware ( nt! ?? ::FNODOBFM::'string'+3aa31 )– Laci K – 2015-05-06T14:01:41.467