BSOD at random moments (ntoskrnl.exe seems to cause it)

[LynG3]

Hello

im getting furstrated with the setup i built in this summer, because it seems to crash at the most random points and it is not constant it is sporadic, it can happen twice a day and then not happen for three weeks.

the setup that i am running is:

I7-4790 3,60GHz
MSI Z97S SLI krait edition (MS-7922)
Kingstion fury 1600Mhz 2x8GB
MSI Geforce GTX 960 2GB
WD blue 1TB
Samsung 850 Evo 250GB SSD
CoolMaster V550S, 550W gold edition

i have tried trouble shooting the hardware by testing the ram one at the time, running memtest on the drives. I have tried to look for the problem in the event manager and form the program Whocrashed, from here it seems that the ntoskrnl.exe might be to blame, but from what i know that is almost never true.

Some times when it BSOD it does not leave a dump file which i find wierd, and when it BSOD's it does not give a clear reason to why it did it, i have tried to google the error codes form the BSOD but that was in vain. So now im here asking for help since i cant seem to trouble shoot this problem whihc i think is software related.

i have attached the zip file you guys ask for, and i picture of the BSOD that comes(sry for the poor quality).

i hope you can help me
Regards
Jacob

 

[LynG3]

anyone?

 

[LynG3]

please help

 

[axe0]

I assume you're still requiring help?
I have a thought what is common with the 0xF4 and seeing there are no dumps since november 2015 it almost confirms it.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

 

[LynG3]

Hey Axe

yes i still require the help as i have not stumbled upon a sure idication of this being gone for good

i just have a question for these tests shall they be preformed on all harddrives in the setup or just the main?

 

[axe0]

For each of them you can choose what hard drive or partition you run them on
For SeaTools and HDtune it is per hard drive, for chkdsk it is per partition.

 

[LynG3]

i will do the test ASAP and get back to you when i have all of what is written
i should state that i updated the firmware of the SSD, after posting the first
post. However we might as well check all this to see if anything else is at fault.

 

[TheSasswagon]

I have had the same BSOD issues, and have the same Motherbord, SSD, and HDD as you. I've been searching for solutions since last October without much luck. I have around 50 mini dump files pointing to ntoskrnl.exe and it doesn't always seem to leave a dump file.

Here is a link to my thread on tom's hardware: Irregular BSOD over three months, ntoskrnl.exe - Windows 7 - Windows 7

It's the only place I got any kind of response, though nothing they suggested helped.

Might be different issues, but I thought since we have the same drives and motherboard along with the same (seeming) issues, I'd throw in my hat too. Its nice to know I'm not the only one with these problems.

 

[LynG3]

hey axe0

sry i didnt post sooner but was away one week because of work i have just now done the things you asked me, The seatools tests showed no errors at all and the disk check the same. I ran all the test with HDtool and i have compressed the screenshots into a rar file and attached them here.

i have had one bluescreen in the last week however it didnt leave any dumpfile and the error code was still the same as the others.

 

[axe0]

What was the bugcheck of the bluescreen you had?

 

[LynG3]

well i have a foto of it here

 

[axe0]

Is the cable that connects the drives damaged or improper connected?

 

[LynG3]

hmm i dont belive so, i have checked that a couple of times and had nearly the whole setup taken out and put backtogether again without noticeing something like that.

however i can check the cables again if that is nesecary

 

[axe0]

Please check the cables including the connections, it is certainly necessary.
A 0xF4 and no dump refers to the hard drive, even though the tests don't find anything.
A next step could be a vanille installation, meaning a clean installation of an updated Windows 7 installation with nothing installed but Microsoft Security Essentials. If with a vanille installation your system still crashes it is either a bad connection on the motherboard, the cable or hard drive.

 

[LynG3]

I am currently not in the reach of the computer however from what i am told the cables doesnt look damaged or anything, however i will check them my self tmrw and post in the evening my results.


The clean installation of Windows 7 with only Microsoft security essentials, might be a little bit problematic just to keep it that way since the BSOD doesnt appear at any specific points so it could take weeks before the BSOD will appear again, however if it is what is neeeded to find the problem i will try to do that.

i will first personally check the connections and then get back to you, and thank you for the help so far.

 

[LynG3]

i decieded that i will try to replace all the sata cables, before the clean install jsut to eliminate that possibility

 

[axe0]

Keep me posted

 

[LynG3]

i will post as soon as it does it again if it does BSOD again after the replacement.

 

[LynG3]

apparently putting in new cables didnt fix the problem as it is now the same fault as before appeared again. The next thing for me as previously mentioned will be to try and repair the installation of windows 7 before doing the discussed clean install.


Update***
the BSOD apperently cause microsoft office programs files to not work anymore after the BSOD and stating that they need a reinstall.

 

[LynG3]

well a repair didnt fix things so now i have reinstalled windows 7 on the pc hoping that this will fix the problem i will keep you posted