Flickering Screen

[SomebodySomeone]

I get an issue when playing PR, the screen goes nuts and starts to flicker. I have to quit the game every time. In the event viewer I get an error saying:

"Unknown error on CMDre 00000001 000000c0 40011e8c 00000004 00000084"

The issue is very random, sometimes it happens after I've played 2-3 maps, other times on the first map, usually when I get wounded. And it only happens on PR, never happened on BF2 or any other game.
Tried re-installing PR, no luck so far

System specs:
Processor:
Intel(R) Pentium(R) 4 CPU 3.00GHz (2 CPUs)
Memory:
2048MB RAM
Video Card:
NVIDIA GeForce 8800 GT
Monitor:
SyncMaster P2270/P2270G,SyncMaster Magic P2270G(Analog)
Sound Card:
Realtek AC97 Audio
Operating System:
Windows XP Home Edition (5.1, Build 2600) Service Pack 3, v.5857 (2600.xpsp_sp3_gdr.090804-1435)

[SomebodySomeone]

Anyone?

[Sgt. Mahi]

I've had the same problem since 0.9 and I haven't been able to figure out what is causing it. I don't think anyone have found a solution yet and you can't take screenshot or record the flickering for some reason. I suspected it had something to do with how many Hz you are running the game in against how many Hz your screen runs but nothing I've tried has been sucessful.

Only good news I can give you: You don't have to quit the game, you can just ALT-TAB out and back in. It will make the flickering disapear.

I don't know if they made a tweak to the suppression effect in 0.9 but it does seems to be related to it. From my experience it happens sometimes when: suppressed, shot>starts to bleed, Jdams in sight.

[SomebodySomeone]

"I don't know if they made a tweak to the suppression effect in 0.9 but it does seems to be related to it. From my experience it happens sometimes when: suppressed, shot>starts to bleed, Jdams in sight."


Exactly, this happens only when I get suppressed or get wounded (Meaning when the screen goes blurry). And on some maps only, particularly Gaza Beach.

[bad_nade]

I haven't found anything solid for this yet, but so far the most promising findings point to PSU being faulty or underpowered, system temperature being too high or a faulty memory module.

[SomebodySomeone]

I haven't found anything solid for this yet, but so far the most promising findings point to PSU being faulty or underpowered, system temperature being too high or a faulty memory module.

But it happens only on PR :/

[bad_nade]

But it happens only on PR :/

PR is quite demanding. So if you don't play other games that require as much RAM or GPU power, you might never run into problems like these.

[Sgt. Mahi]

PR is quite demanding. So if you don't play other games that require as much RAM or GPU power, you might never run into problems like these.

I'm not buying it. It only started to happen since 0.9 and you can temporarily fix it with an ALT-TAB out. That doesn't sound like a perfomance issue to me.

[Nagard]

Firing the discussion up again:

I get those problems after being supressed or wounded, too.

Started to happen with 0.9.

I guess no one's found a solution yet?

Edit: .95 is released and the problem persists.

[Sgt. Mahi]

Yep I also still have it...

[thepalerider]

You guys running the game @ the same res. as your desktops?
Try turning AA off or at least down?

[Sgt. Mahi]

UPDATE: Nvidia have released a new driver in this month that actually solved my problem and have also given me a slightly better perfomance in PR...

So if you have a Nvidia 8xxx graphic card and the flickering screen problem try out the new driver 260.89. Remember to uninstall old drivers before installing the new one.

I have a Nvidia 8600gt graphic card and it solved my problem.. YAY!!!

[Nagard]

You guys running the game @ the same res. as your desktops?
Try turning AA off or at least down?

Yes aaaand yes... But I will try wether those new drivers will work. (Eventhough I have a 9xxx card but I guess/hope that shouldn't matter that much)

[Sgt. Mahi]

Yes aaaand yes... But I will try wether those new drivers will work. (Eventhough I have a 9xxx card but I guess/hope that shouldn't matter that much)

Please report back so we can confirm it's a driver issue