SSD and Memory Issues?

[Vera Feiyd]

Hey guys, I've been experiencing some odd blue screens in the past month that I can't exactly remember the codes for, but have lead me to sort of double take and take a look across my entire machine. In trying out the Windows Memory Diagnostic tool, I was told I had some hardware issues but nothing explicit was.. said? I do know one blue screen was a ram error but I was playing quite a few games with memory leaks at the time so i payed it not.. much mind. I moved on to a ran as admin command window and did the usual chkdsk and this is what I have currently, not really sure how to proceed. Any Ideas?

C:\Windows\system32>chkdsk
The type of the file system is NTFS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
Attribute record (30, "") from file record segment 11A18C
is corrupt.
Attribute list entry with type code 30 in file 11A18C is corrupt.
1639936 file records processed.
File verification completed.
Phase duration (File record verification): 18.86 seconds.
29651 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.

Errors found. CHKDSK cannot continue in read-only mode.

C:\Windows\system32>chkdsk /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\Windows\system32>

 

[Vera Feiyd]

My second drive passed a chkdsk perfectly fine, so its just my C drive and these curious "memory hardware issues" that the WMDiagnostic tool told me to contact my manufacterer about.

 

[xilolee]

Hi!

Reboot and leave check disk resolves the errors.

 

[Vera Feiyd]

It took a few tries, honestly, each reboot wouldnt choose to repair the drive. What I ended up doing was a dism /online /cleanup-image /restorehealth, for it to fail as well, so I decided to boot in safe mode, and it froze. After that I restarted, automatic repair started doing its job, and the corruption fixed itself, no errors in sfc scan, chkdsk, or dism

Still wondering about my memory issue bluescreen, I decided to run a memtest86 run and it.. failed after 1000 errors, so I guess its time to look at new ram :/

 

[xilolee]

Check if the the RAM is set in the BIOS to the frequency/speed advised for your CPU, or less than that.
If it's set to a higher speed the system could become instable...
If this is the case, re-try the memory test after the change.

 

[Vera Feiyd]

I see, interesting. From looking it up, "i7-6700K processor supports DDR4 RAM at speeds of 2133 MHz and 1866 MHz", and I guess in turning on XMP I probably caused a bit of instability then, as it was running at 3200. I understand. Do you think its savable at this point? I've turned it down to 2133 now, but I'm wondering with how my CPU is if theres a middle ground I can strike if i do need new sticks.

TIA

 

[xilolee]

Re-try the RAM test.
If it fails before it performs eight passes, try to set the RAM speed to 1866 and re-try the test.