Windows 10: BSOD while playing Arma 3

Hello there,

I just got my RAM fixed and I started playing some games. However, I recently received several BSOD's from playing games like Arma 3 or Wargame. I updated my drivers and such but no hope so far for me. I would really appreciate it if somebody could solve my problem thanks.

Yours Faithfully

Hel

:)

 

Crashes and blue screens

Ok I uninstalled eset and turned on windows defender and my firewall.... do you think that caused the issue? I can provide you more details of the problem if you wish. It happens while playing a video game called arma 3 usually in almost all cases.

 

Bad_module_info has stopped working [bug for steam games]

I too have had this issue a lot.

But what I have found is it has something to do with
BattlEye Anti-Cheat and something in Win 10 FCU.

I tested this with a ARMA 3 Dedicated Server with BattleEye disabled, as well as on the ARMA 3 client, and I stopped getting "Bad_module_info" errors.

But this is not practical solution, as it will prevent anyone playing on servers with BattlEye running.

 

You abandoned your previous thread right after @philc43 asked you to uninstall Kaspersky. I see it's still installed now. Did you try uninstalling it and running with Windows Defender as suggested?

As for your dumps, the two newer 5/14 and 5/20 dumps don't have any useful information I can see. The older dump from 5/6 indicates a problem with your Nvidia driver: .
Code: BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+fbc48 )[/quote] You have the latest Nvidia driver available. You could try uninstalling and reinstalling it as follows:

Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.

 

I just updated my graphics driver to the latest driver. However, to answer to your question the Kaspersky problem has been solved by a technicians and the support from the Kaspersky Company. So in turn I will mark the other thread as "solved". Many thanks for the help, I really appreciate it.

 

Hello there

It's been a while now but, I still receive BSOD's such as from today a "PFN_CORRUP_LIST" error and such. I updated the graphics driver but, since then it did not solve my problems because sometimes my games crashed with no reasons why. I put another .zip file of the system to look at it if somebody finds something that is causing problem would be very appreciated.

Hel

 

BugCheck 4E, {2, 238fd3, 42e5ff, 1600}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+19c3d )
Use !analyze -v to get detailed debugging information.BugCheck 1A, {5003, ffffdf0010804310, 1cd0f, 12d910035b1e}Probably caused by : memory_corruption

Use !analyze -v to get detailed debugging information.BugCheck 1A, {41284, 4ef9000, 1380c, ffff990010804310}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14b6a )

BugCheck A, {0, 2, 0, fffff802890f7ee0}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption ( nt!MiInsertUnusedSubsection+bc )
BugCheck 133, {0, 501, 500, 0}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+fbc48 )


Dienstname: NVIDIA KMSDienstdateiname: \??\C:\Program Files\NVIDIA Corporation\NvStreamSrv\NvStreamKms.sysDiensttyp: KernelmodustreiberDienststarttyp: Manuell startenDienstkonto:




The above analysis from Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64

ntkrnlmp.exe
nvlddmkm.sys

Unfortunately many of the logs cannot be read/interpreted (language)

Open administrative command prompt and type or copy and paste these commands:

1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan

Post the results of the above by right clicking on the top bar of the administrative command prompt box > left click edit > left click select all > then right click the top bar again > left click copy > paste into the forum

4) open device manager and view all video drivers and delete all NVIDIA drivers
5) reinstall NVIDIA drivers
6) run memtest86+ for at least 8 runs (the more the better) (it may take many hours so plan to run it overnight)
7) If bsod continue to occur place your computer in clean boot so that you will be able to complete the memtest86+ 8 or more runs.
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

https://support.microsoft.com/en-us/...oot-in-windows

 

Alright I just did all the Command Prompt comands, next I am going to reinstall the driver and start memtest.
I put the results in a text file.

 

I just received two BSOD's from starting my computer and the automatic repair tool was activated. I tried to get a save point but, was not able to. This happened after Memtest was done

 

Did scannow report no integrity violations or did it find and repair violations?
Did restorehealth complete successfully?

The debugger so far has NVDIA, memory, and registry.

Only you can read the event viewer (language).
See if there is anything in this log: eventlog in the attached file.

Are you getting these new bsod in clean boot?

The following steps may be useful:
We can use windows driver verifier to stimulate the misbehaving drivers and force bsods to identify them.
You must be comfortable with the windows advanced troubleshooting menu to be able to turn windows driver verifier off with the verifier /reset command.

There is software that will enable you to get an immediate assessment on bsod: whocrashed and bluescreenview.
Download and install both so that you can immediately process the bsod.

Resplendence Software - WhoCrashed, automatic crash dump analyzer
Blue screen of death (STOP error) information in dump files.

Each time you use windows driver verifier it will display a stop code. Typically it is driver verifier detected violation. Sometimes it will display the misbehaving driver with *.sys. More often the minidump files must be viewed to find the misbehaving driver.

Open system control panel > advanced system settings > startup and recovery settings > uncheck automatically restart.

BSOD Finding and fixing them - Microsoft Community

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

To turn on windows driver verifier type verifier in the left lower corner search.
Follow the instructions in the above link for the custom settings.
To turn windows driver verifier off you will need to go to the windows advanced troubleshooting menu and choose startup options. In startup options click restart and choose safe mode with command prompt. Type verifier /reset
The reboot to desktop and open each whocrashed and bluescreen view and compare the analysis of the bsod.
Sometimes they differ so also post your new bsod while using windows driver verifier.
Uninstall any identified driver/application.
If the driver is essential reinstall the one recommended by your computer manufacturer.
First attempt reinstalling the same driver if it is recommended. If it fails again then choose an older driver.
Keep repeating the windows driver verifier until you no longer have any bsod. Then use the computer for 36 hours of typical use. If there are no longer any bsod then that is success.
If there are bsod while using windows driver verifier that cannot be fixed by un-installation and re-installation of software then you may have to find other software that is more stable with your software/hardware environment.

 

Well, I think it's not necessary since it's Memory Corruption and not caused by a driver because I did some research myself. I used the Windows Debugging Tools to analyze the cause of the BSOD. To my conclusion it's clear that it is a faulty memory modul or the dimm slot is damaged or broken. I did another Memory test run with memtest with 10 passes showing me over 70'000 errors and afterwards it did not crash. I haven't tested the individual RAM model yet but I will do that soon. Also, here is the english version of the .zip

 

Sounds like you are on the right path to solving this. Good luck.

 

OK so now you need to run one RAM module at a time to make sure that you differentiate the RAM sticks. Also this will enable you differentiate a RAM problem from a dim slot.

 

Alright I found out that it s a failing RAM module that is causing it. Thank god not the motherboard but, still I have to order new RAM modules. Thanks for the help

 

Your welcome. Anytime.