First of all, I'd have to apologize for my English.

I've experienced a lots of BSOD's for about the last six months, but haven't succeed to fix it, and I hope you guys will find it out.

I'll attach DMP and the string I'd found a bit weird.

Summary: Infocare (IBM/Lenovo's NBD-guys) has been here for like four times now, and did change the motherboard and one RAM-module. First we got MEMORY-BSOD's, but infocare nor me did find any issues regarding the RAM. But after the switch, no BSOD-parameter tells me that it is MEMORY anymore, but "WIN8_DRIVER_FAULT".

Did re-install it a while back ago (e.g four months ago-ish) but the problem did persist, and we thought it were hardware related, but after all the hardware exchange, our minds go to software. I'm confused, yeah.

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x13C

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8032aa0b50b to fffff8032a5d59a0

STACK_TEXT:  
ffffd000`28306b48 fffff803`2aa0b50b : 00000000`0000013c ffffe000`e43f81c0 00000000`00000001 00000000`00000000 : nt!KeBugCheckEx
ffffd000`28306b50 fffff803`2a850100 : 00000000`00000000 00000000`00000000 ffffe000`e43f81c0 ffffe000`de248540 : nt! ?? ::NNGAKEGL::`string'+0x5929b
ffffd000`28306bc0 fffff803`2a4f16cf : 00000000`00000000 fffff803`2a743fe0 ffffe000`e43f81c0 00000000`00000000 : nt!ObpRemoveObjectRoutine+0x64
ffffd000`28306c20 fffff803`2a52db01 : ffffe000`e43f81c0 ffffe000`e43f8750 ffffe000`e23a7040 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0x8f
ffffd000`28306c60 fffff803`2a5303ac : fffff803`2a52da60 fffff803`2a743fe0 ffffe000`e23a7040 fffff803`2a737300 : nt!PspReaper+0xa1
ffffd000`28306c90 fffff803`2a55d280 : 00000000`00000000 ffffe000`e23a7040 00000000`00000080 ffffe000`e23a7040 : nt!ExpWorkerThread+0x28c
ffffd000`28306d40 fffff803`2a5dbfc6 : ffffd000`6892e180 ffffe000`e23a7040 ffffe000`de34d880 00000000`00da7a64 : nt!PspSystemThreadStartup+0x58
ffffd000`28306da0 00000000`00000000 : ffffd000`28307000 ffffd000`28301000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+5929b
fffff803`2aa0b50b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+5929b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0c2f7

BUCKET_ID_FUNC_OFFSET:  5929b

FAILURE_BUCKET_ID:  0x13C_nt!_??_::NNGAKEGL::_string_

BUCKET_ID:  0x13C_nt!_??_::NNGAKEGL::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x13c_nt!_??_::nngakegl::_string_

FAILURE_ID_HASH:  {81c667ca-13fd-6170-97a0-9063500f733d}

Followup: MachineOwner
---------

https://sftp.geodata.no/public/file/Ml2QywkOuU2OTDfsRrnXww/MEMORYFELIPE.DMP (Password: "password")

Thanks in advance, and I have a good feeling about you guys solving this problem.

-Ed

ED

Happy to help but on my 300Mb D/L link the MEMORY.DMP of 700+ Mb is downloading at 5Mb.  Do you have a minidump, or can you put the full DMP elsewhere?

Hello Team ZigZag,

@ 5Mbps it shouldn't take too long. 
Where do you want me to put it? Where are you located?

Do not have access to a minidump.

Ty!

https://sftp.geodata.no/public/file/G3nC6SzZFUaBXkdIbxL7eA/MEMDUMP.rar

That should work.

Ed

No worries I will just let it run in the background.

This was related to memory management and 99% of the time it is a mis behaving driver so changing hardware would not have helped. I would run driver verifier to find the underlying driver.