i neeed help
-
Re: i neeed help
In Folder Options you might need to have Hidden Files and Folder showing plus System Files.
You can see if C:\WINDOWS\Minidump has the same date as the above: 02 06 08
If so it is probably the same file.
-
i manage to locate the Mini020608-01.dmp under the C:\WINDOWS\Minidump. So whats next??
-
1) Download and install the
Debugging Tools from Microsoft
All you need do is download and install this. Make no attempt to start or run it.
2) Download and install this
debugwiz
This is a DOS based batch file that will command the above Microsoft Tools.
3) Open the Wiz & Browse to, or paste in the path to, your .dmp file.
4) After the Wiz creates a Text document post it back to your thread.
-
i have installed the microsoft debugging tool.
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\Minidump\Mini020608-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 ntkrnlmp.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.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Feb 6 20:12:25.484 2008 (GMT+8)
System Uptime: 0 days 0:07:16.036
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
.................................................. .................................................. .............................
Loading User Symbols
Loading unloaded module list
...........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {e18ba000, 0, ff96c782, 1}
***** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 : ntkrnlmp.exe ( nt!PsRemoveLoadImageNotifyRoutine+b9 )
Followup: MachineOwner
---------
kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e18ba000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: ff96c782, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45e54690
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e18ba000
FAULTING_IP:
+ffffffffff96c782
ff96c782 668b30 mov si,word ptr [eax]
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 80633890 to ff96c782
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
effacbe4 80633890 81df77d8 00000468 effacc24 0xff96c782
effacc04 805fbca4 81df77d8 00000468 effacc24 nt!PsRemoveLoadImageNotifyRoutine+0xb9
effacc48 80586334 ff6a4008 7afd0000 effacd18 nt!LsaFreeReturnBuffer+0x118a1
effacca4 8057e94a 00000004 ff679cd0 effacd18 nt!NtQuerySystemInformation+0x1015
effacd34 804dd99f 0000023c ffffffff 0012c7c0 nt!NtMapViewOfSection+0x22f
effacd64 7c90eb94 badb0d00 0012c6f0 00000000 nt!KiDeliverApc+0xb9e
effacd68 badb0d00 0012c6f0 00000000 00000000 0x7c90eb94
effacd6c 0012c6f0 00000000 00000000 00000000 0xbadb0d00
effacd70 00000000 00000000 00000000 00000000 0x12c6f0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PsRemoveLoadImageNotifyRoutine+b9
80633890 56 push esi
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PsRemoveLoadImageNotifyRoutine+b9
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
eax=e18ba000 ebx=ff9740b8 ecx=00000002 edx=e18b9f00 esi=00004200 edi=80568680
eip=ff96c782 esp=effac84c ebp=effacbe4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
ff96c782 668b30 mov si,word ptr [eax] ds:0023:e18ba000=????
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
effacbe4 80633890 81df77d8 00000468 effacc24 0xff96c782
effacc04 805fbca4 81df77d8 00000468 effacc24 nt!PsRemoveLoadImageNotifyRoutine+0xb9
effacc48 80586334 ff6a4008 7afd0000 effacd18 nt!LsaFreeReturnBuffer+0x118a1
effacca4 8057e94a 00000004 ff679cd0 effacd18 nt!NtQuerySystemInformation+0x1015
effacd34 804dd99f 0000023c ffffffff 0012c7c0 nt!NtMapViewOfSection+0x22f
effacd64 7c90eb94 badb0d00 0012c6f0 00000000 nt!KiDeliverApc+0xb9e
effacd68 badb0d00 0012c6f0 00000000 00000000 0x7c90eb94
effacd6c 0012c6f0 00000000 00000000 00000000 0xbadb0d00
effacd70 00000000 00000000 00000000 00000000 0x12c6f0
start end module name
804d7000 806fd000 nt ntkrnlmp.exe Wed Feb 28 17:08:32 2007 (45E54690)
806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 13:59:09 2004 (41107B2D)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 21:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 14:00:51 2004 (41107B93)
bf9d5000 bf9e3000 ialmrnt5 ialmrnt5.dll Mon Jan 24 02:55:58 2005 (41F3F33E)
bf9e3000 bfa02000 ialmdnt5 ialmdnt5.dll Mon Jan 24 02:55:52 2005 (41F3F338)
bfa02000 bfa2da20 ialmdev5 ialmdev5.DLL Mon Jan 24 02:55:40 2005 (41F3F32C)
bfa2e000 bfb0b000 ialmdd5 ialmdd5.DLL Mon Jan 24 03:04:19 2005 (41F3F533)
ef7d8000 ef818280 HTTP HTTP.sys Fri Mar 17 08:33:09 2006 (441A03C5)
ef899000 ef8a8900 Cdfs Cdfs.SYS Wed Aug 04 14:14:09 2004 (41107EB1)
efa97000 efaab400 wdmaud wdmaud.sys Wed Jun 14 17:00:44 2006 (448FD03C)
efc54000 efc62d80 sysaudio sysaudio.sys Wed Aug 04 14:15:54 2004 (41107F1A)
efcdc000 efd2d480 srv srv.sys Mon Aug 14 18:34:39 2006 (44E051BF)
efd56000 efd67500 tmcomm tmcomm.sys Mon Jul 31 14:41:15 2006 (44CDA60B)
eff20000 eff4c400 mrxdav mrxdav.sys Wed Aug 04 14:00:49 2004 (41107B91)
eff65000 eff676c0 mdmxsdk mdmxsdk.sys Thu Apr 10 04:48:53 2003 (3E948735)
f00f1000 f00f4280 ndisuio ndisuio.sys Wed Aug 04 14:03:10 2004 (41107C1E)
f015d000 f0167000 secdrv secdrv.sys Wed Sep 13 21:18:32 2006 (45080528)
f01f5000 f020c480 dump_atapi dump_atapi.sys Wed Aug 04 13:59:41 2004 (41107B4D)
f0235000 f0258000 Fastfat Fastfat.SYS Wed Aug 04 14:14:15 2004 (41107EB7)
f0258000 f0320a60 avg7core avg7core.sys Thu Oct 11 00:23:39 2007 (470CFC8B)
f0321000 f038fa00 mrxsmb mrxsmb.sys Fri May 05 17:41:42 2006 (445B1DD6)
f0390000 f03baa00 rdbss rdbss.sys Fri May 05 17:47:55 2006 (445B1F4B)
f045b000 f047bf00 ipnat ipnat.sys Thu Sep 30 06:28:36 2004 (415B3714)
f0498000 f049a900 Dxapi Dxapi.sys Sat Aug 18 04:53:19 2001 (3B7D843F)
f04a4000 f04c5d00 afd afd.sys Wed Aug 04 14:14:13 2004 (41107EB5)
f04c6000 f04edc00 netbt netbt.sys Wed Aug 04 14:14:36 2004 (41107ECC)
f04ee000 f0545e80 tcpip tcpip.sys Wed Oct 31 01:20:52 2007 (472767F4)
f0546000 f0558400 ipsec ipsec.sys Wed Aug 04 14:14:27 2004 (41107EC3)
f869f000 f86a1280 rasacd rasacd.sys Sat Aug 18 04:55:39 2001 (3B7D84CB)
f86b7000 f870fe80 update update.sys Mon Apr 23 18:32:54 2007 (462C8B56)
f8710000 f8720e00 psched psched.sys Wed Aug 04 14:04:16 2004 (41107C60)
f8721000 f8737680 ndiswan ndiswan.sys Wed Aug 04 14:14:30 2004 (41107EC6)
f8738000 f87b5d80 SndTDriverV32 SndTDriverV32.sys Fri Aug 11 21:52:15 2006 (44DC8B8F)
f87b6000 f87c9900 parport parport.sys Wed Aug 04 13:59:04 2004 (41107B28)
f8815000 f8838980 portcls portcls.sys Wed Aug 04 14:15:47 2004 (41107F13)
f8839000 f8a65800 ALCXWDM ALCXWDM.SYS Fri Oct 01 10:23:58 2004 (415CBFBE)
f8a66000 f8b0bf80 HSF_CNXT HSF_CNXT.sys Fri Nov 14 00:18:33 2003 (3FB3AED9)
f8b0c000 f8c0a980 HSF_DP HSF_DP.sys Fri Nov 14 00:16:48 2003 (3FB3AE70)
f8c0b000 f8c2d680 ks ks.sys Wed Aug 04 14:15:20 2004 (41107EF8)
f8c2e000 f8c61580 HSFHWBS2 HSFHWBS2.sys Fri Nov 14 00:19:45 2003 (3FB3AF21)
f8c62000 f8c84e80 USBPORT USBPORT.SYS Wed Aug 04 14:08:34 2004 (41107D62)
f8c85000 f8c98780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 14:07:04 2004 (41107D08)
f8c99000 f8d5d5a0 ialmnt5 ialmnt5.sys Mon Jan 24 03:05:05 2005 (41F3F561)
f8d6e000 f8d76700 netbios netbios.sys Wed Aug 04 14:03:19 2004 (41107C27)
f8d7e000 f8d86c00 AFS2K AFS2K.SYS Fri Oct 08 09:16:03 2004 (4165EA53)
f8dbe000 f8dcc100 usbhub usbhub.sys Wed Aug 04 14:08:40 2004 (41107D68)
f8dde000 f8de7480 NDProxy NDProxy.SYS Sat Aug 18 04:55:30 2001 (3B7D84C2)
f8dee000 f8df7f00 termdd termdd.sys Wed Aug 04 13:58:52 2004 (41107B1C)
f935f000 f9379580 Mup Mup.sys Wed Aug 04 14:15:20 2004 (41107EF8)
f937a000 f93a6a80 NDIS NDIS.sys Wed Aug 04 14:14:27 2004 (41107EC3)
f93a7000 f9433400 Ntfs Ntfs.sys Fri Feb 09 19:10:31 2007 (45CC56A7)
f9434000 f944a780 KSecDD KSecDD.sys Wed Aug 04 13:59:45 2004 (41107B51)
f944b000 f945eb40 drvmcdb drvmcdb.sys Tue Oct 22 05:53:22 2002 (3DB47752)
f945f000 f9470f00 sr sr.sys Wed Aug 04 14:06:22 2004 (41107CDE)
f9471000 f9472000 fltmgr fltmgr.sys unavailable (00000000)
f9491000 f94a8480 atapi atapi.sys Wed Aug 04 13:59:41 2004 (41107B4D)
f94a9000 f94c7880 ftdisk ftdisk.sys Sat Aug 18 04:52:41 2001 (3B7D8419)
f94c8000 f94d8a80 pci pci.sys Wed Aug 04 14:07:45 2004 (41107D31)
f94d9000 f9506d80 ACPI ACPI.sys Wed Aug 04 14:07:35 2004 (41107D27)
f9528000 f9530c00 isapnp isapnp.sys Sat Aug 18 04:58:01 2001 (3B7D8559)
f9538000 f9542500 MountMgr MountMgr.sys Wed Aug 04 13:58:29 2004 (41107B05)
f9548000 f9554c80 VolSnap VolSnap.sys Wed Aug 04 14:00:14 2004 (41107B6E)
f9558000 f9560e00 disk disk.sys Wed Aug 04 13:59:53 2004 (41107B59)
f9568000 f9574200 CLASSPNP CLASSPNP.SYS Wed Aug 04 14:14:26 2004 (41107EC2)
f9578000 f9586e80 ohci1394 ohci1394.sys Wed Aug 04 14:10:05 2004 (41107DBD)
f9588000 f9595000 1394BUS 1394BUS.SYS Wed Aug 04 14:10:03 2004 (41107DBB)
f95b8000 f95c7180 nic1394 nic1394.sys Wed Aug 04 13:58:28 2004 (41107B04)
f95c8000 f95d0900 msgpc msgpc.sys Wed Aug 04 14:04:11 2004 (41107C5B)
f95e8000 f95f4000 SASKUTIL SASKUTIL.sys Tue Feb 06 01:49:28 2007 (45C76E28)
f95f8000 f9600700 wanarp wanarp.sys Wed Aug 04 14:04:57 2004 (41107C89)
f9608000 f9610880 Fips Fips.SYS Sat Aug 18 09:31:49 2001 (3B7DC585)
f9618000 f9626d80 arp1394 arp1394.sys Wed Aug 04 13:58:28 2004 (41107B04)
f96f8000 f9700d00 intelppm intelppm.sys Wed Aug 04 13:59:19 2004 (41107B37)
f9718000 f9722380 imapi imapi.sys Wed Aug 04 14:00:12 2004 (41107B6C)
f9728000 f9734180 cdrom cdrom.sys Wed Aug 04 13:59:52 2004 (41107B58)
f9738000 f9746080 redbook redbook.sys Wed Aug 04 13:59:34 2004 (41107B46)
f9748000 f9756b80 drmk drmk.sys Wed Aug 04 14:07:54 2004 (41107D3A)
f9758000 f9767d80 serial serial.sys Wed Aug 04 14:15:51 2004 (41107F17)
f9768000 f9774e00 i8042prt i8042prt.sys Wed Aug 04 14:14:36 2004 (41107ECC)
f9778000 f9784880 rasl2tp rasl2tp.sys Wed Aug 04 14:14:21 2004 (41107EBD)
f9788000 f9792200 raspppoe raspppoe.sys Wed Aug 04 14:05:06 2004 (41107C92)
f9798000 f97a3d00 raspptp raspptp.sys Wed Aug 04 14:14:26 2004 (41107EC2)
f97a8000 f97ae200 PCIIDEX PCIIDEX.SYS Wed Aug 04 13:59:40 2004 (41107B4C)
f97b0000 f97b4900 PartMgr PartMgr.sys Sat Aug 18 09:32:23 2001 (3B7DC5A7)
f97b8000 f97bcde0 PxHelp20 PxHelp20.sys Fri Sep 24 08:24:24 2004 (41536938)
f97c0000 f97c7d80 viaagp1 viaagp1.sys Wed Jul 24 17:44:31 2002 (3D3E76FF)
f9800000 f9806000 symlcbrd symlcbrd.sys Sun Aug 15 20:36:33 2004 (411F58D1)
f9868000 f986d000 usbuhci usbuhci.sys Wed Aug 04 14:08:34 2004 (41107D62)
f9870000 f9876800 usbehci usbehci.sys Wed Aug 04 14:08:34 2004 (41107D62)
f9878000 f987f580 Modem Modem.SYS Wed Aug 04 14:08:04 2004 (41107D44)
f9880000 f9885200 RTL8139 RTL8139.SYS Fri Jun 13 13:29:46 2003 (3EE9614A)
f9888000 f9889000 fdc fdc.sys unavailable (00000000)
f9890000 f9895a00 mouclass mouclass.sys Wed Aug 04 13:58:32 2004 (41107B08)
f9898000 f989dd00 PS2 PS2.sys Tue Jul 30 06:43:48 2002 (3D45C524)
f98a0000 f98a6000 kbdclass kbdclass.sys Wed Aug 04 13:58:32 2004 (41107B08)
f98a8000 f98ac880 TDI TDI.SYS Wed Aug 04 14:07:47 2004 (41107D33)
f98b8000 f98bc580 ptilink ptilink.sys Sat Aug 18 04:49:53 2001 (3B7D8371)
f98c0000 f98c4080 raspti raspti.sys Sat Aug 18 04:55:32 2001 (3B7D84C4)
f98d0000 f98d5000 flpydisk flpydisk.sys Wed Aug 04 13:59:24 2004 (41107B3C)
f98e8000 f98ee180 HIDPARSE HIDPARSE.SYS Wed Aug 04 14:08:15 2004 (41107D4F)
f98f0000 f98f5200 vga vga.sys Wed Aug 04 14:07:06 2004 (41107D0A)
f98f8000 f98f9000 Msfs Msfs.SYS unavailable (00000000)
f9900000 f9907880 Npfs Npfs.SYS Wed Aug 04 14:00:38 2004 (41107B86)
f9908000 f990f000 SASDIFSV SASDIFSV.SYS Wed Oct 04 07:02:46 2006 (4522EC16)
f9918000 f991ec80 avg7rsxp avg7rsxp.sys Tue Jan 30 23:08:42 2007 (45BF5F7A)
f9930000 f9934500 watchdog watchdog.sys Wed Aug 04 14:07:32 2004 (41107D24)
f9938000 f993b000 BOOTVID BOOTVID.dll Sat Aug 18 04:49:09 2001 (3B7D8345)
f993c000 f993f580 RecAgent RecAgent.sys Tue Jan 13 21:03:28 2004 (4003ECA0)
f9940000 f9943500 nv_agp nv_agp.sys Sat Sep 07 03:37:05 2002 (3D7903E1)
f99f4000 f99f7c80 serenum serenum.sys Wed Aug 04 13:59:06 2004 (41107B2A)
f99f8000 f99fa580 ndistapi ndistapi.sys Sat Aug 18 04:55:29 2001 (3B7D84C1)
f9a0c000 f9a0fc80 mssmbios mssmbios.sys Wed Aug 04 14:07:47 2004 (41107D33)
f9a28000 f9a29b80 kdcom kdcom.dll Sat Aug 18 04:49:10 2001 (3B7D8346)
f9a2a000 f9a2b100 WMILIB WMILIB.SYS Sat Aug 18 05:07:23 2001 (3B7D878B)
f9a2c000 f9a2d580 intelide intelide.sys Wed Aug 04 13:59:40 2004 (41107B4C)
f9a36000 f9a37000 ParVdm ParVdm.SYS unavailable (00000000)
f9a42000 f9a43360 avgtdi avgtdi.sys Thu Aug 25 17:59:58 2005 (430D969E)
f9a4e000 f9a4f100 swenum swenum.sys Wed Aug 04 13:58:41 2004 (41107B11)
f9a52000 f9a53280 USBD USBD.SYS Sat Aug 18 05:02:58 2001 (3B7D8682)
f9a60000 f9a61f00 Fs_Rec Fs_Rec.SYS Sat Aug 18 04:49:37 2001 (3B7D8361)
f9a62000 f9a63080 Beep Beep.SYS Sat Aug 18 04:47:33 2001 (3B7D82E5)
f9a64000 f9a65080 mnmdd mnmdd.SYS Sat Aug 18 04:57:28 2001 (3B7D8538)
f9a66000 f9a67080 RDPCDD RDPCDD.sys Sat Aug 18 04:46:56 2001 (3B7D82C0)
f9a68000 f9a69080 avg7rsw avg7rsw.sys Tue Jul 26 20:10:51 2005 (42E6284B)
f9a94000 f9a95100 dump_WMILIB dump_WMILIB.SYS Sat Aug 18 05:07:23 2001 (3B7D878B)
f9b95000 f9b95c00 audstub audstub.sys Sat Aug 18 04:59:40 2001 (3B7D85BC)
f9bd0000 f9bd0d00 dxgthk dxgthk.sys Sat Aug 18 04:53:12 2001 (3B7D8438)
f9c52000 f9c53000 Null Null.SYS unavailable (00000000)
f9c53000 f9c54000 avgclean avgclean.sys Mon Dec 03 20:09:01 2007 (4753F1DD)
Unloaded modules:
efa49000 efa74000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9b98000 f9b99000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
efa74000 efa97000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f03bb000 f03c8000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f95d8000 f95e6000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9a6c000 f9a6e000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f048d000 f04a4000 ialmsbw.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f95d8000 f95e2000 amdk7.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8d5e000 f8d67000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f86a3000 f86a7000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f98e0000 f98e5000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt
-
Run MemTest:
http://www.memtest.org/
You will need to put this onto a floppy or ISO CD if you do not have a floppy drive.
Floppy is the easy way.
Your error is often a sign of failing RAM (memory sticks).
-
how do i use this software, do i run it under safe mode or normal mode?? do i use the bootable ISO, Bootable binary or for the floppy?? which extention should i use?? .gz, .zip??
Last edited by ramesh help; 09-02-2008 at 12:46 PM.
-
If you have a floppy drive that is the easiest:
http://www.memtest.org/download/2.00....00.floppy.zip
This floppy will be a boot disk.
Make sure your BIOS is set to boot the floppy drive first then start the computer with this floppy installed.
That's all. It will boot and run until you stop it.
-
what happends after the boot?? will my PC be better after this or should i post something to you?
-
When you start the PC MemTest will run until you stop it.
If you have a severe RAM problem it will start off listing data in a RED box = ERRORS
If you do not have a severe RAM problem then it will run "passes" through the system and show any errors that occur.
Let it run for as few hours and see if you get any errors.
After a few hours just stop it and remove the floppy.
There is nothing to "fix" here. This tool will just show whether or not your RAM is failing. If it is there is nothing to "fix". Most RAM has a "lifetime" warranty so if it is "bad" you should be able to replace it for shipping costs.