TechSpot

system crashes on with BugCheckCode 00000024 and 10000050

By sssvmuni_k
Nov 13, 2005
  1. Hi,

    I have new computer with following configurations

    CPU: intel 4 640 3.3 ghz
    mother broad: intel 955 xbk
    ram: 2 gigs
    HDD: 150 gb sata
    os : window xp professional sp2
    --------------------------------------------------------
    error error 1
    minidumps :
    Loading dump file Mini111305-01.dmp
    ----- 32 bit Kernel Mini Dump Analysis

    DUMP_HEADER32:
    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 68c21000
    PfnDataBase 81043000
    PsLoadedModuleList 805694a0
    PsActiveProcessHead 8056f558
    MachineImageType 0000014c
    NumberProcessors 00000002
    BugCheckCode 00000024
    BugCheckParameter1 001902fe
    BugCheckParameter2 af782c70
    BugCheckParameter3 af78296c
    BugCheckParameter4 f7b79242
    PaeEnabled 00000000
    KdDebuggerDataBlock 805592e0
    MiniDumpFields 00000dff

    TRIAGE_DUMP32:
    ServicePackBuild 00000200
    SizeOfDump 00010000
    ValidOffset 0000fffc
    ContextOffset 00000320
    ExceptionOffset 000007d0
    MmOffset 00001068
    UnloadedDriversOffset 000010a0
    PrcbOffset 00001878
    ProcessOffset 000024c8
    ThreadOffset 00002728
    CallStackOffset 00002980
    SizeOfCallStack 0000191c
    DriverListOffset 00004530
    DriverCount 00000083
    StringPoolOffset 00006c18
    StringPoolSize 00001210
    BrokenDriverOffset 00000000
    TriageOptions 00000041
    TopOfStack af7826e4
    DebuggerDataOffset 000042a0
    DebuggerDataSize 00000290
    DataBlocksOffset 00007e28
    DataBlocksCount 00000007


    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
    compatible

    Kernel base = 0x804de000 PsLoadedModuleList =0x805694a0
    Debug session time: Sun Nov 13 18:36:12 2005
    System Uptime: 0 days 0:01:08
    start end module name
    804de000 80704000 nt Checksum: 0020D6EC Timestamp: Wed
    Mar 02 06:
    27:27 2005 (42250F77)

    Unloaded modules:
    b29e7000 b29e8000 drmkaud.sys Timestamp: unavailable (00000000)
    b013c000 b0149000 DMusic.sys Timestamp: unavailable (00000000)
    afe64000 afe87000 aec.sys Timestamp: unavailable (00000000)
    b014c000 b015a000 swmidi.sys Timestamp: unavailable (00000000)
    b0290000 b0292000 splitter.sys Timestamp: unavailable (00000000)
    f77bf000 f77c4000 Cdaudio.SYS Timestamp: unavailable (00000000)
    bafb4000 bafb7000 Sfloppy.SYS Timestamp: unavailable (00000000)
    f77b7000 f77bc000 Flpydisk.SYS Timestamp: unavailable (00000000)
    f77af000 f77b6000 Fdc.SYS Timestamp: unavailable (00000000)

    Finished dump check

    ----------------------------------------------------
    other error i also found is following.. This is most common error.
    ----- 32 bit Kernel Mini Dump Analysis

    DUMP_HEADER32:
    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 19d2b000
    PfnDataBase 81043000
    PsLoadedModuleList 805694a0
    PsActiveProcessHead 8056f558
    MachineImageType 0000014c
    NumberProcessors 00000002
    BugCheckCode 10000050
    BugCheckParameter1 f7f3e04a
    BugCheckParameter2 00000000
    BugCheckParameter3 f7f3e04a
    BugCheckParameter4 00000000
    PaeEnabled 00000000
    KdDebuggerDataBlock 805592e0
    MiniDumpFields 00000dff

    TRIAGE_DUMP32:
    ServicePackBuild 00000200
    SizeOfDump 00010000
    ValidOffset 0000fffc
    ContextOffset 00000320
    ExceptionOffset 000007d0
    MmOffset 00001068
    UnloadedDriversOffset 000010a0
    PrcbOffset 00001878
    ProcessOffset 000024c8
    ThreadOffset 00002728
    CallStackOffset 00002980
    SizeOfCallStack 0000112c
    DriverListOffset 00003d40
    DriverCount 00000083
    StringPoolOffset 00006428
    StringPoolSize 00001210
    BrokenDriverOffset 00000000
    TriageOptions 00000041
    TopOfStack aed66ed4
    DebuggerDataOffset 00003ab0
    DebuggerDataSize 00000290
    DataBlocksOffset 00007638
    DataBlocksCount 00000002


    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
    compatible

    Kernel base = 0x804de000 PsLoadedModuleList = 0x805694a0
    Debug session time: Sat Nov 12 09:42:31 2005
    System Uptime: 0 days 2:10:50
    start end module name
    804de000 80704000 nt Checksum: 0020D6EC Timestamp: Wed
    Mar 02 06:
    27:27 2005 (42250F77)

    Unloaded modules:
    b29b7000 b29b8000 drmkaud.sys Timestamp: unavailable (00000000)
    b0021000 b002e000 DMusic.sys Timestamp: unavailable (00000000)
    afea9000 afecc000 aec.sys Timestamp: unavailable (00000000)
    b0031000 b003f000 swmidi.sys Timestamp: unavailable (00000000)
    f79b7000 f79b9000 splitter.sys Timestamp: unavailable (00000000)
    f77bf000 f77c4000 Cdaudio.SYS Timestamp: unavailable (00000000)
    bafb4000 bafb7000 Sfloppy.SYS Timestamp: unavailable (00000000)
    f77b7000 f77bc000 Flpydisk.SYS Timestamp: unavailable (00000000)
    f77af000 f77b6000 Fdc.SYS Timestamp: unavailable (00000000)

    Finished dump check
    ----------------------------------------------

    I am not sure which driver or device is root cause of this problem. Pl.
    help me to debug and resolve this problems.

    with regards
    Muni.
     
  2. sssvmuni_k

    sssvmuni_k TS Rookie Topic Starter

    attachments.

    seems that attachements did not attached!!
     
  3. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    Two system crashes are related to memory corruption. The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    Suggestion
    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    Make sure that the CPU fan works properly
    2. Reseat the memory stick to another memory slot
    3. Downclock the ram. Check to default setting if you video card is overclocked.
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    6. Check the bios setting about memory timing and make sure that it is on
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    2. If you have only one memory stick, replace the ram

    Debug report of Mini111305-01.dmp
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    !chkimg -lo 50 -d !Ntfs
    f7b79236 - Ntfs!NtfsReadFileRecord+2f

    [ 80:b8 ]
    f7b7923e - Ntfs!NtfsReadFileRecord+37 (+0x08)

    [ 00:3c ]
    2 errors : !Ntfs (f7b79236-f7b7923e)

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: LARGE
    STACK_COMMAND: .cxr ffffffffaf78296c ; kb
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
    BUCKET_ID: MEMORY_CORRUPTION_LARGE
    Followup: memory_corruption
     
  4. sssvmuni_k

    sssvmuni_k TS Rookie Topic Starter

    quicky query

    Hi,

    I have also notice from mini dump report, which communicates that there are two cpus in the machine. However, in my machine there only single pentium 4 640 process. why is that minidump is communicating my system has two processors.

    with regards
    Muni
     
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    From your minidumps, it shows that your PC have two processors.

    Mini110505-01.dmp.txt:THREAD 89bfb830 Cid 0004.0018 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 1
    Mini110605-01.dmp.txt:THREAD 88f834c0 Cid 07a0.07a8 Teb: 7ffde000 Win32Thread: 00000000 RUNNING on processor 0
    Mini110805-01.dmp.txt:THREAD 89bb6450 Cid 0004.0070 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
    Mini110805-02.dmp.txt:THREAD 89549760 Cid 0310.0378 Teb: 7ffab000 Win32Thread: e2acb008 RUNNING on processor 1
    Mini110905-01.dmp.txt:THREAD 8901a4e8 Cid 00b8.00bc Teb: 7ffdf000 Win32Thread: e2db4eb0 RUNNING on processor 0
    Mini110905-02.dmp.txt:THREAD 8957f798 Cid 0480.04a8 Teb: 7ffd9000 Win32Thread: e1a9c5b8 RUNNING on processor 0
    Mini111105-01.dmp.txt:THREAD 88f35948 Cid 038c.0390 Teb: 7ffdd000 Win32Thread: e2206a50 RUNNING on processor 1
    Mini111105-02.dmp.txt:THREAD 89bfa020 Cid 0004.0028 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
    Mini111205-01.dmp.txt:THREAD 89b466d0 Cid 0004.0070 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 1
    Mini111205-02.dmp.txt:THREAD 88209020 Cid 0e68.0f4c Teb: 7ffdf000 Win32Thread: e334a008 RUNNING on processor 0
    Mini111205-03.dmp.txt:THREAD 88f6b9f8 Cid 0650.0224 Teb: 7ffab000 Win32Thread: e22371e8 RUNNING on processor 0
    Mini111305-01.dmp.txt:THREAD 88e86950 Cid 0650.0bfc Teb: 7ff7c000 Win32Thread: e2658008 RUNNING on processor 1

    The module list also shows that it is Mutiple Processor Windows Kernel
    start end module name
    804de000 80704000 nt ntkrnlmp.exe Wed Mar 02 08:57:27 2005 (42250F77) <-- This is MP Windows Kernel
    80704000 80724d00 hal halmacpi.dll Wed Aug 04 13:59:09 2004 (41107B2D)
     
  6. sssvmuni_k

    sssvmuni_k TS Rookie Topic Starter

    no of processors

    thank your analysis of CPC. my apologies that i did not do it earlier itself. Physically on the mother broad, there is only one processor with hyper threading. I have observed that from the information code dump and also task manager, indication is given is that there are two processor the machine. Does HT does indicate as two processors ?

    with regards
    Muni
     
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...