Search the Community
Showing results for tags 'bsod'.
Found 2 results
Hi, So I've been getting a Machine Check Exception While play Arma 3. I already posted the results of my troubleshooting on Steam but support there is scarce. So after a few minutes of playing the game crashes with a blue screen. I've updated every driver for my system. Other games like Battlefield V and Total War Warhammer 2 run on ultra with no problems. Does anybody have any clue of what it might be? The game is unplayable and most of the hours I've spent in game was doing troubleshooting. I've also run 3DMark benchmarks and everything is fine. My machine: - MB: Asus Prime Z390M-Plus - CPU: i5-9600K - GPU: MSI RTX2070 ARMOR 8G - RAM: 16GB - OS: Windows 10 Pro 64-bit Things I've already tried: - Making sure all the drivers are up to date (everything is up to date) - Reinstallling GPU drivers (didn't solve) - Check CPU temperatures (not an issue) - Check for CPU Bottleneck (not an issue) - Run Steam file check (found no problem) - Reinstalling the game (nope) - Running RAM on it's lowest speed (didn't solve) - Running the game on Windows 7 compatibility (didn't solve) - Reset Windows 10 (didn't solve) Checked the minidump created with the blue screen. It's something related to intelppm.sys file. No other program, or game is creating this problem. Do you guys have any more recommendations? It's been tiresome.
There is a known issue with the insider builds that are causing BSOD errors across all games that have anti-cheat systems installed. It has been noted on the Flight Hub that fixes are being rolled out. I am still having issues being unable to play the game with Battleye running. I don't know if this has been reported to you or not. Im thinking this is the error that it is spitting out. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8055e860333, The address that the exception occurred at Arg3: ffff870cb514f7e8, Exception Record Address Arg4: ffff870cb514f030, Context Record Address Looks to be coming from BEDaisy.sys if im reading the crash dump correctly. https://blogs.windows.com/windowsexperience/2019/04/10/announcing-windows-10-insider-preview-build-18875/#urRQqJMPrtfb7Ayb.97