Re: Windows Crashed Big Time
- From: "cquirke (MVP Windows shell/user)" <cquirkenews@xxxxxxxxxxxxxxx>
- Date: Tue, 18 Oct 2005 12:08:46 +0200
>"colegg" <colegg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>I don't inow what the problem was initially...perhaps a trojan of something
>> of the kind, so I took advice from many & reinstalled Windows (Home...from
>> original OME disc).
That's one of many troubles with "just re-install". When this doesn't
fix the problem, as is often the case, you've not only learned nothing
about what the problem was, but have destroyed your best source of
information about that problem (the original installation).
See http://cquirke.mvps.org/reinst.htm
>> After doing that successfully, I installed sp1, then sp1. All went well.
Is that a typo, or do you mean SP1 and then SP2? Or is it XP SP1 and
then IE 6 SP1 or something like that?
FYI, it's not necessary to install XP SP1 before XP SP2. You can
install SP2 directly over original XP, and it will do everything
needed. But if your HD is > 137G and your original OS is the original
XP, then you should slipstream at least SP1 into the file set before
you do the initial install; the original XP is unsafe > 137G.
>> When I had reconnected to the net & went to the MS Update page, there were
>> 27 priority updates. I downloaded all in the normal update fashion (via the
>> update page) then installation began. As the installation was going, the
>> pute restarted...showing the following once it initially shut down.
>> On a blue screen, I saw;
>> Stop; c0000269 (Illegal system DLL relocation). The system DLL USER32.DLL
>> was relocated in memory. Tha application will not run properly. The
>> relocation occurred because the DLL C:\windows\system32\NTDLL.DLL occupied
>> an address range reserved for windows system DLL's. The vendor supplying the
>> DLL should %%
Interesting this applies to code files loaded after the initial
NTOSKrnl etc. This smells like the sort of issue I mentioned earlier;
the initial part of the OS load may lack support for "large" HDs, and
require needed files to be on the right side of that capacity barrier.
Events that shift files around within the address space - including
patching that replaces them - can break this requirement.
When installing the OS onto a bare drive, it is unlikely for any of
the files to be located beyond this capacity horizon. But then "just"
re-installing and then patching up an existing installation, the risk
is greater that some files will be over the horizon.
>> By this time I was so fed up with all the hassles from the earlier
>> trojan or whatever it was...that I just reformatted the partition &
>> started again. Reinstalled everything up to sp1 (did not
>> install sp2 this time) & all seems to be working fine.
If HD is > 137G, SP1 will work, but is prone to data corruption
because some particular contexts don't support > 137G - e.g. when the
system does a memory dump after a crash, that code isn't 137G+OK.
For this reason, as well as the more familiar safety/security
concerns, I'd favor SP2 over SP1 if it is at all possible.
>> Any ideas?
As above. Make sure your firewall is enabled! Because you have no
idea whether your previous installation was malware'd or not, you have
no idea whether your current installation process is open to similar
malware attack - so make sure your defenses are good.
I'd also step back and check for hardware defects at this point.
>--------------- ---- --- -- - - - -
I'm baaaack!
>--------------- ---- --- -- - - - -
.
- References:
- Re: Windows Crashed Big Time
- From: Glen
- Re: Windows Crashed Big Time
- Prev by Date: Re: Scheduled Restarts
- Next by Date: Re: Registry keys
- Previous by thread: Re: Windows Crashed Big Time
- Next by thread: Identifying a user
- Index(es):
Relevant Pages
|
