Tech Support Forum banner
Status
Not open for further replies.
1 - 16 of 16 Posts

·
Registered
Joined
·
14 Posts
Discussion Starter · #1 ·
Windows XP : 5.1 Build 2600 (service pack 3)
Pentium4 : 2.66 ghz
Directx : 9.0c
BIOS : Phoenix Award
80GB Master: IDE with windows xp installed
500GB : IDE slave
ATI Radeon : Graphics card (Removed after step 1 as I suspected this might
have caused the problem!)
HP Printer : Removed
3.5 floppy
2 x Writeable DVD drives

Use Norton 2005 Antivirus
ZoneAlarm firewall
Windows auto update on
Windows Firewall off

1. Soon after SP3 was installed Windows began crashing at odd intervals.
My first encounter with FLTMGR.SYS error. Also no Start bar.

Blue screen OD Details:

"A problem has been detected and windows has shut down to prevent damage to your computer.
If this is the first tim ... etc
Check to be sure you have adequate disc space. If a driver is identified in the stop message
disable the drive or check with the manufacturer for driver updates. Try changing video adapters.

Check with your hardware vendor for ant BIOS updates. Disable BIOS memory options such as
caching and shadowing. If you need to use Safe Mode to remove or disable components, restart .. etc

Technical info :
STOP: 0x0000007e (0x00000005,0xF7 ... ETC

FLTMGR.SYS - Address F74F22B2 ... ETC"

2. I decided to see if the recovery console might solve the problem
(having used it successfully before)
3. Used Recovery console to repair, but PC Crashed towards the end!
4. Tried following the "Microsoft troubleshoot configuration errors" guide but couldn't
copy the week old RP folder files in Safe Mode(e.g. SOFTWARE, DEFAULT, SAM, SYSTEM & SERCURITY)
from SystemsInformationVolume to c:\windows\system32\config)
5. Tried Recovery console a second time ... but somehow it decided to reinstall Windows XP!
6. Windows restart after this XP reinstall but reboot failed as SOFTWARE was in error (see point 4!)
7. Couldn't access Repair Console and perform CHKDSK /r as needed an ADMIN password
that I did not have! Wouldn't take a simple carriage return! Frustration!
8. Found BartPE. Copied files using a friends'laptop running XP. Booted PC using the CD
9. Managed CHKDSK /r using BartPE. No bad sectors.
10. Copied registry files as in 4.
11. PC Now boots in Safe Mode.
12. Still get FLTMGR.SYS blue screen error on "normal boot". Also no Start bar.
13. In Safe Mode device manager hardware config : Microsoft System Managment BIOS driver :
Yellow exclamation mark!
Cannot access properties.
Also tried : copied over mssmbios.sys from friends laptop XP.
14. Managed to decipher one of the c:\windows\minidump files. Here are the results!

Opened log file 'c:\debuglog.txt'
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
WARNING: Whitespace at end of path element
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> reload;!analyze -v;r;kv;lmnt;.logclose;q
^ Bad register error in 'reload;!analyze -v;r;kv;lmnt;.logclose;q'
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
Unable to load image fltmgr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: f763870a, The address that the exception occurred at
Arg3: a3dd1aa0, Trap Frame
Arg4: 00000000

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: fltmgr

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47b0c01c

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

FAULTING_IP:
fltmgr+170a
f763870a f6462002 test byte ptr [esi+20h],2

TRAP_FRAME: a3dd1aa0 -- (.trap 0xffffffffa3dd1aa0)
.trap 0xffffffffa3dd1aa0
ErrCode = 00000000
eax=87750600 ebx=828b5c40 ecx=00000000 edx=00000001 esi=06088775 edi=87750602
eip=f763870a esp=a3dd1b14 ebp=a3dd1b60 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
fltmgr+0x170a:
f763870a f6462002 test byte ptr [esi+20h],2 ds:0023:06088795=??
.trap
Resetting default scope

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from f763a2a0 to f763870a

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a3dd1b60 f763a2a0 00dd1ba8 00000000 a3dd1ba8 fltmgr+0x170a
a3dd1b74 f763ac48 a3dd1ba8 00000000 877e0ba0 fltmgr+0x32a0
a3dd1b90 f7647809 a3dd1b01 00000000 804e8a41 fltmgr+0x3c48
a3dd1bc0 804e37f7 877e0ba0 828ff008 a3dd1c18 fltmgr+0x10809
a3dd1c58 8057aa9f 86ec14d0 828ff008 829132e8 nt+0xc7f7
a3dd1d00 8057aadf 00000410 00000470 00000000 nt+0xa3a9f
a3dd1d34 804de7ec 00000410 00000470 00000000 nt+0xa3adf
a3dd1d64 7c90e4f4 badb0d00 00e65840 a47b4d98 nt+0x77ec
a3dd1d68 badb0d00 00e65840 a47b4d98 a47b4dcc 0x7c90e4f4
a3dd1d6c 00e65840 a47b4d98 a47b4dcc 00000000 0xbadb0d00
a3dd1d70 a47b4d98 a47b4dcc 00000000 00000000 0xe65840
a3dd1d74 a47b4dcc 00000000 00000000 00000000 0xa47b4d98
a3dd1d78 00000000 00000000 00000000 00000000 0xa47b4dcc


STACK_COMMAND: kb

FOLLOWUP_IP:
fltmgr+170a
f763870a f6462002 test byte ptr [esi+20h],2

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: fltmgr+170a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: fltmgr.sys

BUCKET_ID: WRONG_SYMBOLS

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

eax=87750600 ebx=828b5c40 ecx=00000000 edx=00000001 esi=06088775 edi=87750602
eip=f763870a esp=a3dd1b14 ebp=a3dd1b60 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
fltmgr+0x170a:
f763870a f6462002 test byte ptr [esi+20h],2 ds:0023:06088795=??
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
a3dd1b60 f763a2a0 00dd1ba8 00000000 a3dd1ba8 fltmgr+0x170a
a3dd1b74 f763ac48 a3dd1ba8 00000000 877e0ba0 fltmgr+0x32a0
a3dd1b90 f7647809 a3dd1b01 00000000 804e8a41 fltmgr+0x3c48
a3dd1bc0 804e37f7 877e0ba0 828ff008 a3dd1c18 fltmgr+0x10809
a3dd1c58 8057aa9f 86ec14d0 828ff008 829132e8 nt+0xc7f7
a3dd1d00 8057aadf 00000410 00000470 00000000 nt+0xa3a9f
a3dd1d34 804de7ec 00000410 00000470 00000000 nt+0xa3adf
a3dd1d64 7c90e4f4 badb0d00 00e65840 a47b4d98 nt+0x77ec
a3dd1d68 badb0d00 00e65840 a47b4d98 a47b4dcc 0x7c90e4f4
a3dd1d6c 00e65840 a47b4d98 a47b4dcc 00000000 0xbadb0d00
a3dd1d70 a47b4d98 a47b4dcc 00000000 00000000 0xe65840
a3dd1d74 a47b4dcc 00000000 00000000 00000000 0xa47b4d98
a3dd1d78 00000000 00000000 00000000 00000000 0xa47b4dcc
start end module name
804d7000 806ed680 nt ntoskrnl.exe Mon Feb 11 22:33:54 2008 (47B0CD52)
806ee000 8070e300 hal hal.dll Mon Feb 11 21:35:41 2008 (47B0BFAD)
a3a8c000 a3ab6180 kmixer kmixer.sys Mon Feb 11 21:48:49 2008 (47B0C2C1)
a4262000 a42a2a80 HTTP HTTP.sys Mon Feb 11 21:44:28 2008 (47B0C1BC)
a42a3000 a42b7480 wdmaud wdmaud.sys Mon Feb 11 22:23:43 2008 (47B0CAEF)
a44f0000 a44fed80 sysaudio sysaudio.sys Mon Feb 11 22:22:20 2008 (47B0CA9C)
a45d8000 a46b0f80 NavEx15 NavEx15.Sys Fri Feb 29 01:20:50 2008 (47C75DF2)
a46b1000 a4709000 SAVRT SAVRT.SYS Mon Mar 07 22:49:41 2005 (422CDA85)
a5631000 a56aa6a0 v124nt v124nt.sys Wed Jan 02 15:58:35 2002 (3C332E2B)
a56ab000 a56ce180 Fastfat Fastfat.SYS Mon Feb 11 22:20:42 2008 (47B0CA3A)
a56f7000 a5726b20 faxnt faxnt.sys Wed Jan 02 16:02:43 2002 (3C332F23)
a57b7000 a57c6900 Cdfs Cdfs.SYS Mon Feb 11 22:20:35 2008 (47B0CA33)
a59ea000 a59f4000 secdrv secdrv.sys Wed Sep 13 14:18:32 2006 (45080528)
a5a92000 a5ae3c00 srv srv.sys Mon Feb 11 22:21:23 2008 (47B0CA63)
a5b0c000 a5b6bf20 k56nt k56nt.sys Wed Jan 02 16:03:58 2002 (3C332F6E)
a5b94000 a5baf980 fsksnt fsksnt.sys Wed Jan 02 16:03:31 2002 (3C332F53)
a5bb0000 a5bf4d40 fallback fallback.sys Wed Jan 02 16:01:32 2002 (3C332EDC)
a5c95000 a5cbd600 atksgt atksgt.sys Sun Jan 29 10:29:17 2006 (43DC98FD)
a5ce2000 a5ce42c0 mdmxsdk mdmxsdk.sys Mon Sep 17 11:00:14 2001 (3BA5C9AE)
a5e76000 a5eb4000 symidsco symidsco.sys Fri Feb 08 00:26:34 2008 (47ABA1BA)
a5eb4000 a5edc8c0 SYMFW SYMFW.SYS Thu Mar 29 03:33:54 2007 (460B2592)
a5ff5000 a600a900 nwlnkipx nwlnkipx.sys Mon Feb 11 21:46:51 2008 (47B0C24B)
a600b000 a6032c00 netbt netbt.sys Tue Feb 12 04:50:59 2008 (47B125B3)
a6033000 a6040a80 nwlnkspx nwlnkspx.sys Fri Aug 17 21:54:16 2001 (3B7D8478)
a60d3000 a60d6300 SYMREDRV SYMREDRV.SYS Thu Mar 29 03:33:57 2007 (460B2595)
a6133000 a613d180 SYMNDIS SYMNDIS.SYS Thu Mar 29 03:33:46 2007 (460B258A)
a6143000 a6150220 tonesnt tonesnt.sys Wed Jan 02 16:01:54 2002 (3C332EF2)
a6173000 a6182700 nwlnknb nwlnknb.sys Fri Aug 17 21:54:16 2001 (3B7D8478)
a61cf000 a61d2760 mdc8021x mdc8021x.sys Tue Oct 21 17:54:29 2003 (3F9564C5)
a62e7000 a62ea900 ndisuio ndisuio.sys Mon Feb 11 21:46:42 2008 (47B0C242)
a862b000 a862f680 lirsgt lirsgt.sys Sun Jan 29 11:06:18 2006 (43DCA1AA)
a863b000 a86429c0 SYMIDS SYMIDS.SYS Thu Mar 29 03:34:03 2007 (460B259B)
a866b000 a8682900 dump_atapi dump_atapi.sys Mon Feb 11 21:43:08 2008 (47B0C16C)
a8683000 a8693200 Udfs Udfs.SYS Mon Feb 11 21:37:13 2008 (47B0C009)
a86bc000 a872b780 mrxsmb mrxsmb.sys Mon Feb 11 22:23:14 2008 (47B0CAD2)
a872c000 a873fac0 prodrv06 prodrv06.sys Thu Oct 07 15:05:05 2004 (41654D11)
a8740000 a876ae80 rdbss rdbss.sys Mon Feb 11 22:34:53 2008 (47B0CD8D)
a876b000 a877e000 SAVRTPEL SAVRTPEL.SYS Mon Mar 07 22:49:43 2005 (422CDA87)
a877e000 a87d0000 SPBBCDrv SPBBCDrv.sys Thu Jul 22 00:08:26 2004 (40FEF76A)
a87d0000 a87f1b80 afd afd.sys Tue Feb 12 04:49:04 2008 (47B12540)
a87f2000 a88510e0 vsdatant vsdatant.sys Fri Mar 14 05:43:30 2008 (47DA1082)
a8852000 a8889180 tcpip6 tcpip6.sys Mon Feb 11 21:51:01 2008 (47B0C345)
a888a000 a88a6dc0 SYMEVENT SYMEVENT.SYS Sat Sep 16 06:48:19 2006 (450B9023)
a88a7000 a88cc500 ipnat ipnat.sys Mon Feb 11 21:48:08 2008 (47B0C298)
a88cd000 a890ca60 SYMTDI SYMTDI.SYS Thu Mar 29 03:33:34 2007 (460B257E)
a8931000 a8933900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
a8935000 a898d380 tcpip tcpip.sys Tue Feb 12 04:50:01 2008 (47B12579)
a898e000 a89a0600 ipsec ipsec.sys Tue Feb 12 04:49:44 2008 (47B12568)
a89a1000 a89b9380 InCDfs InCDfs.SYS Thu Jan 27 17:08:00 2005 (41F91FF0)
a89da000 a89fd000 klif klif.sys Tue May 15 09:40:47 2007 (4649720F)
a89fd000 a8a14000 iksyssec iksyssec.sys Wed Dec 05 00:28:45 2007 (4755F0BD)
a8a14000 a8a29000 iksysflt iksysflt.sys Mon Dec 03 23:01:35 2007 (47548ACF)
bf000000 bf011600 dxg dxg.sys Mon Feb 11 21:48:50 2008 (47B0C2C2)
bf012000 bf05f000 ati2dvag ati2dvag.dll Sat Mar 29 04:04:32 2008 (47EDBFD0)
bf05f000 bf0de000 ati2cqag ati2cqag.dll Sat Mar 29 03:12:57 2008 (47EDB3B9)
bf0de000 bf14e000 atikvmag atikvmag.dll Sat Mar 29 03:21:15 2008 (47EDB5AB)
bf14e000 bf17c000 atiok3x2 atiok3x2.dll Sat Mar 29 04:40:33 2008 (47EDC841)
bf17c000 bf483820 ati3duag ati3duag.dll Sat Mar 29 03:43:56 2008 (47EDBAFC)
bf484000 bf632f00 ativvaxx ativvaxx.dll Sat Mar 29 03:36:31 2008 (47EDB93F)
bf800000 bf9c2300 win32k win32k.sys Mon Feb 11 22:35:33 2008 (47B0CDB5)
f605b000 f60785a0 Uim_IM Uim_IM.sys Thu Mar 29 13:20:14 2007 (460BAEFE)
f6079000 f60d1e80 update update.sys Mon Feb 11 21:42:13 2008 (47B0C135)
f60d2000 f60e2e00 psched psched.sys Mon Feb 11 21:47:16 2008 (47B0C264)
f60e3000 f60f9580 ndiswan ndiswan.sys Tue Feb 12 04:50:43 2008 (47B125A3)
f60fe000 f6101f60 HPZipr12 HPZipr12.sys Fri Oct 21 08:28:57 2005 (435898B9)
f610a000 f610db00 usbscan usbscan.sys Mon Feb 11 22:01:28 2008 (47B0C5B8)
f6184000 f6196720 NAVENG NAVENG.Sys Fri Feb 29 01:21:51 2008 (47C75E2F)
f6197000 f61aa900 parport parport.sys Mon Feb 11 21:42:43 2008 (47B0C153)
f61ab000 f61d12c0 AmosNt AmosNt.SYS Wed Jan 02 15:56:15 2002 (3C332D9F)
f61d2000 f625a4e0 HSF_CNXT HSF_CNXT.sys Wed Jan 02 16:06:01 2002 (3C332FE9)
f625b000 f626d940 basic2 basic2.sys Wed Jan 02 15:59:13 2002 (3C332E51)
f626e000 f6291200 USBPORT USBPORT.SYS Mon Feb 11 21:49:23 2008 (47B0C2E3)
f6292000 f62b5a80 portcls portcls.sys Mon Feb 11 22:26:18 2008 (47B0CB8A)
f62b6000 f66a5b00 ALCXWDM ALCXWDM.SYS Thu Jan 24 08:35:49 2008 (47984DE5)
f66a6000 f66c8700 ks ks.sys Mon Feb 11 22:23:00 2008 (47B0CAC4)
f66c9000 f66dcf00 VIDEOPRT VIDEOPRT.SYS Mon Feb 11 21:48:12 2008 (47B0C29C)
f66dd000 f6b03000 ati2mtag ati2mtag.sys Sat Mar 29 04:04:09 2008 (47EDBFB9)
f6b73000 f6b7f300 HPZid412 HPZid412.sys Fri Oct 21 08:28:51 2005 (435898B3)
f6b93000 f6b9de00 Fips Fips.SYS Mon Feb 11 21:38:34 2008 (47B0C05A)
f749d000 f74a0f00 MODEMCSA MODEMCSA.sys Fri Aug 17 21:57:37 2001 (3B7D8541)
f74c1000 f74c4c80 mssmbios mssmbios.sys Mon Feb 11 21:42:25 2008 (47B0C141)
f74e5000 f74feb80 Mup Mup.sys Mon Feb 11 22:23:20 2008 (47B0CAD8)
f74ff000 f751b420 prohlp02 prohlp02.sys Thu Oct 07 15:09:22 2004 (41654E12)
f751c000 f752d000 sfdrv01 sfdrv01.sys Mon Apr 04 11:43:21 2005 (42511A49)
f752d000 f7541000 srescan srescan.sys Tue Dec 04 22:30:06 2007 (4755D4EE)
f7541000 f756d980 NDIS NDIS.sys Tue Feb 12 04:50:39 2008 (47B1259F)
f756e000 f75fa600 Ntfs Ntfs.sys Mon Feb 11 22:21:59 2008 (47B0CA87)
f75fb000 f760df00 WudfPf WudfPf.sys Fri Sep 29 02:55:43 2006 (451C7D1F)
f760e000 f7624880 KSecDD KSecDD.sys Mon Feb 11 21:36:35 2008 (47B0BFE3)
f7625000 f7636f00 sr sr.sys Mon Feb 11 21:39:46 2008 (47B0C0A2)
f7637000 f7656b00 fltmgr fltmgr.sys Mon Feb 11 21:37:32 2008 (47B0C01C)
f7657000 f766e900 atapi atapi.sys Mon Feb 11 21:43:08 2008 (47B0C16C)
f766f000 f768d880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
f768e000 f769ea80 pci pci.sys Mon Feb 11 21:42:22 2008 (47B0C13E)
f769f000 f76ccd80 ACPI ACPI.sys Mon Feb 11 21:42:12 2008 (47B0C134)
f76ee000 f76f7180 isapnp isapnp.sys Mon Feb 11 21:42:19 2008 (47B0C13B)
f76fe000 f7708580 MountMgr MountMgr.sys Mon Feb 11 21:42:13 2008 (47B0C135)
f770e000 f7717000 sfsync02 sfsync02.sys Thu Apr 14 13:12:32 2005 (425E5E30)
f771e000 f772ac80 VolSnap VolSnap.sys Mon Feb 11 21:43:45 2008 (47B0C191)
f772e000 f7736e00 disk disk.sys Mon Feb 11 21:43:27 2008 (47B0C17F)
f773e000 f774a180 CLASSPNP CLASSPNP.SYS Mon Feb 11 22:22:48 2008 (47B0CAB8)
f774e000 f775c000 ikfilesec ikfilesec.sys Mon Dec 10 03:37:01 2007 (475CB45D)
f775e000 f7766b60 PxHelp20 PxHelp20.sys Wed Aug 09 18:27:31 2006 (44DA1B03)
f776e000 f7776f00 SISAGPX SISAGPX.sys Thu Feb 20 01:18:33 2003 (3E542CE9)
f77ce000 f77d6e00 intelppm intelppm.sys Mon Feb 11 21:35:46 2008 (47B0BFB2)
f77de000 f77e8480 imapi imapi.sys Mon Feb 11 21:43:42 2008 (47B0C18E)
f77ee000 f77f6c00 AFS2K AFS2K.SYS Fri Oct 08 02:16:03 2004 (4165EA53)
f77fe000 f780d600 cdrom cdrom.sys Mon Feb 11 21:43:25 2008 (47B0C17D)
f780e000 f781c100 redbook redbook.sys Mon Feb 11 21:43:02 2008 (47B0C166)
f781e000 f782cb00 drmk drmk.sys Mon Feb 11 21:48:53 2008 (47B0C2C5)
f782e000 f783c3e0 SOAR SOAR.SYS Wed Jan 02 15:55:21 2002 (3C332D69)
f783e000 f784b5a0 rksample rksample.sys Wed Jan 02 15:58:55 2002 (3C332E3F)
f784e000 f785dc00 serial serial.sys Mon Feb 11 22:22:09 2008 (47B0CA91)
f785e000 f786ad00 i8042prt i8042prt.sys Mon Feb 11 22:24:29 2008 (47B0CB1D)
f786e000 f787a880 rasl2tp rasl2tp.sys Tue Feb 12 04:49:45 2008 (47B12569)
f787e000 f7888200 raspppoe raspppoe.sys Mon Feb 11 21:48:31 2008 (47B0C2AF)
f788e000 f7896900 msgpc msgpc.sys Mon Feb 11 21:47:12 2008 (47B0C260)
f789e000 f78a9d00 raspptp raspptp.sys Tue Feb 12 04:50:02 2008 (47B1257A)
f78ae000 f78b7f00 termdd termdd.sys Mon Feb 11 21:44:21 2008 (47B0C1B5)
f78be000 f78c7e80 NDProxy NDProxy.SYS Mon Feb 11 21:48:28 2008 (47B0C2AC)
f78ee000 f78fc880 usbhub usbhub.sys Mon Feb 11 21:49:25 2008 (47B0C2E5)
f791e000 f792c000 KCOM KCOM.SYS Fri Mar 23 00:22:00 2007 (46031DA8)
f792e000 f7936700 wanarp wanarp.sys Mon Feb 11 21:48:19 2008 (47B0C2A3)
f793e000 f7946f00 ip6fw ip6fw.sys Mon Feb 11 21:44:02 2008 (47B0C1A2)
f794e000 f7956780 netbios netbios.sys Mon Feb 11 21:46:47 2008 (47B0C247)
f796e000 f7974180 PCIIDEX PCIIDEX.SYS Mon Feb 11 21:43:07 2008 (47B0C16B)
f7976000 f797ad00 PartMgr PartMgr.sys Mon Feb 11 21:43:29 2008 (47B0C181)
f797e000 f7982300 hotcore3 hotcore3.sys Thu Mar 29 13:18:28 2007 (460BAE94)
f7986000 f798e000 sfhlp02 sfhlp02.sys Wed Feb 23 15:59:54 2005 (421CA87A)
f799e000 f79a4200 UimBus UimBus.sys Thu Mar 29 13:20:08 2007 (460BAEF8)
f79a6000 f79ab000 flpydisk flpydisk.sys Mon Feb 11 21:43:00 2008 (47B0C164)
f79be000 f79c5d80 usbccgp usbccgp.sys Mon Feb 11 21:49:26 2008 (47B0C2E6)
f79c6000 f79cb200 vga vga.sys Mon Feb 11 21:48:12 2008 (47B0C29C)
f79ce000 f79d2a80 Msfs Msfs.SYS Mon Feb 11 21:37:16 2008 (47B0C00C)
f79d6000 f79dd880 Npfs Npfs.SYS Mon Feb 11 21:37:17 2008 (47B0C00D)
f79e6000 f79ec500 usbprint usbprint.sys Mon Feb 11 22:03:57 2008 (47B0C64D)
f79ee000 f79f3440 HPZius12 HPZius12.sys Fri Oct 21 08:22:46 2005 (43589746)
f7a16000 f7a1a500 watchdog watchdog.sys Mon Feb 11 21:48:38 2008 (47B0C2B6)
f7a36000 f7a3c000 symlcbrd symlcbrd.sys Sun Aug 15 13:36:33 2004 (411F58D1)
f7a7e000 f7a86000 Afc Afc.sys Wed Feb 23 06:58:55 2005 (421C29AF)
f7a86000 f7a8b300 pfc pfc.sys Sat Sep 20 00:45:46 2003 (3F6B952A)
f7a8e000 f7a95100 InCDPass InCDPass.sys Thu Jan 27 17:07:33 2005 (41F91FD5)
f7a96000 f7a9cc80 incdrm incdrm.SYS Thu Jan 27 17:07:27 2005 (41F91FCF)
f7a9e000 f7aa2300 usbohci usbohci.sys Mon Feb 11 21:49:23 2008 (47B0C2E3)
f7aa6000 f7aad600 usbehci usbehci.sys Mon Feb 11 21:49:23 2008 (47B0C2E3)
f7aae000 f7ab5e00 sisnic sisnic.sys Wed Jul 10 09:39:32 2002 (3D2BF2C4)
f7ab6000 f7abd580 Modem Modem.SYS Mon Feb 11 21:51:21 2008 (47B0C359)
f7abe000 f7abf000 fdc fdc.sys unavailable (00000000)
f7ac6000 f7acba00 mouclass mouclass.sys Mon Feb 11 21:42:15 2008 (47B0C137)
f7ace000 f7ad4000 kbdclass kbdclass.sys Mon Feb 11 21:42:15 2008 (47B0C137)
f7ad6000 f7adaa80 TDI TDI.SYS Mon Feb 11 21:51:08 2008 (47B0C34C)
f7ae6000 f7aea580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
f7aee000 f7af2080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
f7af6000 f7afa880 hamachi hamachi.sys Thu Aug 16 00:05:00 2007 (46C3869C)
f7afe000 f7b01000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
f7b9a000 f7b9c200 InCDrec InCDrec.SYS Thu Jan 27 17:08:07 2005 (41F91FF7)
f7b9e000 f7ba0280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
f7bb6000 f7bb8f00 ws2ifsl ws2ifsl.sys Fri Aug 17 21:55:58 2001 (3B7D84DE)
f7bbe000 f7bc1000 tunmp tunmp.sys Mon Feb 11 21:46:45 2008 (47B0C245)
f7bc2000 f7bc51c0 cdrbsdrv cdrbsdrv.SYS Mon Mar 08 03:55:49 2004 (404BEEC5)
f7bd6000 f7bd9d80 serenum serenum.sys Mon Feb 11 21:42:45 2008 (47B0C155)
f7bda000 f7bdc980 gameenum gameenum.sys Mon Feb 11 21:49:16 2008 (47B0C2DC)
f7bde000 f7be0780 ndistapi ndistapi.sys Mon Feb 11 21:48:27 2008 (47B0C2AB)
f7bee000 f7befb80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
f7bf0000 f7bf1100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f7bf2000 f7bf3780 siside siside.sys Mon Oct 21 05:40:03 2002 (3DB38523)
f7bf4000 f7bf5780 sonyhcb sonyhcb.sys Mon Nov 05 00:23:13 2001 (3BE5DBF1)
f7bf6000 f7bf72e0 sfhlp01 sfhlp01.sys Mon Dec 01 15:20:51 2003 (3FCB5C53)
f7c06000 f7c07a80 ParVdm ParVdm.SYS Fri Aug 17 21:49:49 2001 (3B7D836D)
f7c38000 f7c39100 swenum swenum.sys Mon Feb 11 21:42:22 2008 (47B0C13E)
f7c3a000 f7c3b600 UimFIO UimFIO.SYS Thu Mar 29 13:20:09 2007 (460BAEF9)
f7c42000 f7c43280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
f7c44000 f7c45f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
f7c46000 f7c47080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
f7c48000 f7c49080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
f7c4a000 f7c4b080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
f7c84000 f7c85100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f7caa000 f7cab600 SYMDNS SYMDNS.SYS Thu Mar 29 03:33:37 2007 (460B2581)
f7cb6000 f7cb6d00 PCIIde PCIIde.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
f7d51000 f7d51a00 Cdralw2k Cdralw2k.SYS Wed Aug 10 19:28:04 2005 (42FA4734)
f7d52000 f7d52b80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
f7d86000 f7d86980 Cdr4_xp Cdr4_xp.SYS Wed Aug 10 19:28:07 2005 (42FA4737)
f7dc5000 f7dc5c00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
f7de4000 f7de4940 SVKP SVKP.sys Mon Mar 10 15:31:42 2003 (3E6CAFDE)
f7de7000 f7de7d00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)

Unloaded modules:
a3bcf000 a3bfa000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a4280000 a42a3000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a4799000 a47a6000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a4490000 a449e000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c5e000 f7c60000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a4255000 a4280000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7e42000 f7e43000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a5d8e000 a5d9b000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a5dce000 a5ddc000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a59a7000 a59ca000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c1e000 f7c20000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f795e000 f7967000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79b6000 f79bb000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b8a000 f7b8d000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7dbe000 f7dbf000 Cdralw2k.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7dbb000 f7dbc000 Cdr4_xp.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7db2000 f7db3000 Cdralw2k.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7db1000 f7db2000 Cdr4_xp.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt


Any help gladly welcome!!!


Thanks

Mike
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Hi Mike


Have you had any luck finding a successful repair yet? If yes, congratulations. If not, read on.

XP Re-Installation Choices
Since you've had so much coming & going, and even had files from a separate laptop PC involved (did you also copy Registry files from that PC?) --- You might be able to have better luck with a repair install that you start from a known point (your last re-install seems to have caught you by surprise --- there may be some question as to whether you performed a repair install or a parallel install). I like Michael Steven's guide for the details and possible 'gotchas' of repair installs --- http://www.michaelstevenstech.com/XPrepairinstall.htm

And even easier choice, if you have good backups, would be simply to start over - using a disk-image backup of your system from before your post-SP3 trials. I'd imagine that you'd have already taken this route if you had such a disk-image (from N. Ghost, or Acronis, etc.... or a "Recovery Disk"). I mention these as "easy" choices not because they are fast (since in many cases a fair amount of data has to be restored from backups), but because they have such a high degree of success.

Fix Current Installation
If you'd like to try and salvage your current installation without having to reinstall Windows - there are a few things to take a look at.

SP3 inspects your PC's drivers, and provides updates to many of them. I have seen some systems have settings for the hard drives change after installing SP3. Have a look in Device Manager for the settings for your hard drives. See if they've reverted to a slower mode than they should be assigned (for example, if an IDE drive is set to PIO mode rather than to DMA-4 or DMA-5). If you see such a discreprancy, try uninstalling the controller in Device Manager, as well as uninstalling the hard drive (don't reboot until both have been uninstalled). Windows will re-detect them & hopefully assign the proper settings - - you will likely have to reboot again to let Windows make the changes after it re-detects the devices. Check in Device Manager afterwards to make sure that the settings are now correct.

In the same manner, you can uninstall any flagged devices you find in Device Manager (such as the Microsoft System Managment BIOS driver), and let Windows attempt to redetect them correctly. You may have inadvertently made matters worse by copying incorrect drivers and files from the laptop to your computer, as the laptop likely has quite different hardware.

Norton & FLTMGR.SYS
*Note* --- another complicating factor might be a possible conflict with the Norton version you have installed and SP3. It's not unusual for antivirus or system-utility software to need to be updated to work well with a major Service Pack release. There was a known issue with Norton & a post-SP2 hotfix (this may likely have been included in SP3) --- http://support.microsoft.com/kb/933215 --- Microsoft links you to their support webpages at the end of that article & mentions that a hotfix is available -- but sometimes for such a download, a fee is required (but not always).

It might be interesting to see what would happen if you download SP3 as a full download ( --- http://www.microsoft.com/downloads/...a8-5e76-401f-be08-1e1555d4f3d4&displaylang=en --- ), and then (offline) uninstall Norton (some versions of Norton can uninstall in Safe Mode, some can't), and then install SP3 offline from your pre-downloaded installer. Certainly, you'd check your device settings & Device Manager afterwards - just in case.

Malware or Hardware issues
And, just to be thorough: sometimes it's coincidental hardware failure or misconfiguration masquerading as a software problem -- or malware infection -- that is complicating things. If your BartPE disk is a UBCD4Win disk, it should have diagnostics on it that you can use to test your system memory and hard drives. Enter Bios Setup for you PC too, to make sure that the CMOS battery doesn't need replacing (which would cause the Bios to not be able to save the correct settings) -- checking the time/date in the Bios is the easiest route to check on that. Go through the main Bios settings while you're in there, to make sure they're all OK.

For malware, the UBCD4Win is an excellent tool to use to run malware scans. If your BartPE does not have such tools, you can create your own UBCD4Win at no cost, so long as you have a WinXP disk handy --- http://www.ubcd4win.com

Best of luck!
. . . Gary
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #3 ·
Thanks for the reply. No I only copied the one file(mssmbios.sys). The registry files were my own!. Sadly I don't have "GHOST" or similar! My next purchase! I have most of my valuable data (My Documents for 4 users) backed up but would rather not lose/reinstall everything in Program files etc! I've also checked RAM (one bank removed as it had errors) and I've cleaned out copious amounts of dust. I've also remove Norton 2005 using the "Norton Removal Tool". I'll maybe try repair install one more time! I'll also give UBCD4Win a go once I have time to download it!
BIOS battery is OK. I removed this for 15 min in an attempt to get around the repair console "Enter an Admin password" .. but it didn't work! Still keeping time OK.
For malware I've run spybot search and destroy

Would I be able to install SP3 in Safe Mode? Is there the slightest chance that this might solve my problem?

Thanks again. I'll let you know what happens!
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Hi again Mike


The editors at PC World mention that they've installed SP3 in Safe Mode (they used the standalone file downloaded ahead-of-time) --- http://www.pcworld.com/article/id,145811-c,xp/article.html ---

The fact that you had one bank of memory that received errors on your tests indicates that your problems might be linked to data corruption resulting from the bad module. It's possible that installing SP3 might help, simply because it will replace so many system files with fresh versions (of course, use a downloaded version of SP3 from after you removed the bad memory module).

If you have the time, I think scanning your hard drive for malware with a recently-made UBCD4Win CD would be an excellent first step to do -- and then proceed to your repair installation and SP3 update. If you want to try slip-streaming SP3 and your earlier version XP files into one CD, here's a tutorial for that --- http://www.howtohaven.com/system/slipstream-xp-service-pack-3.shtml

If particular programs on your systems also experienced serious data corruption, they might also have to be reinstalled. But if the memory module's problem was a recent failure, and your programs were installed long ago when the module was working OK, then you might be OK.

Best of luck
. . . Gary
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #5 ·
Unfortunately I can't get SP3 to install as I don't have cryptographic services running.. and I can't make cryptographic services start because RPC is stuck in "starting" status ... and it looks like I need RPC in "started" mode b4 I can get crypto going! Ho hum!
Me thinks it might be time to format c:\ and start from scratch! Thanks for the note on memory faults causing corruptions. Is this a case of senile dementia for PC's? It copies data to memory, forgets part of it and then copies it back? No wonder the PC is in a mess!

Thanks again!
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Hi again


Hope it works out OK.

You are right that data corruption is like dementia for PCs. When a module is failing, it might not copy the data correctly from the hard drive, and then copies it's error(s) back onto the hard drive (when the file is saved, or the program exits) often overwriting good files with bad copies. It can make the copying errors nearly at any time when saving things to the hard drive. Ouch!

I've got a system on the test bench for some rebuilding ... maybe I'll experiment a bit with installing SP3 in Safe Mode, just to see for myself what little details might trip things up. RPC should start in Safe Mode, unless it's either disabled or there's an error in the Registry --- http://support.microsoft.com/kb/838428 --- (I'll assume, too, you were logged on with administrative priviledges).

At least we don't lack for puzzles!
. . . Gary


P.S. ... hmm -- one harmless thing you could try, before going the full-reinstall route, is a run of Windows File Protection (Xp's name for a utility very much like the Win9x System File Checker). If you've your Windows XP CD (or good copies of the .cabs on your hard drive) handy, from the Start/Run box, type cmd (to bring up a command line in a window), and from the command line, type sfc /scannow (it might ask you either for the location of your Windows CD, or the spot on the hard drive where your .cabs are stored). After that procedure has finished, see if you can start RPC and Cryptograhic Services in Safe Mode -- and if so, you should be OK to install SP3.
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #7 ·
Tried registry change on RPC but no go. Still stuck in "starting" mode. it never gets to "started".
Had previously tried scannow but this did not do anything ... no activity showing in "Task Manager" .... obviously the registry must be in a REAL mess!

So ... I've formatted c: and reinstalled XP! The PC now works in "normal" mode.

HOWEVER!

In my innocence I thought reinstalling XP on the master c: would leave my internal HDD Slave f: drive untouched. However, I am now prompted to format this drive! I presume all the data is still there! Any suggestions about how I can access it?

The original slave was marked as F: as I had a C: and two DVD drives. When I installed the slave HDD that logically ended up as F:. However, as part of the XP reinstall the HDD has now been lettered D: ... as the hard drives are allocated letters before any CD/DVD drives!
AAaaarrgghh!
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Hi again


It's always an adventure with the drive letters during installs/reinstalls. Memory-card readers can add to the adventure too (you can end up with your system drive being drive letter I or J ... since each reader slot gets a drive letter. I imagine this legacy artifact from the first days of the IBM PC will eventually get fixed (meaning: flexible allotment of such drive assignments during the install itself).

Curious -- if you boot from the UBCD4Win (or other Bart PE disk), can you read your large drive them?

When you first installed your 500gb drive, was your motherboard able to recognize it's full extent? Or did you have to use 'drive-overlay' software to get around not having 48-bit LBA on the motherboard? If you used drive-overlay software (such as EZ-Bios, Disk Manager, etc.) -- that could explain the odd format request.

If your motherboard had 48-bit LBA support built-in already (or if you added an IDE controller with 48-bit support), another thing you could try is to go into Device Manager, and "uninstall" the 500gb hard drive (and don't reboot just yet) and then also "uninstall" the IDE controller that it's attached to (I believe you have both drives on the Primary IDE controller) --- and then reboot. XP will re-detect the drives & the controllers, this can sometimes help if things weren't detected properly.

Should none of the above apply or help, do you see any "Access Denied" messages while trying to view the drive, or any such disk-related messages in Event Viewer? (Event Viewer is in the Administrative Tools in the Control Panel).

As Lewis Carroll has Alice proclaim .... "curiouser and curiouser"
. . . Gary
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #9 ·
Thanks for the speedy reply!
Panic over! I think it might have something to do with the base level XP?
Could this work with 500MB HDD?
I have never used level of XP before as the PC came with SP1 already installed.
I have since installed SP1 and the drive is now readable again. Pheew!
I also had initial problems connecting to the internet via my wired wireless router... and then I remebered that I needed SP2 for the better router drivers!
One other point of interest (which I expect you already know) is that you no longer deal with a human when requesting to reinstall XP product key. It's all done by inputing info via the phone. At least it avoids having to explain at great lengths why you need to do it!
Now for SP3 ... and holding breath ... reinstall Norton antivirus!
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Hi again


Yes, you were correct in your guess that Windows XP in it's original version did not natively support drives larger than 127gb (the native support arrived with SP1). I was thinking that when you reinstalled, you then added the service packs and updates just after that. . . Glad that SP1 got you going again.

XP's Service Pack 3 has worked well on all the systems I've updated . . . and I haven't had any customers call with SP3 problems. (Vista's Service Pack 1 is another story!)

Congratulations again,
. . . Gary
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #11 ·
I'm now 90% back to normal. I had another issue with the monitor defaulting to vga.sys and being stuck in 640 x 480. It also did not appear on the Device Manager tree!
Fortunately I managed to dig out the device drivers that came with the PC which solved that problem. Have still to install SP3. Thinks I'll ghost the HDD after SP3 before installing Norton or reinserting the graphics card! I also need to get some replacement memory! Thanks for all the help and advice!
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Sounds pretty good so far. I imagine you've heard of the possible confict between Norton and SP3 (false positives which can lead to a few unfortunate Registry changes) ... but by installing SP3 in either Safe Mode or offline with Norton turned off, or with Norton temporarily uninstalled --- you can avoid those particular headaches. So I think you'll soon be back into the smooth sailing side of computing.
. . . Gary
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #13 ·
I installed SP3 and then contacted Norton to find out how to avoid the reigistry problem.
I allowed them remote access ... so they installed the registry patch first and then installed Norton, all in "normal" mode. Very nifty! What's more everything still works! I'm still waiting on Amazon to deliver "Norton Ghost" ... so I'm not going to install anything else until I'm backed up.
One further ... and hopefully last question!
I presume Ghost copies the whole partition to backup? Does this mean that I need a partition on my external HDD .. or does Ghost simply treat the backed-up partition as one large file?
Also, if I have a 500GB external drive is there an advantage to having it partitioned?
If so then why ... and what would be a good partition size? Currently it has one partition only!
 

·
TSF Team Emeritus , Microsoft Visiting Expert
Joined
·
3,258 Posts
Hi again


You don't have to create a separate partition for the Ghost backup images (thankfully). You should have plenty of room on a 500gb drive for both full and incremental backups. The newer versions of Ghost have lots of options for your backup plans.

One strategy I like to employ when possible: have at least one of your full backup images saved to a bootable DVD set (Ghost can automatically make images saved to DVDs bootable for you). That way, in the event of hardware failure on your backup hard drive(s), you have a nice safety net & can avoid saying all those words that aren't in the Bible :)

Best of luck!
. . . Gary


P.S. glad to hear that Norton support was so quick and capable with their help.
 

·
Registered
Joined
·
14 Posts
Discussion Starter · #15 ·
Thanks for the hint re the bootable DVD. Have now installed Ghost v14. Does a backup v quickly! Backoffice used to take an age but Ghost backed up the c: and my documents separately in a little over half an hour. I feel a lot safer now ... perhaps too safe??!
 
1 - 16 of 16 Posts
Status
Not open for further replies.
Top