Results 1 to 10 of 10

Thread: Random bsod Unexpected kernel mode trap, caused by ntoskrnl.exe+7cc40 - help!?

  1. #1
    hentai's Avatar
    hentai is offline Beginner
    Join Date
    May 2010
    Posts
    32

    Unhappy Random bsod Unexpected kernel mode trap, caused by ntoskrnl.exe+7cc40 - help!?

    its been some time since ive been here but this random bsod im having lately is driving me nuts well ill attach the latest minidump here you go , this is like the second bsod in like 5 days no idea why -.-'


    111911-17971-01.dmp

    Last edited by hentai; 19th November 2011 at 04:32.

  2. #2
    japp's Avatar
    japp is offline Gold Member
    Join Date
    Jan 2011
    Location
    Norway
    Posts
    818

    Default

    I can't help, but if you google "ntoskrnl.exe+7cc40 bsod" there are many having the same problem so you might find your solution out there.

  3. #3
    hentai's Avatar
    hentai is offline Beginner
    Join Date
    May 2010
    Posts
    32

    Default

    thats not much of help tbh -.-'

  4. #4
    HappyAndyK's Avatar
    HappyAndyK is offline Site Administrator
    Join Date
    Jun 2008
    Posts
    7,530

    Default

    I can think of two possibilities: Some problem with some Device Driver or maybe its a faulty RAM.

    Try using Memtest86+ or BlueScreenView or WhoCrashed.

  5. #5
    Capt.Jack's Avatar
    Capt.Jack is offline Moderator
    Join Date
    Sep 2010
    Posts
    296

    Default

    Hello there!

    The dump files didn't have lot of information we need. Please run this tool and upload the files. Mean while Run Hardware Diagnostic to make sure all the components are intact.

    Uninstall all your security softwares including spywares and install Microsoft Security Essentials till we figure out your problem. Because the Bugcheck 0x7f are mostly caused by third party firewalls.

    Update InpOutx64.sys drivers seems like they are from 2008. Check this thread to know how to update them.

    Bugcheck:

    Code:
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000006f8
    Arg4: fffff800034e2ce6
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800034dc1e9 to fffff800034dcc40
    
    STACK_TEXT:  
    fffff800`04d9ed28 fffff800`034dc1e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
    fffff800`04d9ed30 fffff800`034da6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`04d9ee70 fffff800`034e2ce6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    ffdff800`04d96560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x26
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`034da6b2 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
    ---------
    
    rax=fffff80004d9ee30 rbx=fffffa8011164c68 rcx=000000000000007f
    rdx=0000000000000008 rsi=0000000000000000 rdi=fffff80004d96608
    rip=fffff800034dcc40 rsp=fffff80004d9ed28 rbp=fffff80004d9eef0
     r8=0000000080050033  r9=00000000000006f8 r10=fffff800034e2ce6
    r11=fffff80004d965b0 r12=0000000000000004 r13=fffffa8011164b60
    r14=0000000000000000 r15=fffff80003652e80
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
    nt!KeBugCheckEx:
    fffff800`034dcc40 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`04d9ed30=000000000000007f
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff800`04d9ed28 fffff800`034dc1e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
    fffff800`04d9ed30 fffff800`034da6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`04d9ee70 fffff800`034e2ce6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 (TrapFrame @ fffff800`04d9ee70)
    ffdff800`04d96560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x26
    Post us back with the results.

  6. #6
    hentai's Avatar
    hentai is offline Beginner
    Join Date
    May 2010
    Posts
    32

    Default

    Quote Originally Posted by HappyAndyK View Post
    I can think of two possibilities: Some problem with some Device Driver or maybe its a faulty RAM.

    Try using Memtest86+ or BlueScreenView or WhoCrashed.
    faulty ram? hardly ive ran memtest 86+ for 2 whole days with 0 errors

    so it deffinitely isnt my ram , driver not quite sure hmmm....and ive viewed my bsod under bluescreen crash viewer or i wouldntve known the ntoskrnl.exe+7cc40 aka ntoskrnl.exe causing the crash

    nonetheless ill do the sf tool asap, hardware diagnostic? thats outdated heres an excerpt from hardware diagnostic site :


    "In Windows 7 we have Windows Diagnostic but I would no longer recommend it. Then best tool to run the Memory Diagnostic is to Download MemTest86+ – Advance Memory Diagnostic Tool"

    we all use memtest86+ nowadays and i dont think my av or firewall are at fault theyre known for being without problems out of all av and firewalls out there aka i use eset32 v5 and commodo firewall combined with malwarebytes thats it and my system is clean not a speck of virus etc on it, microsoft security essentials youre joking right , and i did a complete clean of my display drivers with driver sweeper and updated to the latest drivers for my 580 gtx card btw since i heard rumours about old remains of past drivers causing these issues with a certain microsoft security update from months ago , but i hope you guys find out the exact source itd be much appreciated , and i monitor my harddrives constantly over a suit called hard disk sentinel it reports the smart status and errors ...all is fine








    heres the ordered 7 folder youre welcome



    http://www.mediafire.com/?nsrgyznubi2owd1
    Last edited by hentai; 19th November 2011 at 21:36.

  7. #7
    Capt.Jack's Avatar
    Capt.Jack is offline Moderator
    Join Date
    Sep 2010
    Posts
    296

    Default

    Hi there!

    Seems like it's some Hardware is causing the system to crash. Unfortunately 0x124 error are hard to troubleshoot because there is no easy way to pinpoint the Hardware,

    Code:
    BugCheck 124, {0, fffffa80070048f8, 0, 0}
    
    Probably caused by : hardware
    Run Prime95 test here is a check list Stop 0x124 - what it means and what to try

    Bugcheck:

    Code:
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80070048f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`03b326f0 fffff800`036c7c59 : fffffa80`070048d0 fffffa80`05512b60 00000000`0000000f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03b32c10 fffff800`035a7f57 : fffffa80`070048d0 fffff800`036222b8 fffffa80`05512b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03b32c40 fffff800`0350f5d5 : fffff800`03683ae0 00000000`00000001 fffffa80`06f3c770 fffffa80`05512b60 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03b32c80 fffff800`0348c001 : fffff880`011dae00 fffff800`0350f5b0 fffffa80`05512b00 38151824`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03b32cb0 fffff800`0371cfee : 00000000`00000000 fffffa80`05512b60 00000000`00000080 fffffa80`054f6040 : nt!ExpWorkerThread+0x111
    fffff880`03b32d40 fffff800`034735e6 : fffff880`03931180 fffffa80`05512b60 fffff880`0393c1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03b32d80 00000000`00000000 : fffff880`03b33000 fffff880`03b2d000 fffff880`033d1540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    
    Followup: MachineOwner
    ---------

  8. #8
    hentai's Avatar
    hentai is offline Beginner
    Join Date
    May 2010
    Posts
    32

    Default

    yeah i got prime95 ill give it a run for 1 day and see what happens i guess on balance right?

    guess prime95 is better to run then linx? cause i use both to stress test my hardware for stability issues once in a while

    update: well i just had it again while i was typing this comment

    and im using firefox heard people have had this bsod while using firefox lately too , didnt even start prime95 yet -.-'
    Last edited by hentai; 20th November 2011 at 06:08.

  9. #9
    Capt.Jack's Avatar
    Capt.Jack is offline Moderator
    Join Date
    Sep 2010
    Posts
    296

    Default

    Quote Originally Posted by hentai View Post
    yeah i got prime95 ill give it a run for 1 day and see what happens i guess on balance right?

    guess prime95 is better to run then linx? cause i use both to stress test my hardware for stability issues once in a while

    update: well i just had it again while i was typing this comment

    and im using firefox heard people have had this bsod while using firefox lately too , didnt even start prime95 yet -.-'
    Na Firefox will not cause BSOD, Mostly it's happen when we have a bad Network drivers.

  10. #10
    hentai's Avatar
    hentai is offline Beginner
    Join Date
    May 2010
    Posts
    32

    Default

    i see well thanks for trying to help , it seems ill have to figure this one out myself could be the windows security update thats supposed to make the kernel mode trap happen , but we shall see atm i havent gotten a bsod , but then again i dare say it cause as soon as i go jumping around flapping my hands in the air ...bam ...bsod , so ill restrain myself for now of any happy feelings ...for bout a week and then i can slowly jump around again

    p.s: the prime test ran flawless btw for a couple of hours till it bsodeŽd again so i guess ill have to reconfigure my oc ....weird its been rock solid since the entire year , hmmmm.....and my ram checks out just fine , well up to another prime run until i get stable

    the funny thing is since prime95 isnt exactly real world usage , and i get some bsods with prime but while normal usage ..none -.-'

    and now well ...i get this kernel mode trap since i last updated a month ago or so where microsoft released a ton of updates 80mb or such, and something is telling me it isnt my hardware but a windows update instead so much for windows 7 being bsod free -.-'
    Last edited by hentai; 21st November 2011 at 17:42.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22