BX300 Win10 Pro Freezes and Error Events

[SandwichPickle]

Hi,

i've picked up a BX300 480GB SSD in january and since that day i am experiencing instability problems and freezes in games. I reinstalled Win10 Pro (on a different NVMe SSD) a dozen times now, because i thought i might have messed something up. But that wasn't the case.

The problem stays the same all the time: I only have (2) games on this SSD and once i start them, i get freezes up from 15 to 60 seconds and more during the game. Freezes happen every some minutes, some shorter, some longer. I can still work on the Windows Desktop while this freeze happens. The game crashes most of the time after those freezes and the eventviewer shows error events similar to these (typically in this order):

Event ID 129, Source: storahci, Reset to device, \Device\RaidPort0, was issued

Event ID 153, Source: Disk, The i/o operation at logical block address "0x61a968" on Disk "0" (PDO-Name: \Device\00000036) was repeated

Event ID 153 Details

Spoiler

+

System

- Provider       [ Name] Disk

- EventID 153       [ Qualifiers] 32772

Level 3

Task 0

Keywords 0x80000000000000

- TimeCreated       [ SystemTime] 2018-03-11T20:21:53.718240400Z

EventRecordID 2600

Channel System

Computer DESKTOP-SS7UFB4

Security

-

EventData

\Device\Harddisk0\DR0

0x61a968

0

\Device\00000036

0F01040004002C0000000000990004800000000000000000000000000000000000000000000000000000042A

---

Binäre Daten:

In Wörtern

0000: 0004010F 002C0004 00000000 80040099
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000 2A040000

In Bytes

0000: 0F 01 04 00 04 00 2C 00 ......,.
0008: 00 00 00 00 99 00 04 80 ....™..€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 04 2A ...*

All errors only happen with files on this very SSD, the NVMe SSD and my other SSHD work fine. Events like the above ones are only triggered on \Device\00000036 and this is the BX300.

I found some articles on the net, saying that you could try to swap the SATA-controller driver from newest vendor driver to standard Microsoft SATA-driver or vice versa. I tried both drivers but that wasn't a success at all.

I've also tried crystaldiskinfo (SMART-info reports the SSD as "good"), chkdsk and so on. None of the tools report a problem at all.

Any ideas how to solve the problem?

Thanks for your help!

Sascha

Box specs:

Gigabyte GA-AX370 Gaming 5, Firmware F21

AMD Ryzen 1700

32 GB G.Skill Trident Z 3200 C14 (4x8 GB, running standard freq - no o/c)

Samsung SM961 NVMe SSD (System/Windows)

Crucial BX300 480 GB

Seagate FireCuda 2 TB SSHD

NVIDIA Geforce GTX 1070

[HWTech]

Programs that provide a  SMART status may not always correctly report the health of an SSD as it depends which attributes they monitor and how they interpret them.   I've seen some cause false alarms and others not cause any alarm at all.   If I suspect I have a drive problem, I personally examine the SMART Attributes myself to see if anything looks like a problem.    Feel free to post the SMART Attribute table and we can make sure nothing looks out of the ordinary.

I notice your first Event ID 129 shows a path for RAIDPort0.    If this SSD is not part of a hardware RAID, then I would check the BIOS/UEFI settings and turn off any RAID support for that port.

[SandwichPickle]

Hi HWtech,

thanks for taking the time to answer to my post.

Im not really into SMART attributes and how to properly read them for different manufacturers. But as suggested i am posting a screenshot of the attributes here:

I also checked for any raid setting in UEFI, but SATA-Mode is properly set to AHCI (not RAID). There is no RAID active in the box, all disks are single volumes and there is no other setting in UEFI concerning RAID. I also did not install any RAID drivers or anything. Really strange, isn't it? Why is the warnung refering to a raid device (which is definitely not present at all)?

Any other ideas or insights you can gain from looking at the SMART attributes?

Thanks for your help! Its really appreciated.

Sascha

[bogdan]

Your picture has been moderated for some reason. Please repost SMART attributes but remember to remove any personal information like serial numbers. 

You can do it with CrystalDiskInfo - use 'Edit > Copy' option, just please remove drive's serial number.

[SandwichPickle]

Hey bogdan,

thanks for the hint. Makes sense to remove the serial *cough*. Done! :-)

[bogdan]

Looking at the SMART data I would say your drive is healthy and in good condition. 

I believe that Event ID 129, Source: storahci may probably mean that you are using MS SATA driver right now. Is that correct? What other vendor driver did you try, what version?

I would probably try to install AMD Chipset Driver ver.17.40 and then AMD SATA/RAID Driver ver.17.40 - of course in case you didn't try that before.

You can also try to set windows power plan to 'High performance'.

[SandwichPickle]

Hi bogdan,

thanks for getting back to my problem. I guess you where pointing me to the right direction.

I did as you said, and cleaned all AMD drivers (AHCI drivers where the standard Microsoft ones, like you mentioned), and reinstalled the 17.40 chipset drivers downloaded from the motherboards support website. So far, so good. After installing the chipset drivers i had a reboot and downloaded the 17.40 raid drivers from the same website and tried to install them. See what happens:

That doesn't really make sense to me. My system is (obviousely) installed on the NVMe SSD. What is happening here? Why would installing a raid driver kill my installation/boot-config or anything?

Any idea how i would get those raid drivers installed without killing my system installation on the NVMe SSD?

Cheers, Sascha

[bogdan]

Hi Sascha,

Unfortunately I have no experience with NVMe drives and their storage drivers, you would need help from someone who has experience with them. I am not sure why installing AHCI/RAID storage driver would render NVMe boot unusable.

Since you have installed chipset driver successfully you can try to set windows power plan to 'High performance' and see how would it go during your gaming sessions. Looking at your issue and specific event viewer warnings you have posted I came across those two articles, please take a look at them. You could try to disable windows feature called 'dynamic tick'. Worth giving a try, I believe.

http://www.pwrusr.com/system-administration/solved-warning-the-io-operation-at-logical-block-address...

https://updatecontroller.wordpress.com/2016/08/08/disabling-dynamic-ticks/

[SandwichPickle]

Hi Bogdan,

thanks for pointing out the possible solutions. I have had a look at them, but i am still worried because of the strange error message about the NVMe-disk possibly beeing destroyed by installing a different driver. So i finally posted a ticket to the motherboard vendor (Gigabyte), because i found more posts of people having the same problem when installing this very AMD SATA controller driver thingie on different B3xx and X3... chipsets. So maybe they have to offer a proper way or a proper driver version, that i´m able to install the way its meant to be done.

I'll post back, when i get a usable reaction from Gigabyte (or from anywhere else).