1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Rebooting Problem - Data Dump Attached

Discussion in 'Windows XP' started by aditya777, 2006/05/19.

  1. 2006/05/19
    aditya777

    aditya777 Inactive Thread Starter

    Joined:
    2006/05/19
    Messages:
    8
    Likes Received:
    0
    Hello,

    I have joined this forum today. I am facing a problem on windows xp home edition computer. It reboots all of a sudden, without any warning. After the system restarts, the dialog box comes, that the computer has recovered from a serious error and a dump has been created in c:\windows\minidump

    When I found this forum via google, I saw the http://www.windowsbbs.com/showthread.php?t=33471 post.

    Accordingly, I have generated debuglog.txt for 4 memory dumps. This i am pasting below. If someone can help solve this problem asap, it will be really helpful. This system is quite important to me. Thank you in advance.

    Please let me know if I need to put more info here.

    Regards.

    ------------------------------------------
    18-5-06 - below message copied from event viewer

    The computer has rebooted from a bugcheck. The bugcheck was: 0x100000c5 (0x0000089d, 0x00000002, 0x00000001, 0x8054ae34). A dump was saved in: C:\WINDOWS\Minidump\Mini051806-01.dmp.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    --------------The debuglog for 18-5-06

    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini051806-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu May 18 22:05:18.953 2006 (GMT+6)
    System Uptime: 0 days 0:22:02.515
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Loading Kernel Symbols
    ...................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *** ERROR: Module load completed but symbols could not be loaded for VETEFILE.SYS
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000C5, {89d, 2, 1, 8054ae34}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *** ERROR: Module load completed but symbols could not be loaded for VETMONNT.SYS
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for VET-FILT.SYS -
    *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
    Probably caused by : VETEFILE.SYS ( VETEFILE+61a7 )

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is
    caused by drivers that have corrupted the system pool. Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 0000089d, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 8054ae34, address which referenced memory

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 43d06767

    BUGCHECK_STR: 0xC5_2

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!ExAllocatePoolWithTag+4f0
    8054ae34 897104 mov [ecx+0x4],esi

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from eeee91a7 to 8054ae34

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ee33c214 eeee91a7 00000000 00000001 206b6444 nt!ExAllocatePoolWithTag+0x4f0
    ee33c224 eeef8ca4 0000000c 84ebda7c eeef8e17 VETEFILE+0x61a7
    ee33c230 eeef8e17 4a89d9d7 85520ea3 ee33c288 VETEFILE+0x15ca4
    ee33c244 eeef9582 ee33c288 85520ea3 ee33c3e4 VETEFILE+0x15e17
    ee33c268 eeef944f 85520ea3 ee33c288 ee33c3e4 VETEFILE+0x16582
    ee33c2d8 eeef94fc 85520ea3 00000000 ee33c3e4 VETEFILE+0x1644f
    ee33c34c eeef94fc 85640001 000006fd ee33c3e4 VETEFILE+0x164fc
    ee33c3c0 eeef5d8d 00000000 00000001 ee33c3e4 VETEFILE+0x164fc
    ee33c3e8 eeef5cbd 85532000 84cfe008 ee33c450 VETEFILE+0x12d8d
    ee33c3f8 eeef2c43 85532000 00000000 00000000 VETEFILE+0x12cbd
    ee33c450 eeef296a 00000000 854f89d8 ee33c4d8 VETEFILE+0xfc43
    ee33c478 eeef0b09 ee33c540 854f89d8 ee33c4d8 VETEFILE+0xf96a
    ee33c4b0 eeee3ba8 00000000 854f89d8 ee33c4d8 VETEFILE+0xdb09
    ee33c564 eeee390e 854f89d8 00000000 00008080 VETEFILE+0xba8
    ee33c5a8 eeee36dc 854f89d8 00000000 00000000 VETEFILE+0x90e
    ee33c684 eeee3663 854f89d8 ee33c7e0 00000000 VETEFILE+0x6dc
    ee33c750 eeee35ca 854f89d8 ee33c7e0 00000000 VETEFILE+0x663
    ee33c804 f7910335 84b61508 f7912628 f7912570 VETEFILE+0x5ca
    ee33c828 f790f67e 84b61508 f7912628 f7912570 VETMONNT+0x2335
    ee33c884 f790f818 84b61508 f7912628 f7912570 VETMONNT+0x167e
    ee33c8e4 f790f79b 84b61508 84d011bc 0000003f VETMONNT+0x1818
    ee33c8f8 f790e6b2 8577d720 84d01008 ee33c92c VETMONNT+0x179b
    ee33c944 f7906d9e 8577d720 84d01008 84d01018 VETMONNT+0x6b2
    ee33c9c0 804e37f7 8564aee8 84d01008 84d01008 VET_FILT+0xd9e
    ee33cab0 8056316c 857d1a68 00000000 85534008 nt!IofCallDriver+0x32
    ee33cb38 8056729a 00000000 ee33cb78 00000040 nt!RtlEqualUnicodeString+0x4cf
    ee33cb8c 80570b73 00000000 00000000 64afa001 nt!ObOpenObjectByName+0xdb
    ee33cc08 80570c42 02ade92c 80100080 02ade8cc nt!FsRtlCurrentBatchOplock+0x212
    ee33cc64 80570d78 02ade92c 80100080 02ade8cc nt!IoCreateFile+0x4f
    ee33cca4 eedd6c88 02ade92c 80100080 02ade8cc nt!NtCreateFile+0x30
    ee33cd30 804de7ec 02ade92c 80100080 02ade8cc vsdatant+0x18c88
    ee33cd64 7c90eb94 badb0d00 02ade894 00000000 nt!ZwYieldExecution+0xb78
    ee33cd68 badb0d00 02ade894 00000000 00000000 0x7c90eb94
    ee33cd6c 02ade894 00000000 00000000 00000000 0xbadb0d00
    ee33cd70 00000000 00000000 00000000 00000000 0x2ade894


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    VETEFILE+61a7
    eeee91a7 c3 ret

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: VETEFILE+61a7

    MODULE_NAME: VETEFILE

    IMAGE_NAME: VETEFILE.SYS

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ---------
    contd in next post
     
  2. 2006/05/19
    aditya777

    aditya777 Inactive Thread Starter

    Joined:
    2006/05/19
    Messages:
    8
    Likes Received:
    0
    contd from above
    ---------

    eax=84ce0088 ebx=80561940 ecx=00000899 edx=00000003 esi=80561988 edi=000001ff
    eip=8054ae34 esp=ee33c1c0 ebp=ee33c214 iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!ExAllocatePoolWithTag+0x4f0:
    8054ae34 897104 mov [ecx+0x4],esi ds:0023:0000089d=????????
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ee33c214 eeee91a7 00000000 00000001 206b6444 nt!ExAllocatePoolWithTag+0x4f0
    ee33c224 eeef8ca4 0000000c 84ebda7c eeef8e17 VETEFILE+0x61a7 (FPO: [1,0,0])
    ee33c230 eeef8e17 4a89d9d7 85520ea3 ee33c288 VETEFILE+0x15ca4 (FPO: [2,0,2])
    ee33c244 eeef9582 ee33c288 85520ea3 ee33c3e4 VETEFILE+0x15e17 (FPO: [2,0,2])
    ee33c268 eeef944f 85520ea3 ee33c288 ee33c3e4 VETEFILE+0x16582 (FPO: [Non-Fpo])
    ee33c2d8 eeef94fc 85520ea3 00000000 ee33c3e4 VETEFILE+0x1644f (FPO: [Non-Fpo])
    ee33c34c eeef94fc 85640001 000006fd ee33c3e4 VETEFILE+0x164fc (FPO: [Non-Fpo])
    ee33c3c0 eeef5d8d 00000000 00000001 ee33c3e4 VETEFILE+0x164fc (FPO: [Non-Fpo])
    ee33c3e8 eeef5cbd 85532000 84cfe008 ee33c450 VETEFILE+0x12d8d (FPO: [Non-Fpo])
    ee33c3f8 eeef2c43 85532000 00000000 00000000 VETEFILE+0x12cbd (FPO: [Non-Fpo])
    ee33c450 eeef296a 00000000 854f89d8 ee33c4d8 VETEFILE+0xfc43 (FPO: [Non-Fpo])
    ee33c478 eeef0b09 ee33c540 854f89d8 ee33c4d8 VETEFILE+0xf96a (FPO: [Non-Fpo])
    ee33c4b0 eeee3ba8 00000000 854f89d8 ee33c4d8 VETEFILE+0xdb09 (FPO: [Non-Fpo])
    ee33c564 eeee390e 854f89d8 00000000 00008080 VETEFILE+0xba8 (FPO: [Non-Fpo])
    ee33c5a8 eeee36dc 854f89d8 00000000 00000000 VETEFILE+0x90e (FPO: [Non-Fpo])
    ee33c684 eeee3663 854f89d8 ee33c7e0 00000000 VETEFILE+0x6dc (FPO: [Non-Fpo])
    ee33c750 eeee35ca 854f89d8 ee33c7e0 00000000 VETEFILE+0x663 (FPO: [Non-Fpo])
    ee33c804 f7910335 84b61508 f7912628 f7912570 VETEFILE+0x5ca (FPO: [Non-Fpo])
    ee33c828 f790f67e 84b61508 f7912628 f7912570 VETMONNT+0x2335 (FPO: [Non-Fpo])
    ee33c884 f790f818 84b61508 f7912628 f7912570 VETMONNT+0x167e (FPO: [Non-Fpo])
    start end module name
    804d7000 806eb100 nt ntoskrnl.exe Wed Mar 02 06:29:37 2005 (42250FF9)
    806ec000 8070c380 hal halaacpi.dll Wed Aug 04 11:29:05 2004 (41107B29)
    bf800000 bf9c1180 win32k win32k.sys Thu Oct 06 05:35:44 2005 (43446A58)
    bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 11:30:51 2004 (41107B93)
    bf9d4000 bf9e1000 ialmrnt5 ialmrnt5.dll Tue Apr 15 23:10:55 2003 (3E9C4427)
    bf9e1000 bfa03000 ialmdnt5 ialmdnt5.dll Tue Apr 15 23:09:42 2003 (3E9C43DE)
    bfa03000 bfa30e00 ialmdev5 ialmdev5.DLL Tue Apr 15 23:09:34 2003 (3E9C43D6)
    bfa31000 bfaa7000 ialmdd5 ialmdd5.DLL Tue Apr 15 23:09:09 2003 (3E9C43BD)
    ee028000 ee068100 HTTP HTTP.sys Sat Oct 09 05:18:20 2004 (41672744)
    ee6d0000 ee6e4400 wdmaud wdmaud.sys Wed Aug 04 11:45:03 2004 (41107EE7)
    ee875000 ee8c6300 srv srv.sys Tue May 10 05:47:49 2005 (427FFDAD)
    ee93f000 ee96b400 mrxdav mrxdav.sys Wed Aug 04 11:30:49 2004 (41107B91)
    eeb9c000 eebb3480 dump_atapi dump_atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
    eebb4000 eec40480 Ntfs Ntfs.SYS Wed Aug 04 11:45:06 2004 (41107EEA)
    eece1000 eed01f00 ipnat ipnat.sys Thu Sep 30 03:58:36 2004 (415B3714)
    eed02000 eed70400 mrxsmb mrxsmb.sys Wed Jan 19 09:56:50 2005 (41EDE18A)
    eed71000 eed9ba00 rdbss rdbss.sys Thu Oct 28 06:43:57 2004 (418047D5)
    eed9c000 eedbdd00 afd afd.sys Wed Aug 04 11:44:13 2004 (41107EB5)
    eedbe000 eee17940 vsdatant vsdatant.sys Thu Mar 16 23:18:29 2006 (4419A4ED)
    eee18000 eee3fc00 netbt netbt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
    eee40000 eee97d80 tcpip tcpip.sys Fri Jan 13 07:58:12 2006 (43C7103C)
    eee98000 eeeaa400 ipsec ipsec.sys Wed Aug 04 11:44:27 2004 (41107EC3)
    eeecb000 eeee2c40 VETEBOOT VETEBOOT.SYS Fri Jan 20 10:00:30 2006 (43D06766)
    eeee3000 eef63fa0 VETEFILE VETEFILE.SYS Fri Jan 20 10:00:31 2006 (43D06767)
    eef90000 eef92900 Dxapi Dxapi.sys Sat Aug 18 02:23:19 2001 (3B7D843F)
    eefdc000 eeff7b60 ialmsbw ialmsbw.sys Tue Apr 15 23:10:51 2003 (3E9C4423)
    eeff8000 ef00b3a0 ialmkchw ialmkchw.sys Tue Apr 15 23:10:44 2003 (3E9C441C)
    f708c000 f708e280 rasacd rasacd.sys Sat Aug 18 02:25:39 2001 (3B7D84CB)
    f7098000 f709b920 VET_REC VET-REC.SYS Fri Apr 29 06:12:32 2005 (427182F8)
    f70a0000 f70a3820 VETFDDNT VETFDDNT.SYS Fri Apr 29 06:12:33 2005 (427182F9)
    f7104000 f7137200 update update.sys Wed Aug 04 11:28:32 2004 (41107B08)
    f7138000 f7148e00 psched psched.sys Wed Aug 04 11:34:16 2004 (41107C60)
    f7199000 f71a7d80 sysaudio sysaudio.sys Wed Aug 04 11:45:54 2004 (41107F1A)
    f71e9000 f71ff680 ndiswan ndiswan.sys Wed Aug 04 11:44:30 2004 (41107EC6)
    f7200000 f725f900 ALCXSENS ALCXSENS.SYS Thu Dec 11 17:08:41 2003 (3FD85741)
    f7260000 f7283980 portcls portcls.sys Wed Aug 04 11:45:47 2004 (41107F13)
    f7284000 f73146c0 ALCXWDM ALCXWDM.SYS Fri Jan 09 20:46:59 2004 (3FFEC5EB)
    f733d000 f735f680 ks ks.sys Wed Aug 04 11:45:20 2004 (41107EF8)
    f7360000 f7373900 parport parport.sys Wed Aug 04 11:29:04 2004 (41107B28)
    f7374000 f7397800 e100b325 e100b325.sys Wed Mar 05 01:26:25 2003 (3E6504E9)
    f7398000 f73bae80 USBPORT USBPORT.SYS Wed Aug 04 11:38:34 2004 (41107D62)
    f73bb000 f73ce780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 11:37:04 2004 (41107D08)
    f73cf000 f73e52e0 ialmnt5 ialmnt5.sys Tue Apr 15 23:09:44 2003 (3E9C43E0)
    f7409000 f7409b80 Null Null.SYS Sat Aug 18 02:17:39 2001 (3B7D82EB)
    f7447000 f7447c00 audstub audstub.sys Sat Aug 18 02:29:40 2001 (3B7D85BC)
    f74b4000 f74ce580 Mup Mup.sys Wed Aug 04 11:45:20 2004 (41107EF8)
    f74cf000 f74fba80 NDIS NDIS.sys Wed Aug 04 11:44:27 2004 (41107EC3)
    f74fc000 f7512780 KSecDD KSecDD.sys Wed Aug 04 11:29:45 2004 (41107B51)
    f7513000 f7536000 Fastfat Fastfat.sys Wed Aug 04 11:44:15 2004 (41107EB7)
    f7536000 f7547f00 sr sr.sys Wed Aug 04 11:36:22 2004 (41107CDE)
    f7548000 f7566780 fltMgr fltMgr.sys Wed Aug 04 11:31:17 2004 (41107BAD)
    f7567000 f757e480 atapi atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
    f757f000 f759d880 ftdisk ftdisk.sys Sat Aug 18 02:22:41 2001 (3B7D8419)
    f759e000 f75aea80 pci pci.sys Wed Aug 04 11:37:45 2004 (41107D31)
    f75af000 f75dcd80 ACPI ACPI.sys Wed Aug 04 11:37:35 2004 (41107D27)
    f75fe000 f7606c00 isapnp isapnp.sys Sat Aug 18 02:28:01 2001 (3B7D8559)
    f760e000 f7618500 MountMgr MountMgr.sys Wed Aug 04 11:28:29 2004 (41107B05)
    f761e000 f762ac80 VolSnap VolSnap.sys Wed Aug 04 11:30:14 2004 (41107B6E)
    f762e000 f7636e00 disk disk.sys Wed Aug 04 11:29:53 2004 (41107B59)
    f763e000 f764a200 CLASSPNP CLASSPNP.SYS Wed Aug 04 11:44:26 2004 (41107EC2)
    f766e000 f7676e40 SMBios SMBios.sys Fri Sep 12 03:50:22 2003 (3F60F526)
    f768e000 f7696d00 intelppm intelppm.sys Wed Aug 04 11:29:19 2004 (41107B37)
    f769e000 f76a8800 dlkfet5b dlkfet5b.sys Wed Jan 19 12:06:59 2005 (41EE000B)
    f76ae000 f76bae00 i8042prt i8042prt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
    f76be000 f76cdd80 serial serial.sys Wed Aug 04 11:45:51 2004 (41107F17)
    f76ce000 f76d8380 imapi imapi.sys Wed Aug 04 11:30:12 2004 (41107B6C)
    f76de000 f76e6c00 AFS2K AFS2K.SYS Fri Oct 08 06:46:03 2004 (4165EA53)
    f76ee000 f76fa180 cdrom cdrom.sys Wed Aug 04 11:29:52 2004 (41107B58)
    f76fe000 f770c080 redbook redbook.sys Wed Aug 04 11:29:34 2004 (41107B46)
    f770e000 f771cb80 drmk drmk.sys Wed Aug 04 11:37:54 2004 (41107D3A)
    f771e000 f772a880 rasl2tp rasl2tp.sys Wed Aug 04 11:44:21 2004 (41107EBD)
    f772e000 f7738200 raspppoe raspppoe.sys Wed Aug 04 11:35:06 2004 (41107C92)
    f773e000 f7749d00 raspptp raspptp.sys Wed Aug 04 11:44:26 2004 (41107EC2)
    f774e000 f7756900 msgpc msgpc.sys Wed Aug 04 11:34:11 2004 (41107C5B)
    f775e000 f7767f00 termdd termdd.sys Wed Aug 04 11:28:52 2004 (41107B1C)
    f776e000 f7777480 NDProxy NDProxy.SYS Sat Aug 18 02:25:30 2001 (3B7D84C2)
    f778e000 f779c100 usbhub usbhub.sys Wed Aug 04 11:38:40 2004 (41107D68)
    f77ae000 f77b6700 netbios netbios.sys Wed Aug 04 11:33:19 2004 (41107C27)
    f77be000 f77c6880 Fips Fips.SYS Sat Aug 18 07:01:49 2001 (3B7DC585)
    f77ce000 f77d6700 wanarp wanarp.sys Wed Aug 04 11:34:57 2004 (41107C89)
    f77ee000 f77fd900 Cdfs Cdfs.SYS Wed Aug 04 11:44:09 2004 (41107EB1)
    f787e000 f7884200 PCIIDEX PCIIDEX.SYS Wed Aug 04 11:29:40 2004 (41107B4C)
    f7886000 f788a900 PartMgr PartMgr.sys Sat Aug 18 07:02:23 2001 (3B7DC5A7)
    f78b6000 f78bb000 usbuhci usbuhci.sys Wed Aug 04 11:38:34 2004 (41107D62)
    f78be000 f78c4800 usbehci usbehci.sys Wed Aug 04 11:38:34 2004 (41107D62)
    f78c6000 f78cc000 kbdclass kbdclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
    f78ce000 f78d3a00 mouclass mouclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
    f78d6000 f78d7000 fdc fdc.sys unavailable (00000000)
    f78de000 f78e2880 TDI TDI.SYS Wed Aug 04 11:37:47 2004 (41107D33)
    f78e6000 f78ea580 ptilink ptilink.sys Sat Aug 18 02:19:53 2001 (3B7D8371)
    f78ee000 f78f2080 raspti raspti.sys Sat Aug 18 02:25:32 2001 (3B7D84C4)
    f78f6000 f78fb000 flpydisk flpydisk.sys Wed Aug 04 11:29:24 2004 (41107B3C)
    f7906000 f790ace0 VET_FILT VET-FILT.SYS Fri Apr 29 06:12:32 2005 (427182F8)
    f790e000 f7913d00 VETMONNT VETMONNT.SYS Mon Feb 20 05:43:09 2006 (43F90995)
    f7916000 f791b200 vga vga.sys Wed Aug 04 11:37:06 2004 (41107D0A)
    f791e000 f7922a80 Msfs Msfs.SYS Wed Aug 04 11:30:37 2004 (41107B85)
    f7926000 f792d880 Npfs Npfs.SYS Wed Aug 04 11:30:38 2004 (41107B86)
    f792e000 f7932500 watchdog watchdog.sys Wed Aug 04 11:37:32 2004 (41107D24)
    f7a0e000 f7a11000 BOOTVID BOOTVID.dll Sat Aug 18 02:19:09 2001 (3B7D8345)
    f7a82000 f7a85c80 serenum serenum.sys Wed Aug 04 11:29:06 2004 (41107B2A)
    f7a8a000 f7a8c580 ndistapi ndistapi.sys Sat Aug 18 02:25:29 2001 (3B7D84C1)
    f7a9a000 f7a9dc80 mssmbios mssmbios.sys Wed Aug 04 11:37:47 2004 (41107D33)
    f7abe000 f7ac1280 ndisuio ndisuio.sys Wed Aug 04 11:33:10 2004 (41107C1E)
    f7afe000 f7affb80 kdcom kdcom.dll Sat Aug 18 02:19:10 2001 (3B7D8346)
    f7b00000 f7b01100 WMILIB WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
    f7b02000 f7b03580 intelide intelide.sys Wed Aug 04 11:29:40 2004 (41107B4C)
    f7b04000 f7b05100 swenum swenum.sys Wed Aug 04 11:28:41 2004 (41107B11)
    f7b06000 f7b07280 USBD USBD.SYS Sat Aug 18 02:32:58 2001 (3B7D8682)
    f7b08000 f7b09f00 Fs_Rec Fs_Rec.SYS Sat Aug 18 02:19:37 2001 (3B7D8361)
    f7b0a000 f7b0b080 Beep Beep.SYS Sat Aug 18 02:17:33 2001 (3B7D82E5)
    f7b0c000 f7b0d080 mnmdd mnmdd.SYS Sat Aug 18 02:27:28 2001 (3B7D8538)
    f7b0e000 f7b0f080 RDPCDD RDPCDD.sys Sat Aug 18 02:16:56 2001 (3B7D82C0)
    f7b1a000 f7b1b100 dump_WMILIB dump_WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
    f7b4a000 f7b4ba80 ParVdm ParVdm.SYS Sat Aug 18 02:19:49 2001 (3B7D836D)
    f7bc6000 f7bc6d00 pciide pciide.sys Sat Aug 18 02:21:49 2001 (3B7D83E5)
    f7d0f000 f7d0fd00 dxgthk dxgthk.sys Sat Aug 18 02:23:12 2001 (3B7D8438)

    Unloaded modules:
    ede44000 ede6e000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    edf0e000 edf38000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ee683000 ee6ad000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7cca000 f7ccb000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ee855000 ee862000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ee865000 ee873000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ee6ad000 ee6d0000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7b58000 f7b5a000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f78fe000 f7903000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f709c000 f709f000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt

    ---------------------------------------------end of 18-5-06
     

  3. to hide this advert.

  4. 2006/05/19
    aditya777

    aditya777 Inactive Thread Starter

    Joined:
    2006/05/19
    Messages:
    8
    Likes Received:
    0
    I apologize for posting often. The data in above post was generated by the WindowsBBS tool. Below i am posting the results from windows debug tool for 17-5-06. (I did this coz windowsBBS log was too long to post for every log. I have 4 logs for 4 minidumps.)

    ----------------------------

    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini051706-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded 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 = 0x8055a420
    Debug session time: Wed May 17 11:34:00.140 2006 (GMT+5)
    System Uptime: 0 days 1:40:54.703
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded 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, {1c, 2, 1, 8053b885}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+64885 )

    Followup: MachineOwner
    ---------
     
  5. 2006/05/19
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412

    You should fix your Symbols first. Re-download and/or re-install.
     
    Arie,
    #4
  6. 2006/05/19
    aditya777

    aditya777 Inactive Thread Starter

    Joined:
    2006/05/19
    Messages:
    8
    Likes Received:
    0
    What do I re-install - the windows program or BBS program?

    Otherwise, is it not possible for you to diagnose the problem? A friend of mine told me to increase the page file size (virtual memory) as the blue screen hasnt been visible till now.
     
  7. 2006/05/19
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
  8. 2006/05/20
    aditya777

    aditya777 Inactive Thread Starter

    Joined:
    2006/05/19
    Messages:
    8
    Likes Received:
    0
  9. 2006/05/22
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Hardware problem

    Hi,

    Your windows is crashed with at eTrust Antivirus. De-install or upgrade eTrust Anti-Virus. If it still crashes, it is hardware problem.
     
    Last edited: 2006/05/22
  10. 2006/05/22
    aditya777

    aditya777 Inactive Thread Starter

    Joined:
    2006/05/19
    Messages:
    8
    Likes Received:
    0
    Yes i do have etrust ez antivirus. I will try replacing the same. Thank you for the help. I have been unable to replace the symbols as per Arie's message.

     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.