Seemingly Random Blue Screens

[Udderfly 0]

DayZ has blue screened almost without fail for the past three weeks or so, allowing for 1-120 minutes in the game before the inevitable memory dump. This is not a hardware issue, as I can play other demanding games without worrying about having a blue screen. Everything has been updated to the latest version (DayZ 1.7.6.1, Battleye 1.201, ArmA 2 Beta patch 104648), and so it doesn't seem to be a version problem. I have even updated things like Microsoft .NET framework and checked for bad files. ArmA 2 Operation Arrowhead runs fine without any problems. Sometimes, when using Six Launcher, DayZ Commander, or Play withSIX, I would blue screen upon start up or part-way through the execution of the server fetching in the program. I have not had this problem while using ArmA II Launcher or when running through Steam. I think the blue screening might have something to do with Battleye, as upon blue screening, instead of the server message saying something like 'Player XXXX XXXX has left the game', it would say, after some time, 'Player XXXX XXXX has been disconnected by Battleye: Client not responding'. The blue screen is always sudden and is not preceded by a common event. The game screen will freeze, as well as the sound, transmitting the last sound and image for about 0.5-2 seconds, followed by a rapid blue screen readout and the memory dump message. After the memory dump is complete, the hard drive shuts off.

Any insight or suggestions would be welcome.

System Specifications:

ASUS CG5290

MS Windows Vista Home Premium 64-bit SP2

Intel Core i7 920 @ 2.67GHz

9.00GB RAM

NVIDIA GeForce GTX 260

[Rage VG 4033]

Deleted text

Hilarious.

@OP, use the program "BlueScreenView" to read your minidump files in order to get a bit more information for us to go on.

Edited May 28, 2013 by Inception.

[Udderfly 0]

Here are the mini dump details from BlueScreenView.

Mini052713-01.dmp 5/27/2013 7:45:47 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa60`104b8000 00000000`00000000 fffff800`03ce6e2e 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+57150 x64 ntoskrnl.exe+57150 C:\Windows\Minidump\Mini052713-01.dmp 6 15 6002 292,080

Mini052613-03.dmp 5/26/2013 11:03:04 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa60`09db4000 00000000`00000000 fffff800`03cede2e 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+57150 x64 ntoskrnl.exe+57150 C:\Windows\Minidump\Mini052613-03.dmp 6 15 6002 292,024

Mini052613-02.dmp 5/26/2013 10:05:12 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa60`0b3a7000 00000000`00000000 fffff800`03d28e2e 00000000`00000000 hal.dll hal.dll+e750 x64 ntoskrnl.exe+57150 C:\Windows\Minidump\Mini052613-02.dmp 6 15 6002 292,040

Mini052613-01.dmp 5/26/2013 9:42:54 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa60`0a04d000 00000000`00000000 fffff800`03cede2e 00000000`00000000 atapi.sys atapi.sys+1996 x64 ntoskrnl.exe+57150 C:\Windows\Minidump\Mini052613-01.dmp 6 15 6002 262,144

I hope that these details can help you.

Edit: bad sentence

Edited May 28, 2013 by Udderfly

[dublea 11]

PAGE_FAULT_IN_NONPAGED_AREA is pretty generic. You either have malware or faulty hardware. Check your ram, video ram, HDD, and scan for malware.

[Udderfly 0]

I did a quick scan with avast! Free Antivirus and it didn't discover any infected files. I will be running a complete scan to see if there's anything the quick scan missed, but new suggestions would be welcome.

[gambla 118]

I did a quick scan with avast! Free Antivirus and it didn't discover any infected files. I will be running a complete scan to see if there's anything the quick scan missed, but new suggestions would be welcome.

Had the same prob a while ago. Nothing i've done helped until a system restore to a previous date. It can be the needle in thehay stack.

[Udderfly 0]

I have just completed the complete avast! scan and have turned up no infected files. I feel as though it would just be better to wait until tomorrow for the new information regarding DayZ comes out and then develop a course of action.

[Udderfly 0]

I found the issue. I didn't install the ArmA 2 Beta patch correctly. I forgot to unzip the files to a new location before running the installer. The blue screening was caused by unresolved errors that the beta patch fixes.