TechSpot

Intermitant stuttering system and two bugcheck reboots...

By Baron_Nogood
Jan 24, 2008
Topic Status:
Not open for further replies.
  1. Hi,

    I recently had to change my motherboard (after busting the other one with a dodgy fan installation:(), and it has been fine, bar for a couple of random restarts and an intermitant problem with some serious stuttering...

    I checked the event log and it appears that the stuttering is caused by the CD ROM drives being constantly polled and not responding or being ready...this causes the entire system to stutter (mouse moves ever second or so)...I assume this is a bus clog up issue and it doesn't happen that often...solved by a restart.

    I have had a couple of bugcheck reboots though (while playing games) got the following two mini dumps and don't know how to debug with them or even understand what they are saying...is there any chance someone more technically minded can look them over?

    Many thanks...
  2. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Inside the minidumps:

    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 : memory_corruption
    Followup: memory_corruption
    ---------------

    Creative sound card driver file.
    Try updating your sound card drivers
  3. Baron_Nogood

    Baron_Nogood Newcomer, in training Topic Starter Posts: 43

    Hi, I already have the most up to date drivers possible for my sound card.

    Do both dumps show memory corruption as the culprit?
  4. Baron_Nogood

    Baron_Nogood Newcomer, in training Topic Starter Posts: 43

    I got the analysis...I have never had my Creative card crash my system like this in the past and I haven't changed anything...would reinstalling the sound card drivers help?

    *******************************************************************************
    * *
    * 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: b6c1f0f8, address which referenced memory

    Debugging Details:
    ------------------




    READ_ADDRESS: 00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    ha10kx2k+5c0f8
    b6c1f0f8 8b03 mov eax,dword ptr [ebx]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 00000000 to b6c1f0f8

    STACK_TEXT:
    00000000 00000000 00000000 00000000 00000000 ha10kx2k+0x5c0f8


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ha10kx2k+5c0f8
    b6c1f0f8 8b03 mov eax,dword ptr [ebx]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: ha10kx2k+5c0f8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ha10kx2k

    IMAGE_NAME: ha10kx2k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 44dc2784

    FAILURE_BUCKET_ID: 0xD1_ha10kx2k+5c0f8

    BUCKET_ID: 0xD1_ha10kx2k+5c0f8

    Followup: MachineOwner
    ---------
  5. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    no, only 1

    You may need to wait, to get more dmp files.

    Or you could fully un-install your sound driver - then download/updated driver from web (preferred)

    Or you could run a memtest on your Ram

    Edit:

    But you can !
  6. Baron_Nogood

    Baron_Nogood Newcomer, in training Topic Starter Posts: 43

    Hi, I memtested my ram recently (lots of repetitions) and there were no errors...the other dump file relates to a general protection fault after a register read was attempted...two different faults...both say "Driver Fault" though...

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    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: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:
    ------------------




    BUGCHECK_STR: 0x7f_d

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: lsass.exe

    LAST_CONTROL_TRANSFER: from 8054086c to 805ea679

    STACK_TEXT:
    b6e3bd44 8054086c 000003c0 00000000 00acf6f4 nt!IopGetDeviceResourcesFromRegistry+0x56
    b6e3bd64 7c90eb94 badb0d00 00acf6a0 00000000 nt!RtlIpv4StringToAddressExA+0x149
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b6e3bd78 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!IopGetDeviceResourcesFromRegistry+56
    805ea679 64a124010002 mov eax,dword ptr fs:[02000124h]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!IopGetDeviceResourcesFromRegistry+56

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

    FAILURE_BUCKET_ID: 0x7f_d_nt!IopGetDeviceResourcesFromRegistry+56

    BUCKET_ID: 0x7f_d_nt!IopGetDeviceResourcesFromRegistry+56

    Followup: MachineOwner
    ---------
  7. Baron_Nogood

    Baron_Nogood Newcomer, in training Topic Starter Posts: 43

    Might be EAX issues...I may have set my games to use EAX components that I don't have...unless "805ea679 64a124010002 mov eax,dword ptr fs:[02000124h]" is just a coincidence...but I don't know a hex with X in it :D (Except 0x)

    Hum
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.