BSOD! [SOLVED]

[franksidebottom 0]

starting yesterday whenever i load into a server and press a key my pc crashes and restarts! has anyone else had this problem?

if i roll back my arma patch on commander i can get into a server and play, then if i update to latest i can get into my normal server, i have updated all drivers,

and everything i can think of to fix this, i have come to the conclusion that its a patch problem

im on windows 8 64 pro

anyone else getting this or know how to fix it?

[AmberHelios 2071]

Your saying your getting a BSOD what does it say on it if it dont stay up long enough you can disable automatic restart on system failure by pressing f8 and selecting the option when windows loads

[LangeName 1]

I'm experiencing the same r similar problem.

Been using Arma 2: 103419 since it came out and haven't experienced any problems with it.

Now when I join a server, my character loads fine, I can look around but the second I hit a key, BSOD.

Checked the dump files.

It's always telling me: Critical_process_died with a apparently random .sys file.and ntoskrnl.exe.

nvlddmkm.sys / beep.sys / tm.sys / vwififit.sys / cdrom.sys

Reverting back to 102591 and all seems well.

This seems strange since 103419 has worked for some time now.

No problems when running memtest86.

Also ran the system file checker and it didn't detect any errors.

I'll run some more tests and post the results.

[daethan 0]

I am having the same problem. After reimaging my computer and checking all the logs I tracked the issue back to the battleye 1.196 update. Notice this will only occurs on servers that use battleye and only after battleye loads. here is an email I sent to battleye detailing the issue. I recommend writing battleye devs and informing them so they hurry the fix out the door.

Hi,

I'm sorry for these issues. The problem has been identified and a fix will be released shortly.

Regards,

Bastian Suter

On 12.05.2013 11:02,

I have run into a major problem with battleye 1.196. On my windows 8 pro platform with the Logitech k800 keyboard and asus p8z77-v deluxe mb battleeye will freeze the c: drive (intel 520 180gb ssd) causing an instant blue screen. I can confirm that 1.195 did not do this and it does not occur when battleye is not running. No other program or test reveals any problem other than battleye 1.196. The freeze is repeatable and tied to any key press on the keyboard from the moment battle eye is loaded. I have gone so far as to restore a complete system image from a time several days ago when there were no issues and as soon as battle eye updates it happens again. Please alert your development team that whatever changes made between 1.195 and 1.196 are total show stoppers and should be addressed. Some other info that may be of use is that I use a uefi boot on a guid partition with secure boot enabled.(though I have tried disabling secure boot to no effect. I would share the windows logs but as the c drive is frozen no log is written to provide any clue. I get the win 8 bsod and instead of writing a crash report the system will reboot because the c: drive is frozen. Thank you for addressing the issue and I await your reply as there are several concerned players in the forums asking about this issue.

Edited May 13, 2013 by daethan

[LangeName 1]

Daethan,

I think you are spot on.

After running some other harware tests (same motherboard btw) I can only conclude it's not the harware itself.

Started thinking it might be the LGS for my g19 & g13, however reverting to an older version did not solve the issue.

The only other change was indeed an BE update.

[daethan 0]

If you are having the issue be sure to write to battleye here [email protected] detailing the issue and hardware/os involved as well as mentioning battleye 1.196

Edited May 13, 2013 by daethan

[LangeName 1]

Just got confirmation that a fix will be released within the next few hours.

[daethan 0]

I just tried 1.197 and it still causes the bsod issue. can you post their reply to your email?

[daethan 0]

v1.197 didn't address this issue. The actual fix will be released within the next few hours.

Edited May 13, 2013 by daethan

[LangeName 1]

1.198 is now out!

[LangeName 1]

I can confirm that 1.198 fixed my problems.