Community
cancel
Showing results for 
Search instead for 
Did you mean: 
RRich14
Beginner
2,019 Views

Could there be someyhing wrong with my SSD5- 540s- 240 G

I ran out of space on my last SSD, a Samsung 80 GB. I bought an Intel 540 - 240 GB.

I decided to install the Win 10 Anniversary and like others I've had nothing but freezing. MS support sent me an ISO for the previous version 1511. At this point after a clean install, I'm still I'm freezing up. Before withe the Samsung I had a perfect ruining machine.

I'm thinking that possibly it's the new drive and not Windows. Could it possibly be the issue?

Has anyone had any issues with the 540?

Thanks

0 Kudos
11 Replies
idata
Community Manager
98 Views

mailto:pbman1953@gmail.com pbman1953@gmail.com,

 

 

If your OS experiences slowness or freezing, you may want to take a look at this solution found in this link: http://www.intel.com/content/www/us/en/support/software/000006198.html Run a Low-Level Format on Intel® Solid State Drives

 

 

If your Intel® SSD Detects a Security Freeze Lock, please access this other link that provides a solution to this specific matter: http://www.intel.com/content/www/us/en/support/software/000006094.html What to Do if Your Intel® SSD Detects a Security Freeze Lock

 

 

*Caution! Always back up your software before you run a low-level format or secure erase

 

 

Let us know if this worked for you.

 

 

Best regards,

 

Aleki
RRich14
Beginner
98 Views

I took your advice and took the time to use Kill disc. Then I reinstalled and the computer worked fine for a day. Then there was one update but not the newer anniversary version, still the pre- anniversary 1511.

Right after it froze.

Any ideas? Installing the most up to date video drivers don't seem to help

Thanks

Rich

idata
Community Manager
98 Views

mailto:pbman1953@gmail.com pbman1953@gmail.com,

 

 

In this case, could you please run a diagnostic using this tool: https://downloadcenter.intel.com/download/26085/Intel-Solid-State-Drive-Toolbox Intel® Solid State Drive Toolbox and send us the logs so we can check it. In the mean time, you can also do the following procedures:

 

 

1. Make sure you have all the latest chipset drivers. Sometimes, certain Windows®10 freeze can be caused by certain BIOS settings such as fast boot. Please disable it and test it in order to see if the situation is resolved.

 

 

2. Check for BIOS updates and update it if there is any available.

 

 

3. Update your SSD firmware. *Make sure to have a back up of all the relevant information in order to avoid data loss.

 

 

Let us know if this helped you.

 

 

Best regards,

 

Aleki

 

 

RRich14
Beginner
98 Views

My replies are-

Bios is up to date

As far as I know drivers are up to date

I think fast boot is disabled because I see the bios info on boot up. But I will check.

What is the simplest way to update the firmware? I thought the SSD toolbox does that?

Last night I ran the full diagnostic test and walked away for the night. When I came back ,this morning, the screen showed me a "can't find boot disc", I had to shut down and re-start. At the end of the test it may have re-started? Then the boot disc message?

Where would the log be kept?

Thanks

idata
Community Manager
98 Views

mailto:pbman1953@gmail.com pbman1953@gmail.com

 

 

To obtain the logs from the Intel® SSD Toolbox you can click on the button to the bottom right that says Export. If possible as well, could please try once more and see if you can get the SMART details.

 

 

Have you had the opportunity to try this drive in a different system and see if the same thing happens?

 

 

Best regards,

 

Aleki
RRich14
Beginner
98 Views

I'll look for the logs and send them in.

I can try the SDD in another machine and see.

Thanks

idata
Community Manager
98 Views

mailto:pbman1953@gmail.com pbman1953@gmail.com,

 

 

Great! We're looking forward to hearing from you soon with the results after trying in another computer and also to get the logs.

 

 

Best regards,

 

Aleki
RRich14
Beginner
98 Views

Did the firmware update and here are the logs- They are big

IntelSSDTDK-

[19:58:38:351] INFO : .\Feature.cpp(88): Feature::Feature: OS: WIN8.1

[19:58:38:367] INFO : .\SystemParser.cpp(73): SystemParser::Initialize: Initialized with status: 1.

[19:58:38:367] DEBUG : .\Adapter_NVMe_Win.cpp(126): DeviceManagement::Adapter_NVMe_Win::FindAdapters: Opening Handle to \\.\SCSI0: to test if it is a NVMe BusType

[19:58:38:367] INFO : .\SystemParser.cpp(73): SystemParser::Initialize: Initialized with status: 1.

[19:58:38:383] DEBUG : .\Adapter_NVMe_Win.cpp(39): DeviceManagement::Adapter_NVMe_Win::Adapter_NVMe_Win: Opening SCSI path / passthrough for this NVMe Windows adapter

[19:58:38:383] INFO : .\SystemParser.cpp(79): SystemParser::Execute: Executing...

[19:58:38:476] DEBUG : .\Adapter_NVMe_Win.cpp(44): DeviceManagement::Adapter_NVMe_Win::Adapter_NVMe_Win: Setting up passthrough command path / 'drive' for \\.\SCSI0:

[19:58:38:476] DEBUG : .\CommandPath_NVME.cpp(344): DeviceManagement::CommandPath_NVME::TestDevice: CommandPath_NVME::TestDevice win Start...

[19:58:38:476] DEBUG : .\SystemParser.cpp(125): SystemParser::GetOperatingSystem: Getting OS information.

[19:58:38:570] DEBUG : .\CommandPath_NVME.cpp(123): DeviceManagement::CommandPath_NVME::SendOpcodeCore: Calling DeviceIoControl()

[19:58:38:570] ERROR : .\CommandPath_NVME.cpp(137): DeviceManagement::CommandPath_NVME::SendOpcodeCore: OS: 1117 = The request could not be performed because of an I/O device error.

[19:58:38:586] DEBUG : .\CommandPath_NVME.cpp(179): DeviceManagement::CommandPath_NVME::SendOpcodeCore: Done copying back data/buffer, command, and status.

[19:58:38:586] ERROR : .\CommandPath_NVME.cpp(184): DeviceManagement::CommandPath_NVME::SendOpcodeCore: Returning IOCTL fail of 18446744073709550499

[19:58:38:586] DEBUG : .\CommandPath_NVME.cpp(373): DeviceManagement::CommandPath_NVME::TestDevice: CommandPath_NVME::TestDevice win End...

[19:58:38:601] ERROR : .\Adapter_NVMe_Win.cpp(58): DeviceManagement::Adapter_NVMe_Win::Adapter_NVMe_Win: In AdapterNVMeWin constructor, tried to TestDevice() on CommandPath_NVMe, but failed

[19:58:38:601] DEBUG : .\Adapter_NVMe_Win.cpp(161): DeviceManagement::Adapter_NVMe_Win::FindAdapters: \\.\SCSI0: device failed NVMe TestDevice() check

[19:58:38:601] DEBUG : .\SystemParser.cpp(203): SystemParser::GetComputerSystem: Getting computer information.

[19:58:38:601] DEBUG : .\Adapter_NVMe_Win.cpp(89): DeviceManagement::Adapter_NVMe_Win::FindAdapters: Failed to get next portkey at portIndex 1, exiting assuming we are at the end of the scsi key list

[19:58:38:617] DEBUG : .\Adapter_Generic_Win.cpp(1106): DeviceManagement::Adapter_Generic_Win::ScanDrives: Scanning for drives

[19:58:38:617] DEBUG : .\SystemParser.cpp(267): SystemParser::GetCPU: Getting CPU information.

[19:58:38:617] DEBUG : .\Adapter_Generic_Win.cpp(136): DeviceManagement::Adapter_Generic_Win::FindPhysical: Looking for physical drives

[19:58:38:617] DEBUG : .\SystemParser.cpp(324): SystemParser::GetDriverVersions: Getting controller information.

[19:58:38:679] INFO : .\Adapter_Generic_Win.cpp(171): DeviceManagement::Adapter_Generic_Win::FindPhysical: Found device: SCSI\DISK&VEN_WDC&PROD_WD5001AALS-00L3B\4&FA535C2&0&020000

[19:58:38:679] INFO : .\Adapter_Generic_Win.cpp(176): DeviceManagement::Adapter_Generic_Win::FindPhysical: Passed filter criteria

[19:58:38:679] INFO : .\SystemParser.cpp(117): SystemParser::Execute: Passed.

[19:58:38:679] DEBUG : .\Adapter_Generic_Win.cpp(191): DeviceManagement::Adapter_Generic_Win::FindPhysical: Retrieved interface data

[19:58:38:695] DEBUG : .\Adapter_Generic_Win.cpp(229): DeviceManagement::Adapter_Generic_Win::FindPhysical: Connected to the drive

[19:58:38:695] INFO : .\Adapter_Generic_Win.cpp(248): DeviceManagement::Adapter_Generic_Win::FindPhysical: Retrieved the physical drive number: \\.\PHYSICALDRIVE1

[19:58:38:695] DEBUG : .\Adapter_Generic_Win.cpp(254): DeviceManagement::Adapter_Generic_Win::FindPhysical: Creating a Drive

[19:58:38:711] DEBUG : .\Adapter_Generic_Win.cpp(261): DeviceManagement::Adapter_Generic_Win::FindPhysical: Intializing Generic Info

[19:58:38:711] DEBUG : .\DeviceIdentification_System.win.cpp(120): DeviceManagement::DeviceIdentification_System::Identify: DeviceIdentification_System::Identify

[19:58:39:273] DEBUG : .\DeviceIdentification_System.win.cpp(217): DeviceManagement::DeviceIdentification_System::Identify: Additional location info for all drives

[19:58:39:289] INFO : .\DeviceIdentification_System.win.cpp(223): DeviceManagement::DeviceIdentification_System::Identify: This drive has a Lun 0

[19:58:39:289] INFO : .\DeviceIdentification_System.win.cpp(226): DeviceManagement::DeviceIdentification_System::Identify: This drive has a Port 0

[19:58:39:289] INFO : .\DeviceIdentification_System.win.cpp(229): DeviceManagement::DeviceIdentification_System::Identify: This drive has a Target ID 0

[19:58:39:304] INFO : .\DeviceIdentification_System.win.cpp(232): DeviceManagement::DeviceIdentification_System::Identify: This drive has a Path ID 2

[19:58:39:304] DEBUG : .\Adapter_Generic_Win.cpp(264): DeviceManagement::Adapter_Generic_Win::FindPhysical: Extracting firmware revision

[19:58:39:304] DEBUG : .\Adapter_Generic_Win.cpp(275): DeviceManagement::Adapter_Generic_Win::FindPhysical: Detecting command path

[19:58:39:320] INFO : .\Adapter_Generic_Win.cpp(278): DeviceManagement::Adapter_Generic_Win::FindPhysical: Detected command path type: ATA

[19:58:39:320] DEBUG : .\Adapter_Generic_Win.cpp(281): DeviceManagement::Adapter_Generic_Win::FindPhysical: Setting Adapter of this Drive to itself for now

[19:58:39:320] INFO : .\Adapter_Generic_Win.cpp(171): DeviceManagement::Adapter_Generic_Win::FindPhysical: Found device: SCSI\DISK&VEN_INTEL&PROD_SSDSC2KW240H6\4&FA535C2&0&000000

[19:58:39:320] INFO : .\Adapter_Generic_Win.cpp(176): DeviceManagement::Adapter_Generic_Win::FindPhysical: Passed filter criteria

[19:58:39:336] DEBUG : .\Adapter_Generic_Win.cpp(191): DeviceManagement::Adapter_Generic_Win::FindPhysical: Retrieved interface data

[19:58:39:336] DEBUG : .\Adapter_Generic_Win.cpp(229): DeviceManagement::Adapter_Generic_Win::FindPhysical: Connected to the drive

[19:58:39:336] INFO : .\Adapter_Generic_Win.cpp(248): DeviceManagement::Adapter_Generic_Win::FindPhysical: Retrieved the physical drive number: \\.\PHYSICALDRIVE0

[19:58:39:351] DEBUG : .\Adapter_Generic_Win.cpp(254): DeviceManagement::Adapter_Generic_Win::FindPhysical: Creating a Drive

[19:58:39:351] DEBUG : .\Adapter_Generic_Win.cpp(261): DeviceManagement::Adapter_Generic_Win::FindPhysical: Intializing Generic Info

[19:58:39:351] DEBUG : .\DeviceIdentification_System.win.cpp(120): DeviceManagement::DeviceIdentification_System::Identify: DeviceIdentification_System::Identify

[19:58:39:914] DEBUG : .\DeviceIdentification_System.win.cpp(217): DeviceManagement::DeviceIdentification_System::Identify: Additional location info for all drives

[19:58:39:914] INFO : .\DeviceIdentification_System.win.cpp(223): DeviceManagement::DeviceIdentification_System::Identify: This drive has a Lun 0

[19:58:39:914] INFO : .\DeviceIdentification_System.win.cpp(226): DeviceManagement::DeviceIdentification_System::Identify: This drive has a Port 0

[19:58:39:929] INFO : .\DeviceIdentification_System.win.cpp(229): DeviceManagement...

idata
Community Manager
98 Views

mailto:pbman1953@gmail.com pbman1953@gmail.com,

We also need the logs from the toolbox. Could you please be so kind and provide the logs extracted from it? Just click on the button that says " Export " in order to create an Excel file and once you have done that, please attach it here. Also, let us know if you had the opportunity to try this drive in a different computer as well.

Best regards,

Aleki

RRich14
Beginner
98 Views

I tried that but it didn't go to the right place on my computer. But in the end I returned the drive. I couldn't handle it any more. I still believe in the excellence of Intel products!

Thanks for you help!

idata
Community Manager
98 Views

mailto:pbman@gmail.com pbman@gmail.com,

 

 

Thank you for your preference and trust in our products. Here is a list of other Intel® SSDs that you be interested to know about them. It is important to consult with your computer manufacturer for compatibility in order to enjoy SSD full functionalities.

 

 

Consumer SSDs

 

http://ark.intel.com/compare/71181,71180,71179,74497,71183 Intel® SSD 525 Series

 

http://ark.intel.com/compare/86741,86739,88743,88744,86742,86740 Intel® SSD 750 Series

 

http://ark.intel.com/compare/81039,81038 Intel® SSD 730 Series

 

http://ark.intel.com/compare/94917,94921,94924,94926 Intel® SSD 600p Series

 

http://ark.intel.com/compare/94204,94421,94209,94434,94207,94331,94203,94328,94213,94334,94420,94332 Intel® SSD 540s Series

 

http://ark.intel.com/compare/86729,86722,86737,86728,86734,86725,86731,86727,86738,89330 Intel® SSD 535 Series

 

http://ark.intel.com/compare/75336,77950,75334,75333,75331,75328,75338,77949,75613,75611,75337,77948... Intel® SSD 530 Series

 

 

Check this link if you would like to see other types of SSDs : http://ark.intel.com/# @SolidStateDrives

 

 

Best regards,

 

Aleki
Reply