ndis.sys+2e503 ntoskrnl.exe+5024ec & ntoskrnl.exe+c0738 are causing BSoD

exodasius

Honorable
Dec 25, 2012
150
0
10,710
Hi everyone.

So, originally, I was getting a BSoD every other day (sometimes sooner, sometimes later) because of ntoskrnl.exe+c0738. However, I decided to run driver verifier to see if there were any other issues which could be causing this, and sadly, I discovered that ndis.sys+2e503 and ntoskrnl.exe+5024ec were also giving trouble too (I know this because they're highlighted red in bluescreenview).

The BSoD started randomly, I didn't downloaded anything to cause it (this was around a month ago), although the possibility of a bad software update can't be ignored. This problem doesn't happen when I switch to an SSD as my primary hard drive, so I know that this is a driver issue and not a ram problem. My computer is 3 years old (built it), and it hasn't given any problems up until a month and a half ago (the BSoD were insane until I changed CPU coolers, so it probably started as a heat issue). I have the complete logs for my 3 last crashes (first one is w.o driver verifier, the 2nd and 3rd are with it.

Does anyone know what the solution to this problem is?

Thanks
 
Solution
Well the thing is that you did what we in the repair field call process of elimination so we know that it is no other hardware in your PC except, possibly, your HDD.

It could be software but BSOD caused by software are very rare.

What are the exception codes you are getting? Have you run a full hard drive diagnostic on the HDD?

exodasius

Honorable
Dec 25, 2012
150
0
10,710


The thing is, the SSD is right now just a clean windows installation. It has nothing on it, and there's no (other) indication that my hard drive is failing.
 
Well the thing is that you did what we in the repair field call process of elimination so we know that it is no other hardware in your PC except, possibly, your HDD.

It could be software but BSOD caused by software are very rare.

What are the exception codes you are getting? Have you run a full hard drive diagnostic on the HDD?
 
Solution