Jump to content

Search the Community

Showing results for tags 'mushkin'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Forum Introduction & Feedback
    • Site Announcements, Rules & New Member Intros
    • TechInferno Forum Feedback
  • Tech News & Reviews
    • News & Reviews
  • Notebook Discussion
    • General Notebook Discussions
    • Notebook OEM Subforums
    • What Notebook Best Fits My Needs?
    • Legacy Articles
  • Desktop & General Hardware
    • General Desktops Discussion
    • Desktop Hardware
    • Overclocking, Cooling & Build Logs
  • Software, Networking & Gaming
    • PC & Console Gaming
    • Video Driver Releases & Discussion
    • Networking
    • General Software Discussion
  • Everything Else
    • Off Topic
  • Legacy Section (Not Actively Supported)
    • DIY e-GPU Projects

Categories

  • SVL7 & Klem VBIOS Mods
    • AMD
    • Alienware M11x R3
    • Alienware M14x R2
    • Alienware M17x R4
    • Alienware M18x R1
    • Alienware M18x R2
    • Kepler VBIOS
    • Lenovo Y400-Y500
    • Lenovo Y410p-Y510p
    • Lenovo Y580-Y480
    • Legacy BIOS/VBIOS
    • Maxwell VBIOS
    • Sony Vaio SVS13 / SVS15 series
  • BAKED BIOS Mods
    • Clevo
  • Utilities

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Steam


AIM


MSN


Website URL


Yahoo


Jabber


Skype


Location


Interests


Occupation

Found 1 result

  1. I have a Mushkin Chronos Deluxe 240GB SSD which I've used as my boot drive for the last two years. Recently I began getting BSOD's when trying to write new data of any significant size to the drive. Note: The drive got to 75% capacity before I ever had any problems. The strange thing is that all the SMART data is green across the board, the drive passes all self-tests, and it reports 100% drive life left. There are never any errors found with chkdsk /r, even after the system crashes trying to write something. It passes BurnInTest sequential data write/read but fails with the same BSOD (0x000000F4) when testing using random write, random seek testing. I duplicated these same BurnInTest results on a desktop PC with the drive installed but not being booted. Only difference is when this machine crashes, there is no BSOD - it just freezes at some point during the randomized BurnInTest. Could the end of the drive just be bad flash memory? Could this happen without tripping any of the drive's self monitoring capabilities and not show as bad sectors in chkdsk /r? This is only the second SSD I ever purchased, and the first failure I've experienced to date. Is this as strange a behavior for SSD's as it seems?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.