Hi,
I followed the instructions on your website to disable automatic rebooting and finally got to see an error message ( it was rebooting too fast for me to see it before). Here's my error message, please help me fix it - it's extremely annoying!

c0000269 [illegal system DLL relocation] system DLL Kernel32.dll was relocated in memory. This application will not run properly. Relocation occured because DLL C:\WINDOWS\SYSTEM32\GDI32.DLL occupied a range reserved for windows system DLLS/

I googled, searched and couldn't find any solutions. My computer reboots a zillion times before it will start up and be useable. I didn't install any new software - this happened after a microsoft update. I tried chkdsk /r - I formated and reinstalled windows =- tried repairing, reinstalling, everything I can thing of! Someone please help!!
Thanks in advance.

I see this issue posted elsewhere resulting from a Windows Update. It appears to be OEM specific. I see Compaq mentioned alot.

That being said are you saying that you reinstalled XP & you still get the same error?

How did you reinstall? Did you restore factory settings from an OEM disk or... ???

Originally Posted by jephree

I see this issue posted elsewhere resulting from a Windows Update. It appears to be OEM specific. I see Compaq mentioned alot.

That being said are you saying that you reinstalled XP & you still get the same error?

How did you reinstall? Did you restore factory settings from an OEM disk or... ???

First of all thanks for replying
I reinstalled a million times - and this last time, I didn't install the updates and it's still crashing & rebooting. It will eventually boot and get me logged in but if I try to open a program or use my modem (yes, I'm still on bloody dial up) it will reboot again and again, eventually starting up and becoming more stable. But the next day I go through the same thing. Very frustrating. I don't think know what OEM is sorry? I'm quite 'puter illiterate as you can see.

You would have an OEM (Original Equipment Manufacturer) version of XP if it was pre-installed on your computer.

You would be using an XP CD supplied by your computer manufacturer rather than one you purchased from Microsoft.

What you can or cannot do with these CD's varies so it is important to know with what type of CD you have reinstalled a million times.

If repeated reinstalls result in the same issues one would be suspicious of hardware rather than software.

Is the error always the same? c0000269 [illegal system DLL relocation] system DLL Kernel32.dll was relocated in memory.

Also: look in your Event viewer: rt. click My Computer then click Manage then Event Viewer.
Or: Administrative Tools/Event Viewer or Start/Run/ eventvwr
Open the system as well as the application tabs & look for X errors. Click error line for details.
Post back the source & event id especially of errors that seem to coincide with a crash.

Also:

What is the full make & model & # of the computer? Is it old? Did it used to work OK?

Thanks once again for your continued help!
Here are the errors in my event viewer:

11/16/2005 Source: application hang
time 7.15.45pm category (101)
type: error event id: 1002

hanging application msiexec.exe version 3.0.370.2096 module hungapp, version 0.0.0.0, hang address 0x0000000
----------------------------------------------------------------------------------------------------

there there's 7 warnings concerning WinMgmt

------------------------------------------------------------------------------------------------
In system there is one warning concerning Print
------------------------------------------------------------------------------------------------
I can't cut and paste all the info - do you need me to write them out? Are these relevant to the crashes? Let me know and I will write them out.

As for my disk it was bought when I bought the PC - as for the PC it's no brand really, a friend of mine built it for me. It used to work fine a couple of weeks back - then all this started happening. It started after I downloaded the updates, but surely when I reinstall they get removed? But the rebooting still continues. I'm starting to think it might be a hardware problem?
Thanks again!

msiexec.exe belongs to the Windows Installer Component and is used to install new programs that use Windows Installer package files (MSI).

A reinstall of XP would remove all updates: yes.

How did you reinstall? A Clean Install? Repair Install?

If repeated successful reinstalls leave you with the same problem then yes I would say hardware.

I would first off check your hard drive. Find out the brand from the Device Manager: Start/Run/ devmgmt.msc

Click the + next to Disk Drives to see the ID.

You can find the diagnostics for major brands here:

http://www.tacktech.com/display.cfm?ttid=287

Hi!
I'm back! I was SO incommunicado it's not even funny! I removedone of the two modems I had and when I reconnected everything I didn't have the driver for it nor could I find the disk I had for it. On top of that, the computer behaved even worse! I ran the hard drive diagnostic program (on the wrong hard drive, idiot that I am), managed to totally format one of my hard drives, lost everything in the process It was all a nightmare. Then when I tried the computer it simply would not stay on long enough for me to do anything! This morning I took my motherboard, ram and processor to a hardware guy and I have no idea what he did (took 3 hours), and it worked fine there, basically I think he tried everything out (power supply, ram, processor etc) and it all seemed to be working, so he cleaned the motherboard. I installed everything when I got back home (took me a while as I've never done this before) and to my dismay it rebooted again however it's working now - and seems stable enough. So far so good - will hopefully post back tomorrow (if everything is still working) and let you know what happened.

Thanks a million for all your help!

Thanks for the thanks & let us know how it goes.

Hi
No BSOD or any reboots apart from when we had a power blackout and I turned the PC on - it did it once or twice and my heart missed a beat! But it's been working fine sine this morning - I've restarted it and shut it down and it's stable. I guess the problem was dust?! When I asked the hardware guy what he had done he said lots of things, so I will never really know what the problem was - but I think it was dust on the processor.

Thanks so much for all the time & help you've given me, I felt I wasn't alone throughout this need I say terrible time! I really appreciate it!

Glad to help!

Let us know if we can help further in the future!

This thread has been Resolved and Locked to prevent other users hijacking the thread and to help others know which threads have been Resolved and which are still being worked on.

If you started this thread and the problem returns or the case has not been properly Resolved, please send a Private Message to a Moderator of this forum to have the thread opened again. If you have a different problem, please start a new thread.