Three times my computer has completely crashed opening DayZ experimental recently. I get a blue screen indicating there was some kind of memory malfunction and the system resets. My system is healthy. This only happens when I launch DayZ and it happens immediately upon double clicking the icon in Steam. I had recently reinstalled DayZ before my recent crash in an attempt to fix it. It didn't work.
Description
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Sometimes
- Operating System
- Windows 7
- Category
- General
I don't know how to reproduce this. Sometimes when I open DayZ experimental I experience complete memory failure.
specs:
windows 7
gtx 970
i5-4690K
16 gigs ddr 3
The crash dump log has no record of these crashes.
Event Timeline
This has happened to me now as well, twice, come s up with a blue screen stop code which states "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED'
I have Windows 10, I7 8th Gen, 16gb Corsair and 11gb 1080Ti. playing through Steam
Hope they can find a fix for this
Hello Solopopo and thank you for the report.
Is there some kind of error message when the blue screen appears (such as mentioned by hubba747: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)? And if so, can you please write it down and post it in here?
Regards,
Geez
Same here with the entire system crash and blue screen of death (windows 10 equivalent screen). Also DayZ looks like its uninstalled from Steam but the files are still present in the steamapps folder. You need to redownload again
I'll update with messages from BSOD next time
Couldn't make out any error message. I get a generic blue screen memory crash. It's only up for a few seconds. I will try to take a picture next time it happens.
I think I managed to find the dump file for the crash. This is what windows has to say about the error. I found this in windows event viewer. I hope this is the right error message. I'll know for sure when it crashes again.
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
DayZ was also removed from Steam for me after my third crash. This has happened to at least two people on Reddit too. I've been able to confirm at least a dozen other people are experiencing general system crashes on Windows 7 and 10 systems.
System_thread_exceptiom_not_handled photo
Here is an image of the error. Happened twice now on each initial PC boot
DayZ was also removed from Steam for me after my third crash. This has happened to at least two people on Reddit too. I've been able to confirm at least a dozen other people are experiencing general system crashes on Windows 7 and 10 systems.
when you start a game steam is writing in some files, the BSOD is corrupting those. thats why you see "install" instead of "play". however the game is still there an can be started manually, steam works ingame and shows you are playing dayz.
I think I managed to find the dump file for the crash. This is what windows has to say about the error. I found this in windows event viewer. I hope this is the right error message. I'll know for sure when it crashes again.
you can analyze your dump file with http://www.resplendence.com/whocrashed which gives quite clear indication on what happend. i'm suspecting whe have the same issue, related to bedaisy.sys, which is part of battle eye.
I hope this is useful. I recently crashed but was not able to catch the code in time. I ran whocrashed, following pe3pa's advice, and these are the results.
I think this is the error code that displayed during the bsod. I made out x00000007. This resembles the error code whocrashed finds, but i'm not completely certain its the same.
BugCheck code: 0x1000007e
Parameter 1: 0xFFFFFFFFC0000005
Parameter 2: 0xFFFFF80003908b6a
Parameter 3: 0xFFFFF880031f5788
Parameter 4: 0xFFFFF880031f4ff0
probably caused by: ntoskrnl.exe
In addition to this error, there is a second which is the same error pe3pa was talking about.
BugCheck: 0x7e
Parameter 1:0xFFFFFFFFC0000005
Paremter 2: 0xFFFFF80003908b6a
Paremter 3: 0xFFFFF880031F5788
Parameter 4: 0xFFFFF880031f4ff0
probably caused by bedaisy.sys
Hello everyone.
BattlEye has confirmed that their client is source of the issue and a fix has been released for the 0.62 stable and 0.63 experimental versions just now. Please let us know in case you experience this issue still even after these updates.
Regards,
Geez