Two Samsung 840 Pro's & 1 840 have failed, 4 at [H]ardOCP (Early review sample SSD's)

[tracerbullet]

Yep - thank you! I may not should have been worried to begin w/ but regardless I do feel better now.

 

[TemjinGold]

So can we maybe update the title of this thread? I can't imagine Samsung is happy with it...

Not that I ahh... work for them or anything...

 

[jwilliams4200]

So can we maybe update the title of this thread? I can't imagine Samsung is happy with it...

Why should the title of the thread be changed? There is no incorrect information there. And I don't see why you think we should care if Samsung is unhappy. Samsung screwed up and sent insufficiently tested SSDs out to reviewers, and some of them failed. It is good that Samsung apparently caught the bug at the last minute and managed to fix it on retail models. But Samsung should never have let such a bug slip past them even on the review models. Reviewers should receive the same firmware version as sold at retail, otherwise there is always the question of whether the review models were not a valid representation of the retail models.

 

[Mfusick]

I think most will realize the failures are early samples...

 

[BTRY B 529th FA BN]

5 yr warranty = so don't sweatem people

i think it was early firmware that bricked'm

 

[TemjinGold]

1) There are no threads indicating an all clear in its title.

2) Only people who have been following the contents of this thread closely know that the retail units were not affected the same way.

Leaving the title of this thread as is with nothing else to balance is horribly misleading to many potential customers. I for one feel this isn't fair to Samsung because they didn't try to sell faulty units to consumers.

 

[jwilliams4200]

anandtech already posted an article today with an update on the issue, so I hardly think further publicity is necessary, but if you feel so strongly about it, why not start a thread with a suitably happy-happy joy-joy title for Samsung?

 

[videoclone]

1) There are no threads indicating an all clear in its title.

2) Only people who have been following the contents of this thread closely know that the retail units were not affected the same way.

Leaving the title of this thread as is with nothing else to balance is horribly misleading to many potential customers. I for one feel this isn't fair to Samsung because they didn't try to sell faulty units to consumers.

i've updated the post with info at the top in BOLD to state what the issue was and link to the Anandtech site stating what they were told by Samsung.

I'm not sure about changing the title of the post as there is a forum rule that its not allowed.
I did edit it though with (early review samples) at the end.
I really like Samsung and i buy allot of their products.. no 3D TV as i prefer passive 3D better.
I was in the market for a second SSD and i was going to grab a 840 Pro but ended up going with an 830 because of the proven reliability.

840 Pro looks great but its still early days!

 

[TemjinGold]

I think the fix is fair. Thanks.

 

[cytg111]

I think the fix is fair. Thanks.

I dont know, if the samples sent to reviewers fails left and right, you gotta wonder what kind of validation they "passed" the first time around and what kind they passed the second time with "non-beta" firmware. Like, wonder alot! I know I'm stearing clear of these some good time to come.
the beta/whatever-firmware explanation sounds nothing but disturbing.

 

[TemjinGold]

I meant I think the fix to the thread title is fair. I'm not talking about the drives.

 

[t0m3k51]

I got my Samsung 840 Pro 256GB today (from Amazon), the firmware version is DXM03B0Q.
I'll post any issues should I encounter any.

 

[videoclone]

Looks like all is well with the Samsung 840 Pro and non Pro... strange that the product so close to release had a major firmware issue fixed just weeks before release.

 

[JPComputers]

Hey guys,

So I decided to try this 840 pro 256gb. I had two samsung 830 128gb in raid 0, and everything was great except for loss of TRIM.

I setup the bios with AHCI, installed windows and noticed it required me to install windows with a GPT partition. Installed fine. Updated drivers, windows update, you know the standard stuff after a fresh install.

Now i'm getting random BSOD, all with the same error, storport.sys driver_irql_not_less_or_equal 0x000000D1.

Whats up with that. So I thought it was a fluke, reinstalled windows. Same thing. Hmmm... 20 reinstalls later and started using intel RSTe release before installing windows and other drivers. No luck.

Thought got a bad draw on the drive, when to Fry's, exchanged it, installed it. Same thing. Ugh!


System info:
Asus sabertooth x79 UEFI AHCI Intel SATA 6gbps Port for SSD samsung 840
Intel 3820 I7 2011LGA
Corsair dominator ram 16gb
Creative X FI Fatality Sound card
Corsair AX1200i PSU
No other storage drives attached.

Drivers:
Win7 Sp1 fully updated x64
Intel(R) Chipset Software Installation Utility V9.2.3.1025
SABERTOOTH X79 BIOS 3102
Asmedia USB 3.0 Driver V1.14.3.0
Intel(R) Rapid Storage Technology enterprise Driver Software V3.5.0.1

 

[JPComputers]

If anyone knows how to read this please let me know xD

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000becff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800190a0d2, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002313100
GetUlongFromAddress: unable to read from fffff800023131c0
0000000000becff8 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
storport!StorPortNotification+22
fffff880`0190a0d2 488b18 mov rbx,qword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TAG_NOT_DEFINED_c000000f: FFFFF880027B8FB0

TRAP_FRAME: fffff880027b18b0 -- (.trap 0xfffff880027b18b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000becff8 rbx=0000000000000000 rcx=0000000000001003
rdx=fffffa8018c8b000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800190a0d2 rsp=fffff880027b1a40 rbp=fffffa800db4c230
r8=0000000000000002 r9=0000000000000000 r10=fffffa8018c8b000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
storport!StorPortNotification+0x22:
fffff880`0190a0d2 488b18 mov rbx,qword ptr [rax] ds:00000000`00becff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800020e3569 to fffff800020e3fc0

STACK_TEXT:
fffff880`027b1768 fffff800`020e3569 : 00000000`0000000a 00000000`00becff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`027b1770 fffff800`020e21e0 : fffffa80`0cae5bc3 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`027b18b0 fffff880`0190a0d2 : fffffa80`0e072943 fffff880`012e80de fffffa80`0e072943 fffffa80`0e059240 : nt!KiPageFault+0x260
fffff880`027b1a40 fffff880`012e6aa8 : fffffa80`0c97ccc0 fffffa80`18c8b000 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x22
fffff880`027b1ac0 fffffa80`0c97ccc0 : fffffa80`18c8b000 00000000`00000002 00000000`00000000 fffff880`027b1b38 : iaStorA+0x63aa8
fffff880`027b1ac8 fffffa80`18c8b000 : 00000000`00000002 00000000`00000000 fffff880`027b1b38 00000000`00000002 : 0xfffffa80`0c97ccc0
fffff880`027b1ad0 00000000`00000002 : 00000000`00000000 fffff880`027b1b38 00000000`00000002 00000000`00009bdb : 0xfffffa80`18c8b000
fffff880`027b1ad8 00000000`00000000 : fffff880`027b1b38 00000000`00000002 00000000`00009bdb fffff880`012edbec : 0x2


STACK_COMMAND: kb

FOLLOWUP_IP:
iaStorA+63aa8
fffff880`012e6aa8 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: iaStorA+63aa8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: iaStorA

IMAGE_NAME: iaStorA.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5021378e

FAILURE_BUCKET_ID: X64_0xD1_iaStorA+63aa8

BUCKET_ID: X64_0xD1_iaStorA+63aa8

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

 

[bbinnard]

I installed am 840 Pro 3 days ago and have had no problems once I got through the cloning process (where I did have problems.) I did NOT use GPT because I had read somewhere that GPT can cause problems with certain aspects of Win7. Once I got my system in a position where it could boot OK from the 840 Pro the drive has worked flawlessly.

 

[jwilliams4200]

JPComputers:

You should probably start your own thread. I see no evidence that your problems are related to the topic in this thread.

 

[Coup27]

JPComputers - Samsung claimed the 830 was designed for MBR use only and whilst there was a thread on this forum which semi supported that claim, it was never totally proven either way that the unit was safe to use in GPT. There have been no statements either way about the 840 or 840 Pro with GPT either.

I would recommend that you secure erase your 840 Pro and then install Windows 7 using standard media (not UEFI) thus creating an MBR partitioning style and see what the results are.

 

[JPComputers]

Thanks for pointing me in the right direction. I guess I expected that since I just built this computer I should be able to use the "advanced" features.

Installed windows with legacy boot option. So far so good, only two BSOD's but different error. I really regret selling both my 830's, never had a problem, everything was great =\

Now I don't know what to do if the issue reappears. I got 2 days to return it...

 

[Amnesia1187]

Thanks for pointing me in the right direction. I guess I expected that since I just built this computer I should be able to use the "advanced" features.

Installed windows with legacy boot option. So far so good, only two BSOD's but different error. I really regret selling both my 830's, never had a problem, everything was great =\

Now I don't know what to do if the issue reappears. I got 2 days to return it...

This has nothing to do with GPT or MBR. The error indicates a problem with your drivers. Specifically it's referencing the Intel IRT driver "iaStorA.sys".

The first thing I would recommend trying is using the standard msahci driver. I would also verify that your boot drive is in the first port, for your board it should be labeled SATA6G_1 (usually not needed, but always a good idea just the same).

Also, do you have your controller set to AHCI or Raid in the bios?

What specific Intel IRT drivers are you using?

For what it's worth. I'm running Windows 8 Pro on an 840Pro in GPT. I use gDisk to check periodically and I'm seeing no issues. I've only ever seen 1 report of someone with a problem using an 830 in GPT, and that was most likely a driver/configuration issue as no one else in his thread was able to reproduce the problem.

Do you see any driver/disk/store related errors in your event logs? They should show under System, but there could also be useful information under Application.

Feel free to PM me if you have questions. Let me know if you start your own thread for the issue. I'll be glad to try and help.

 

[JPComputers]

Thanks Amnesia1187,

I started a new thread.

http://forums.anandtech.com/showthread.php?t=2288883&highlight=

Thanks

 

[videoclone]

JPComputers:

You should probably start your own thread. I see no evidence that your problems are related to the topic in this thread.

Agreed .. this is another issue un-related to drives failing.

 

[danieln2]

hi all

I need the older firmware version DXM03B0Q for Samsung SSD 840 Pro.
Can somebody that has downloaded it send it to my private mail.

After upgrading from DXM03B0Q to DXM04B0Q my system runs in Sata1
speeds, It's a long story.

Thank you very much
daniel

 

[Amnesia1187]

hi all

I need the older firmware version DXM03B0Q for Samsung SSD 840 Pro.
Can somebody that has downloaded it send it to my private mail.

After upgrading from DXM03B0Q to DXM04B0Q my system runs in Sata1
speeds, It's a long story.

Thank you very much
daniel

I would guess there is no way roll back the firmware. The first thing most firmware updates do is check to see if the current version is the same or newer.

Regardless, a roll back should not be necessary. Either your system is configured wrong or there is something wrong with the drive and you would be better off getting it replaced rather than trying to band aid it.

Have you tried plugging it into a new port? Have you tried secure erasing the drive?

What motherboard/controller are you using? How is your controller set in the bios (AHCI, Legacy, Raid, etc). Where are you seeing the drive report SATA1? What transfer speeds are you actually seeing?

 

[Coup27]

+1 to the above.

Nobody will have the release firmware in a file format other than Samsung. You don't get access to the release firmware because obviously it is already on the drive you buy. You only get subsequent updates.

I also concur that there is either something wrong with the drive or your computer and attempting to flash it backwards is not the solution.