Solved BSOD caused by ntoskrnl.exe

[Hykon]

I tried the swapping out the cables and even using different SATA ports. I also tried installing Windows on my HDD.

Since this is my first build, I don't have any other parts to swap out in an attempt to isolate the disruption.

Although, after changing my memory timings, this problem seemed to almost entirely fade away. I have had one BSOD in the last 4 days or so of continuous usage when before I was averaging at least a BSOD per hour. essenbe helped me get to that point. The problem may not be entirely gone, but for now I can deal with it until I can possibly get another mobo or PSU to see if that helps anything.

Thank you very much for your detailed analysis of my dump files. I was never able to realize what exactly was going wrong until you explained it.

 

[essenbe]

If you have recently bought the motherboard, you have a warranty and can RMA it. I would go that route before buying a new one or just putting up with the problem.

 

[Britton30]

did you try what I suggested in post #94?

 

[Hykon]

No, I haven't used the proper memtest to check my RAM. But from what Vir Gnarus said, RAM isn't the issue that causes my error. I could still try though. Still, I'm content currently as I haven't had any issues lately besides that one random BSOD the other night. The system is far more stable than what it was a week ago.

 

[Britton30]

I tried the swapping out the cables and even using different SATA ports. I also tried installing Windows on my HDD.

Since this is my first build, I don't have any other parts to swap out in an attempt to isolate the disruption.

Although, after changing my memory timings, this problem seemed to almost entirely fade away. I have had one BSOD in the last 4 days or so of continuous usage when before I was averaging at least a BSOD per hour. essenbe helped me get to that point. The problem may not be entirely gone, but for now I can deal with it until I can possibly get another mobo or PSU to see if that helps anything.

Thank you very much for your detailed analysis of my dump files. I was never able to realize what exactly was going wrong until you explained it.

I was going by your statement above in red.

 

[Vir Gnarus]

This problem could be caused by memory issues, because it deals with the act of pulling drive data and placing it into memory. While the error code itself does not specifically point to a memory problem, there could be an instance where the device object it was trying to point to got smudged by a memory error. I wouldn't be able to analyze if this was the case or not without access to a kernel dump (MEMORY.DMP in Windows directory). Regardless, having it this consistent kinda has me believe otherwise, as if it was a memory issue, it would most certainly be causing a whole variety of bugcheck codes. Plus, the most common cause I've had with 0xF4 bugchecks is because of a disk I/O issue, of which this is also one.