Windows 10: Multiple BSOD of Various Types while Playing Ark: Survival Evolved

Hello all!
Just recently my PC has come down with a reoccurring BSOD problem that is really bumming me out...most of these crashes thusfar have occurred while I was playing a game, Ark: Survival Evolved, but the most recent error occured on the desktop. I only thought to write down the last error's name unfortunately when it happened...my PC diagnosed it as a IRQL_NOT_LESS_OR_EQUAL, but I'm pretty sure another one said it was some kind of paging error and another one was a kernel error. I only just recently bought this HDD brand-new and installed a fresh copy of Win10 on it, and it is already acting up. I have already ran a Windows 10 Defender scan, as well as a MalwareBytes scan with no results, and I ran sfc /scannow but it only could get to 88% before it couldn't continue for some reason. Any help would be greatly appreciated! Thanks to all of you in advance!

:)

 

Microsoft store-PC

Yes i would like to restore my purchase of ark survival evolved as i cannot play the game on my laptop.

 

Ark: Survival Evolved...will they be able to utilize the Play Anywhere feature?

Hi Jordan,

As you have a query on Ark: Survival Evolved game, it would be better if you contact the Ark: Survival Evolved game support regarding this matter for assistance.

Here is the link:
https://arkservers.net/support

Thank You.

 

Hi wilyweasel1,

Welcome to the BSOD forum.

Let's see what's happening with the operating system and evaluate the RAM /DIMM. There is 32 GB RAM and this will take a very long time to check. If you can be without the computer for days then it would be best to test all the RAM during one setting. If you cannot be without the computer for days then see if you can test 16GB at one time. This could take one to two hours per GB. If that is not possible then you can test 8GB at a time.

The RAM appears to all have the same speed, size and part number. Is all of the RAM the same age? Is the RAM in use single or dual channel RAM?

There are multiple problem signatures with: UE4!C:/Program Files (x86)/Steam/steamapps/common/ARK/ShooterGame/Binaries/Win64/!Game!0

Can this be uninstalled or uninstalled and reinstalled after troubleshooting?

Make sure that there is no over clocking while troubleshooting.


Sometimes there are problems in the bios that produce bsod.

The bios in your computer: BIOS Version/Date American Megatrends Inc. 2501, 6/24/2015


Please check to see if this is the most up to date version.


To ensure that there are no improper bios settings please reset the bios.


Sometimes there can be failure to boot after resetting the bios.

So please make sure your files are backed up.

Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free


And please create a restore point.




How to Clear Your Computers CMOS to Reset BIOS Settings:


How to Clear Your Computers CMOS to Reset BIOS Settings


3 Ways to Reset Your BIOS - wikiHow:


3 Ways to Reset Your BIOS - wikiHow







Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

5) Run memtest86+ version 5.01 for at least 8 runs.
This may take many hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool
When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 BSOD Tutorials

6) turn off windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials


Code: BugCheck 50, {ffffd80355291db8, 10, ffffd80355291db8, 2}Could not read faulting driver nameProbably caused by : memory_corruption[/quote] Code: BugCheck 50, {ffff858c3d4eb708, 0, fffff80172853c87, 2}Could not read faulting driver name*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: BugCheck 7F, {8, fffff800ff864e70, ffffea8183fc3720, fffff800fdbf28a7}Probably caused by : memory_corruptionFollowup: memory_corruption[/quote]
Code: BugCheck 1A, {61941, 9376000, f, ffff9f80b6ed5b00}Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/quote] Code: BugCheck A, {200000000000, 2, 0, fffff802d089a9ef}Probably caused by : memory_corruptionFollowup: memory_corruption[/quote] Code: Crash dump initialization failed![/quote] Code: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Startup Repair failed.[/quote]

 

First off thanks for the speedy reply!

I ran the requested commands in cmd and have pasted the results below:

My win10 version is Version 1703 (OS Build 15063.483)


Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>winverC:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 381184 file records processed.File verification completed. 12773 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 473334 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 46076 data files processed.CHKDSK is verifying Usn Journal... 39470784 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 976247807 KB total disk space. 498268808 KB in 311804 files. 187380 KB in 46077 indexes. 0 KB in bad sectors. 521211 KB in use by the system. 65536 KB occupied by the log file. 477270408 KB available on disk. 4096 bytes in each allocation unit. 244061951 total allocation units on disk. 119317602 allocation units available on disk.C:\WINDOWS\system32>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I will now run the memtest86 test on my ram. All four of my RAM sticks are CORSAIR Vengeance 8GB 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800), and are dual-channel based. I bought 2 of the sticks when I built the computer about 2 years ago, and the other two more recently, maybe a year ago or so. Again, thanks for the help, and I will get to work with the RAM test and the BIOS update!

 

Windows Resource Protection found corrupt files but was unable to fix someof them.
Restorehealth was able to fix the corruption.
At some time please repeat the sfc /scannow to confirm that there are no integrity violations.
Create a new Macrium image now that the corruption has been fixed.
And create a new restore point now that the corruption has been fixed.

The memory testing may take a very long time as there is 32 GB of RAM (it may take the whole weekend) It will be very useful to check the RAM together as it is dual channel. In the event that you cannot be without the computer for this duration then check 16GB at a time.

 

Once again thanks for the speedy reply sir!

I have decided to run the complete test on all 32GB of my RAM per your advice, and after only 6 hours of testing have come up with 36000 errors. At this point would it safe to assume that the bulk of my issues are stemming from RAM related issues, and not my HDD? Once the test has run its course I will run sfc /scannow immediately and create those updated images and restore points before proceeding with any hardware or software changes as well. Thanks again for the help, I am learning a lot about PC troubleshooting...too bad its on my own pc!

Link to Screenshot of Memtest86 progress using Microsoft Onedrive:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

There is no need to continue testing all 32 Gb ram at one time.
Now test two at one time.
Just 1 error is enough to determine that the RAM or DIMM is faulty.
The time is now spent differentiating good RAM from defective RAM and making sure each DIMM is good.
Since it is dual channel ram you can test two at the same time.
If an error appears then test one of the two.
If no error appears then test the next pair of RAM.
At times there are false positives and false negatives. So at least 8 passes are needed to reduce the false negatives.
Test all the RAM in the same two DIMMS.
Once you have gone 8 runs and no errors you know that the RAM and DIMM are good.
So by process of elimination you will know good versus defective RAM.
Once the defective RAM is identified it will be removed from the system and you will then check for system stability with typical computer use.

 

So an interesting developement...

All 4 of my RAM sticks check out fine with 0 errors...however when I put any two of them in the 2 DIMM slots closest to my CPU my computer gets stuck in a power on/power off loop. That is, whenever I hit the power on to my MOBO it doesn't even POST, but starts turning on and off until I pull the plug. Would this most likely be physical hardware damage to the DIMM slots themselves? I suppose its good news that I know I can run off of 16GB on my good slots, but if there is something that could be done to repair the other two DIMMs (other than buying a new MOBO that is!) I would like to try. Thanks again for the help, it definitely is narrowing the problem down!

 

There were 36000 errors reported testing all 4 RAM (32 GB). And there were 0 errors checking the same 4 RAM (32GB)? How did you check the 32 GB twice in such short time?

 

Hmm I'm not sure, it seemed the memtest only took 2-3 hours when I just used two sticks together. I put in two sticks at a time on the two bottom DIMMS and ran the mem test 10 times using the default test settings...both tests came up with zero errors after completion and prompted me to end the test with the ESC key. However when I put either pair of RAM sticks in the other two DIMMs my PC won't even turn on at all. Instead it just keeps turning on and off repeatedly until I pull out the plug. Also worthy of note I ran sfc /scannow once again and this time it verified 100% with zero integrity errors, as opposed to the partial success I had previously. Very strange!

 

When you perform any Memtest86+ testing please make an image and post into the thread.
The current results are confusing.
Please test only 8GB of RAM in one DIMM. Continue to use the same DIMM for all RAM.
Please post an image for each of the RAM with 8 passes or more.
Depending on the results we will move to other DIMM slots.