Test SSD for errors?

claptonman

claptonman

New Member
I got a bluescreen earlier and I want to test my SSD, but the WD Lifeguard didn't complete. What's the best way to test it? It's my Corsair Force 3.
 
SSD benchmark.

Are you thinking the bsod came from the ssd? Run bluescreenview and it will give us a better idea.

Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
I'm not sure. I had WD lifeguard installed anyways so I figured I'd test it.

Code: 
==================================================
Dump File         : 122112-4680-01.dmp
Crash Time        : 12/21/2012 12:36:39 AM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff880`13d525dd
Parameter 2       : 00000000`00000001
Parameter 3       : fffff802`e2ec5b9b
Parameter 4       : 00000000`00000001
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7b340
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7b340
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122112-4680-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 9200
Dump File Size    : 297,520
==================================================

I tested my RAM overnight a couple weeks ago with no errors.
 
Is your firmware up-to-date? I know Corsair had a lot of issues with bad firmware in the past which resulted in BSODs.
 
Can you zip up that minidump and attach it to your next post?

C:\Windows\Minidump\122112-4680-01.dmp
 
claptonman said:
No idea. I've had this SSD for, actually, one year to the day with no problems.
Click to expand...

Update your firmware. If your drive was made around April-June 2011, it could possibly have shipped with the bad firmware. Update your firmware anyway and see if that solves the problem.
 
You must log in or register to reply here.
Back
Top