Exception error code

[Jared]

Do you have any idea what this exception error code means?

0x80000004 (2147483652) - No such interface supported

I'm guessing it means the device tried to access something that just wasn't supported at all but I can't find anything on it apart from an IE error...

 

[niemiro]

It could be a driver bug, but I don't think that's likely. Much more likely to be a corruption, either in the registry (registration of DLLs, COM components etc.), or in the file system. First port of call would be to run sfc /scannow and see if you can dig out a corrupt file. If that doesn't work, see if you can find an Event Log entry which matches up. Hopefully that will include a full CLSID which you can then trace, then re-register that DLL on the OP's computer.

The reality is though that this error is very hard to fix, and a lot of the time you probably won't manage to find the corruption if it lies in the registry. It could be in very many places (I've only mentioned the common ones we can fix, but there are many others, most of which I don't know).

 

[Jared]

Thanks a lot Richard, this is the callstack which I find... interesting to say the least.

ffffd000`a89d1108 fffff800`4164befb : 00000000`0000001e ffffffff`80000004 fffff800`415cc081 ffffd000`a89d2128 : nt!KeBugCheckEx
ffffd000`a89d1110 fffff800`415d5846 : 00000000`00003000 00000000`00000000 00000000`00000020 00630061`0050013e : nt!KiFatalFilter+0x1f
ffffd000`a89d1150 fffff800`415b3d56 : 00350037`00390032 007e0039`00310037 00660062`00310033 00360035`00380033 : nt! ?? ::FNODOBFM::`string'+0x696
ffffd000`a89d1190 fffff800`415cc1ed : 00000000`00000000 ffffd000`a89d1330 ffffd000`a89d2128 ffffd000`a89d1330 : nt!_C_specific_handler+0x86
ffffd000`a89d1200 fffff800`415593a5 : 00000000`00000001 fffff800`41471000 ffffd000`a89d2100 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd000`a89d1230 fffff800`4155825f : ffffd000`a89d2128 ffffd000`a89d1e30 ffffd000`a89d2128 00000000`00000100 : nt!RtlDispatchException+0x1a5
ffffd000`a89d1900 fffff800`415d08c2 : fffffff6`00000002 00000001`ffffffff 00000000`00000004 fffff800`4140769a : nt!KiDispatchException+0x61f
ffffd000`a89d1ff0 fffff800`415cdea2 : 0000000f`00000000 00000001`00000003 00000000`fffffffd ffff3ab6`38d07ab8 : nt!KiExceptionDispatch+0xc2
ffffd000`a89d21d0 fffff800`415cc081 : fffff800`4141076a 00000000`00000000 ffffe000`b64d9b40 ffffe000`b55e1b20 : nt!KiDebugTrapOrFault+0x1a2
ffffd000`a89d2368 fffff800`4141076a : 00000000`00000000 ffffe000`b64d9b40 ffffe000`b55e1b20 00000000`00000002 : nt!RtlCopyMemoryNonTemporal+0x61
ffffd000`a89d2370 fffff800`41428dc8 : 00000000`00000410 ffffe000`00000410 ffffe000`b5dba410 00000000`00000100 : hal!HalpDmaSyncMapBuffers+0x112
ffffd000`a89d2430 fffff800`41427c47 : 00000000`00000000 00000000`00000501 ffffe000`b8474c08 ffffe000`b8463a80 : hal!HalpDmaMapScatterTransferV2+0xfc
ffffd000`a89d2490 fffff800`41422ad9 : ffffe000`b8474c08 00000000`00000501 ffffe000`b5dba3d0 ffffe000`b8463af8 : hal!HalpMapTransferV2+0x7f
ffffd000`a89d2520 fffff800`41429681 : ffffe000`b8474c08 00000000`00000501 ffffe000`b5dba3d0 ffffd000`a89d2610 : hal!IoMapTransferInternal+0x11c75
ffffd000`a89d2570 fffff800`41427b49 : ffffe000`b7c64050 ffffe000`b8463a80 ffffe000`b8474b01 22406b18`000005ac : hal!HalpAllocateAdapterCallbackV2+0xd5
ffffd000`a89d2610 fffff800`4141eb8e : ffffe000`b7c64050 ffffe000`b5dba410 ffffe000`b5dba3d0 ffffe000`b8474bc0 : hal!HalAllocateAdapterChannelV2+0x129
ffffd000`a89d2650 fffff800`cfc7110b : ffffe000`b5dba3d0 ffffe000`b7c64050 ffffe000`b5dba3d0 ffffe000`b5dba410 : hal!HalBuildScatterGatherListV2+0x1735e
ffffd000`a89d26f0 fffff800`d0af2638 : ffffe000`b845e000 00000000`00000000 ffffe000`b8467210 ffffd000`a89d2800 : ndis!NdisMAllocateNetBufferSGList+0x10b
ffffd000`a89d27b0 ffffe000`b845e000 : 00000000`00000000 ffffe000`b8467210 ffffd000`a89d2800 ffffe000`b8474bc0 : Rt630x64+0x12638
ffffd000`a89d27b8 00000000`00000000 : ffffe000`b8467210 ffffd000`a89d2800 ffffe000`b8474bc0 00000000`000001c0 : 0xffffe000`b845e000

The cause is seems pretty obvious but I'm always interested into why it happened.
Why was that particular exception error generated?

sfc /scannow would be a good choice though.

 

[Patrick]

WinDbg mislabels this exception (afaik) in a way similar to how it labels a misaligned IP to a hardware fault, and it's better known as a single-step exception. Generally it's caused by what Richard mentioned (OS corruption), however bad RAM or a buggy driver can cause this exception to be thrown as well. I've seen it occur more in user mode apps than I have in kernel-mode.

In your case, it looks like the Realtek drivers was the root cause (maybe).

 

[Jared]

Thanks a lost Patrick.