Stop 0x00000050 ntfs.sys problem [now with dump data]

Hi.

I have added a few new programs to my XP installation over thew past month, and last night I thought it was about time to make a new disk image of it.
One of the new programs was Norton System Works 2005 premiere - which includes the new version of ghost V.9. I set it off backing up before going to bed last night, and this morning I awoke to find a BSOD - page fault in nonpaged area - stop 0x00000050 Ntfs.sys.
I checked about online, found lots of suggestions to check the memory - and sure enough after running memtest86 - my memory had errors, I swapped another stick of RAM in, ran memtest again - fine.
Tried rebooting - same thing. my system is dual boot - both OS's give this same problem.
Tried booting to the recovery console - same thing.
I have removed all cards apart from my graphics card checked it with yet another stick of RAM but what ever I do does not seem to make the slightest bit of difference.
I'm stuck! Can anyone offer any assistance?
Thanks
Spotta.

 

After experimenting
I have managed to boot up using my original stick of RAM in slot 3 rather than slot 0 and by disconnecting every hard drive and optical on the system apart from my boot drive.
I have three minidumps for today - here is the data from the most recent one


Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini022305-03.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
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Feb 23 09:40:24.732 2005 (GMT+0)
System Uptime: 0 days 0:02:07.222
Loading Kernel Symbols
................................................................................................................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {18e, 2, 0, 804e3f27}

*** ERROR: Module load completed but symbols could not be loaded for a347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d347bus.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000018e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e3f27, address which referenced memory

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


READ_ADDRESS: 0000018e

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+11
804e3f27 8b7904 mov edi,[ecx+0x4]

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from f8933095 to 804e3f27

STACK_TEXT:
f21b8ba8 f8933095 0000018a 00000000 00000000 nt!KeSetEvent+0x11
f21b8bc8 f892f035 825d09b0 821f81c0 e34486d8 Npfs!NpSetClosingPipeState+0x183
f21b8bf8 f892f0a7 826272f0 00000000 82159790 Npfs!NpCommonCleanup+0x6f
f21b8c10 804e3d77 826272f0 821f81c0 821f81c0 Npfs!NpFsdCleanup+0x19
f21b8c20 8056b1d3 82159778 82fedca0 00000001 nt!IopfCallDriver+0x31
f21b8c54 80567391 820f7460 826272f0 0012019f nt!IopCloseFile+0x27c
f21b8c84 8056753b 820f7460 82159790 82fedca0 nt!ObpDecrementHandleCount+0x119
f21b8cac 805675ac e351dcd0 82159790 00000308 nt!ObpCloseHandleTableEntry+0x14d
f21b8cf4 805675f6 00000308 00000001 00000000 nt!ObpCloseHandle+0x87
f21b8d08 f85fb072 00000308 f21b8d64 017efd5c nt!NtClose+0x1d
WARNING: Stack unwind information not available. Following frames may be wrong.
f21b8d30 f85d4862 00000308 804e2af1 804e7160 a347bus+0xe072
f21b8d58 804df06b 00000308 017efd5c 7c90eb94 d347bus+0xd862
f21b8d58 7c90eb94 00000308 017efd5c 7c90eb94 nt!KiFastCallEntry+0xf8
017efd4c 00000000 00000000 00000000 00000000 0x7c90eb94


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
804e30e4-804e30e7 4 bytes - nt!KiServiceTable+3c4

[ 8f 60 66 80:b0 40 5d f8 ]
4 errors : !nt (804e30e4-804e30e7)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

STACK_COMMAND: kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

eax=00000000 ebx=e34486d8 ecx=0000018a edx=27950009 esi=f21b8be8 edi=00000000
eip=804e3f27 esp=f21b8b9c ebp=f21b8ba8 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeSetEvent+0x11:
804e3f27 8b7904 mov edi,[ecx+0x4] ds:0023:0000018e=????????
ChildEBP RetAddr Args to Child
f21b8ba8 f8933095 0000018a 00000000 00000000 nt!KeSetEvent+0x11 (FPO: [Non-Fpo])
f21b8bc8 f892f035 825d09b0 821f81c0 e34486d8 Npfs!NpSetClosingPipeState+0x183 (FPO: [Non-Fpo])
f21b8bf8 f892f0a7 826272f0 00000000 82159790 Npfs!NpCommonCleanup+0x6f (FPO: [Non-Fpo])
f21b8c10 804e3d77 826272f0 821f81c0 821f81c0 Npfs!NpFsdCleanup+0x19 (FPO: [Non-Fpo])
f21b8c20 8056b1d3 82159778 82fedca0 00000001 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f21b8c54 80567391 820f7460 826272f0 0012019f nt!IopCloseFile+0x27c (FPO: [Non-Fpo])
f21b8c84 8056753b 820f7460 82159790 82fedca0 nt!ObpDecrementHandleCount+0x119 (FPO: [Non-Fpo])
f21b8cac 805675ac e351dcd0 82159790 00000308 nt!ObpCloseHandleTableEntry+0x14d (FPO: [Non-Fpo])
f21b8cf4 805675f6 00000308 00000001 00000000 nt!ObpCloseHandle+0x87 (FPO: [Non-Fpo])
f21b8d08 f85fb072 00000308 f21b8d64 017efd5c nt!NtClose+0x1d (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be wrong.
f21b8d30 f85d4862 00000308 804e2af1 804e7160 a347bus+0xe072
f21b8d58 804df06b 00000308 017efd5c 7c90eb94 d347bus+0xd862
f21b8d58 7c90eb94 00000308 017efd5c 7c90eb94 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f21b8d64)
017efd4c 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806eb780 nt ntoskrnl.exe Wed Aug 04 07:19:48 2004 (41108004)
806ec000 806ffd80 hal halacpi.dll Wed Aug 04 06:59:04 2004 (41107B28)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 07:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 07:00:51 2004 (41107B93)
bf9d3000 bfd64f00 nv4_disp nv4_disp.dll Thu Oct 14 08:11:19 2004 (416E2697)
f3930000 f3953000 Fastfat Fastfat.SYS Wed Aug 04 07:14:15 2004 (41107EB7)
f3a83000 f3a8b8a0 NPDRIVER NPDRIVER.SYS Tue Aug 31 05:38:34 2004 (413400CA)
f3e43000 f3e45e80 secdrv secdrv.sys Fri Jan 16 13:16:04 2004 (4007E414)
f3e53000 f3ea5180 srv srv.sys Wed Aug 04 07:14:44 2004 (41107ED4)
f3ef6000 f3f0c580 PPSCAN PPSCAN.SYS Fri Mar 29 20:58:25 2002 (3CA4D571)
f3f35000 f3f61400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
f423a000 f423dee0 Aspi32 Aspi32.SYS Mon May 06 17:43:02 2002 (3CD6B296)
f4bbe000 f4bc1280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
f5b35000 f5b4c480 dump_atapi dump_atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
f5b59000 f5b5b900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
f5bed000 f5c5b400 mrxsmb mrxsmb.sys Wed Jan 19 04:26:50 2005 (41EDE18A)
f5cac000 f5cd6a00 rdbss rdbss.sys Thu Oct 28 02:13:57 2004 (418047D5)
f5d77000 f5d98d00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
f5d99000 f5dc0c00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
f5dc1000 f5e015a0 symidsco symidsco.sys Wed Nov 24 01:08:22 2004 (41A3DF06)
f5e02000 f5e2a9e0 SYMFW SYMFW.SYS Sat Jan 22 05:57:51 2005 (41F1EB5F)
f5e2b000 f5e4bf00 ipnat ipnat.sys Wed Sep 29 23:28:36 2004 (415B3714)
f5e4c000 f5e8bda0 SYMTDI SYMTDI.SYS Sat Jan 22 05:55:40 2005 (41F1EADC)
f5e8c000 f5ee3a80 tcpip tcpip.sys Wed Aug 04 07:14:39 2004 (41107ECF)
f5ee4000 f5ef6400 ipsec ipsec.sys Wed Aug 04 07:14:27 2004 (41107EC3)
f5f6f000 f5fce400 BsUDF BsUDF.SYS Mon Aug 25 03:27:28 2003 (3F497410)
f5fcf000 f5fdf280 Udfs Udfs.SYS Wed Aug 04 07:00:27 2004 (41107B7B)
f5fe0000 f5ff6020 meiudf meiudf.sys Fri Jan 31 08:45:54 2003 (3E3A37C2)
f6017000 f6027960 NAVENG NAVENG.Sys Thu Dec 30 21:46:10 2004 (41D47722)
f6028000 f60c0a60 NavEx15 NavEx15.Sys Thu Dec 30 21:45:19 2004 (41D476EF)
f60c1000 f60daa80 SYMEVENT SYMEVENT.SYS Tue Oct 19 22:18:08 2004 (41758490)
f60db000 f612c000 SAVRT SAVRT.SYS Sat Nov 01 11:26:37 2003 (3FA3986D)
f722c000 f722e280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
f73fc000 f742f200 update update.sys Wed Aug 04 06:58:32 2004 (41107B08)
f7430000 f7452680 ks ks.sys Wed Aug 04 07:15:20 2004 (41107EF8)
f7453000 f7483100 rdpdr rdpdr.sys Wed Aug 04 07:01:10 2004 (41107BA6)
f7504000 f7514e00 psched psched.sys Wed Aug 04 07:04:16 2004 (41107C60)
f7515000 f752b680 ndiswan ndiswan.sys Wed Aug 04 07:14:30 2004 (41107EC6)
f752c000 f753f900 parport parport.sys Wed Aug 04 06:59:04 2004 (41107B28)
f7540000 f7562e80 USBPORT USBPORT.SYS Wed Aug 04 07:08:34 2004 (41107D62)
f7563000 f7576780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 07:07:04 2004 (41107D08)
f7577000 f78291e0 nv4_mini nv4_mini.sys Thu Oct 14 08:15:31 2004 (416E2793)
f782a000 f7839d80 serial serial.sys Wed Aug 04 07:15:51 2004 (41107F17)
f783a000 f7843200 amdk7 amdk7.sys Wed Aug 04 06:59:19 2004 (41107B37)
f78aa000 f78b2700 wanarp wanarp.sys Wed Aug 04 07:04:57 2004 (41107C89)
f78ba000 f78c2880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
f7e45000 f7e47680 pfc pfc.sys Thu Jan 23 04:37:35 2003 (3E2F718F)
f7e49000 f7e4cc80 mssmbios mssmbios.sys Wed Aug 04 07:07:47 2004 (41107D33)
f834c000 f834e580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
f8354000 f8357c80 serenum serenum.sys Wed Aug 04 06:59:06 2004 (41107B2A)
f8360000 f8363300 cdrbsvsd cdrbsvsd.SYS Wed Jul 16 07:58:28 2003 (3F14F794)
f8364000 f8366f80 mouhid mouhid.sys Fri Aug 17 21:47:57 2001 (3B7D82FD)
f83e0000 f83fa580 Mup Mup.sys Wed Aug 04 07:15:20 2004 (41107EF8)
f83fb000 f8427a80 NDIS NDIS.sys Wed Aug 04 07:14:27 2004 (41107EC3)
f8428000 f84b4480 Ntfs Ntfs.sys Wed Aug 04 07:15:06 2004 (41107EEA)
f84b5000 f84cb780 KSecDD KSecDD.sys Wed Aug 04 06:59:45 2004 (41107B51)
f84cc000 f84e1360 PQV2i PQV2i.sys Mon Nov 22 23:51:56 2004 (41A27B9C)
f84e2000 f84f3f00 sr sr.sys Wed Aug 04 07:06:22 2004 (41107CDE)
f84f4000 f8512780 fltmgr fltmgr.sys Wed Aug 04 07:01:17 2004 (41107BAD)
f8513000 f852a800 SCSIPORT SCSIPORT.SYS Wed Aug 04 06:59:39 2004 (41107B4B)
f852b000 f8542480 atapi atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
f8543000 f8568700 dmio dmio.sys Wed Aug 04 07:07:13 2004 (41107D11)
f8569000 f8587880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
f8588000 f8598a80 pci pci.sys Wed Aug 04 07:07:45 2004 (41107D31)
f8599000 f85c6d80 ACPI ACPI.sys Wed Aug 04 07:07:35 2004 (41107D27)
f85c7000 f85ece00 d347bus d347bus.sys Sun Aug 22 14:31:09 2004 (4128A01D)
f85ed000 f8614380 a347bus a347bus.sys Fri Apr 30 07:37:01 2004 (4091F40D)
f8636000 f863ec00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
f8646000 f8650500 MountMgr MountMgr.sys Wed Aug 04 06:58:29 2004 (41107B05)
f8656000 f8662c80 VolSnap VolSnap.sys Wed Aug 04 07:00:14 2004 (41107B6E)
f8666000 f866f7c0 hpt3xx hpt3xx.sys Fri Oct 11 10:20:40 2002 (3DA697E8)
f8676000 f867ee00 disk disk.sys Wed Aug 04 06:59:53 2004 (41107B59)
f8686000 f8692200 CLASSPNP CLASSPNP.SYS Wed Aug 04 07:14:26 2004 (41107EC2)
f8696000 f86a0500 viaagp viaagp.sys Wed Aug 04 07:07:42 2004 (41107D2E)
f86a6000 f86b4e80 ohci1394 ohci1394.sys Wed Aug 04 07:10:05 2004 (41107DBD)
f86b6000 f86c3000 1394BUS 1394BUS.SYS Wed Aug 04 07:10:03 2004 (41107DBB)
f86f6000 f86fef80 LHidUsb LHidUsb.Sys Fri Nov 08 23:58:54 2002 (3DCC4FBE)
f8706000 f870ed80 HIDCLASS HIDCLASS.SYS Wed Aug 04 07:08:18 2004 (41107D52)
f8716000 f8725520 LMouFlt2 LMouFlt2.sys Fri Nov 08 23:58:27 2002 (3DCC4FA3)
f8726000 f8735900 Cdfs Cdfs.SYS Wed Aug 04 07:14:09 2004 (41107EB1)
f8736000 f8740000 SYMNDIS SYMNDIS.SYS Sat Jan 22 05:57:07 2005 (41F1EB33)
f8746000 f874e700 netbios netbios.sys Wed Aug 04 07:03:19 2004 (41107C27)
f8756000 f875ef20 PQIMount PQIMount.SYS Tue Nov 23 00:08:52 2004 (41A27F94)
f8776000 f8782e00 i8042prt i8042prt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
f8786000 f8792880 rasl2tp rasl2tp.sys Wed Aug 04 07:14:21 2004 (41107EBD)
f8796000 f87a0200 raspppoe raspppoe.sys Wed Aug 04 07:05:06 2004 (41107C92)
f87a6000 f87b1d00 raspptp raspptp.sys Wed Aug 04 07:14:26 2004 (41107EC2)
f87b6000 f87be900 msgpc msgpc.sys Wed Aug 04 07:04:11 2004 (41107C5B)
f87f6000 f87fff00 termdd termdd.sys Wed Aug 04 06:58:52 2004 (41107B1C)
f8806000 f8812180 cdrom cdrom.sys Wed Aug 04 06:59:52 2004 (41107B58)
f8816000 f8824080 redbook redbook.sys Wed Aug 04 06:59:34 2004 (41107B46)
f8846000 f884f480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
f8856000 f8864100 usbhub usbhub.sys Wed Aug 04 07:08:40 2004 (41107D68)
f8876000 f8886000 SAVRTPEL SAVRTPEL.SYS Sat Nov 01 11:26:40 2003 (3FA39870)
f88b6000 f88bc200 PCIIDEX PCIIDEX.SYS Wed Aug 04 06:59:40 2004 (41107B4C)
f88be000 f88c2900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
f88c6000 f88ca0a0 PxHelp20 PxHelp20.sys Sat Jul 26 00:49:00 2003 (3F21C1EC)
f88ce000 f88d4d00 viaagp1 viaagp1.sys Wed Jul 02 11:08:01 2003 (3F02AF01)
f88fe000 f8903880 LHidFlt2 LHidFlt2.Sys Fri Nov 08 23:58:36 2002 (3DCC4FAC)
f891e000 f8923200 vga vga.sys Wed Aug 04 07:07:06 2004 (41107D0A)
f8926000 f892aa80 Msfs Msfs.SYS Wed Aug 04 07:00:37 2004 (41107B85)
f892e000 f8935880 Npfs Npfs.SYS Wed Aug 04 07:00:38 2004 (41107B86)
f8936000 f893b060 SYMREDRV SYMREDRV.SYS Sat Jan 22 05:58:32 2005 (41F1EB88)
f893e000 f89451e0 SYMIDS SYMIDS.SYS Sat Jan 22 05:59:16 2005 (41F1EBB4)
f895e000 f8962500 watchdog watchdog.sys Wed Aug 04 07:07:32 2004 (41107D24)
f899e000 f89a4000 symlcbrd symlcbrd.sys Sun Aug 22 09:10:18 2004 (412854EA)
f89ce000 f89d2a00 KTC111 KTC111.SYS Fri Mar 16 18:30:21 2001 (3AB25BBD)
f89d6000 f89db000 usbuhci usbuhci.sys Wed Aug 04 07:08:34 2004 (41107D62)
f89de000 f89df000 fdc fdc.sys unavailable (00000000)
f89e6000 f89ec000 kbdclass kbdclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
f89ee000 f89f5580 Modem Modem.SYS Wed Aug 04 07:08:04 2004 (41107D44)
f89f6000 f89fa880 TDI TDI.SYS Wed Aug 04 07:07:47 2004 (41107D33)
f89fe000 f8a02580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
f8a06000 f8a0a080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
f8a0e000 f8a13a00 mouclass mouclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
f8a16000 f8a1d000 GearAspiWDM GearAspiWDM.SYS Tue Mar 23 18:44:48 2004 (406085A0)
f8a1e000 f8a26000 Asapi Asapi.SYS Wed Apr 17 19:27:01 2002 (3CBDBE75)
f8a2e000 f8a33000 flpydisk flpydisk.sys Wed Aug 04 06:59:24 2004 (41107B3C)
f8a3e000 f8a44180 HIDPARSE HIDPARSE.SYS Wed Aug 04 07:08:15 2004 (41107D4F)
f8a46000 f8a49000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
f8a4a000 f8a4c480 BsStor BsStor.sys Thu Jun 06 07:41:41 2002 (3CFF0425)
f8a4e000 f8a50240 hptpro hptpro.sys Fri Oct 18 03:37:21 2002 (3DAF73E1)
f8b36000 f8b37b80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
f8b38000 f8b39100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f8b3a000 f8b3b500 viaide viaide.sys Wed Aug 04 06:59:42 2004 (41107B4E)
f8b3c000 f8b3d700 dmload dmload.sys Fri Aug 17 21:58:15 2001 (3B7D8567)
f8b3e000 f8b3f480 d347prt d347prt.sys Sun Aug 22 14:31:48 2004 (4128A044)
f8b40000 f8b41480 a347scsi a347scsi.sys Fri Apr 30 07:32:58 2004 (4091F31A)
f8b66000 f8b67100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f8b6e000 f8b6f700 RootMdm RootMdm.sys Fri Aug 17 21:57:36 2001 (3B7D8540)
f8b70000 f8b71100 swenum swenum.sys Wed Aug 04 06:58:41 2004 (41107B11)
f8b76000 f8b77280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
f8b7e000 f8b7ff00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
f8b80000 f8b81080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
f8b82000 f8b83080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
f8b84000 f8b85080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
f8b86000 f8b87640 SYMDNS SYMDNS.SYS Sat Jan 22 05:56:20 2005 (41F1EB04)
f8bcc000 f8bcda80 ParVdm ParVdm.SYS Fri Aug 17 21:49:49 2001 (3B7D836D)
f8bce000 f8bcf1e0 WBHWDOCT WBHWDOCT.SYS Thu Jun 14 03:54:07 2001 (3B28274F)
f8c31000 f8c31b80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
f8c61000 f8c61a80 PQNTDrv PQNTDrv.SYS Fri Mar 14 20:18:28 2003 (3E723914)
f8c62000 f8c62d00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
f8c64000 f8c64c00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
f8c65000 f8c65b80 mbmiodrvr mbmiodrvr.sys Sat Apr 10 15:42:35 2004 (407807DB)
f8d67000 f8d67860 BANTExt BANTExt.sys Thu May 28 03:43:29 1998 (356CCF51)

Unloaded modules:
f8766000 f8771000 imapi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f835c000 f8360000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8916000 f891b000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f8378000 f837b000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt


I see it says memory corruption near the top - is this definately the cause of my problems?
Have to go and do some work now, but I'll be leaving it running - hopefully it'll be alright when I get back.

Spotta

 

0:000> .formats 804e30e4^804e30e7
Evaluate expression:
Decimal: 3
Binary: 00000000 00000000 00000000 00000011

See how the last 2 bits are flipped here?

This is the debugger telling you that the in-memory version of this file does not match the on-disk version. For the vast majority of these cases, its a direct result of bad ram, overclocking, bad timing, etc.

I have managed to boot up using my original stick of RAM in slot 3 rather than slot 0 and by disconnecting every hard drive and optical on the system apart from my boot drive.

im glad that got you into the machine, my guess it was the thermal cycling that made that ram behave, more than swapping slots. Have you tried putting it back in slot 0? wonder if you lost that slot..

This is really a hardware problem at this point, not my area of expertise, but you have some swap and fiddle in your future.

 

Well - if anything it is now worse!
I am using a stick of RAM (256mb) that works in 2 other machines fine and passes Memtest86. every single PCI card and IDE device is disconnected apart from my boot drive.
Now it gets to the verifying DMI pool data screen then reboots. it will just keep doing this if I do not switch it off.
I have tried a different power supply - no joy
Do you think my motherboard could be faulty?
regards
Spotta

 

well those bits didnt flip themselves

passes Memtest86 This is NOT an authoritative test. It can only indicate a positive, and software testers generally cannot report most errors that occur with ram. The machine that tests ram is a dedicated hardware device.

However, i dont think its the ram, since youve tested some good permutations. motherboard, BIOS, CPU are all on the list of 'whats next'

 

AN UPDATE.

ntfs.sys BSOD was caused by my 60GB drive - the one where ghost 9 was writing the image file too - it caused the same problem on 2 other machines when connected and I have now done a low-level format on it and it seems ok - not sure if I should trust it 100% anymore though....... this drive had my second OS on it which was backed up on another drive so no data lost.

My Main OS drive also had problems - this caused the continual rebooting. once I had it connected to another PC with it's own OS and booted it up disk check ran and found lots of problems. I ended up with 410MB of recovered files in my found.000 folder.

I have been running my original stick of 512MB since last night (still gives errors in memtest) and have not had any further problems yet.....

Do you think my memory has slight errors which although do not cause any problems in day to day running - caused the new Norton Ghost 9 to crash, corrupting both hdd's in the process?

I think I'll go back to the old Ghost for now that backs up drives in pc-dos mode rather than when the OS is running.

Although I have a RAID mobo, after hearing lots of problems people have rebuilding RAID arrays, I have always had lots of hdd's installed without RAID and manually made sure that every important partition in my machine is cloned to a disk image on a seperate hdd somewhere.
I shall stick to doing things this way as otherwise I am sure I would have lost a hell of a lot of important data.

Regards

Spotta

 

Do you think my memory has slight errors which although do not cause any problems in day to day running - caused the new Norton Ghost 9 to crash, corrupting both hdd's in the process?

This is like playing roulette. at some point, your going to get a winner.

 

Joe - does this mean you think I am correct?
I have already ordered a new stick - I have spent 2 days pulling my hair out getting my PC back to how it is now and would just like some confirmation from people who probably know a lot more than me.
If I wanted a riddle to solve - I would have gone elsewhere.
I realise that you are trying to help me, but could you be a little less cryptic

Thanks for the help so far

Spotta