Weird Unreal Tournament 2004 issue

[neecap]

When im playing UT 2004, all is fine. Not a single problem. But its when i quit UT 2004 (from the menu like its supposed to) My machine gets a bluescreen saying:
IRQL_ NOT_LESS_OR _EQUAL
And i have to reboot.
Its really irritating and i am clueless to what the cause are.

My machine specs are:
AMD athlon 64 processor 3500+¨
1024 RAM
Windovs xp proffesional (5.1, build 2600)

[neecap]

i managed to get a glimpse of the ut2004 error message before the machine went RS, it said something about "unknown processor"

[neecap]

hallo?

[neecap]

Ive managed to copy the error message before my machine restarted....:

UT2004 Build UT2004_Build_[2004-11-11_10.48]

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD Unknown processor @ 2213 MHz with 1023MB RAM
Video: NVIDIA GeForce4 Ti 4200 (6693)

General protection fault!

History: CheckTag <- LoadSummary <- ULinkerLoad::ULinkerLoad <- UGameEngine::Init <- InitEngine <- FMallocWindows::Free <- FMallocWindows::Free

What does this mean?

[neecap]

Thanks to ZERO/NADA/NIET/NO support from this forum and ATARI i had to solve the issue my self.

To anyone it may concern, Behold the solution to the UT2004 issue described above:

after much back and forth, and some wild google action, i managed to turn of the read only attributes to boot.ini and turn of DEP.
If anyone else wonders about how, or have my UT2004 issue, heres the solution in its fullest:
(always remeber to take backups, im not responisble for screw ups of any kind.. :P)

Ive found out that DEP (Data execution prevention) was the reason to the UT2004 issue.


To remove the DEP feature:

Description
No-execute and execute protection are all names for DEP. This process feature increases security, but may cause problems with certain programs.


Directions
Several OSs have no-execute or execute protection. Microsoft has added this as well in SP2 with data execution prevention (DEP). This precents code execution in memory regions already marked as storage. This is a powerful tool against buffer overrun exploits.

1. Press Start > Run
2. Type Boot.ini
3. Now a notepad should appear. Make a backup off it. Dont call the backup boot.ini EX booty.ini
4. Under "[operating systems]" find "/execute=optin"
5. Change "/execute=optin" To "/execute=AlwaysOff"
6. Save it. (cant save it? Check the steps below to disable the read only attribute for boot.ini)
7. Restart pc

To remove the read only attribute from the boot.ini file:
1. Press start > Run
2. Type cmd.exe
3. in the windov that pops up, type the following command dir c:\boot.ini /ah (ah stands for attribute hidden and if nothing happens use a another directory)
4. Ignore the notepad windov that pops up, and write in the black windov:
attrib c:\boot.ini -s -h -r
5. Follow the steps above to modify your DEP
6. To make the boot.ini hidden and read only again: type attrib c:\boot.ini +s +h +r in the black windov.