Windows 10 Disk 600p Heavy Disk Queuing Issues

[JLock2]

I'm having some quite heavy disk queuing issues with my new 600p under Windows 10 Pro OEM.

Scenario 1:

- Running World of Warcraft in quite high settings

- Streaming FRAPS at 60fps in 2k res to disk (usually runs between 70-130mb/s)

- Once the file has hit around 16GB the issue arises

Scenario 2:

- Running Intel SSD Toolbox Full Diagnostic Scan (no errors from the scan)

Both Scenarios:

- Drive is primary disk

- No memory paging enabled

- No other applications running

- Bog standard install of Windows 10

System specifications:

- Intel m.2 600p 512GB

- Intel Core i7 6800k - Overclocked by 17% running at approximately 4Ghz

- Asus X99-A II, Intel X99

- 32GB (4x8GB) Corsair DDR4 PC4-25600 (3200) - Clocked at 2800

- NVIDIA GTX 1080

- 850W EVGA BQ, 80 PLUS Bronze

System Information:

- Microsoft Windows 10 Pro (Version 10.0.14393)

- Standard SATA AHCI Controller Driver 10.0.14393.206

- Microsoft Storage Spaces Controller 10.0.14393.351

- Standard NVM Express Controller 10.0.14393.206

System Tuner:

- No ready boost

- No Defragmenter- Superfetch/Prefetch - Feature is optimized

Drive Details:

- PCI + Subsystem Vendor: 8086

- Serial Number: Available if required

- Model Number: INTEL SSDPEKKW512G7

- Firmware Revision: PSF100C

- ... More available if required

I've spent most of tonight trying to diagnose the issue with little avail. I've spent about 5 hours Googling around and everything others have mentioned has simply not worked for me.

Side note: I'm a software engineer so if you need anything more technical please ask.

Thanks,

James

[JLock2]

Thanks for reassuring me that it wasn't just me and it was the SSD causing the issue Oggy. I've read through the article https://www.pcper.com/reviews/Storage/Intel-SSD-600p-Series-256GB-Full-Review-Low-Cost-M2-NVMe/Seque... Intel SSD 600p Series 256GB Full Review - Low Cost M.2 NVMe | Sequential Performance - HDTach, HDTune, File Copy, YAPT (… and it sounds exactly like what I'm experiencing. This makes sense why I was noticing the disk issues after 16GB of sequential writes as Fraps adds a buffer to the file when writing which I think is around 2-4GB depending on output quality.

[idata]

JamesTheMage,

Sorry for the radio silence. We've been reaching out to our additional resources, and working with our engineering team to try and shed some light on your problem.Please keep checking back on this thread every couple of days, I will post any updates we receive. Best regards,Carlos A.

[JLock2]

Hey Carlos,

Due to the ongoing performance issues making it's use inoperable for me I've had to return the disk to the vendor.

I'm happy to close this off now.

Thanks,

James

[idata]

Hello JamesTheMage,

We're sorry to hear this, but would like to thank you for bringing this issue up to our attention.

We'll close your case for now, but will continue working towards finding a solution. Thank you for your time and for all of the data you have provided us.

Best regards,

Carlos A.