HDR freezes my computer

G

gtobias

Guest
In both DOD:S and LC, whenever I have HDR (including bloom) on, my computer freezes. The game completely locks up with looping sound and I have to restart my computer. I can play for several hours without HDR with no lockup, but with HDR, I freeze after about 10 minutes. I updated my drivers too. Why is this happening.

Specs:
ATI Radeon 9700 Pro
3.06 GHZ P4
1 GB ram
 
I got the same problem, even in normal HL2 with HDR off, since the infamous update. It seems to go away in HL2 if I increase the heapsize, in LC with standard heapsize it locks after 5 seconds, with increased heapsize after about a minute. This leads me to believe there's something strange going on with the memory system in the game.
 
its most probable ur GFX card, its so old#, & isn't capable of rendering HDR
 
The 9800 Pro is an alright card, cheap, and capable of HDR. I'd recommend that if you're a little strapped for cash.
 
Happens to me too...my card should not have any issues, should it? I have enough RAM and processing power too...I think it's a driver issue, but I can't figure out how to fix. All my drivers are current.

Any ideas now?
 
Sickmind said:
Happens to me too...my card should not have any issues, should it? I have enough RAM and processing power too...I think it's a driver issue, but I can't figure out how to fix. All my drivers are current.

Any ideas now?
Hmm... Well then it might be caused by IRQ conflicts or hardware conflicts. :/
If you've got two sticks of RAM, try booting the computer only with one and see if it still occurs. If it does, do the same with the other stick. If it still occurs, it's probably a motherboard issue or a hardware conflict.
 
I have the same problem. If you look up at steampowered.com, it says it might relate to soundcards. But that's not true for me atleast, I tried with -nosound and still get the freeze.
Also... I once managed to get the crash with HL2 singleplayer ofcourse without HDR, when I was using 16x AF. I think it has something to do with lots of strain on the gfx card, and Source cant handle it. I dont get this kind of crash in any other game, and BF2 and FEAR certainly can create alot of stress to the gfx card.
My specs: a64 3000+, 9600xt, 1024mb ram, SB Audigy 2 ZS. No overclocking.

EDIT: Also, I too didnt get this before Lost Coast. Update ****ed things up.
EDIT: Has someone emailed Valve about this so we could know if this is a known bug?
 
Beerdude26 said:
Try taking it out and playing it without.
I already tried playing with -nosound. That should have the same effect.
However, I have still tried moving the Soundblaster to another PCI Slot, because according to Steampowered, it should be on slot 1 or 2 to work perfectly. I moved it as close to the gfx card as it can get, and according to Windows, it is on slot 3. But according to my mobo manual, it should be on slot 2. So meh...
And anyway, if it would be a hardware related problem, why dont I have any problems with other games?

Other things I have so far tried: Removing onboard sound chip drivers, disabling onboard sound chip from BIOS, disabling DirectSound accelration from dxdiag, and finally updating my SoundBlaster drivers. No help whatsoever.
 
Go to Start>Run, type msinfo32 and click OK.
Under the Device resources (or whatever it is called in your Windows), look at the sharing/conflicts and IRQ list. Either take a screenshot of each list or type them out here.
 
gtobias said:
In both DOD:S and LC, whenever I have HDR (including bloom) on, my computer freezes. The game completely locks up with looping sound and I have to restart my computer. I can play for several hours without HDR with no lockup, but with HDR, I freeze after about 10 minutes. I updated my drivers too. Why is this happening.

Specs:
ATI Radeon 9700 Pro
3.06 GHZ P4
1 GB ram

...um...dont use HDR? :p
 
Llama said:
...um...dont use HDR? :p
Ofcourse! Why didnt we think of that!
Sheesh.

Anyway, here's the screenshots. Looks all OK to me?
my.php

my.php

Yes, they are in finnish.
 
Cukel said:
I already tried playing with -nosound. That should have the same effect.
However, I have still tried moving the Soundblaster to another PCI Slot, because according to Steampowered, it should be on slot 1 or 2 to work perfectly. I moved it as close to the gfx card as it can get, and according to Windows, it is on slot 3. But according to my mobo manual, it should be on slot 2. So meh...
And anyway, if it would be a hardware related problem, why dont I have any problems with other games?
Lol no it doesn't; just try taking it out.
And if it should be on slot 2, it should be on slot 2

You might have a perfect reason why your game doesn't work, but you're too lazy :p
 
Tried it, took it out. No banana. Exact same crash, with every little detail.
And about the slot thing. Now, the motherboard layout I have says that the first pci slot under the agp slot is PCI slot 1. Under that is PCI slot 2. That's where my card is now. But Windows, on the other hand, says it's on PCI Slot 3. So I dont know what's going on, and it doesnt really matter, because it doesnt have anything to do with the Soundblaster.
 
Cukel said:
Tried it, took it out. No banana. Exact same crash, with every little detail.
And about the slot thing. Now, the motherboard layout I have says that the first pci slot under the agp slot is PCI slot 1. Under that is PCI slot 2. That's where my card is now. But Windows, on the other hand, says it's on PCI Slot 3. So I dont know what's going on, and it doesnt really matter, because it doesnt have anything to do with the Soundblaster.
Ok. I just gave that advice because I've heard stories about Audigy's completely crapping out on HL2 and taking the game with it.

Have you checked for IRQ conflicts? (Google it, forgot the exact way how to do it)
 
I posted the screenshots of msinfo32 a few posts ago... about IRQ and conflicts. I myself cant understand a word of it.
 
Cukel said:
Ofcourse! Why didnt we think of that!
Sheesh.

Anyway, here's the screenshots. Looks all OK to me?
my.php

my.php

Yes, they are in finnish.

Näyttää siltä videokorttisi ja IEEE 1394 (Firewire)-portti jakavat samat resurssit.
Jos et käytä Firewireä mihinkään, kehoittaisin poistaa se käytöstä Oman tietokoneen ominaisuuksien kautta Laitehallinnasta, IEEE 1394 -väylän isäntäohjaimien kohdalta. Lopuksi käynnistä kone uudestaan.

It looks like the video card and the IEEE 1394 (Firewire) port are sharing the same resources.
If you are not using Firewire, you should disable it from My Computer's Device Manager under the IEEE 1394 Host Controllers category. Restart.
 
CommandoSR, I did what you said, and it didnt work. I didnt see any hint of IEEE 1394 relating to FireWire though, it said it was the graphics card port or something. No mention of Firewire or 1334 anywhere else in Device Manager, either.
 
Ok, I googled for IRQ shit, couldnt find anything actually useful. So I improvised - I went into BIOS and tweaked all sorts of kinky shite. I disabled SATA, because I dont use it, seemed to clear up the IRQ list. Also updated Catalysts to 5.10.
Shot from msinfo32 included:
my.php


Result: No help, same crash. (Everything else still works fine despite of my BIOS tweaking.)

Maybe I should just give up and give my computer the good old hammertime.
 
Back
Top