Possible SSD problem

Edgar Villalba

Reputable
Jul 26, 2015
16
0
4,510
Hi people, i'm despaired because i was having some BSOD and i think it's because the SSD, how can i know that the SSD is working fine? i tested my RAM's with memtest64 and there was not any error... i tested them both running in single channel and there wasn't nothing at all... some of the BSOD was RQL_NOT_LESS_OR_EQUAL / PAGE_FAULT_IN_NONPAGED_AREA / IRQL_NOT_LESS_OR_EQUAL AND THE LAST ONE WAS MEMORY_MANAGEMENT, i really don't know what causes the problem, I formatted the SSD and with no results. i ran chkdsk and no errors, some programs like AS SSD BENCHMARK says everything is OK, what else can be? thanks in advance

The OS is Windows 8.1 Enterprise

i7 4770
B85 Asus Vanguard
R9 270 Asus
SSD Kingston SV300 240GB
8GB Ram 2x4GB (Tested with no errors)
 
Solution


It could have affected your RAM. I have heard of this exact problem being caused by bad RAM. Try a different stick.

Edgar Villalba

Reputable
Jul 26, 2015
16
0
4,510


yeah i did it already, and according those programs everything is OK. i reinstalled Windows before... the problem is with the file ntoskrnl.exe, but i don't know why

take a look

11781867_1508543406102977_8886489289280125727_n.jpg
 

Looby219

Honorable
Nov 26, 2013
125
0
10,710


ntoskrnl.exe is a vital system kernal image. you need to do a clean windows install and try not to get that problem again.
 

Edgar Villalba

Reputable
Jul 26, 2015
16
0
4,510


i did it 1 day ago... i didn't install anything else, just vital drivers, and all of them are from the official manufacturer webpage (Asus and AMD)
 

Edgar Villalba

Reputable
Jul 26, 2015
16
0
4,510
and what about to restart the computer with the restart button, because it all started when i did that... because when i configured the monitor to turn off in 1 minute and i was back, i moved the mouse, but it didn't respond, so i had to restart, after that, it started to happen... i thought it was a Windows corrupted driver due that but no, even reinstalling it happens anyways
 

Looby219

Honorable
Nov 26, 2013
125
0
10,710


It could have affected your RAM. I have heard of this exact problem being caused by bad RAM. Try a different stick.
 
Solution

Edgar Villalba

Reputable
Jul 26, 2015
16
0
4,510


and even if memtest86 gives no errores? ok i will test it