Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

bsod unexpected_kernel_mode_trap windows 8


  • Please log in to reply
9 replies to this topic

#1 paulos123

paulos123

  • Members
  • 313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:greece
  • Local time:10:34 PM

Posted 18 September 2014 - 12:03 PM

i had before a while twice this bsod unexpected_kernel_mode_trap.

it started propably after installing emsisoft internet security cause everything was fine.

i ll be waiting for your help guys thanks.



BC AdBot (Login to Remove)

 


#2 paulos123

paulos123
  • Topic Starter

  • Members
  • 313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:greece
  • Local time:10:34 PM

Posted 18 September 2014 - 12:08 PM

and thats the problem according to bsod viewer.

 

==================================================
Dump File         : 091814-21562-01.dmp
Crash Time        : 18/9/2014 7:50:42 μμ
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x1000007f
Parameter 1       : 0x00000008
Parameter 2       : 0x806d4000
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : USBPORT.SYS
Caused By Address : USBPORT.SYS+6cbc
File Description  : Πρόγραμμα οδήγησης θύρας USB 1.1 & 2.0
Product Name      : Λειτουργικό σύστημα Microsoft® Windows®
Company           : Microsoft Corporation
File Version      : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor         : 32-bit
Crash Address     : ntoskrnl.exe+1df720
Stack Address 1   : USBPORT.SYS+702f
Stack Address 2   : USBPORT.SYS+3c94
Stack Address 3   : USBPORT.SYS+35f0
Computer Name     : 
Full Path         : C:\Windows\Minidump\091814-21562-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 150.640
Dump File Time    : 18/9/2014 7:52:10 μμ
==================================================


#3 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 AM

Posted 18 September 2014 - 02:40 PM

Can you upload the dump files for analysis.

Go to

C:\Windows\minidump

Upload all those files by copying them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

#4 paulos123

paulos123
  • Topic Starter

  • Members
  • 313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:greece
  • Local time:10:34 PM

Posted 19 September 2014 - 01:21 AM

memory dmp file....

Attached Files


Edited by paulos123, 19 September 2014 - 01:22 AM.


#5 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 AM

Posted 19 September 2014 - 03:51 AM

8263a06c 8d73302f 00000200 0000001c 70627375 nt!ExAllocatePoolWithTag+0x2a0
8263a108 8d72fc94 bf8d9698 02897b78 00000000 USBPORT!USBPORT_Core_AllocTransferEx+0x4f2
8263a1a4 8d72f5f0 bf897b78 88517d28 8c076600 USBPORT!USBPORT_ProcessURB+0x40f
8263a1d0 8150280f 02b14028 95b140e0 bf9c0030 USBPORT!USBPORT_Dispatch+0x164
8263a1ec 8c8c5215 00000000 bf897cc0 bf98f00f nt!IofCallDriver+0x3f
8263a214 8c8c5034 bf9c0030 8e687028 bf9c0030 usbhub!UsbhPdoInternalDeviceControl+0x1a2
8263a228 8150280f bf9c0030 bf897b78 bf98f0f0 usbhub!UsbhGenDispatch+0x2f
8263a244 8e96e594 00000000 bf98f0f0 bf897b78 nt!IofCallDriver+0x3f
8263a2a8 8e96e453 0000000f bf897b78 bf98f0e8 usbccgp!DispatchPdoUrb+0x131
8263a2c8 8e96e17f 00000000 bf98f030 bf9ba00f usbccgp!DispatchPdoInternalDeviceControl+0x6a
8263a30c 8150280f bf98f030 bf897b78 bf9ba0f4 usbccgp!USBC_Dispatch+0x17a
8263a328 bdb904d6 00000000 bf9ba028 0000000f nt!IofCallDriver+0x3f
WARNING: Stack unwind information not available. Following frames may be wrong.
8263a33c 8150280f 00000000 bf897b78 00000005 ew_usbenumfilter+0x4d6
8263a358 85e4449f 8263a3bc c5b18c78 00000000 nt!IofCallDriver+0x3f
8263a374 8dd3fa93 8b7559c8 929fbd38 bf96e010 Wdf01000!imp_WdfRequestSend+0x121
8263a3bc 8dd3fb4c c5b18c78 00000000 c5b18c78 ew_jubusenum+0x3a93
8263a3d0 8dd3fd98 3a4e7300 c5b18c78 bf968210 ew_jubusenum+0x3b4c
8263a440 8dd3fe90 c5b18c78 00000000 4060f198 ew_jubusenum+0x3d98
8263a468 8dd41e6b c5b18c78 00000000 4060f198 ew_jubusenum+0x3e90
8263a4a4 8dd41f12 0064e288 4060f198 40691fe8 ew_jubusenum+0x5e6b
8263a4dc 8dd453bd 4064e288 88f5c008 0000024e ew_jubusenum+0x5f12
8263a504 bdbb1c8e 4064e288 88f5c008 0000024e ew_jubusenum+0x93bd
8263a53c bdbb1dd1 8263a580 bf9ef480 bf9f5198 ew_jucdcacm+0x8c8e
8263a550 bdbad61a bf9f5198 bf9ef480 bf9f5198 ew_jucdcacm+0x8dd1
8263a580 bdbb2325 bf9f5198 40610c60 407d6d80 ew_jucdcacm+0x461a
8263a5a8 85e53f57 406b7210 40610c60 0000024e ew_jucdcacm+0x9325
8263a5c4 85e6cb5a 406b7210 40610c60 0000024e Wdf01000!FxIoQueueIoRead::Invoke+0x2e
8263a60c 85e45499 40610c60 bf948e5c bf9ef398 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x27265
8263a640 85e4488d bf9ef302 00000000 bf9f5010 Wdf01000!FxIoQueue::DispatchEvents+0x289
8263a684 85e44665 019f5010 bf9ef302 00000000 Wdf01000!FxPkgIo::EnqueueRequest+0x209
8263a6ac bdbab0a9 bf9ef398 bf9f5010 40610c60 Wdf01000!imp_WdfDeviceEnqueueRequest+0x9f
8263a6e8 85e42386 4060afe8 40610c60 00000000 ew_jucdcacm+0x20a9
8263a798 8150280f 0189cef0 01487cf0 bf9d5030 Wdf01000!FxDevice::DispatchWithLock+0x66e
8263a7b4 8e92f454 00000000 bf9d5030 88f5c004 nt!IofCallDriver+0x3f
8263a7c8 8150280f 93487da8 93487cf0 88f5c008 modem!UniWrite+0x6a
8263a7e4 bda1446e 88f89b00 8854fc88 88f89bb0 nt!IofCallDriver+0x3f
8263a814 bda142a9 885a75b8 88e83420 bf99fb88 asyncmac!AsyncSendNB+0x16c
8263a828 81e5a06f 8854fc88 88f89b00 00000000 asyncmac!AsyncMpCoSendNetBufferListChain+0x69
8263a840 81e5ad85 bf99fb88 88f89b00 00000000 ndis!ndisCoSendNetBufferListsToNetBufferLists+0x3c
8263a854 aafb4650 bf99fb88 88f89b00 00000000 ndis!NdisCoSendNetBufferLists+0x15
8263a87c aaf9cec8 8263a960 aaf9cef8 89de8dc8 ndiswan!SendOnLink+0x205
8263a960 aafb4260 88f89b00 8263a984 00000001 ndiswan!FramePacketFast+0x1c0
8263a9a4 aafb4853 00000000 8263a9cc 00100001 ndiswan!SendFromProtocol+0x11c
8263a9e0 aaf9d05c 88e5cd70 885a75b8 00000001 ndiswan!SendPacketOnBundle+0x19b
8263aa10 aaf9e152 88f89b00 89de8dc8 00000000 ndiswan!NdisWanQueueSend+0x147
8263aa60 aaf9a144 88f89b00 88e920e8 00000000 ndiswan!ApplyQoSAndQueueSend+0x489
8263aa80 81e2c838 884d5248 88f89b00 00000000 ndiswan!MPSendNetBufferListChain+0x132
8263aad8 81e35a3c 00e2c252 88e920e8 01f89b00 ndis!ndisCallSendHandler+0x24d
8263ab20 81e60dd4 81e2c252 88e920e8 c4e5be40 ndis!ndisInvokeNextSendHandler+0x94e4
8263ab58 81e5d897 00e920e8 88f89b00 00000000 ndis!ndisSendNBLToFilter+0xed
8263aba0 81e5e096 88e920e8 8263ac00 00000001 ndis!ndisMSendPacketsToNetBufferLists+0x98
8263abdc 81e5e155 88eea3c8 8263ac00 00000000 ndis!ndisSendPacketsWithPause+0x1dd
8263abf4 8dd35053 88eefd98 95a3d064 8b7fba00 ndis!ndisSendWithPause+0x32
8263ac14 8dd353da 00000000 95a3d064 8b7fba00 oanet+0x3053
8263ac34 8dd3314d 935fb4c0 8b7fba00 89744924 oanet+0x33da
8263ac50 81e5d9d2 00000003 8263acc0 00000004 oanet+0x114d
8263ac7c 81e5d18f 8263acc0 8263acc0 00000000 ndis!ndisMSendPacketsXToMiniport+0xe5
8263ace8 81e28676 8c06b0e8 884ff718 00000000 ndis!ndisMSendNetBufferListsToPackets+0x76
8263adc8 8c7d1158 88ece960 884ff718 00000000 ndis!NdisSendNetBufferLists+0x431
8263ae2c 8602a5e3 905dd0d0 00000000 00000000 wanarp!WanIpSendPackets+0x2cf
8263aea0 8602b442 00000000 89856c54 861430b0 tcpip!IppFragmentPackets+0x22e
8263af00 8602aefe 89856c54 89856c50 8263b0f0 tcpip!IppDispatchSendPacketHelper+0x250
8263afa8 86028b84 000000d8 8613b7e0 861430b0 tcpip!IppPacketizeDatagrams+0x289
8263b038 8602eadc 00000007 89df4cb0 8263b0f0 tcpip!IppSendDatagramsCommon+0x6b1
8263b058 86031f43 8982eb40 8263b0f0 00000000 tcpip!IpNlpSendDatagrams+0x41
8263b220 86058108 00000000 000239e8 00000000 tcpip!TcpTcbSend+0x720
8263b268 8601198f 896c6100 896c6008 00000000 tcpip!TcpFlushDelay+0x237
8263b2b0 860117fe 00000001 8263b302 8263b348 tcpip!TcpDeliverInput+0x12d
8263b2f8 86011852 8263b348 8c2110f2 896c6008 tcpip!TcpRequestReceive+0x16b
8263b300 8c2110f2 896c6008 8263b328 8263b448 tcpip!TcpTlConnectionReceive+0x19
8263b348 8c210d51 896d6f98 8263b38b 00000000 tdx!TdxReceiveConnection+0x130
8263b410 8603391e 88eb76a0 8263b448 8263b5b0 tdx!TdxEventReceiveConnection+0x214
8263b4c0 86033195 8263b5b0 8263b4fc 8263b4f4 tcpip!TcpIndicateData+0x146
8263b578 8603365a 8263b5b0 8263b5ac 00000000 tcpip!TcpDeliverDataToClient+0x91
8263b5cc 86044d75 89661c90 89661c90 0000053a tcpip!TcpDeliverReceive+0x6e

I'm not going to go through it all as it would take a long time but we can clearly see that some USB/network related routines causing problems here, we must take note of this line:

 

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

 

Meaning whatever is in the callstack before this might not be related to the crash.

 

Your Huawei Technologies drivers are outdated and need either removing or updating.

 

OnlineArmor Service this appears to be causing problems as well, I recommend removing it.


Edited by Jared44, 19 September 2014 - 03:56 AM.


#6 paulos123

paulos123
  • Topic Starter

  • Members
  • 313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:greece
  • Local time:10:34 PM

Posted 19 September 2014 - 05:26 AM

it was online armor cause after installing it i had bsod.now i uninstalled it and no problem.i installed now avast internet security.



#7 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 AM

Posted 19 September 2014 - 06:12 AM

Good work.
Any other issues let me know.

#8 paulos123

paulos123
  • Topic Starter

  • Members
  • 313 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:greece
  • Local time:10:34 PM

Posted 19 September 2014 - 07:08 AM

cool thanks again



#9 sina2000

sina2000

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:04 AM

Posted 26 November 2014 - 07:20 AM

hello jared
I have the same problem like paulos, my pc crashed many time and error was unexpected_kernel_mode_trap in win8.
I send upload 4 last minidump files here. hope you can help me to solve this bad problem.
thanks

Attached Files


Edited by sina2000, 26 November 2014 - 07:22 AM.


#10 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 AM

Posted 26 November 2014 - 03:15 PM

It seems to be related to your display driver and ESET anti virus.

Your ESET anti virus is over 2 years old.

0: kd> lmvm epfw
start    end        module name
927a8000 927d1000   epfw     T (no symbols)           
    Loaded symbol image file: epfw.sys
    Image path: \SystemRoot\system32\DRIVERS\epfw.sys
    Image name: epfw.sys
    Timestamp:        Fri Dec 21 11:59:38 2012 (50D44F2A)
    CheckSum:         000277C4
    ImageSize:        00029000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That's not good at all, you need to update ESET.

0: kd> lmvm igdkmd32
start    end        module name
91a20000 91d11000   igdkmd32 T (no symbols)           
    Loaded symbol image file: igdkmd32.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
    Image name: igdkmd32.sys
    Timestamp:        Sat May 17 05:17:49 2014 (5376E2ED)
    CheckSum:         002DBC85
    ImageSize:        002F1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel graphics driver could do with an update, try visiting the Intel download centre, then download the latest display driver.

 

I haven't posted much of an analysis as I'm short for time. I hope this helps.

Any queries then just ask.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users