Windows 10: BSOD caused by ntsoskrnl.exe

So uh, yeah, this is causing me issues.

Attachment 42120

:)

 

BSOD Caused by ntoskrnl.exe

It doesn't all of a sudden turn of, before it turns of the blue screen error thing pops up first then it restarts. Forgot to mention, blue screens are also much more frequent when I use it in battery saver for some
reason. I did fully remove avast as you posted. Am currently in University so I don't have any fans lying around, but I will go out to get one during the week. It did BSOD once yesterday link 031818-19750-01 1.dmp

 

BSOD Caused by ntoskrnl.exe

The crash dump says a Cache error in the processor was observed:

Error : DCACHEL0_EVICT_ERR (Proc 2 Bank 1)

Status : 0xbb80000000000174

Looks like the processor is either failing or overheating.

BCC124 General guide:

https://answers.microsoft.com/en-us/windows/wik...

Please run IPDT and post back the results:

https://downloadcenter.intel.com/download/19792...

 

Hi Nosco,

Please test your memory
Code: Probably caused by : memory_corruption[/quote]




Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Hello hello, I've left it running for a long time and 8 passes have occurred without anything red appearing.

My ram frequency on paper is 1600 but in bios it says 1300, possible cause?

I did make a thread before and I was getting NTFS bsods as well. You told me to run seatools and chkdsk and they turned out fine, but I am not convinced that the hdd is fine because its an old hdd (like 8 months, which was used in a very bad pc that consistently was plagued with bsod issues).

 

The frequency could be the cause yes.

An HDD of 8 months isn't old at all, but not new either.
The average age of an HDD before it starts failing is a few years.

A BSOD has many causes depending on what the error code is like

• memory issues
  • non-volatile (HDD/SSD)
  • volatile(RAM),
• RAM frequency,
• dust,
• component not properly connected or wrong connected,
• broken connection, can be seen as not properly connected
• drivers out of date,
• overclocking,
• bugs in drivers
• GPU damage,
• PSU problems, but this would more give a sudden shutdown or reboot
• bugs in Windows (rare but fixable via SFC/DISM and Windows Update)
• Motherboard failure or faulty
• software not properly coded, in the past the Nvidia Streamer Service was giving problems and same with Google Chrome (Chrome could be still current)
• BIOS settings
• BIOS bugs

 

Right so, I enable xmp and it changed to 1600. I'll let you know if I get anymore bsods. If I do, I will inform you.

But if I do, should I reinstall my windows, since I used to received NTFS bsod causes and let you know if that improved anything?

 

There is for now no reason to reinstall Windows, you have no failing hard drive so if there is NTFS activity it is definitely something else.

FYI, I see in your previous thread you edited a few times your last post.
Please don't edit posts after a few hours, I won't be notified with edited posts but I do get notified with new posts.
This is the reason why I have never answered your question.

 

Okay, sorry. So uh, what could be causing NTFS then?

I did do an upgrade from Windows 7 to 10 without a clean install.

 

In that case it is an option to do a clean install, with the upgrade there are a lot bugs coming your way which can't be avoided without a clean install.

 

Ahhh, I should've guessed. Thank you very much for the support. Luckily I have an ISO, just have to create it on my USB.

If no BSODs occur for a week after the re-install, I'll mark the thread as solved.