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.

Windows restarts without authorization [Dump Data]

Discussion in 'Windows XP' started by alexs2074, 2008/01/20.

  1. 2008/01/20
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    Lately, for no reason, my XP has been rebooting itself. The event viewer suggests that the problem has to do with the NDISUIO driver not being installed properly, causing the wireless zero configuration to not work properly. My wireless networking and all other aspects of my computer work great, but my computer reboots anyway, and it is totally random. Sometimes every couple of minutes, sometimes not for hours. The CPU temp is 39C. I have disabled the NOD32 and all other programs and drivers I have installed lately, but to no effect. I have restored the computer to a date in which it didnt do this, but even after the restore, it still does it. Anybody have any ideas? It may be a RAM issue, but I can also have many apps going at once with no problems, then when I have no apps it decides to reboot. 1.4GHz AMD Athlon, 512MB RAM, offboard video, sound, netgear.
     
  2. 2008/01/20
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    alexs2074 - Welcome to the Board :)

    First go to Control Panel > System > Advanced tab > Startup and Recovery > Settings - under System Failure uncheck 'Automatically restart'. From the dropdown box under 'Write debugging information' select 'Kernel memory dump' and uncheck 'Overwrite any existing file'.

    If it a system failure which is causing the computer to reboot these settings will stop the computer at the Blue Screen of Death (BSOD) on which will be given the Stop Error and often the file which caused it. A memory dump will be produced which may be debugged using our Wizard and the dump data posted here.

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

    ndisuio.sys is a process belonging to the NDIS User Mode I/O (NDISUIO) NDIS protocol driver which offers support for wireless devices such as Bluetooth and the like. Dump data should indicate if that is the cause of the problem.

    As a rider I should add ....
     

  3. to hide this advert.

  4. 2008/01/21
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    Where are these memory dumps located?
     
  5. 2008/01/21
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    From the URL I posted ....
     
  6. 2008/01/21
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Location might be C:\WINDOWS\MEMORY.DMP as I had a crash last night that produced a MEMORY.DMP in the Windows folder.

    I suppose I may have somehow changed the default location sometime in the past for a MEMORY.DMP but, in case I didn't, there you go. :)
     
  7. 2008/01/27
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    The debug wizard does not work. I downloaded the MS debug software but the wizard does not locate it and does not offer me the chance to tell it where to find it, the browse button is not functional. my computer crashes every few minutes, so I cant write too much here.
     
  8. 2008/01/27
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    When I click on 'download debug tools', the program stops responding and I have to kill the process. when I attempt to generate a log of the dump file, it says that it will be generated after the dos prompt closes. There never is any dos prompt.
     
  9. 2008/01/27
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I can but suggest that your download/install of the Wizard is corrupted or other malfunctions within the computer are causing it problems. There have been no reported problems with the Wizard over the few years it has been available.

    Did you set up the computer as suggested so that it does not restart on System Failure? If you did make a note of the Stop messages and if a file is referenced note that also and post here.

    You may like to check out the RAM - 512 Mb - is that 1 stick or 2? Try swapping it around the memory slots. If you are running 2 sticks run with one at a time - the computer will be painfully slow, but swapping sticks around and using single sticks helps to pinpoint a bad one. In this context ....
     
  10. 2008/01/29
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    It would appear that my computer is stable when I alter the BIOS configuration to run the CPU at a slower speed. I run it at 1050MHz instead of 1400MHz and it has not crashed yet, whereas at 1400MHz it was restarting every few minutes. Is this a clue?

    Is there another way to generate a core dump log that can be analyzed. For some reason the debugwiz.exe program does not work on my computer.
     
  11. 2008/01/29
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    I figured out how to generate a debug file using debugwiz. The instructions on the BBS site fail to mention to use the advance radio and browse to the MS tools executable. Anyway, here it is;

    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:\WINDOWS\MEMORY4.DMP]
    Kernel Summary Dump File: Only kernel address space is 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
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Sun Jan 27 02:20:42.119 2008 (GMT-8)
    System Uptime: 0 days 0:05:26.694
    Loading Kernel Symbols
    ............................................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 8E, {c0000005, 805677b1, f8675918, 0}


    PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details

    PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
    Probably caused by : hardware ( nt!CmpParseKey+9 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    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: 805677b1, The address that the exception occurred at
    Arg3: f8675918, Trap Frame
    Arg4: 00000000

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


    PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details

    PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details

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

    FAULTING_IP:
    nt!CmpParseKey+9
    805677b1 0000 add byte ptr [eax],al

    TRAP_FRAME: f8675918 -- (.trap 0xfffffffff8675918)
    .trap 0xfffffffff8675918
    ErrCode = 00000002
    eax=000001ff ebx=f8675b80 ecx=0000004c edx=0000006d esi=e3206ab8 edi=e3206ab8
    eip=805677b1 esp=f867598c ebp=f86759bc iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    nt!CmpParseKey+0x9:
    805677b1 0000 add byte ptr [eax],al ds:0023:000001ff=??
    .trap
    Resetting default scope

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: explorer.exe

    MISALIGNED_IP:
    nt!CmpParseKey+9
    805677b1 0000 add byte ptr [eax],al

    LAST_CONTROL_TRANSFER: from 8051d6ef to 8053354e

    STACK_TEXT:
    f86754e0 8051d6ef 0000008e c0000005 805677b1 nt!KeBugCheckEx+0x1b
    f86758a8 804df235 f86758c4 00000000 f8675918 nt!KiDispatchException+0x3b1
    f8675910 804df1e6 f86759bc 805677b1 badb0d00 nt!CommonDispatchException+0x4d
    f8675930 80565099 e324a008 f8675901 00000000 nt!KiExceptionExit+0x18a
    f86759bc 80567882 f86759ec 00000004 f8675b6c nt!ObCheckObjectAccess+0xd3
    f8675ba0 8056336c 00000020 823c3980 819ead60 nt!CmpParseKey+0x10d
    f8675c28 8056749a 00000000 f8675c68 00000040 nt!ObpLookupObjectName+0x56a
    f8675c7c 80567dfd 00000000 823c3980 00000001 nt!ObOpenObjectByName+0xeb
    f8675d50 804de7ec 00fafa10 02000000 00faf754 nt!NtOpenKey+0x1af
    f8675d50 7c90eb94 00fafa10 02000000 00faf754 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00faf77c 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!CmpParseKey+9
    805677b1 0000 add byte ptr [eax],al

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!CmpParseKey+9

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

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

    eax=ffdff13c ebx=805677b1 ecx=00000000 edx=804db4ae esi=f86758c4 edi=00000000
    eip=8053354e esp=f86754c8 ebp=f86754e0 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
    nt!KeBugCheckEx+0x1b:
    8053354e 5d pop ebp
    ChildEBP RetAddr Args to Child
    f86754e0 8051d6ef 0000008e c0000005 805677b1 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
    f86758a8 804df235 f86758c4 00000000 f8675918 nt!KiDispatchException+0x3b1 (FPO: [Non-Fpo])
    f8675910 804df1e6 f86759bc 805677b1 badb0d00 nt!CommonDispatchException+0x4d (FPO: [0,20,0])
    f8675930 80565099 e324a008 f8675901 00000000 nt!KiExceptionExit+0x18a
    f86759bc 80567882 f86759ec 00000004 f8675b6c nt!ObCheckObjectAccess+0xd3 (FPO: [Non-Fpo])
    f8675ba0 8056336c 00000020 823c3980 819ead60 nt!CmpParseKey+0x10d (FPO: [Non-Fpo])
    f8675c28 8056749a 00000000 f8675c68 00000040 nt!ObpLookupObjectName+0x56a (FPO: [Non-Fpo])
    f8675c7c 80567dfd 00000000 823c3980 00000001 nt!ObOpenObjectByName+0xeb (FPO: [Non-Fpo])
    f8675d50 804de7ec 00fafa10 02000000 00faf754 nt!NtOpenKey+0x1af (FPO: [Non-Fpo])
    f8675d50 7c90eb94 00fafa10 02000000 00faf754 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f8675d64)
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00faf77c 00000000 00000000 00000000 00000000 0x7c90eb94
    start end module name
    804d7000 806eb500 nt ntoskrnl.exe Wed Feb 28 01:10:41 2007 (45E54711)
    806ec000 806ffd80 hal halacpi.dll Tue Aug 03 22:59:04 2004 (41107B28)
    b9122000 b9162280 HTTP HTTP.sys Thu Mar 16 17:33:09 2006 (441A03C5)
    b94a7000 b94a9b20 ScFBPNT2 ScFBPNT2.SYS Thu Feb 18 16:19:51 1999 (36CCAE27)
    b94ab000 b94fc480 srv srv.sys Mon Aug 14 03:34:39 2006 (44E051BF)
    b96b5000 b972f8c0 amon amon.sys Thu May 10 23:22:58 2007 (46440BC2)
    b9758000 b9784400 mrxdav mrxdav.sys Tue Aug 03 23:00:49 2004 (41107B91)
    b99e3000 b99f2900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
    b9a53000 b9a67400 wdmaud wdmaud.sys Wed Jun 14 02:00:44 2006 (448FD03C)
    b9af8000 b9b06d80 sysaudio sysaudio.sys Tue Aug 03 23:15:54 2004 (41107F1A)
    bf000000 bf011580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
    bf012000 bf463580 nv4_disp nv4_disp.dll Sun Oct 22 14:02:50 2006 (453BDC7A)
    bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 05:47:34 2007 (45F013F6)
    bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 00:56:56 2004 (411096C8)
    f6874000 f688b480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
    f688c000 f68af000 Fastfat Fastfat.SYS Tue Aug 03 23:14:15 2004 (41107EB7)
    f6977000 f6997f00 ipnat ipnat.sys Wed Sep 29 15:28:36 2004 (415B3714)
    f6998000 f6a06a00 mrxsmb mrxsmb.sys Fri May 05 02:41:42 2006 (445B1DD6)
    f6a07000 f6a31a00 rdbss rdbss.sys Fri May 05 02:47:55 2006 (445B1F4B)
    f6a32000 f6a53d00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
    f6a54000 f6a7bc00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
    f6a7c000 f6ad3d80 tcpip tcpip.sys Thu Apr 20 04:51:47 2006 (444775D3)
    f6ad4000 f6ae6400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
    f6ae7000 f6b00200 InCDFs InCDFs.sys Fri Nov 10 07:15:43 2006 (4554979F)
    f7c41000 f7c43900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
    f7c69000 f7c9c200 update update.sys Tue Aug 03 22:58:32 2004 (41107B08)
    f7c9d000 f7ccd100 rdpdr rdpdr.sys Tue Aug 03 23:01:10 2004 (41107BA6)
    f7cf6000 f7d06e00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
    f7da7000 f7dbd680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
    f7dbe000 f7e1c680 netwg311 netwg311.sys Thu Jun 17 13:41:13 2004 (40D201E9)
    f7e1d000 f7e5fd00 3c1807 3c1807.sys Fri Nov 18 10:00:09 2005 (437E16A9)
    f7e60000 f7eb0560 3c1807pd 3c1807pd.sys Fri Nov 18 10:02:04 2005 (437E171C)
    f7eb1000 f7ed3e80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
    f7ed4000 f7ef6680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
    f7ef7000 f7f1a980 portcls portcls.sys Tue Aug 03 23:15:47 2004 (41107F13)
    f7f1b000 f7f2e900 parport parport.sys Tue Aug 03 22:59:04 2004 (41107B28)
    f7f2f000 f7f42780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
    f7f43000 f8312400 nv4_mini nv4_mini.sys Sun Oct 22 14:08:02 2006 (453BDDB2)
    f835b000 f8375580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
    f8376000 f83a2a80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
    f83a3000 f842f400 Ntfs Ntfs.sys Fri Feb 09 03:10:31 2007 (45CC56A7)
    f8430000 f8446780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
    f8447000 f8458f00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
    f8459000 f8478780 fltMgr fltMgr.sys Mon Aug 21 02:14:57 2006 (44E97991)
    f8479000 f8490480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
    f8491000 f84b6700 dmio dmio.sys Tue Aug 03 23:07:13 2004 (41107D11)
    f84b7000 f84d5880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
    f84d6000 f84e6a80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
    f84e7000 f8514d80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
    f8536000 f853ec00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
    f8546000 f8550500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
    f8556000 f8562c80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
    f8566000 f856ee00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
    f8576000 f8582200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
    f8586000 f858eb80 PxHelp20 PxHelp20.sys Fri Feb 02 13:23:57 2007 (45C3ABED)
    f8596000 f85a0080 sisagp sisagp.sys Tue Aug 03 23:07:42 2004 (41107D2E)
    f85c6000 f85d0380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
    f85d6000 f85e2180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
    f85e6000 f85f4080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
    f85f6000 f85fe400 InCDRm InCDRm.sys Fri Nov 10 07:17:49 2006 (4554981D)
    f8606000 f860ff00 es1371mp es1371mp.sys Thu Jul 19 15:28:37 2001 (3B575F15)
    f8616000 f8622880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
    f8626000 f8630200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
    f8636000 f8641d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
    f8646000 f864e900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
    f86a6000 f86b4a20 odysseyIM3 odysseyIM3.sys Tue Jan 06 16:42:40 2004 (3FFB5600)
    f86b6000 f86bff00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
    f86c6000 f86cf480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
    f86f6000 f8704100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
    f8716000 f871e700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
    f8726000 f872e880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
    f8736000 f873e700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
    f8776000 f877ea00 processr processr.sys Tue Aug 03 22:59:14 2004 (41107B32)
    f8786000 f8792e00 i8042prt i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
    f8796000 f87a5d80 serial serial.sys Tue Aug 03 23:15:51 2004 (41107F17)
    f87a6000 f87b4b80 drmk drmk.sys Tue Aug 03 23:07:54 2004 (41107D3A)
    f87b6000 f87bc200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
    f87be000 f87c2900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
    f882e000 f8833a00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
    f8836000 f883c000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
    f883e000 f8844b00 fdc fdc.sys Tue Aug 03 22:59:25 2004 (41107B3D)
    f8846000 f884a280 usbohci usbohci.sys Tue Aug 03 23:08:34 2004 (41107D62)
    f884e000 f8855a80 InCDPass InCDPass.sys Fri Nov 10 07:16:33 2006 (455497D1)
    f8856000 f885e000 sisnic sisnic.sys Wed Oct 29 00:55:09 2003 (3F9F725D)
    f885e000 f8865580 Modem Modem.SYS Tue Aug 03 23:08:04 2004 (41107D44)
    f8866000 f886a880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
    f887e000 f8882580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
    f8886000 f888a080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
    f88ae000 f88b3000 flpydisk flpydisk.sys Tue Aug 03 22:59:24 2004 (41107B3C)
    f88d6000 f88dc180 HIDPARSE HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
    f88de000 f88e3200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
    f88e6000 f88eaa80 Msfs Msfs.SYS Tue Aug 03 23:00:37 2004 (41107B85)
    f88ee000 f88f5880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
    f8906000 f890a500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
    f8946000 f8949000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
    f89de000 f89e0980 InCDrec InCDrec.SYS Fri Nov 10 07:15:55 2006 (455497AB)
    f89e2000 f89e4280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
    f89ea000 f89ecf00 ws2ifsl ws2ifsl.sys Fri Aug 17 13:55:58 2001 (3B7D84DE)
    f89f6000 f89f9c80 serenum serenum.sys Tue Aug 03 22:59:06 2004 (41107B2A)
    f89fa000 f89fc980 gameenum gameenum.sys Tue Aug 03 23:08:20 2004 (41107D54)
    f8a06000 f8a08580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
    f8a2e000 f8a31c80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
    f8a36000 f8a37b80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
    f8a38000 f8a39100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
    f8a3a000 f8a3b700 dmload dmload.sys Fri Aug 17 13:58:15 2001 (3B7D8567)
    f8a5a000 f8a5be00 oslib oslib.sys Fri Nov 18 09:59:43 2005 (437E168F)
    f8a60000 f8a61100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
    f8a72000 f8a73100 PfModNT PfModNT.sys Wed Dec 15 20:14:08 1999 (38586710)
    f8a74000 f8a75280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
    f8a82000 f8a83f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
    f8a84000 f8a85080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
    f8a86000 f8a87080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
    f8a88000 f8a89080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
    f8a8a000 f8a8bde0 nod32drv nod32drv.sys Thu May 10 23:23:05 2007 (46440BC9)
    f8a96000 f8a97100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
    f8ae2000 f8ae3a80 ParVdm ParVdm.SYS Fri Aug 17 13:49:49 2001 (3B7D836D)
    f8afe000 f8afed00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
    f8b19000 f8b19d00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)
    f8c11000 f8c11d00 GenPort2 GenPort2.SYS Wed Dec 23 04:23:33 1998 (3680E0C5)
    f8c16000 f8c16d00 GenPort GenPort.SYS Wed Dec 23 03:20:33 1998 (3680D201)
    f8c20000 f8c20b80 msmpu401 msmpu401.sys Fri Aug 17 13:59:59 2001 (3B7D85CF)
    f8c22000 f8c22c00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)
    f8c33000 f8c33b80 Null Null.SYS Fri Aug 17 13:47:39 2001 (3B7D82EB)
    f8c34000 f8c34f80 AvgAsCln AvgAsCln.sys Tue Sep 05 09:03:16 2006 (44FD9FC4)
    f8c46000 f8c47000 guard guard.sys Wed May 30 04:55:24 2007 (465D662C)

    Unloaded modules:
    f8c48000 f8c49000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b9965000 b9990000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b9990000 b99b3000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba598000 ba5a5000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b9ab8000 b9ac6000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f8a68000 f8a6a000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f89da000 f89de000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f88ce000 f88d3000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f89d6000 f89d9000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
  12. 2008/01/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    As I noted before ....
    However it does appear to reference hardware and I would suggest that you check out the memory as I indicated in an earlier post.
    It probably is - I take it that you were not overclocking? Doesn't seem like it.

    I'll ask one of the Team Members to comment if he will.
     
  13. 2008/01/29
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    alexs2074,

    Welcome to the board. Pete bumped me a quick note and I just reviewed your thread. At first blush, it appears that by changing your bus speed from 133Mhz to 100Mhz (my assumption) you have been able to achieve more stability and avoid the random restarts. As to what I would term a rather astute observation and your question, "Is this a clue? ", my answer would be an unequivocal yes.

    Now for the hard part - isolating the problem and identifying a solution. In my book, Pete has given you some very good guidance in suggesting that you check out your memory. Thats not to say that your memory is no good but it suggests that something is causing a potential memory related problem. This can lead one in a few different directions, but it would be helpful if you could identify your motherboard, your memory, your power supply and give us a little more information on your processor. To my knowledge, AMD manufactured at least three different 1400MHz processors and I might be able to provide some suggestions if I know a little more about your system.

    Unfortunately, I don't read memory dumps so I can provide little or no direct assistance in that regard, however, your changing the bus speed (again, my assumption) does give us a very good clue.

    ;)
     
  14. 2008/01/30
    alexs2074

    alexs2074 Inactive Thread Starter

    Joined:
    2008/01/20
    Messages:
    13
    Likes Received:
    0
    CPU-AMD Athlon 1.4MHz
    Motherboard-Mainboard's K7S5A (socket-A for AMD k7 CPUs)
    SiS 735 chipset
    512MB DIMM DDR
    OS XP SP2, fully updated
    Off board sound, video, wi-fi, and modem.
    have no idea about the power supply.

    Can anyone recommend a free memory test, that doesnt require expertise and hours of trying to figure out instructions that probably are not correct.
     
  15. 2008/01/30
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    I would like you to download and install Everest 2.20 which is available here. This will give us a better look at the specific information I requested.

    Please understand, I'm not trying to make this difficult but there were three different versions of the K7S5a (1.1, 3.1 and 3.1b) and there was a K7S5a Pro. I also want to know if you are using a Thunderbird 200Mhz CPU, A Thunderbird 266MHz CPU or a Palomino or a Thoroughbred. And, since my suspicion is that you have a memory related problem, it is important to identify what kind of 168 Pin DDR memory you are using and what its rated speed is (ie: PC2100 or PC2700 and mfg as a minimum). Lastly, since the PSU and its condition can have a major impact on both core voltage and DIMM voltage, you may need to pull the cover off the case to help identify your PSU if Everest doesn't give us the information we need.

    alexs2074, I don't read dump files but I've got a fair understanding of socket 462 Athlons and may be able to provide some assistance once I've got a better handle on your components. I did spend a little time reading some technical information about your ECS board but I don't yet know enough about your specific hardware to start making any recommendations. In the meantime, you can start here relative to a memory test.

    ;)
     
    Last edited: 2008/01/30
  16. 2008/01/30
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I would certainly not discourage you from running MS Memory Diagnostic tool as linked to by Rockster, but please bear in mind the caveat I posted earlier ....
    If no problems are revealed by WMD this does not mean that there are no memory problems :)

    Hence my suggestion to swap the RAM modules around. If you have a single 512 Mb stick switch it between slots on the mobo. If you have 2x 256 Mb sticks, run with one, switch it around the slots, repeat for the other and then run both in combination using spare slots if available.

    If you have further memory dumps let's see a couple more sets of dump data - we may see something.
     
  17. 2008/01/30
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    I'm in 100% agreement with Pete re: the lack of validity of most memory tests and would encourage you to follow Pete's suggestions. His approach is going to tell us more than most memory tests will.

    ;)
     

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.