Author Topic: lock ups? (Read 213 times)

killnu · « **on:** March 10, 2006, 08:09:57 PM »

ok, system ....
amd64x2
2 gig ram
gf6600 256 pci express
Windows XP media edition

ive read the sticky, checked my boot.ini file in msconfig, it doesnt have that extra bit that needs deleted like overlag had stated, but...
i still get the lock up that i have to reboot puter to get out of, cant even get back to desktop. and its random. i can fly for 20 minutes and get it, or 2 hours then get it. seems to happen most when i got to tower out after flight. dont recall it happening in flight yet. happened just as i was shot down and suppose to go to tower, as i pressed .ef enter. happened one other time with me sitting in tower looking around.

any other ideas other than the boot.ini thing?
and preferably not having to shut down a processor?

killnu · « **Reply #1 on:** March 11, 2006, 11:35:57 AM »

help?

Kev367th · « **Reply #2 on:** March 11, 2006, 04:42:41 PM »

Try this, it's a registry fix from nVidia that disables the dual core support in their drivers.

1. Go into Regedit and determine the current primary display card by looking in HKey_Local_Machine\Hardware/DeviceMap\Video and note the GUID (global unique indentifier assigned by Windows) for the entry "\device\video0" which is the long string at the end of the entry in brackets { }.

2. Edit HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\Video\{guid}\0000, where {guid} is the number derived from the above step.

3. Open the "0000" directory and enter a new key called OGL_ThreadControl and give it a value of 2. This will disable multithreading in the driver for all OGL apps.

4. In the same "0000" directory, to disable driver multithreading for all D3D apps, you can enter WTD_EXECMODEL and give a value of 0.

Both are DWORDS.

This doesn't disable any core, just dual core support in the dirvers.

SAVE YOUR REGISTRY FIRST!!!!!

killnu · « **Reply #3 on:** March 12, 2006, 03:36:48 PM »

that didnt work.

Brooke · « **Reply #4 on:** March 12, 2006, 04:04:00 PM »

Skuzzy has posted how to disable one of the cores of AMD dual-core processors, which fixes lock ups that happen supposedly as a result of incompatibility between AMD dual-core processors and Windows XP.

Use the BB search functionality for author "Skuzzy" and terms like "windows" and "disable". You'll find it.

Note: There is no problem with Intel dual-core processors, Windows XP, and Aces High, which all work fine together. Some folks mistakenly post that the problem is with all dual-core processors, but this is not the case.

killnu · « **Reply #5 on:** March 12, 2006, 04:18:15 PM »

oh, i can disable it, once in the game. my problem now is getting into the game.
Only way i can get in, is to restart the computer, while everything is still loadingn up, start AH, get in the game, then can go back to windows to disable the processor.

if i log and want back in, i have to restart the computer and get in while everything else loads up, otherwise, the clipboard comes up to go online/offline/etc, then the screen darkens a bit and a page on the clipboard does this helicopter thing and spins. now, i can still log into game, but if i do, it locks up instantly before it loads fully. only way out once it locks up is to reboot the computer. cant even get to windows.

quite a pain in the posterior.

Brooke · « **Reply #6 on:** March 12, 2006, 05:39:23 PM »

Quote

Originally posted by killnu
oh, i can disable it, once in the game.

You disable one of the cores in your bios, totally outside of the game and everything else. What you are doing is not what I was talking about.

killnu · « **Reply #7 on:** March 12, 2006, 06:20:07 PM »

why would i disable one of the cores for, so its disabled all the time? just for AH? dont think so.

Ill stick with running AH off one core.
regardless, its still a pain in butt. by a better system to have it not work on a game just suks.

Brooke · « **Reply #8 on:** March 12, 2006, 07:11:18 PM »

Quote

Originally posted by killnu
why would i disable one of the cores for, so its disabled all the time? just for AH? dont think so.

Ill stick with running AH off one core.
regardless, its still a pain in butt. by a better system to have it not work on a game just suks.

You asked how to solve your problem. This is the way to solve it.

If you don't want to do it this way, then you can put up with the lock ups until (1) there is a patch for Windows XP that solves the problem or (2) you switch to Windows 2000, which supposedly doesn't have the incompatibility.

As for disabling one core, unless you have programs that are multithreaded (and most these days are not yet multithreaded), you won't notice much difference. In fact, you might not notice any difference at all.

It might be worth a try on your part to see. You can always re-enable the other core if you don't like doing it this way. Otherwise, you might find it works just fine this way until Microsoft or AMD issues a Windows XP patch to fix the problem.