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.

XP Stop errors

Discussion in 'Windows XP' started by MrRam, 2008/03/28.

  1. 2008/03/28
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    I am having a problem that no one (even Microsoft) can seem to fix. Periodically my computer suddenly stops and I get: "Stop error to protect your computer" 0X0000008E (0xC000001D, 0X8056FAF3, 0XB71A5C68, 0x00000000) the third sequence in bold changes from time to time to: 0XADBF8C68 or 0XB530AC68. Also, in Diskkeeper it shows numerous "Low Performing System Files" yet Microsoft tech can't answer that either. Any ideas or suggestions welcomed.
    Thank you
     
  2. 2008/03/28
    I am hopeless

    I am hopeless Inactive

    Joined:
    2008/03/28
    Messages:
    3
    Likes Received:
    0
    What antispyware and anti-virus programmes have you run? What have you installed permanently and what freeware and online scanners have you used in order to locate a possible infection?
     

  3. to hide this advert.

  4. 2008/03/28
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    MrRam - Welcome to the Board :)
    Setup your computer to give a Memory Dump and follow the instructions below to debug it and post the dump log .....

    http://www.windowsbbs.com/showthread.php?t=33471

    I would not lose a second's sleep over "Low Performing System Files" flagged by Diskeeper. If you Google a bit you will find suggestions that a boot time defrag may help - or not as the case may be. IMHO leave sleeping dogs lie - I have had the odd problem in the past with a boot time defrag and avoid it :)

    I doubt that you would notice any performance boost in 'fixing' them and switching to the file structure view rather than file performance resolves the problem nicely :) Seriously though people get really hung up on disk fragmentation - much to the benefit of Diskeeper and other software vendors.

    FWIW - I run Diskeeper Pro 2008 on XP Pro SP3 and a quck check shows no "Low Performing System Files "

    I am hopeless IMO you are in the wrong ball park - this has nothing to do with malware.
     
  5. 2008/03/28
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, MrRam. Welcome to Windows BBS! :)

    • aumha.org: Troubleshooting Windows STOP Messages

    Please carefully follow all the instructions in this link and then paste DebugWiz-generated BSOD dump log analysis reports for a few of your most recent crashes in this thread.

    Sometimes seeing a few dump logs helps us determine whether there is any pattern to the crashes or not. The additional information the DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

    NOTE:

    EDIT: Hi, Pete. Ya beat me to it this time. :)
     
    Last edited: 2008/03/28
  6. 2008/03/28
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Faster, Mailman, faster :D :D
     
  7. 2008/03/28
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    I Hope this dump is done right

    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Comment: 'Dr. Watson generated MiniDump'
    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
    Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: SingleUserTS
    Debug session time: Fri Mar 28 10:19:04.000 2008 (GMT-5)
    System Uptime: not available
    Process Uptime: 0 days 0:07:22.000
    ..................................................................................................................................................
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (930.78c): Access violation - code c0000005 (first/second chance not available)
    eax=00000000 ebx=00000000 ecx=0579fe87 edx=00000000 esi=251cb458 edi=81a1000f
    eip=251746a4 esp=0579fe94 ebp=0579fea0 iopl=0 nv up ei pl zr na pe nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for seal.dll -
    seal!DllUnregisterServer+0x1f38f:
    251746a4 891d00000000 mov dword ptr ds:[0],ebx ds:0023:00000000=????????
    0:012> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for msnmetal.dll -
    *** ERROR: Module load completed but symbols could not be loaded for msn.exe
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for sealdef.dll -
    *** WARNING: Unable to verify checksum for sqlse20.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for sqlse20.dll -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for txduser.dll -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for hmssm9.dll -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for Flash9e.ocx -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for DAVAdptr.dll -
    *** WARNING: Unable to verify checksum for nview.dll
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for nview.dll -
    *************************************************************************
    *** ***
    *** ***
    *** 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: kernel32!pNlsUserInfo ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: kernel32!pNlsUserInfo ***
    *** ***
    *************************************************************************

    FAULTING_IP:
    seal!DllUnregisterServer+1f38f
    251746a4 891d00000000 mov dword ptr ds:[0],ebx

    EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
    .exr 0xffffffffffffffff
    ExceptionAddress: 251746a4 (seal!DllUnregisterServer+0x0001f38f)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000001
    Parameter[1]: 00000000
    Attempt to write to address 00000000

    DEFAULT_BUCKET_ID: APPLICATION_FAULT

    PROCESS_NAME: msn.exe

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

    WRITE_ADDRESS: 00000000

    BUGCHECK_STR: ACCESS_VIOLATION

    LAST_CONTROL_TRANSFER: from 251a7597 to 251746a4

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0579fea0 251a7597 251cb458 0037cd28 00000000 seal!DllUnregisterServer+0x1f38f
    0579feb8 251a67b2 00000000 00000000 00377128 seal!DllUnregisterServer+0x52282
    0579ff30 251a50b0 0037ce00 0037d8e8 251cb164 seal!DllUnregisterServer+0x5149d
    0579ff48 25174ca6 00377128 0b79e818 0037e578 seal!DllUnregisterServer+0x4fd9b
    0579ff64 251751e3 251cb138 2516d110 7c91056d seal!DllUnregisterServer+0x1f991
    0579ff88 2515b908 00000000 251cb138 00000000 seal!DllUnregisterServer+0x1fece
    0579ffb4 7c80b683 011cb138 7c91056d 00000000 seal!DllUnregisterServer+0x65f3
    0579ffec 00000000 2515b86e 251cb138 00000000 kernel32!BaseThreadStart+0x37


    FAULTING_THREAD: 0000078c

    FOLLOWUP_IP:
    seal!DllUnregisterServer+1f38f
    251746a4 891d00000000 mov dword ptr ds:[0],ebx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: seal!DllUnregisterServer+1f38f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: seal

    IMAGE_NAME: seal.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 45ff9490

    STACK_COMMAND: ~12s; .ecxr ; kb

    BUCKET_ID: ACCESS_VIOLATION_seal!DllUnregisterServer+1f38f

    FAILURE_BUCKET_ID: seal.dll!DllUnregisterServer_c0000005_APPLICATION_FAULT

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

    eax=00000000 ebx=00000000 ecx=0579fe87 edx=00000000 esi=251cb458 edi=81a1000f
    eip=251746a4 esp=0579fe94 ebp=0579fea0 iopl=0 nv up ei pl zr na pe nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
    seal!DllUnregisterServer+0x1f38f:
    251746a4 891d00000000 mov dword ptr ds:[0],ebx ds:0023:00000000=????????
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0579fea0 251a7597 251cb458 0037cd28 00000000 seal!DllUnregisterServer+0x1f38f
    0579feb8 251a67b2 00000000 00000000 00377128 seal!DllUnregisterServer+0x52282
    0579ff30 251a50b0 0037ce00 0037d8e8 251cb164 seal!DllUnregisterServer+0x5149d
    0579ff48 25174ca6 00377128 0b79e818 0037e578 seal!DllUnregisterServer+0x4fd9b
    0579ff64 251751e3 251cb138 2516d110 7c91056d seal!DllUnregisterServer+0x1f991
    0579ff88 2515b908 00000000 251cb138 00000000 seal!DllUnregisterServer+0x1fece
    0579ffb4 7c80b683 011cb138 7c91056d 00000000 seal!DllUnregisterServer+0x65f3
    0579ffec 00000000 2515b86e 251cb138 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo])
    start end module name
    00400000 0041c000 msn msn.exe Tue Mar 20 02:59:40 2007 (45FF946C)
    00960000 00ad0000 nview nview.dll Thu Oct 12 10:53:25 2006 (452E64F5)
    00c20000 00c2f000 PATROLPRO PATROLPRO.DLL Mon Mar 26 13:03:20 2007 (46080AE8)
    00c60000 00c69000 normaliz normaliz.dll Thu Jun 29 10:05:42 2006 (44A3EC46)
    01130000 013f5000 xpsp2res xpsp2res.dll Wed Aug 04 02:56:41 2004 (411096B9)
    01b20000 01b35000 nvwddi nvwddi.dll Sun Oct 22 17:26:01 2006 (453BEFF9)
    03080000 0308b000 LGMSGHK LGMSGHK.DLL Thu Jan 08 13:09:59 2004 (3FFDAB07)
    03600000 03688000 shdoclc shdoclc.dll Wed Aug 04 02:56:37 2004 (411096B5)
    077b0000 0782a000 msnap msnap.dll Wed Oct 11 22:17:11 2006 (452DB3B7)
    0ffd0000 0fff8000 rsaenh rsaenh.dll Tue Jul 06 21:17:12 2004 (40EB5D28)
    10000000 10007000 LgWndHk LgWndHk.dll Thu Jan 08 13:10:00 2004 (3FFDAB08)
    1b000000 1b00c000 imgutil imgutil.dll Tue Oct 17 14:57:55 2006 (453535C3)
    20060000 20286000 msnmetal msnmetal.dll Tue Mar 20 02:59:26 2007 (45FF945E)
    20760000 207af000 msnmtllc msnmtllc.dll Tue Mar 20 02:53:00 2007 (45FF92DC)
    208c0000 208f6000 txduser txduser.dll Tue Mar 20 02:59:07 2007 (45FF944B)
    209b0000 20a15000 txsrvc txsrvc.dll Tue Mar 20 02:59:17 2007 (45FF9455)
    20bb0000 20c0d000 winpc winpc.dll Tue Mar 20 02:59:49 2007 (45FF9475)
    21800000 21961000 mailui mailui.dll Tue Mar 20 03:00:36 2007 (45FF94A4)
    21d00000 21d93000 mailapi mailapi.dll Tue Mar 20 03:00:29 2007 (45FF949D)
    22500000 22522000 mailutil mailutil.dll Tue Mar 20 03:00:27 2007 (45FF949B)
    22580000 2258d000 mailares mailares.dll Tue Mar 20 02:58:18 2007 (45FF941A)
    22bd0000 22cab000 mailres mailres.dll Tue Mar 20 02:58:51 2007 (45FF943B)
    23800000 23831000 custsat custsat.dll Tue Mar 20 03:00:41 2007 (45FF94A9)
    25080000 250b1000 micore micore.dll Tue Mar 20 02:59:51 2007 (45FF9477)
    25140000 251ec000 seal seal.dll Tue Mar 20 03:00:16 2007 (45FF9490)
    25420000 2543a000 sealdef sealdef.dll Tue Mar 20 02:59:53 2007 (45FF9479)
    255f0000 25634000 DAVAdptr DAVAdptr.dll Tue Mar 20 02:59:56 2007 (45FF947C)
    26140000 26158000 Calrecur Calrecur.dll Tue Mar 20 03:00:12 2007 (45FF948C)
    26180000 26244000 hmssm9 hmssm9.dll Tue Mar 20 03:00:05 2007 (45FF9485)
    26380000 263c8000 mailf mailf.dll Tue Mar 20 03:00:11 2007 (45FF948B)
    27280000 272dd000 msninst msninst.dll Mon Mar 19 17:44:38 2007 (45FF1256)
    29000000 2901b000 sqlse20 sqlse20.dll Mon Oct 27 13:43:26 2003 (3F9D674E)
    29020000 29045000 sqldb20 sqldb20.dll Mon Oct 27 13:55:30 2003 (3F9D6A22)
    30000000 303ae000 Flash9e Flash9e.ocx Tue Nov 20 18:04:03 2007 (474375F3)
    38a70000 38a7c000 MSOXMLMF MSOXMLMF.DLL Thu Oct 26 23:31:00 2006 (45418B84)
    41e30000 41e3e000 pngfilt pngfilt.dll Thu Jan 10 23:53:32 2008 (4787045C)
    42010000 42067000 dxtmsft dxtmsft.dll Wed Dec 19 17:01:06 2007 (4769A2B2)
    420c0000 420f9000 dxtrans dxtrans.dll Thu Dec 06 20:21:45 2007 (4758AE39)
    42990000 429d5000 iertutil iertutil.dll Thu Dec 06 20:21:51 2007 (4758AE3F)
    42b40000 42b73000 msrating msrating.dll Thu Dec 06 20:21:50 2007 (4758AE3E)
    42b90000 42c07000 mshtmled mshtmled.dll Thu Dec 06 20:21:49 2007 (4758AE3D)
    42c10000 42cdf000 wininet wininet.dll Thu Dec 06 20:21:48 2007 (4758AE3C)
    42cf0000 42e17000 urlmon urlmon.dll Thu Dec 06 20:21:48 2007 (4758AE3C)
    42ef0000 434bd000 ieframe ieframe.dll Thu Dec 06 20:21:49 2007 (4758AE3D)
    435d0000 43944000 mshtml mshtml.dll Thu Dec 06 20:21:48 2007 (4758AE3C)
    4d4f0000 4d548000 winhttp winhttp.dll Wed Aug 04 02:57:07 2004 (411096D3)
    4ec50000 4edf3000 GdiPlus GdiPlus.dll Wed Aug 04 02:55:55 2004 (4110968B)
    58760000 58792000 iepeers iepeers.dll Tue Nov 07 23:03:34 2006 (45516526)
    59000000 5903a000 msgsc_8_1_0178_00 msgsc.8.1.0178.00.dll Fri Jan 19 14:36:25 2007 (45B12BC9)
    5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 02:56:43 2004 (411096BB)
    5b0a0000 5b0a7000 umdmxfrm umdmxfrm.dll Sat Aug 18 00:35:53 2001 (3B7DFEB9)
    5b860000 5b8b4000 netapi32 netapi32.dll Thu Aug 17 07:28:27 2006 (44E460EB)
    5cd70000 5cd77000 serwvdrv serwvdrv.dll Sat Aug 18 00:35:55 2001 (3B7DFEBB)
    5ddc0000 5ddc9000 qmgrprxy qmgrprxy.dll Wed Aug 04 02:56:30 2004 (411096AE)
    5e0c0000 5e0cd000 pstorec pstorec.dll Wed Aug 04 02:57:03 2004 (411096CF)
    63380000 633f8000 jscript jscript.dll Tue Oct 17 14:59:54 2006 (4535363A)
    63f00000 63f0c000 mscorie mscorie.dll Tue Oct 23 22:29:38 2007 (471EBC22)
    662b0000 66308000 hnetcfg hnetcfg.dll Wed Aug 04 02:56:16 2004 (411096A0)
    68100000 68124000 dssenh dssenh.dll Fri May 14 20:06:23 2004 (40A56D0F)
    69000000 6900e000 SwSupport SwSupport.dll Wed Jan 09 04:38:35 2002 (3C3C1DAB)
    6d430000 6d43a000 ddrawex ddrawex.dll Wed Aug 04 02:56:17 2004 (411096A1)
    71a50000 71a8f000 mswsock mswsock.dll Wed Aug 04 02:59:20 2004 (41109758)
    71a90000 71a98000 wshtcpip wshtcpip.dll Wed Aug 04 02:57:49 2004 (411096FD)
    71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 02:57:39 2004 (411096F3)
    71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 02:57:38 2004 (411096F2)
    71ad0000 71ad9000 wsock32 wsock32.dll Wed Aug 04 02:57:51 2004 (411096FF)
    71bf0000 71c03000 samlib samlib.dll Wed Aug 04 02:56:29 2004 (411096AD)
    71d40000 71d5c000 actxprxy actxprxy.dll Wed Aug 04 02:56:04 2004 (41109694)
    722b0000 722b5000 sensapi sensapi.dll Wed Aug 04 02:56:28 2004 (411096AC)
    72cf0000 72cf7000 msadp32 msadp32.acm Wed Aug 04 02:57:19 2004 (411096DF)
    72d10000 72d18000 msacm32 msacm32.drv Sat Aug 18 00:33:30 2001 (3B7DFE2A)
    72d20000 72d29000 wdmaud wdmaud.drv Wed Aug 04 02:56:54 2004 (411096C6)
    73000000 73026000 winspool winspool.drv Wed Aug 04 02:56:38 2004 (411096B6)
    73760000 737a9000 ddraw ddraw.dll Wed Aug 04 02:56:16 2004 (411096A0)
    73bc0000 73bc6000 dciman32 dciman32.dll Wed Aug 04 02:56:15 2004 (4110969F)
    73ee0000 73ee4000 ksuser ksuser.dll Wed Aug 04 02:56:29 2004 (411096AD)
    73f10000 73f6c000 dsound dsound.dll Wed Aug 04 02:57:08 2004 (411096D4)
    746c0000 746e9000 msls31 msls31.dll Tue Nov 07 23:03:34 2006 (45516526)
    746f0000 7471a000 msimtf msimtf.dll Wed Aug 04 02:58:33 2004 (41109729)
    74720000 7476b000 msctf msctf.dll Wed Aug 04 02:57:30 2004 (411096EA)
    74980000 74a93000 msxml3 msxml3.dll Tue Jun 26 01:08:16 2007 (4680AD50)
    74d90000 74dfb000 usp10 usp10.dll Wed Aug 04 02:56:42 2004 (411096BA)
    74e30000 74e9c000 riched20 riched20.dll Mon Nov 27 08:54:06 2006 (456AFC0E)
    754d0000 75550000 cryptui cryptui.dll Wed Aug 04 02:56:06 2004 (41109696)
    755c0000 755ee000 msctfime msctfime.ime Wed Aug 04 02:57:31 2004 (411096EB)
    75cf0000 75d81000 mlang mlang.dll Wed Aug 04 02:56:29 2004 (411096AD)
    75e60000 75e73000 cryptnet cryptnet.dll Wed Aug 04 02:56:04 2004 (41109694)
    75e90000 75f40000 sxs sxs.dll Thu Oct 19 08:56:28 2006 (4537840C)
    75f80000 7607d000 browseui browseui.dll Thu Sep 14 03:31:25 2006 (4509135D)
    76080000 760e5000 msvcp60 msvcp60.dll Wed Aug 04 02:59:13 2004 (41109751)
    76360000 76370000 winsta winsta.dll Wed Aug 04 02:56:40 2004 (411096B8)
    76380000 76385000 msimg32 msimg32.dll Wed Aug 04 02:58:31 2004 (41109727)
    76390000 763ad000 imm32 imm32.dll Wed Aug 04 02:56:30 2004 (411096AE)
    763b0000 763f9000 comdlg32 comdlg32.dll Wed Aug 04 02:56:32 2004 (411096B0)
    76780000 76789000 shfolder shfolder.dll Wed Aug 04 02:56:40 2004 (411096B8)
    767f0000 76817000 schannel schannel.dll Wed Apr 25 09:21:15 2007 (462F63DB)
    769c0000 76a73000 userenv userenv.dll Wed Aug 04 02:56:41 2004 (411096B9)
    76b20000 76b31000 atl atl.dll Wed Aug 04 02:56:55 2004 (411096C7)
    76b40000 76b6d000 winmm winmm.dll Wed Aug 04 02:57:10 2004 (411096D6)
    76bf0000 76bfb000 psapi psapi.dll Wed Aug 04 02:56:58 2004 (411096CA)
    76c00000 76c2e000 credui credui.dll Wed Aug 04 02:56:42 2004 (411096BA)
    76c30000 76c5e000 wintrust wintrust.dll Wed Aug 04 02:56:41 2004 (411096B9)
    76c90000 76cb8000 imagehlp imagehlp.dll Wed Aug 04 02:56:25 2004 (411096A9)
    76d40000 76d58000 mprapi mprapi.dll Wed Aug 04 02:56:47 2004 (411096BF)
    76d60000 76d79000 iphlpapi iphlpapi.dll Fri May 19 07:59:41 2006 (446DC13D)
    76e10000 76e35000 adsldpc adsldpc.dll Wed Aug 04 02:56:13 2004 (4110969D)
    76e80000 76e8e000 rtutils rtutils.dll Wed Aug 04 02:56:36 2004 (411096B4)
    76e90000 76ea2000 rasman rasman.dll Wed Aug 04 02:56:29 2004 (411096AD)
    76eb0000 76edf000 tapi32 tapi32.dll Wed Aug 04 02:56:38 2004 (411096B6)
    76ee0000 76f1c000 rasapi32 rasapi32.dll Wed Aug 04 02:56:25 2004 (411096A9)
    76f20000 76f47000 dnsapi dnsapi.dll Mon Jun 26 12:37:10 2006 (44A01B46)
    76f50000 76f58000 wtsapi32 wtsapi32.dll Wed Aug 04 02:57:55 2004 (41109703)
    76f60000 76f8c000 wldap32 wldap32.dll Wed Aug 04 02:56:43 2004 (411096BB)
    76fb0000 76fb8000 winrnr winrnr.dll Wed Aug 04 02:56:35 2004 (411096B3)
    76fc0000 76fc6000 rasadhlp rasadhlp.dll Mon Jun 26 12:37:10 2006 (44A01B46)
    76fd0000 7704f000 clbcatq clbcatq.dll Mon Jul 25 23:39:44 2005 (42E5BE90)
    77050000 77115000 comres comres.dll Wed Aug 04 02:56:36 2004 (411096B4)
    77120000 771ab000 oleaut32 oleaut32.dll Tue Dec 04 12:38:12 2007 (47559E94)
    773d0000 774d3000 comctl32 comctl32.dll Fri Aug 25 10:45:55 2006 (44EF1B33)
    774e0000 7761d000 ole32 ole32.dll Mon Jul 25 23:39:47 2005 (42E5BE93)
    77690000 776b1000 ntmarta ntmarta.dll Wed Aug 04 02:57:02 2004 (411096CE)
    77710000 77751000 es es.dll Mon Jul 25 23:39:45 2005 (42E5BE91)
    77760000 778d0000 shdocvw shdocvw.dll Mon Sep 04 01:12:56 2006 (44FBC3E8)
    77920000 77a13000 setupapi setupapi.dll Wed Aug 04 02:56:32 2004 (411096B0)
    77a80000 77b14000 crypt32 crypt32.dll Wed Aug 04 02:56:01 2004 (41109691)
    77b20000 77b32000 msasn1 msasn1.dll Wed Aug 04 02:57:23 2004 (411096E3)
    77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 02:56:36 2004 (411096B4)
    77bd0000 77bd7000 midimap midimap.dll Wed Aug 04 02:56:25 2004 (411096A9)
    77be0000 77bf5000 msacm32_77be0000 msacm32.dll Wed Aug 04 02:57:03 2004 (411096CF)
    77c00000 77c08000 version version.dll Wed Aug 04 02:56:39 2004 (411096B7)
    77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 02:59:14 2004 (41109752)
    77c70000 77c93000 msv1_0 msv1_0.dll Wed Aug 04 02:59:11 2004 (4110974F)
    77cc0000 77cf2000 activeds activeds.dll Wed Aug 04 02:56:03 2004 (41109693)
    77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 02:56:23 2004 (411096A7)
    77e70000 77f01000 rpcrt4 rpcrt4.dll Mon Jul 09 08:16:16 2007 (46923520)
    77f10000 77f57000 gdi32 gdi32.dll Tue Jun 19 08:31:19 2007 (4677DAA7)
    77f60000 77fd6000 shlwapi shlwapi.dll Thu Sep 14 03:31:29 2006 (45091361)
    77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 02:56:49 2004 (411096C1)
    78130000 781cb000 msvcr80 msvcr80.dll Tue Oct 23 22:02:06 2007 (471EB5AE)
    79000000 79046000 mscoree mscoree.dll Wed Oct 24 02:35:46 2007 (471EF5D2)
    7c420000 7c4a7000 msvcp80 msvcp80.dll Tue Oct 23 22:04:07 2007 (471EB627)
    7c800000 7c8f5000 kernel32 kernel32.dll Mon Apr 16 10:52:53 2007 (46239BD5)
    7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 02:56:36 2004 (411096B4)
    7c9c0000 7d1d7000 shell32 shell32.dll Thu Oct 25 22:33:59 2007 (47216027)
    7d1e0000 7d49e000 msi msi.dll Wed Apr 18 11:12:21 2007 (46264365)
    7e410000 7e4a0000 user32 user32.dll Thu Mar 08 09:36:28 2007 (45F02D7C)
    Closing open log file c:\debuglog.txt
     
  8. 2008/03/28
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    You posted an application crash (user mode program crash) dump log. We're looking for a BSOD (kernel mode system crash) dump log. :)

    When using the DebugWiz tool to browse to the C:\WINDOWS\Minidump\ folder, look for dump files that are named as follows.
    If you do not find the appropriate minidumps in your C:\WINDOWS\Minidump\ folder, then look for a MEMORY.DMP file (with date/time that matches your system crash) located either in C:\WINDOWS\ or C:\. Otherwise, search your hard drive for MEMORY.DMP and please let us know those locations.
     
    Last edited: 2008/03/28
  9. 2008/03/28
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    Can't find dump

    I guess I am not as good at this as I thought. I have checked everywhere!! I downloaded the debugging tools for windows and debugwiz but I guess I didn't do something right, would you mind helping me out. Thanks
     
  10. 2008/03/28
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Your dump log has a symbol problem - you must be connected to the internet while debugging - as noted in the instructions for our Dump Data Collection Tool :)
     
  11. 2008/03/28
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    I have been connected to the internet all day. I must not be doing something right as I said, I am not good at this at all and I am getting frustrated trying to get you a dump file. I will try to find someone to help me execute this right and get back to you with the correct dump file. Thank you for your help so far.
     
  12. 2008/03/28
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    File too large

    I have found a file in Dr Watson but it is too large to post.
    What do you reccomend?

    Application exception occurred:
    App: C:\Program Files\MSN\MSNCoreFiles\msn.exe (pid=2352)
    When: 3/28/2008 @ 10:18:55.890
    Exception number: c0000005 (access violation)

    *----> System Information <----*
    Computer Name: PETER-3UPB7PZH6
    User Name: Peter
    Terminal Session Id: 0
    Number of Processors: 1
    Processor Type: x86 Family 15 Model 2 Stepping 4
    Windows Version: 5.1
    Current Build: 2600
    Service Pack: 2
    Current Type: Uniprocessor Free
    Registered Organization:
    Registered Owner: Peter
     
  13. 2008/03/28
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    Dr Watson Dump File

    Do you want the dump file in sections? Or is there a way to send you a zip of it?
     
  14. 2008/03/28
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Actually all we want to see is the debug output from running the Dump Data Collection Tool. If this is too large for one post split it over 2.
     
  15. 2008/03/28
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    PeteC, I have also had those "wrong symbols" notices in my dump log when I recently used DebugWiz to analyze a program crash dump (while connected to the Internet) so MrRam may be doing at least that part right. (My DebugWiz-generated BSOD dump logs do not report any troubles with the symbols.)


    MrRam, is your computer configured for Error Reporting and memory dumps according to the following documents?

    Have you ever changed the location of your Pagefile or fiddled with its settings before?


    EDIT: Other resources that might be helpful (though I have not viewed/listened to all the information yet) are the following links.
     
    Last edited: 2008/03/28
  16. 2008/03/28
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    That Dr Watson dump is a user mode program crash dump and is not the same as the 0x0000008E kernel mode STOP error you identified in your first post. We need to focus on creating/locating the C:\WINDOWS\Minidump\Mini03xx08.dmp files or the C:\MEMORY.DMP or C:\WINDOWS\MEMORY.DMP file (the two most likely locations for the MEMORY.DMP file).

    If your computer is not creating the Mini03xx08.dmp or MEMORY.DMP files, then I think we need to focus on configuring your computer properly (as I suggested in my post above) such that your computer does write debugging information for STOP errors (a.k.a. kernel mode errors).

    ===========

    If we cannot get a DebugWiz report for your kernel mode system crash, then let's see what we can find via Event Viewer.

    Instructions About How to Access and Use "Event Viewer ":

    1. Click Start.
    2. Right-click My Computer.
    3. Select "Manage" to open the "Computer Management" window.
      (Event Viewer will be displayed under the "System Tools" directory item.)
    4. Expand "Event Viewer" and then select "System ".
    5. Look for "error" events that occurred around the time your system crashes occurred. These events will be displayed as icons with either a white X on red background or a black exclamation point on yellow background.
    6. Double-click on an individual event to open the "Event Properties" window which shows details about the event.
      • You can use the up/down arrow buttons in the "Event Properties" window to move your focus to other events in the list.
      • Use the button below the up/down arrows to copy the details for an event to your clipboard for pasting elsewhere (such as a follow-up post in this thread :)).
      • Click on the "http://go.microsoft.com/fwlink/events.asp" link in the "Event Properties" window to view more information from Microsoft about the event.

    Alternatively, Event Viewer may be accessed as follows.
    • Click Start > Run...
    • Type [FONT= "Courier New"][SIZE= "3"]eventvwr.msc[/SIZE][/FONT] in the "Open:" field.
    • Click the OK button.
     
    Last edited: 2008/03/28
  17. 2008/03/30
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    Dump follow up

    First, I found that I was not set up to report errors. Second, I do not know where the page file is...so no, I never messed with it. Third, I found that in the Add & Remove in the control panel, I have a long area of Black and white lines separating between G entries and then F entries (not sure what this is). Fourth, in the events window I found the errors but they only pertained to:

    The Windows Media Player Network Sharing Service service depends on the Universal Plug and Play Device Host service which failed to start because of the following error:
    The dependency service or group failed to start.
    and

    The Universal Plug and Play Device Host service depends on the SSDP Discovery Service service which failed to start because of the following error:
    The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    and

    The Universal Plug and Play Device Host service depends on the SSDP Discovery Service service which failed to start because of the following error:
    The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    There was nothing referring to anything else and there were numerous entries of the above three errors 2/20/08.
    I found these also:

    Windows Defender Real-Time Protection agent has detected changes. Microsoft recommends you analyze the software that made these changes for potential risks. You can use information about how these programs operate to choose whether to allow them to run or remove them from your computer. Allow changes only if you trust the program or the software publisher. Windows Defender can't undo changes that you allow.
    For more information please see the following:
    http://go.microsoft.com/fwlink/?linkid=74409
    Scan ID: {78F28C4F-BF5D-45F5-830B-59DBFE762253}
    User: PETER-3UPB7PZH6\Peter
    Name: Unknown
    ID:
    Severity: Not Yet Classified
    Category: Not Yet Classified
    Path Found: regkey:HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce\\RFADelTempStaff;runonce:HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce\\RFADelTempStaff;file:C:\WINDOWS\system32\cleartmp.cmd
    Alert Type: Unclassified software
    Detection Type:

    Windows Defender Real-Time Protection agent has detected changes. Microsoft recommends you analyze the software that made these changes for potential risks. You can use information about how these programs operate to choose whether to allow them to run or remove them from your computer. Allow changes only if you trust the program or the software publisher. Windows Defender can't undo changes that you allow.
    For more information please see the following:
    http://go.microsoft.com/fwlink/?linkid=74409
    Scan ID: {6A80F220-D394-422D-B402-35B427595BFD}
    User: PETER-3UPB7PZH6\Peter
    Name: Unknown
    ID:
    Severity: Not Yet Classified
    Category: Not Yet Classified
    Path Found: file:C:\WINDOWS\system32\drivers\etc\Hosts
    Alert Type: Unclassified software
    Detection Type:
    That's about it, no mini dumps found and I have no idea of this other stuff.
     
  18. 2008/03/30
    cpc2004

    cpc2004 Inactive

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

    The most debug information of your problem is 0xC000001D which means IP misalignment. This is the symptom of hardware problem. 60% of the problem is related to faulty ram. 40% of the problem is related to faulty MB, video card or PSU. Reseating the memory module to another memory slot may fix the problem.

     
  19. 2008/03/31
    MrRam

    MrRam Inactive Thread Starter

    Joined:
    2008/03/28
    Messages:
    8
    Likes Received:
    0
    Error problems

    I have had the added RAM in for over 8 months and did not have any problems until recently. The main error that keeps coming up is 0X000001D and the third sequence changes from 0XB71A5C68 to 0XADBF8C68 or 0XB530AC68. This all seemed to start after I did the Microsoft automatic updates. I just ran a defrag, and the "Low Performing System Files" notice has increased from my first message to alot more!!! Call me nuts, but if this keeps increasing each day there must be something else I can do, or do I have to do the "Reload" everything clean from scratch.... if no other choice. I originally upgraded from 98SE with an upgrade CD to XP Pro. Could this have been the problem since it is an upgrade and not a "New Complete" install?
     

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.