Solved BSOD Crash on new SAMSUNG 850 PRO SSD 256 GB install

[themasterpc]

Hello 7forumteam,

I didn't tought that this things can happen to me , but it seems that I need your help

Recently I purchased a new SSD, the all famous 850 PRO SSD ... but as soon as installed Windows on it, got several crashes.

I couldn't install successfully all windows updates, because some of them failed and after that some got corrupted, tried to repair with all available tools, but still left 1-2 updates ... anyway, pointed my hand on RAPID because of accessing the memory and this was a possible reason, because some stability was reached after it was disabled( and disabled stay after my last successfully install of windows)

Anyway, because of those not sucessfully updates, started from scratch again with a new windows install, but didn't installed at all the samsung magician latest version till I was able to do a complet install + all updates ... installed the samsung magician and even without rapid mode I get BSOD.

Don't know what to say, but I want to remind you that I hadn't any issue in last 4 years with my system, no BSOD , no memory issue, my last windows install was 3 years ago ...

I don't know which hw or driver is conflicting with the SSD, so I'm posting my minidumps files.

Hope to get this fixed otherwise I will RMA this SSD back to samsung.

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[themasterpc]

Hi Golden,

Thanks for your reply , I'm at my workplace now, the minidumps were submitted on my email.

That's why I didn't posted them in your requested format, is there anything else that you need?

Will run the collector once that I reach home and post here the requested files.

 

[Golden]

OK. Run it and upload once you are home. I'll look at the .dmp files in the meantime, but its easier to analyse if I have the additional information the log collector provides/

I'll keep visiting back so just upload when you can.

 

[Golden]

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff8800125bb21, fffff880091e8eb0, 0}

Probably caused by : [COLOR="Red"][B]hardware[/B][/COLOR] ( Ntfs!NtfsFsdWrite+51 )

Followup: MachineOwner
---------

4: kd> !thread
GetPointerFromAddress: unable to read from fffff80002d07000
THREAD fffffa8006dfe7d0  Cid 06bc.0bc4  Teb: 000000007ef2a000 Win32Thread: 0000000000000000 RUNNING on processor 4
IRP List:
    Unable to read nt!_IRP @ fffffa8007aa8010
Not impersonating
GetUlongFromAddress: unable to read from fffff80002c46ba8
Owning Process            fffffa8006ef2240       Image:         [B][B][COLOR="Red"]AS SSD Benchma[/COLOR][/B][/B]
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      45939        
Context Switch Count      19             IdealProcessor: 4             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000708264c2
Stack Init fffff880091e9db0 Current fffff880091e9180
Base fffff880091ea000 Limit fffff880091e4000 Call 0
Priority 25 BasePriority 25 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5

Try this please.....install Samsung Magician and see if you can update the firmware of the SSD. This might fix the issue, but we need to try it first.

 

[themasterpc]

I have it installed, the latest Samsung Magician 4.4 and the latest firmware is installed (as samsung magician says)

But I'm aware that you need all files, we can speculate anything now.

I will force it to crash once that I reach home by keeping RAPID on and doing some memtest to utilize some memory.

 

[themasterpc]

Please check the first post for the new zipfile.

 

[themasterpc]

@Golden: Can you please review this post or assign it to another member from bsod team ... the system is somehow stable but I need to know what caused the crash, in case that happens in the near future.

Thanks.

 

[Golden]

I've asked Arc to have a look for you if he has the time.

 

[themasterpc]

great, thank you very much.

 

[Arc]

Multiple bugcheck codes are blaming hardware there.

First plan to update the BIOS to Version F4 from GIGABYTE - Motherboard - Socket AM3 - GA-890FXA-UD7 (rev. 2.0)

Then do some hardware tests.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[themasterpc]

Hi Arc,

OK ... so hardware is the culprit?

I may confirm your theory with the upgrade of the BIOS as new technologies from samsung may not match with the old F2.

But I really don't like to upgrade to F4, I had F3 and F4, both couldn't get stable overclocks at all(what I wanted), I benched almost all combination of FSBs with memory timmings and I wasn't satisfied with and downgraded back to F2 and stayed like this in the last 3 years.

But I will upgrade to F4 because this may be the main issue.

About the rest of tests I may say that don't know if I'm able to do overnight tests, I have a custom case like a open dangerden case and it's noisy with all the fans.

I want to mention that my system was very stable before the upgrade to SSD, not any issue in the last 3 years and I forced the hw every time and found stable settings, runned everytime Prime95 and HiperPi and all possible syntetic test and was fine with great temps, don't know what to say.

Memtest86+ tests I made right after the crash but I didn't let to complete the test, because no error was found.

I runned also the Furmark to stress the hw and ofcourse it crashed because RAPID was on (did the test last night).

My CPU temps are fine for 4Ghz , on IDLE I have 37-39 degrees and 55-57 on full load, but on normal usage doesn't go over 43 degrees.

I will inform you after the bios upgrade.

 

[Arc]

Now you need to disable overclocking and need to see how it runs with stock settings.

If (and only if) if crashes even with stock hardware settings, then (and only then) we will need to concentrate on the SSD. Because the bugchecks are not indicating to the SSD primarily, but to hardware, and overclocking is one of the base reasons behind it.

 

[themasterpc]

I upgraded to F4 and I set back my known settings of stable overclock. (3.84 Ghz)

It seems to be stable as I forced a memory consumption of 6GB of ram with Memtest with a cpu usage of ~ 35% and no crashing occured. (+RAPID ON, which also is know that consumes up to 1.5 Ghz, if there's usage)

I wasn't able to do all the tests because of time, but will try what you suggested.

 

[Arc]

No problem, take your time.

 

[themasterpc]

I downgraded to stock settings and did some tests, but it's stable

Changed back to my overclock settings and hit it hard with prime, after that hyperpi , furmark, then pcmark 7 with all possibles tests ... stable.

For now it's a confirm that the old BIOS caused the issues, I don't know why I didn't think to this as F4 version has the new CPU AGESA 3.7.1.0 codes and as AGESA is responsible for the initialization of the procesor coreshttp://en.wikipedia.org/wiki/Central_processing_unit, memory and the HT controller ... my poor SSD wasn't too friendly with the F2 version.

Anyway, I'm glad that you pointed correctly Arc, nice catch and I thank you very much.

To close this topic and mark it as resolved I will post some pictures about this fast deamon.

 

[Arc]

Good news!

Let us know for any further issue.

 

[giorgosperi]

Hi, i see many people they have the same issue with me if you can help me also to figure out. I have two Samsung SSD'S 840 EVO, 850 PRO and i have on both of them the same issue after i enable the rapid mode.
Usually happens when i install something big. If you can help me also its driving me crazy...thank you in advance.

 

[Ninj]

Hi,

@giorgosperi: you give the solution in your question!

To everyone having freezes of SSD under Windows 7 or higher : RAPID mode is the problem, some motherboard will just not handle it with SSD. Disable RAPID weither it is Intel or Samsung software. You won't see much difference but will have a stable system.