Windows 10: BSOD Crash ntoskrnl.exe

**EDIT** Added Complete Log files.

I keep getting BSOD's with Strings like: KERNAL_STACK_INPAGE_ERROR, MEMORY_MANAGEMENT, REFERENCE_BY_POINTER, BAD_POOL_HEADER, ETC..

I've ran memory test and checked HDD. I'm not seeing any issues there. Can someone please take a look? I would greatly appreciate it.

PS. DM log collector tool hangs on the MSINFO collection. It won't finish. I'll upload what it was successful at grabbing. *Mad

:)

 

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.

 

ntoskrnl.exe constantly BSODing or crashing applications

Like the subject says ntoskrnl.exe keeps crashing every application and sometimes makes me BSOD. Any way to fix?

 

I'm re-running Memtest86.. figure I'll be asked to anyway so might as well get started. *cry

 

Yes, better you do it first. The versatility of the bugchecks and lack of flagged drivers is giving an impression that a complete test of RAM would be very necessary.
Test your RAM modules for possible errors.MemTest86+ - Test RAM Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

Depending on the result, we have to decide our next step.

 

On it. Thank you, sir.

 

Try running DM log collector as Administrator.

 

It just sits there after it gathers the msinfo data..

Also, my son turned the computer off during Memtest86. Last I saw it was at 14hours and 5 passes with no errors. I'll run it again tonight. FML.

Attachment 88594

 

Gathering the msinfo data takes some time, because it is a lot to gather. It could take some minutes before it is finished.

 

Hah, that took much longer than I had anticipated. You're a saint. Thank you. Attachment 88625