Black Screen Sound Loop crash.

[Jaegermeister]

It doesn't happen all the time but it happens mostly with Ostfront. I think its something driver related because it happens in other games but not nearly as much as ostfront. Happened in IL-2 Stumovik once. I'm just trying to find out whats going on in the log and if anyone may have a fix for it. It usually happens on a sound like somebody firing and right when the firing happens my screen goes black and I lose the monitor signal. Then I get a sound loop where the loop is approximately 1 min long or so. Here's the Log from RO.


Log: Collecting garbage
Log: Purging garbage
Log: Garbage: objects: 57191->57190; refs: 835483
Log: ROPlayer setplayer WindowsViewport
Log: Precaching: RO-Barashka.LevelInfo0
Log: Static mesh batches: 37137228 vertex bytes, 3145122 index bytes
Log: Allocating 16384 byte dynamic index buffer.
Log: Allocating 229692 byte dynamic index buffer.
Log: Allocating 236784 byte dynamic index buffer.
Log: Allocating 281700 byte dynamic index buffer.
Log: Allocating 65536 byte dynamic vertex buffer.
Log: Allocating 70448 byte dynamic vertex buffer.
Log: Allocating 102424 byte dynamic vertex buffer.
Log: Allocating 102620 byte dynamic vertex buffer.
Log: Finished precaching geometry in 3.021 seconds
Log: Finished precaching textures in 6.841 seconds
Log: Allocating 103656 byte dynamic vertex buffer.
Log: Allocating 103768 byte dynamic vertex buffer.
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:00AE) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:01D8) Accessed None 'PlayerReplicationInfo'
Log: Allocating 103936 byte dynamic vertex buffer.
Log: Allocating 104160 byte dynamic vertex buffer.
Log: Allocating 105448 byte dynamic vertex buffer.
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:00AE) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:01D8) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:00AE) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:01D8) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:00AE) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:01D8) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:00AE) Accessed None 'PlayerReplicationInfo'
Warning: ROSPECIES_Human None (Function ROEngine.ROSPECIES_Human.Setup:01D8) Accessed None 'PlayerReplicationInfo'
Warning: MG34ClientTracer RO-Barashka.MG34ClientTracer (Function ROGame.ROClientTracer.ProcessTouch:014D) Accessed None 'Instigator'
Warning: MG34Client

 

[kAMIKAZE]

To Jaegermeister:

What you are experiencing is a classic case called Machine Check Exception.

It's either a video card driver problem/bug or a hardware problem.

But first do this first (see below):

1. Log on to Windows with administrative privileges.
2. Click Start->Control Panel->System.
3. In System Properties window, click the Advanced tab.
4. In Startup and Recovery section, click Settings.
5. In Startup and Recovery window, click Edit.
6. In Boot.ini, add the /NoExecute=AlwaysOff option.

Example Boot.ini:

[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Professional" /fastdetect /NoExecute=AlwaysOff


If after doing the above, you still get the error. Make sure your CPU, GPU and Northbridge chipset have normal temps. Their fans are working okay. The heatsinks and fans are free from dust. While your at it check your power supply voltages if they are normal. Memtest your RAM too.

Last, try to lower the game's video resolution down one notch. See if that will help.

 

[Jaegermeister]

Interesting, I've already checked fans, temps, voltages, etc. It seems to happen more when I OC the vidcard. What maybe the downsides of doing this with the boot.ini? Its happened at 1280x1024 and higher. Thanks for your input on this. I'll try and see what happens.

 

[kAMIKAZE]

To Jaegermeister:

You said the magic word OC, I forgot about that. The Unreal engine is sensitive to OC. So you should not OC your video card.

Regarding the No Execute, please see this link http://www.techweb.com/wire/security/166403451. When you turn on No Execute, Windows will also turn on Physical Address Extension. The problem is some games have a problem running with Physical Address Extension turned on.

 

[Jaegermeister]

hmm even more weird, card is 7800 GS OC so stock overclocked, but i'll try that with the no execute thanks kamikaze

 

[kAMIKAZE]

To Jaegermeister:

If your video card is overclocked direct from the manufacturer. You have nothing to worry about.

If turning No Execute off does not solve the problem then it could be a video card driver problem.

If you are already using the latest video driver then you have no option but to hope that it gets fixed on the next video driver release.