Windows 10: BSOD normally caused by ntoskrnl.exe but sometimes different.

Hello, i have been getting bsods for months now.
I have tried updating drivers, totally resetting the computer, scanning for viruses / malware i also scanned for errors on seatools for dos and it found some and fixed them and didn`t crash for 5 days so i thought i had fixed it but i just had another bsod..
here`s the log collecter info : Attachment 121203

:)

 

0x139 Bug check BSOD happening a lot.

i only know from bluescreenview that the bsods were caused by ntoskrnl.exe and sometimes random drivers.

heres the link to the skydrive containing the 32 minidumps: OneDrive

 

BSOD errors without an identifiable cause

Okay I may or may not be onto something now. Since, from what I've read, it seems that most ntoskrnl.exe BSODs are not actually caused by ntoskrnl, but by another driver that takes up the krnl's space. When ntoskrnl.exe finds it, it throws the system into
a BSOD to prevent damage. Looking the the dump files, I found that there was a driver called hal.dll, but the crash address was different from the driver address. The crash address was ntoskrnl.exe+14ec00, the same as my above post. There is also another driver
called dxgmms2.sys who's crash address was ntoskrnl.exe+14ec00. I'm not sure if this will help or if it means anything but I'm looking for anything at this point.

 

*Arrow Run HDTune to

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

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

Attachment 121296Attachment 121293Attachment 121294Attachment 121295

 

Please run chkdsk again, same command.

 

Let us know if the problem occurs again *Smile

 

got another bluescreen this time it said driver not less or equal Attachment 121389

 

How old is the hardware?

 

I got the pc in 2015, not sure if it was used before me though.

 

Just had another blue screen. I really hope my computer isn't totally broken and its fixable. Here is the log collector thing:Attachment 122024

 

I would suggest to try another drive, install Windows on it and see how it goes.

 

Do you have a spare hard drive or could you borrow one to install Windows on for testing?
This is a test to confirm if my suspicious about the hard drive failing is right.

 

No, i don't think a spare hard drive would be possible, is there not anything else it could be? *Sad

 

I don't think so, various BSODs and these kind of event logs point to the HDD.
Code: Event[2220]: Log Name: System Source: disk Date: 2017-02-10T16:13:42.608 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-NLF5JQL Description: The device, \Device\Harddisk0\DR0, has a bad block.[/quote]