Hello,

I was hoping someone could help me out here. Let me describe the issue. For quite a while I was using Windows 8.1 fine and did not have any problems, however I recently burned my PSU somehow and then the problems started. Which I somewhy find odd, cause the BSoD's are related to a driver issue(?). The driver which seems to cause the problem, is Intel(R) Engine Management Interface.

"This device cannot start. (Code 10)

A device which does not exist was specified"

Event Viewer displays the following error:
"Intel(R) Engine Management Interface driver has failed to perform a handshake with the Firmware."

Since it says "A device which does not exist was specified.", I assume I don't need this driver at all, so I tried disabling it and uninstalling, but it keeps coming back every time I restart my PC. I even tried looking for a newer driver, but couldn't find anything. The newest driver is for Windows 7 x64/x86. I found out you could possibly disable it in bios, but I couldn't find the option to do so in my bios. I went thru every option 1 by 1, just to make sure, I wouldn't miss it.

Here's my PC:

Motherboard: Gigabyte GA-H55M-S2 (F4 BIOS)
CPU: Intel i3 540 @ 3.07GHz (Overclocked to 4,03GHz)
Cooler: Cooler Master Hyper 212 EVO
GPU: NVIDIA GeForce GTX 660 (GV-N660OC-2GD)
RAM: 2 x Kingston 4GB 1333MHz DDR3
HDD: Western Digital 500GB

At the very moment, I have installed a fresh copy of Windows 8.1 Professional x64 and the problem still seems to exist. I have tried and googled for everything I can think off, now I'm just stuck at this problem.

I hope someone can help me out here, or at the very least, guide me in the right direction.

Link to minidump: http://1drv.ms/1H6E4uh

• Edited by HaiK1NG Thursday, March 19, 2015 6:27 PM Added download for minidump

I'm sorry, it said I'm not allowed to post links and/or images until my account has been approved as I was posting this question. I've uploaded 3 BSoD mini dumps in a zip file to my OneDrive, however I believe the first one (oldest), might be related to something else (random).

I would also like to add, that I sometimes have trouble starting windows, as it freezes/hangs at loading screen, where the circle goes around. As well as sometimes the computer just randomly restarting w/o a blue screen or anything at all (instantly). Sometimes it freezes the screen, where it should show a blue screen, but it doesn't. After a short period of time, it restarts PC and a mini dump is created (despite the fact, I didn't see an actual blue screen, just a frozen image of what I was viewing at the moment of crash).

Here's a link to download: http://1drv.ms/1H6E4uh

• Edited by HaiK1NG Thursday, March 19, 2015 5:43 PM

I ran the verifier, rebooted PC and I'm currently waiting for a BSoD, I will upload and post the dumps later. I'm assuming the bad driver is Intel Engine Management Interface, if that's the case, how can I remove it? Disabling it doesn't seem to help and uninstalling does nothing, as it comes back after every reboot.

Also, sometimes it just reboots instantly, no BSoD or nothing, what could this mean?

I have a feeling it might be a bad memory slot on motherboard as well or something like that, so I will run the memtest at night

• Edited by HaiK1NG Friday, March 20, 2015 11:50 AM

Apparently there's a lot more errors, not just the Engine Management Interface one.

Here's a link to OneDrive download: http://1drv.ms/1DFIjvC

• Edited by HaiK1NG Friday, March 20, 2015 4:22 PM

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8012d4359f0, 2, 8, fffff8012d4359f0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+23a )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8012d4359f0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8012d4359f0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80108f64138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 fffff8012d4359f0 

CURRENT_IRQL:  2

FAULTING_IP: 
+8c228a89b114
fffff801`2d4359f0 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  svchost.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  ffffd00027a58120 -- (.trap 0xffffd00027a58120)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0a00000000000020 rbx=0000000000000000 rcx=0000000000000002
rdx=fffff8012d4359f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8012d4359f0 rsp=ffffd00027a582b0 rbp=0001da10001da171
 r8=00000000001da130  r9=02200000001da347 r10=7100a1ef05420000
r11=0000000000000042 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff801`2d4359f0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80108d5d4e9 to fffff80108d519a0

FAILED_INSTRUCTION_ADDRESS: 
+8c228a89b114
fffff801`2d4359f0 ??              ???

STACK_TEXT:  
ffffd000`27a57fd8 fffff801`08d5d4e9 : 00000000`0000000a fffff801`2d4359f0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffd000`27a57fe0 fffff801`08d5bd3a : 00000000`00000008 ffffe000`8f89b0f8 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`27a58120 fffff801`2d4359f0 : 00000000`00000000 00000000`00000000 00000000`000e293f 00000000`00000000 : nt!KiPageFault+0x23a
ffffd000`27a582b0 00000000`00000000 : 00000000`00000000 00000000`000e293f 00000000`00000000 00000000`0001358b : 0xfffff801`2d4359f0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+23a
fffff801`08d5bd3a 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+23a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54c832b2

IMAGE_VERSION:  6.3.9600.17668

BUCKET_ID_FUNC_OFFSET:  23a

FAILURE_BUCKET_ID:  AV_CODE_AV_BAD_IP_nt!KiPageFault

BUCKET_ID:  AV_CODE_AV_BAD_IP_nt!KiPageFault

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_code_av_bad_ip_nt!kipagefault

FAILURE_ID_HASH:  {73cd60cc-83fa-6b76-df08-1961c31d7403}

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

It points to incorrect memory page access obviously. It generally caused by some driver like you found. update all drivers should be resolved. Have you tried ever?

• Edited by Chilam.Wa Tuesday, March 24, 2015 9:43 AM additional