Unexpected kernel trap mode error

I installed windows8  in my lenovo G580. . . But when i connect to internet in 15-20 minute. . .My laptop restart  with bluescreen and show unexpected kernel trap mode error. . . Plizz Help

My 5 mini dump file is here => http://www51.zippyshare.com/v/30900556/file.html

You are aware that these dump files are ~2 to 3 months old, correct? Anyway, we have various different bug checks from the attached DMP files:


This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

If we take a look at the call stack (warning, it's quite large):

WARNING: Stack unwind information not available. Following frames may be wrong.
afd5cffc 92f7067c 89783000 afd5d074 afd5d024 igdkmd32+0x196d00
afd5d00c 92f6c574 88ad0970 afd5d074 88a52614 igdkmd32+0x13467c
afd5d024 92e60892 88a4e000 afd5d074 00000000 igdkmd32+0x130574
afd5d084 92f0a03e 88a4e000 afd5d5bc 88a4e000 igdkmd32+0x24892
afd5d5d4 92f0a3dd 88a4e000 00000000 afd5d630 igdkmd32+0xce03e
afd5d5e4 92eb29b2 88a4e000 00000000 88a4e000 igdkmd32+0xce3dd
afd5d630 92e5833f 88a4e000 00000000 00000000 igdkmd32+0x769b2
afd5d684 9040b12a 88a4e000 00000000 afd5d798 igdkmd32+0x1c33f
afd5d698 818efba9 8038e840 88833248 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x2c
afd5d6ac 8198567d 8038e840 88833248 a4d6887d nt!KiInterruptMessageDispatch+0x12
afd5d6ac 8187fcfb 8038e840 88833248 a4d6887d nt!KiInterruptDispatch+0x6d
afd5d798 8187f7b6 884c1998 884c1998 856105d8 nt!SepNormalAccessCheck+0x113
afd5d864 8187f1e9 856105c4 00000000 00000001 nt!SepAccessCheck+0x163
afd5d94c 818a8503 856105c4 00000000 afd5d988 nt!SeAccessCheckWithHint+0x3a0
afd5d998 8bb90bff 856105c4 884c1998 00000000 nt!SeAccessCheckFromStateEx+0x52
afd5d9f8 8bb915cd 00000000 afd5da34 00000000 NETIO!KfdReleaseCachedFilters+0x24a
afd5da58 8bb8e76d 8a1c0178 afd5df40 85613978 NETIO!KfdReleaseCachedFilters+0xc18
afd5dc88 82087257 0000002c afd5df40 85613978 NETIO!KfdClassify+0x25d
afd5ded8 82079408 afd5df40 00000000 00000000 tcpip!WfpAleClassify+0x50
afd5dfb4 820797bf 85969120 0000002c 00000002 tcpip!WfpAlepReauthorizeInboundConnection+0x8d0
afd5e054 8207745d 00000011 8585c750 00000000 tcpip!WfpAleReauthorizeInboundConnection+0xc2
afd5e13c 8207df38 00000002 00000000 884a70bc tcpip!WfpAleReauthorizeConnection+0x2a9
afd5e234 82086408 85969120 00000002 8585c750 tcpip!TlShimOptionalReauthorizeConnection+0x3c1
afd5e32c 8208c051 00000011 00000002 00006c07 tcpip!ProcessALEForTransportPacket+0x181
afd5e72c 8208cfbd 00000002 00006c07 00006cf0 tcpip!WfpProcessInTransportStackIndication+0xb5e
afd5e7a8 8208dbb7 85969120 00000002 00006c07 tcpip!InetInspectReceiveDatagram+0x105
afd5e868 8208d88b 8578e8a0 00000014 8a3a41e8 tcpip!UdpBeginMessageIndication+0x4f
afd5e924 8208d4f9 85492ba4 afd5e950 afd5e954 tcpip!UdpDeliverDatagrams+0x9d
afd5e9d4 8208d11f 8578e8a0 8a3a41e8 afd5ea10 tcpip!UdpReceiveDatagrams+0x251
afd5e9e4 8208a462 afd5e9f4 8214efc8 8578e8a0 tcpip!UdpNlClientReceiveDatagrams+0x12
afd5ea10 8208a0d0 00000011 00000000 8214efc8 tcpip!IppDeliverListToProtocol+0x3a
afd5ea4c 82089bc9 8214efc8 afd5eaac afd5eaa4 tcpip!IppProcessDeliverList+0x53
afd5ead8 820787ae 8214efc8 afd5eb14 82151770 tcpip!IppReceiveHeaderBatch+0x1c1
afd5eb38 820778c8 8a3a41e8 8a3a41e8 857d4940 tcpip!IppLoopbackIndicatePackets+0x35c
afd5ee08 8207d1d1 afd5ee54 8214efc8 00000001 tcpip!IppLoopbackEnqueue+0x2e9
afd5ee90 8207ca2a 8214efc8 8579384c 8579384c tcpip!IppDispatchSendPacketHelper+0x4ea
afd5ef40 8207b8e4 8578e8a0 8214f22c 00000006 tcpip!IppPacketizeDatagrams+0x2b0
afd5efe4 82083d82 afd5f008 820829f0 00000004 tcpip!IppSendDatagramsCommon+0x66a
afd5f004 afd5f278 820833af 86d98ed0 afd5f0c8 tcpip!RssHashComputeToeplitzPortHash+0x47
00000000 00000000 00000000 00000000 00000000 0xafd5f278

We can see many tcpip.sys and a few NETIO,.sys calls. These are Microsoft network related calls and routines. We then reach a DirectX Kernel call into a few igdkmd32.sys calls which is the Intel Graphics driver.

With this said, we likely have a 3rd party source (antivirus, firewall, some 3rd party network app) causing NETBIOS conflicts, and a need to update the video card drivers.


On one of the many *7F's we have, there are a ton of cfosspeed6.sys calls which is the
cFosSpeed - The Internet Accelerator driver.

We also have a REFERENCE_BY_POINTER (18) bug check.

This indicates that the reference count of an object is illegal for the current state of the object.

If we take a look at the call stack:

bb93b3c4 81bd113f 00000018 00000000 86330940 nt!KeBugCheckEx
bb93b3e8 81a96702 00010224 863205f0 b883f300 nt! ?? ::FNODOBFM::`string'+0x35e37
bb93b444 81a96d5c 863205f0 b883f300 224bf394 nt!ExpApplyPriorityBoost+0x110
bb93b49c 81a93297 863205f0 baa02598 d3f8f108 nt!ExpWaitForResource+0xbf
bb93b4e4 d0952713 863205f0 00000001 97ab6420 nt!ExAcquireResourceExclusiveLite+0x191
bb93b520 d093e206 863204b0 97ab6674 00000000 fastfat!FatAcquireExclusiveVcb_Real+0x2b
bb93b774 d093de9a 97ab66b4 00000000 863203b8 fastfat!FatCommonCreate+0x2fc
bb93b7b4 81a8fd02 013203b8 8636f6d8 85afbe08 fastfat!FatFsdCreate+0x4c
bb93b7d0 8069ea9f 00000000 85e25568 8636f6d8 nt!IofCallDriver+0x3f
bb93b80c 806b92dd bb93b850 00000000 00000000 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24c
bb93b86c 81a8fd02 cfbbb730 8636f6d8 86360005 FLTMGR!FltpCreate+0x2d8
bb93b888 81cfde43 224bfea0 81cfd935 82810012 nt!IofCallDriver+0x3f
bb93b9a8 81cb4b96 8636ae00 85068040 85604d20 nt!IopParseDevice+0x512
bb93ba2c 81cfbc99 00000000 bb93ba88 01000040 nt!ObpLookupObjectName+0x251
bb93ba90 81cfaf0f 038dfb50 85068040 00000001 nt!ObOpenObjectByName+0xfe
bb93bb0c 81cf9538 038dfb18 00100081 038dfb50 nt!IopCreateFile+0x2a5
bb93bb58 90db6a8a 038dfb18 00100081 038dfb50 nt!NtCreateFile+0x36
WARNING: Stack unwind information not available. Following frames may be wrong.
bb93bbe0 81b9352c 038dfb18 00100081 038dfb50 bdselfpr+0x7a8a
bb93bbe0 771d6954 038dfb18 00100081 038dfb50 nt!KiFastCallEntry+0x12c
038dfba4 00000000 00000000 00000000 00000000 0x771d6954

Unable to load image \??\C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bdselfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdselfpr.sys

^^ BitDefender Self Protection Driver



1. Uninstall cFosSpeed - The Internet Accelerator.

2. Remove and replace BitDefender with Windows 8's built-in Windows Defender:

BitDefender removal - http://www.bitdefender.com/support/how-to-uninstall-bitdefender-333.html

3. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

4. Just a side question, I see you have TuneUpUtilities installed. What are you using it for?


Debugger/Reverse Engineer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated March 24, 2018 Views 699 Applies to: