1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

Seemingly random shutdowns on a newly built system, HELP!

By cpopperwell
Sep 14, 2007
  1. Please HELP! Please help me find out why this PC is crashing.

    Hi everyone, I hope you can help, i'm having some strange problems with a system I have just rebuilt for a friend.
    Clean install WinXp Home and all the updates, drivers and wotnot.
    I've tracked it down to whenever we start playing a game.

    Here is the Bug check
    0x000000a (0x00000004, 0x000000ff,0x00000001, 0x804f8a19)
    and i've attatched the dump file.

    The system is a Compaq AS5020AN, running...
    AMD Athlon XP 2400+
    2.00 GHz, 1.00GB of RAM
    ASUS ATI Radeon 9550GE

    I match the ram to the FSB and CPU bus for optimal performance.

    Please if anyone can help i will be very grateful.
    Chris P

    I have done some more reading and managed to expand the DMP file but I'm still not quite sure of what it all means, here it is...
    Microsoft (R) Windows Debugger Version 6.7.0005.1
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [F:\Documents and Settings\Chris Popperwell\Desktop\Mini091507-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: F:\Program Files\Support Tools\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Sat Sep 15 12:27:25.734 2007 (GMT+12)
    System Uptime: 0 days 0:11:28.299
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {4, ff, 1, 804f8a19}

    *** WARNING: Unable to verify timestamp for kmixer.sys
    Probably caused by : kmixer.sys ( kmixer!CreateSinkPin+39 )

    Followup: MachineOwner

    kd> !analyze -v
    * *
    * Bugcheck Analysis *
    * *

    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 a kernel debugger is available get the stack backtrace.
    Arg1: 00000004, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804f8a19, address which referenced memory

    Debugging Details:

    WRITE_ADDRESS: 00000004


    804f8a19 894508 mov dword ptr [ebp+8],eax




    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from e5ccf000 to 804f8a19

    a80b1cbc e5ccf000 857e3e78 00000000 a80b1cec nt!FsRtlRemoveLargeMcbEntry+0x3b
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a80b1cd4 9a3a3559 85703528 865c4b50 86595758 0xe5ccf000
    a80b1d50 9a391e9d 86595758 865c4b50 86595810 kmixer!CreateSinkPin+0x39
    a80b1d84 9a3922a7 00595758 00000000 00000000 kmixer!MxWorker+0x26d
    a80b1dac 8057d0f0 86595758 00000000 00000000 kmixer!PinDispatchIoControl+0x57
    a80b1ddc 804f827a 9a3921f0 86595758 00000000 nt!NtQuerySystemInformation+0x4e3
    a80b1df8 00000000 00000000 00000000 00001f80 nt!RtlInsertElementGenericTableFullAvl+0xd0


    9a3a3559 ?? ???


    SYMBOL_NAME: kmixer!CreateSinkPin+39

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: kmixer

    IMAGE_NAME: kmixer.sys


    FAILURE_BUCKET_ID: 0xA_W_kmixer!CreateSinkPin+39

    BUCKET_ID: 0xA_W_kmixer!CreateSinkPin+39

    Followup: MachineOwner

    I have run Memtest and it found ) errors,
    The system has brand new (1 week old) ram and brand new Graphics card.
    I rebuilt the system with a clean install and everything.
    I'm at my wits end trying to solve this.

    Any help you can give me will be appreciated

    Chris P

    Attached Files:

  2. cpopperwell

    cpopperwell TS Rookie Topic Starter

    Yes I'm double posting because...

    Nearly 100 of you have looked and no one has commented. Can SOMEONE PLEASE just let me know something, good, bad, or ugly!!!
    If i'm in the wrong area then please direct me to the right one.
    If you need more info, ask me.
    PLEASE help.
    Chris P
  3. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Your windows are crashed without pattern. Especially it crashed 3 times at kmixer. Kmixer is a stable routine. If it crashes, it is related to faulty ram. Run Memtest to stress test the ram or reseat the memory module to another memory slot.

    Mini091507-01.dmp BugCheck 1000000A, {4, ff, 1, 804f8a19}
    Probably caused by : kmixer.sys ( kmixer!MixOneBuff+949 )

    Mini091907-02.dmp BugCheck 1000000A, {0, 2, 1, 8069b857}
    Probably caused by : hardware ( nt!`string'+1f )

    Mini092007-01.dmp BugCheck 10000050, {9d75bdc0, 0, 9d529e9a, 0}
    Probably caused by : kmixer.sys ( kmixer!MxSetCurrentPosition+14a )

    Mini092107-01.dmp BugCheck 100000D1, {ec998e03, 2, 1, f4c3be13}
    Probably caused by : hardware ( ALCXWDM+5be13 )

    Mini092207-05.dmp BugCheck 1000007E, {c0000005, 9b57ba11, 9bc7ebd4, 9bc7e8d0}
    Probably caused by : kmixer.sys ( kmixer!OptimizeSource+461 )
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...