TechSpot

Cant understand the minidump file Maybe RAM?

By jumperg123
Nov 30, 2009
  1. Hi All, I have been having random blue screens and have figured out how to produce a minidump file and analize it!! Great, but what does it mean? I have the follow:
    Windows XP Professional Service Pack 3 (build 2600)
    2.80 gigahertz Intel Pentium 4
    16 kilobyte primary memory cache
    1024 kilobyte secondary memory cache
    ASUSTeK Computer INC. P4S800D-X Rev 1.xx
    Bus Clock: 133 megahertz
    2048 Megabytes Installed Memory
    Slot 'DIMM0' has 1024 MB
    Slot 'DIMM1' has 512 MB
    Slot 'DIMM2' is Empty
    Slot 'DIMM3' has 512 MB
    c: (NTFS on drive 0) 203.92 GB 35.52 GB free
    f: (FAT32 on drive 1) 10.23 GB 9.55 GB free
    NVIDIA GeForce FX 5200 [Display adapter]
    SndTVideo [Display adapter]
    Default Monitor

    Everything is up-to-date maybe a few non-essential driver out of date... Not sure.

    Here is the dump file: Also, after it dumps and I restart I usaully cant find the drive to load windows unless I wait a while then it will restart. Also mutiple event log errors.
     
  2. jumperg123

    jumperg123 TS Rookie Topic Starter

    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
    Debug session time: Fri Jan 9 22:12:43.820 2009 (GMT-5)
    System Uptime: 0 days 13:16:27.578
    Loading Kernel Symbols
    ................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 0, f78bea8c, f78be788}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    Probably caused by : ntoskrnl.exe ( nt!IoPageRead+1b )

    Followup: MachineOwner
    ---------

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 00000000, The address that the exception occurred at
    Arg3: f78bea8c, Exception Record Address
    Arg4: f78be788, Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    +0
    00000000 0000 add byte ptr [eax],al

    EXCEPTION_RECORD: f78bea8c -- (.exr 0xfffffffff78bea8c)
    Cannot read Exception record @ f78bea8c

    CONTEXT: f78be788 -- (.cxr 0xfffffffff78be788)
    Unable to read context, Win32 error 0n30

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x7E

    EXCEPTION_STR: 0x0

    LAST_CONTROL_TRANSFER: from 804f95ff to 00000000

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    f78beb5c 804f95ff 8a661ee8 88ef410b 88ef40f8 0x0
    f78beb7c 804f92c9 88cb53f0 88ef41e8 88ef40f8 nt!IoPageRead+0x1b
    f78bebf0 804eba6a 6950d8c0 c6020000 c0318080 nt!MiDispatchFault+0x2fc
    f78bec40 804f67f3 00000000 c6020000 00000000 nt!MmAccessFault+0x5bc
    f78bec80 804ff901 c6020000 00000000 80557398 nt!MmCheckCachedPageState+0x461
    f78bed2c 804ff6b4 8a6bfd60 805622c0 8a67e340 nt!CcPerformReadAhead+0x1f1
    f78bed74 804e426b 8a6bfd60 00000000 8a67e340 nt!CcWorkerThread+0x147
    f78bedac 8057aeff 8a6bfd60 00000000 00000000 nt!ExpWorkerThread+0x100
    f78beddc 804f88ea 804e4196 00000000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    FOLLOWUP_IP:
    nt!IoPageRead+1b
    804f95ff 5d pop ebp

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!IoPageRead+1b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48a404ab

    STACK_COMMAND: .cxr 0xfffffffff78be788 ; kb

    FAILURE_BUCKET_ID: 0x7E_nt!IoPageRead+1b

    BUCKET_ID: 0x7E_nt!IoPageRead+1b

    Followup: MachineOwner
     
  3. jumperg123

    jumperg123 TS Rookie Topic Starter

    Blue screen translated with Nirsoft bluescreenview

    ==================================================
    Dump File : Mini112209-03.dmp
    Crash Time : 2009-11-22 6:38:51 PM
    Bug Check String : IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x0000000a
    Parameter 1 : 0x00000004
    Parameter 2 : 0x00000002
    Parameter 3 : 0x00000001
    Parameter 4 : 0x804dc0ac
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini112209-03.dmp
    ==================================================

    ==================================================
    Dump File : Mini112209-02.dmp
    Crash Time : 2009-11-22 5:46:37 PM
    Bug Check String : PFN_LIST_CORRUPT
    Bug Check Code : 0x0000004e
    Parameter 1 : 0x0000008f
    Parameter 2 : 0x00040747
    Parameter 3 : 0x000600a7
    Parameter 4 : 0x00000000
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini112209-02.dmp
    ==================================================

    ==================================================
    Dump File : Mini112209-01.dmp
    Crash Time : 2009-11-22 10:19:15 AM
    Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
    Bug Check Code : 0x0000007f
    Parameter 1 : 0x0000000d
    Parameter 2 : 0x00000000
    Parameter 3 : 0x00000000
    Parameter 4 : 0x00000000
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini112209-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini111509-01.dmp
    Crash Time : 2009-11-15 6:53:58 PM
    Bug Check String : PFN_LIST_CORRUPT
    Bug Check Code : 0x0000004e
    Parameter 1 : 0x0000008f
    Parameter 2 : 0x0005f47d
    Parameter 3 : 0x00043d5d
    Parameter 4 : 0x00000000
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini111509-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini110709-01.dmp
    Crash Time : 2009-11-07 2:26:24 PM
    Bug Check String : BAD_POOL_CALLER
    Bug Check Code : 0x000000c2
    Parameter 1 : 0x00000040
    Parameter 2 : 0x00000000
    Parameter 3 : 0x80000000
    Parameter 4 : 0x00000000
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini110709-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini110609-01.dmp
    Crash Time : 2009-11-06 12:02:58 PM
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : 0xc0000005
    Parameter 2 : 0x8054bf87
    Parameter 3 : 0xf78e6c18
    Parameter 4 : 0xf78e6914
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini110609-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini100909-01.dmp
    Crash Time : 2009-10-09 6:40:07 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 0x00000020
    Parameter 2 : 0x88b395d8
    Parameter 3 : 0x88b39618
    Parameter 4 : 0x0a080005
    Caused By Driver : Ntfs.sys
    Caused By Address : Ntfs.sys+66ba
    File Description : NT File System Driver
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 5.1.2600.5512 (xpsp.080413-2111)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini100909-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini093009-02.dmp
    Crash Time : 2009-09-30 1:19:25 PM
    Bug Check String : NTFS_FILE_SYSTEM
    Bug Check Code : 0x00000024
    Parameter 1 : 0x001902fe
    Parameter 2 : 0xb71671e0
    Parameter 3 : 0xb7166edc
    Parameter 4 : 0x8056afab
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini093009-02.dmp
    ==================================================

    ==================================================
    Dump File : Mini093009-01.dmp
    Crash Time : 2009-09-30 12:42:24 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 0x00000020
    Parameter 2 : 0x88d636e4
    Parameter 3 : 0x88d63d8c
    Parameter 4 : 0x88d50f00
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini093009-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini081809-01.dmp
    Crash Time : 2009-08-18 9:55:49 PM
    Bug Check String : IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x0000000a
    Parameter 1 : 0x00000004
    Parameter 2 : 0x00000002
    Parameter 3 : 0x00000001
    Parameter 4 : 0x804dc0ac
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini081809-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini081309-01.dmp
    Crash Time : 2009-08-13 10:46:55 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 0x00000020
    Parameter 2 : 0x88d72ae8
    Parameter 3 : 0x88d72b10
    Parameter 4 : 0x0a050013
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini081309-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini073109-01.dmp
    Crash Time : 2009-07-31 9:02:09 PM
    Bug Check String : DRIVER_CORRUPTED_MMPOOL
    Bug Check Code : 0x000000d0
    Parameter 1 : 0x00000000
    Parameter 2 : 0x00000002
    Parameter 3 : 0x00000001
    Parameter 4 : 0x8054a180
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini073109-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini070709-01.dmp
    Crash Time : 2009-07-07 2:25:24 PM
    Bug Check String : KERNEL_DATA_INPAGE_ERROR
    Bug Check Code : 0x0000007a
    Parameter 1 : 0x00000003
    Parameter 2 : 0xc0000005
    Parameter 3 : 0x00137d90
    Parameter 4 : 0x00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+5c806
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini070709-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini062709-01.dmp
    Crash Time : 2009-06-26 11:28:03 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 0x00000020
    Parameter 2 : 0xe58ca598
    Parameter 3 : 0xe58ca6b8
    Parameter 4 : 0x0c240201
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini062709-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini050609-01.dmp
    Crash Time : 2009-05-06 3:00:33 PM
    Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000008e
    Parameter 1 : 0xc0000005
    Parameter 2 : 0x8054bbad
    Parameter 3 : 0xb4e81840
    Parameter 4 : 0x00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+74bad
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini050609-01.dmp
    ==================================================

    ==================================================
    Dump File : Mini041109-01.dmp
    Crash Time : 2009-04-11 7:48:28 AM
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : 0x0000002c
    Parameter 2 : 0x00000002
    Parameter 3 : 0x00000000
    Parameter 4 : 0xb972bd7f
    Caused By Driver :
    Caused By Address :
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : 32-bit
    Computer Name :
    Full Path : C:\WINDOWS\minidump\Mini041109-01.dmp
    ==================================================
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    With the varying types of errors there are three possibilities at this point (but certainly not ruling anything else out):

    1. Scan your system for infections.

    2. Do harddrive diagnostics. Find the make of your harddrive, go to their website, and download and run their free harddrive diagnostics utility.

    3. Run Memtest on your memory to see if any is corrupted. This is my first suspicion.


    See the link below and follow the instructions. There is a newer version than is listed but either one should work. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

    Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. There are 8 individual tests per Pass (8 tests = 1 Pass). Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced.

    Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


    Link: http://www.techspot.com/vb/topic62524.html


    * Get back to us with the results.
     
  5. jumperg123

    jumperg123 TS Rookie Topic Starter

    Thanks

    Yea Route44 good info. I actually ran the memtest last night with 59 passes but did not remove all but one stick each time. Will try that. Also, we are starting to suspect HArd drive failure and I will run that diag as well. Notiice that all my bluescreen shutdowns are from different reasons. If it was one issue wouldn't they be the same? I'll try those things first thanks.
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Bad RAM has been known to pass Memtest but I would say that with 59 Passes with all sticks in the harddrive diagnostics is the next logical choice.

    The reason that I suspected RAM in the first place is because corrupted memory can throw out all kinds of errors and cite other causes. I've seen it happen many times.

    If you could attach your five most recent minidumps I could read them because what you list doesn't give us the category of Probable Cause.
     
  7. jumperg123

    jumperg123 TS Rookie Topic Starter

    Actually, they are the most recent. I did chkdsk and defrag, adaware, malwarebytes, updated drivers and all that stuff Last week. Haven't Blue screened yet but as you can see from the dates it can happen 2 - 3 times in one day or not for 3 weeks. I wanted to really dig this time. Have a few event errors also. Always some red in there.
     
  8. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

  9. jumperg123

    jumperg123 TS Rookie Topic Starter

    Ok Great. I have some work to do. Thanks
     
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...