You are the IT professional who work in an International company named Wiikigo. You are experienced in troubleshooting operating systems and applications that are not working correctly, identifying code defects and so on. You have enough knowledge on windows internals and you provide technical support for the company. There is a complete kernel dump that was generated on an unresponsive computer. You debug the kernel dump by using WinDbg.

You receive the following output from WinDbg.

kd> kv

ChildEBP RetAddr Args to Child

f9bfeed8 f98857fa 000000e2 00000000 00000000 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])

f9bfeef4 f9885032 00644d40 010000c6 00000000 i8042prt!I8xProcessCrashDump+0x237 (FPO: [Non-Fpo])

f9bfef3c 8054093d 815c84c8 81644c88 00010009 i8042prt!I8042KeyboardInterruptService+0x21c (FPO: [Non-Fpo])

f9bfef3c f9e9938a 815c84c8 81644c88 00010009 nt!KiInterruptDispatch+0x3d (FPO: [0,2] TrapFrame @ f9bfef60)

WARNING: Stack unwind information not available. Following frames may be wrong.

f9bfefd0 80540f7d f9e998a0 00000000 00000000 pldkrl+0x38a

f9bfeff4 80540c4a f7627b50 00000000 00000000 nt!KiRetireDpcList+0x46 (FPO: [0,0,0])

f9bfeff8 f7627b50 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a (FPO: [Uses EBP] [0,0,1])

80540c4a 00000000 00000009 bb835675 00000128 0xf7627b50

kd> .trap f9bfef60

ErrCode = 00000000

eax=ffdff980 ebx=ffdff000 ecx=f9e9938a edx=f9e998a0 esi=00000000 edi=806d02e2

eip=f9e9938a esp=f9bfefd4 ebp=ffdff980 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0000 es=e8ae fs=0000 gs=c20e efl=00000246

pldkrl+0x38a:

f9e9938a ebfe jmp pldkrl+0x38a (f9e9938a)

You have to find out what is causing the computer to become unresponsive. So what is causing the problem?

A.
It is caused by a stack overflow.

B.
It is caused by an infinite loop.

C.
It is caused by an invalid DPC pointer.

D.
It is caused by an invalid jump instruction.