Event 129 secnvme

FAQ, getting help, user experience about PrimoCache
neatchee
Level 5
Level 5
Posts: 49
Joined: Tue Feb 12, 2019 8:38 pm

Re: Event 129 secnvme

Post by neatchee »

New motherboard, same problem :(
neatchee
Level 5
Level 5
Posts: 49
Joined: Tue Feb 12, 2019 8:38 pm

Re: Event 129 secnvme

Post by neatchee »

Talked to Samsung today. They're pointing the finger at Windows 10 versions 1803-1809. Hopefully that means a future release of Windows will fix the issue?

In the meantime I'm abandoning this endeavor. Not worth the hassle anymore. Gonna sell these two Samsung drives and grab something from another manufacturer and hope for the best.
User avatar
Jaga
Contributor
Contributor
Posts: 692
Joined: Sat Jan 25, 2014 1:11 am

Re: Event 129 secnvme

Post by Jaga »

It's too bad you're running into the issue and dumping the Samsung drives. I consider them the leader in the field for SSDs and NVMes. And you'd think if it was widespread there would be a lot more people running into it and reporting it. I'm currently running 1803 with a 970 NVMe and haven't had any issues at all with the drive. :(

Will be interesting to see if a replacement changes the outcome of the problem for you.
neatchee
Level 5
Level 5
Posts: 49
Joined: Tue Feb 12, 2019 8:38 pm

Re: Event 129 secnvme

Post by neatchee »

I agree. There's a reason I went with the 970 in the first place :(

What main chipset are you on? My research strongly suggests it's something to do with the Z270 and Z170 in particular.

Either way, it may not hit the bar for "widespread" but I'm definitely not alone. A quick search for "event 129" + "samsung" reveals a not-insignificant number of reports of similar issues.
User avatar
Jaga
Contributor
Contributor
Posts: 692
Joined: Sat Jan 25, 2014 1:11 am

Re: Event 129 secnvme

Post by Jaga »

Running this machine with a Skylake processor, on the Intel Z170 (rev 31) chipset. Motherboard is a Z170A Gaming M5 from MSI. No issues at all, even with heavy load (though I don't typically copy/write more than 50GB at one shot to the NVMe).
neatchee
Level 5
Level 5
Posts: 49
Joined: Tue Feb 12, 2019 8:38 pm

Re: Event 129 secnvme

Post by neatchee »

Maybe just the Z270 then :-\
neatchee
Level 5
Level 5
Posts: 49
Joined: Tue Feb 12, 2019 8:38 pm

Re: Event 129 secnvme

Post by neatchee »

Picked up the following new parts:

* adata xpg sx8200 pro 512gb NVMe
* Corsair HX850i 850wt Platinum PSU

Still on the Gigabyte mobo but reseated everything and ran all new cabling.

Problems have disappeared. PrimoCache is now running flawlessly using the ADATA XPG as an L2 Cache.

So there you have it. Either my PSU was bad and causing all the problems, or the Samsung 970 series really does have a serious compatibility problem with the Z270 chipset and Windows 10 v1803+
User avatar
Support
Support Team
Support Team
Posts: 3623
Joined: Sun Dec 21, 2008 2:42 am

Re: Event 129 secnvme

Post by Support »

I suspect this issue is caused by multiple factors together: Windows, motherboard chipset, and hard drive. They are all involved in the power management. However, as far as I know, this issue mostly happened in Samsung SSDs. Maybe their firmware cannot handle it in good manner.
Anyway, neatchee, thank you very much for lots of testing and sharing.
neatchee
Level 5
Level 5
Posts: 49
Joined: Tue Feb 12, 2019 8:38 pm

Re: Event 129 secnvme

Post by neatchee »

My pleasure :) I'm happy to have helped document all of the possible troubleshooting steps for this issue. Hopefully it will help someone someday!
Post Reply