Crashing to desktop without clues

[Where is my towel?]

Hi devs,

Please your help. PR crashes since a week to desktop within minutes after launching. Both online multiplayer as offline co-op. No clues in the W10 event manager. Software firewall is offline due to external firewall and modem in the 1 GB wired internal network. I have 3 crash proc dumps for further investigation. But I am not allowed to post it here. Latest W10 version, latest PR version. All drivers up to date. The rig fits the hardware requirements. No clue what is hitting me.

Thank you in advance for any help!

Kr Herman

[Mats391]

Please check Project Reality BF2\mods\pr\bin\PRLauncher.log for errors

[Where is my towel?]

Hi, thanks for the reply. The log says;

Code: Select all

Project Reality Log File
PRLauncher.exe started at: 2020-11-07T23:42:57

Warning: Error keep alive request returned NULL

This morning I have updated Windows 10 with several updates and reboots. After that, tried offline Co-op and online Free Candy Van. No crashes so far after 15 minutes of playing, I think I'm good to go.

[Mats391]

Always good to hear when issues resolve themselves

[Where is my towel?]

Indeed, thanks and have a nice Sunday!

[AlonTavor]

If it starts happening again, set your profile folder in my documents to read only. It seems like on a few systems BF2 likes to flush incomplete files to it

[Where is my towel?]

I just crashed while waiting to join an online game. And read your comment regarding the PR profile folder. I have set properties to read only. But the log refers to driver files generating errors while parsing.

Code: Select all

Project Reality Log File
PRLauncher.exe started at: 2020-11-08T22:00:47

Warning: Error 1 in WinApi parsing modulesC:\WINDOWS\SYSTEM32\D3DSCache.dll
Warning: Error 1 in WinApi parsing modulesC:\WINDOWS\SYSTEM32\amsi.dll

[Where is my towel?]

In addition, restarting PR generated an error 1322: "Error verifying profile settings. Please confirm the profile files are not read-only and try again. If the problem continues, try resetting all profiles to default in the options menu."

And PR refuses to start.

[Where is my towel?]

Set the Property folder to readable again.

Run PR with admin privileges.

New crash;

Code: Select all

Project Reality Log File
PRLauncher.exe started at: 2020-11-09T21:43:35

Warning: Error updating video settings: Resolution: ReadOnly
Warning: Error updating video settings: Resolution: ReadOnly
Warning: Error updating video settings: Resolution: ReadOnly

[Where is my towel?]

Two crashes to desktop after this, no new entries in the log file though.

[AlonTavor]

-Uninstall Avast if you're using it
-See if procdump catches anything https://www.realitymod.com/forum/showth ... p?t=147961
-Set read-only only after launching, not before. Likely not the issue as this one comes with a known error message

[Where is my towel?]

Hi Alon, thanks for your help. It took some days to find time to test again.

- Avast is not installed. All firewalls on this PC are disabled due to a separate router with firewall.

- procdump.exe caught a crash within minutes of starting COOP local;


[16:48:47] Exception: C0000005.ACCESS_VIOLATION
[16:48:47] Dump 1 initiated: C:\Users\Beheerder\Downloads\Procdump (1)\PRBF2.exe_201112_164847.dmp
[16:48:47] Dump 1 complete: 18 MB written in 0.4 seconds
[16:48:48] Dump count reached.

See next post for output.

[Where is my towel?]

OK, I found the Win 10 app Debugger (WinDBG) and installed it. Run the verbose analysis on the dump file. The Exception Analysis is below.


Microsoft (R) Windows Debugger Version 10.0.20153.1000 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Beheerder\Downloads\Procdump (1)\PRBF2.exe_201112_164847.dmp]
Comment: '
*** procdump.exe -mm -b -e 1 -g prbf2.exe
*** First chance exception: C0000005.ACCESS_VIOLATION'
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19041 MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.x86fre.vb_release.191206-1406
Machine Name:
Debug session time: Thu Nov 12 16:48:47.000 2020 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:09:39.000
................................................................
...........................................................
Loading unloaded module list
................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(3bd8.2ec0): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
eax=008ac530 ebx=4cb69754 ecx=00000000 edx=008ac530 esi=4cb69754 edi=4cb67114
eip=004fa079 esp=0019f984 ebp=0019f9a8 iopl=0 nv up ei ng nz ac pe cy
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210297
PRBF2+0xfa079:
004fa079 8b01 mov eax,dword ptr [ecx] ds00000000=????????
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 2109

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 106133

Key : Analysis.Memory.CommitPeak.Mb
Value: 152

Key : Analysis.System
Value: CreateObject

Key : Timeline.Process.Start.DeltaSec
Value: 579

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

COMMENT:
*** procdump.exe -mm -b -e 1 -g prbf2.exe
*** First chance exception: C0000005.ACCESS_VIOLATION

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=008ac530 ebx=4cb69754 ecx=00000000 edx=008ac530 esi=4cb69754 edi=4cb67114
eip=004fa079 esp=0019f984 ebp=0019f9a8 iopl=0 nv up ei ng nz ac pe cy
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210297
PRBF2+0xfa079:
004fa079 8b01 mov eax,dword ptr [ecx] ds00000000=????????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 004fa079 (PRBF2+0x000fa079)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

PROCESS_NAME: PRBF2.exe

READ_ADDRESS: 00000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%p verwijst naar geheugen op 0x%p. Het geheugen kan niet worden %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000000

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0019f9a8 07bfe705 0063349c 061b59f4 4863349c PRBF2+0xfa079
0019f9c0 07c009d3 4cb67114 061b59f4 06125de4 RendDX9!deinitDll+0xb9df5
0019fa04 07c015e0 061b59f4 06125de4 0496e054 RendDX9!deinitDll+0xbc0c3
0019fa30 07b0112b 00000000 01c1fe74 00000000 RendDX9!deinitDll+0xbccd0
0019fcb8 0045347f 00000000 3f928000 3c940000 RendDX9+0x3112b
0019fd38 0040d3da 00000000 3c940000 010001f4 PRBF2+0x5347f
0019fe0c 004029e9 775d5b70 779f2e00 00000000 PRBF2+0xd3da
0019fe70 00402b9d 00400000 00000000 00eb3c3f PRBF2+0x29e9
0019feb8 00402c89 00eb3c3f 00eb3c3f 0019ff70 PRBF2+0x2b9d
0019fec8 0083d61d 00400000 00000000 00eb3c3f PRBF2+0x2c89
0019ff70 779efa29 0029d000 779efa10 0019ffdc PRBF2+0x43d61d
0019ff80 77d975f4 0029d000 fd04ae8c 00000000 kernel32!BaseThreadInitThunk+0x19
0019ffdc 77d975c4 ffffffff 77db7355 00000000 ntdll!__RtlUserThreadStart+0x2f
0019ffec 00000000 0083d498 0029d000 00000000 ntdll!_RtlUserThreadStart+0x1b


SYMBOL_NAME: PRBF2+fa079

MODULE_NAME: PRBF2

IMAGE_NAME: PRBF2.exe

STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_PRBF2.exe!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

FAILURE_ID_HASH: {7b8c6930-6ef3-a887-5285-cd7f25f5ecbc}

Followup: MachineOwner
---------

[AlonTavor]

I'll check when I'm home

[AlonTavor]

Not sure yet, not an error i've seen. Can I have the dump file? Need some data

[Where is my towel?]

Hi Alon, I have send you a dropbox link to the file via a PM as I don't see an option to attach files.

[Where is my towel?]

After deleting the Project Reality folder in My documents, and restoring my online profile, the crashes have gone. Thanks very much Alon, this thread can be closed.