What causing of this memory.dmp

[DC Support]

Hi there

We have this iMac machine that running on Windows 10 and it's been running ok and deployed to the to the user. The user has admin access to the machine so he can install any updates softwares/devices.

A week later, we have BSOD on here's the memory dump that I ran via http://www.osronline.com/dump

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.63.amd64fre.th2_release.160104-1513
Machine Name:
Kernel base = 0xfffff800`4ba12000 PsLoadedModuleList = 0xfffff800`4bcf0c70
Debug session time: Wed Feb  3 20:12:26.513 2016 (UTC - 5:00)
System Uptime: 0 days 0:00:15.221
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: ffffd00135ac9a70, (reserved)
Arg3: 0000000000000002, (reserved)
Arg4: ffffffffc000014c, usually the NT status code.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x74

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8004bfca577 to fffff8004bb54770

STACK_TEXT: 
ffffd001`35ac9998 fffff800`4bfca577 : 00000000`00000074 00000000`00000002 ffffd001`35ac9a70 00000000`00000002 : nt!KeBugCheckEx
ffffd001`35ac99a0 fffff800`4ba1b125 : 00000005`b59bbfff ffffe000`83d2a080 fffff800`4bf26d88 00000000`00000002 : nt! ?? ::NNGAKEGL::`string'+0x61d27
ffffd001`35ac9c10 fffff800`4bb59916 : ffffd001`39444180 ffffe000`83d2a080 fffff800`4ba1b0e4 00000000`00000246 : nt!PspSystemThreadStartup+0x41
ffffd001`35ac9c60 00000000`00000000 : ffffd001`35aca000 ffffd001`35ac4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+61d27
fffff800`4bfca577 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+61d27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  568b1c58

FAILURE_BUCKET_ID:  X64_0x74_nt!_??_::NNGAKEGL::_string_+61d27

BUCKET_ID:  X64_0x74_nt!_??_::NNGAKEGL::_string_+61d27

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

We know it's a driver issue but we can't pin point what it is. I got a feeling it's something to do with Brother printer which they said it's compatible with Windows 10 but the installation is labelled Windows 8. Again it could be something else.

Any ideas what causing this?

 

[Trouble]

Looks to me like the bugcheck is pretty much telling you that it is a registry problem.
Does the machine boot at all? Can or have you done a system restore to an earlier point in time?
Have you gotten other BSODs on this computer? Are they always the same error? Is this the one and only?