ntoskrnl.exe BSOD?

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 x64
       #1

    ntoskrnl.exe BSOD?


    Hello!
    Having a BSOD while playing Guild Wars 2.
    First minidump showed ntoskrnl.exe and then ctaud2k.sys.
    Forums suggested "remove NVidia HD Audio driver" as a solution.
    Did it. After a while got another BSOD. In this case the last one was ASACPI.sys, which is pretty old asus mb driver.
    Strange thing is that I use this motherboard for quite a while, but BSODs are haunting me for the last days, after reinstalling Windows.
    And in both minidump cases right before the last line in stack was ntoskrnl.exe. Maybe that's the reason?
    Can somebody help me to solve this mystery please?
    Thank you
    dumps and sf info are attached
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome..I see no attachment?
      My Computer


  3. Posts : 6
    Windows 7 x64
    Thread Starter
       #3

    thanks
    yeah, my mistake, added one
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Thanks

    BSOD Analyze

    One of your dumps indicate hardware problem, but its not necessary that its true.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {ffffffffffffff8e, a, 0, fffff88005f20647}
    
    Unable to load image ha10kx2k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ha10kx2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
    Probably caused by : hardware ( ha10kx2k+eb647 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: ffffffffffffff8e, memory referenced
    Arg2: 000000000000000a, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88005f20647, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f8100
     ffffffffffffff8e 
    
    CURRENT_IRQL:  a
    
    FAULTING_IP: 
    ha10kx2k+eb647
    fffff880`05f20647 48              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff80000b9c5e0 -- (.trap 0xfffff80000b9c5e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000780
    rdx=fffff88008c95758 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88005f20647 rsp=fffff80000b9c770 rbp=00000000000000be
     r8=00000000000000be  r9=0000000000000002 r10=0000000000000001
    r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    ha10kx2k+0xeb647:
    fffff880`05f20647 48              ???
    Resetting default scope
    
    MISALIGNED_IP: 
    ha10kx2k+eb647
    fffff880`05f20647 48              ???
    
    LAST_CONTROL_TRANSFER:  from fffff800030c8769 to fffff800030c91c0
    
    STACK_TEXT:  
    fffff800`00b9c498 fffff800`030c8769 : 00000000`0000000a ffffffff`ffffff8e 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c4a0 fffff800`030c73e0 : fffffa80`07b3bc10 fffffa80`0909bda0 fffffa80`0909bda0 fffffa80`07abd1f0 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c5e0 fffff880`05f20647 : fffffa80`08382c20 fffff880`05f20926 00000000`00dc0000 fffffa80`06f02ba8 : nt!KiPageFault+0x260
    fffff800`00b9c770 fffffa80`08382c20 : fffff880`05f20926 00000000`00dc0000 fffffa80`06f02ba8 fffffa80`085cb580 : ha10kx2k+0xeb647
    fffff800`00b9c778 fffff880`05f20926 : 00000000`00dc0000 fffffa80`06f02ba8 fffffa80`085cb580 00000000`000000be : 0xfffffa80`08382c20
    fffff800`00b9c780 00000000`00dc0000 : fffffa80`06f02ba8 fffffa80`085cb580 00000000`000000be fffffa80`0710c5f0 : ha10kx2k+0xeb926
    fffff800`00b9c788 fffffa80`06f02ba8 : fffffa80`085cb580 00000000`000000be fffffa80`0710c5f0 fffff880`08c95758 : 0xdc0000
    fffff800`00b9c790 fffffa80`085cb580 : 00000000`000000be fffffa80`0710c5f0 fffff880`08c95758 00000000`000000be : 0xfffffa80`06f02ba8
    fffff800`00b9c798 00000000`000000be : fffffa80`0710c5f0 fffff880`08c95758 00000000`000000be fffff880`05f214e8 : 0xfffffa80`085cb580
    fffff800`00b9c7a0 fffffa80`0710c5f0 : fffff880`08c95758 00000000`000000be fffff880`05f214e8 fffffa80`07abd1f0 : 0xbe
    fffff800`00b9c7a8 fffff880`08c95758 : 00000000`000000be fffff880`05f214e8 fffffa80`07abd1f0 fffff880`08c95758 : 0xfffffa80`0710c5f0
    fffff800`00b9c7b0 00000000`000000be : fffff880`05f214e8 fffffa80`07abd1f0 fffff880`08c95758 fffffa80`08386b90 : 0xfffff880`08c95758
    fffff800`00b9c7b8 fffff880`05f214e8 : fffffa80`07abd1f0 fffff880`08c95758 fffffa80`08386b90 fffffa80`07abd1f0 : 0xbe
    fffff800`00b9c7c0 fffffa80`07abd1f0 : fffff880`08c95758 fffffa80`08386b90 fffffa80`07abd1f0 fffff880`08c95758 : ha10kx2k+0xec4e8
    fffff800`00b9c7c8 fffff880`08c95758 : fffffa80`08386b90 fffffa80`07abd1f0 fffff880`08c95758 fffff880`05f141af : 0xfffffa80`07abd1f0
    fffff800`00b9c7d0 fffffa80`08386b90 : fffffa80`07abd1f0 fffff880`08c95758 fffff880`05f141af fffffa80`085cb580 : 0xfffff880`08c95758
    fffff800`00b9c7d8 fffffa80`07abd1f0 : fffff880`08c95758 fffff880`05f141af fffffa80`085cb580 00000000`00000000 : 0xfffffa80`08386b90
    fffff800`00b9c7e0 fffff880`08c95758 : fffff880`05f141af fffffa80`085cb580 00000000`00000000 fffffa80`07a09000 : 0xfffffa80`07abd1f0
    fffff800`00b9c7e8 fffff880`05f141af : fffffa80`085cb580 00000000`00000000 fffffa80`07a09000 00000000`00000000 : 0xfffff880`08c95758
    fffff800`00b9c7f0 fffffa80`085cb580 : 00000000`00000000 fffffa80`07a09000 00000000`00000000 00000000`00000000 : ha10kx2k+0xdf1af
    fffff800`00b9c7f8 00000000`00000000 : fffffa80`07a09000 00000000`00000000 00000000`00000000 fffff880`05f217ca : 0xfffffa80`085cb580
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ha10kx2k+eb647
    fffff880`05f20647 48              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  ha10kx2k+eb647
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_ha10kx2k.sys
    
    BUCKET_ID:  X64_IP_MISALIGNED_ha10kx2k.sys
    
    Followup: MachineOwner
    BSOD Index

    Your other dump shows ctaud2k.sys

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffffa804f2c2f6c, 2, 1, fffff880044cfe60}
    
    Unable to load image ctaud2k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ctaud2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
    Probably caused by : ctaud2k.sys ( ctaud2k+ae60 )
    
    Followup: MachineOwner
    Its drivers are pretty old, so you should update it.
    Driver Reference Table - ctaud2k.sys

    Code:
    2: kd> lmvm ctaud2k
    start             end                 module name
    fffff880`044c5000 fffff880`04596d80   ctaud2k  T (no symbols)           
        Loaded symbol image file: ctaud2k.sys
        Image path: ctaud2k.sys
        Image name: ctaud2k.sys
        Timestamp:        Thu Mar 18 18:18:42 2010 (4BA21A22)
        CheckSum:         000D3E03
        ImageSize:        000D1D80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Your Bios version is too old, get an update for it as well from your manufacturers website.

    Code:
    BIOS Version/Date    American Megatrends Inc. 0704, 10/30/2007
    Post back once you've done these
      My Computer


  5. Posts : 6
    Windows 7 x64
    Thread Starter
       #5

    So, I've installed Nvidia drivers (this time with HD audio driver).
    Removed audigy sound card, disabled onboard sound. I will use Nvidia HD audio to avoid conflicts.
    Updated motherboard BIOS and some of the drivers.
    Tested ram (with memtest86+) and HDD with HDDScan. No errors here.
    Tested graphics card with MSI Kombustor. Works fine.
    And now I will start testing games thoroughly. Will post back afterwards.
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Keep us updated.
      My Computer


  7. Posts : 6
    Windows 7 x64
    Thread Starter
       #7

    So far so good. So I hope it's an end of story :)
    Thanks for help!
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    Thanks :)
    Keep us posted if you get more BSODS. Observer your computer for 2 or 3 days more and come back and mark this thread as solved.
      My Computer


  9. Posts : 6
    Windows 7 x64
    Thread Starter
       #9

    will do :) thanks
      My Computer


  10. Posts : 6
    Windows 7 x64
    Thread Starter
       #10

    no recurrences, so i'm closing the thread
    thanks again!
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:39.
Find Us