August 2018
Hi, I bought it yesterday and I tried what you said in the topic; in offline mode the game starts but crash when you have to create the licence with the photo, I think is something related with the webcam like many said about USB interference, but I cannot fix it. I tried also to replace the save files with the files from the originale game but they failed at the start.
I suppose a way to fix it fast is to download some saves after the creation of the licence, but cannot find them on the web. Can someone please share them? Maybe at least I Can try it offline
August 2018
At first I noticed in log that ur Current Mode: 1280 x 1024 (32 bit) (75Hz) but Native Mode: 1280 x 1024(p) (60.020Hz) - it is normal? )
In a dump my eyes have seen only two potential problematic software:
"C:\Program Files\Prio\prio32.dll' -> "Prio" - "Process Priority Control" from "O&K Software"
NvCameraWhitelisting32.dll -> NVIDIA Camera software
But I dont think that this programs is a problem, but u can try uninstall "Prio" and "nVidia GeForce Experience" if u can/have it.
Another possible problem is ur CPU Pentium G3220 witch have 2 cores and 2 threads, but in min sysreq for BPR is Intel i3 2120 CPU witch have 2 cores and 4 threads.
@EA_Andy can someone confirm that this game not run on 2 threads CPU?
August 2018 - last edited August 2018
Could you look at my file too please?
August 2018 - last edited August 2018
Thank you for the reply!
Yes, that is the resolution I normally use, but since then I switched it back to native. I also got completely rid of Prio and GeForce Experience (along with the NvCameraWhitelisting32.dll and Ansel as a whole). Still no luck :/
If it is the CPU's fault, then it's really a shame, because it can handle every other game I play(ed) just fine. The Crew 2 had some kind of CPU limitations before, but they fixed it in a later patch. Now my rig handles even that game pretty well.
Anyway, I'm attaching the newest crash dump after these steps, in hopes that you find something new. Also, in hopes that EA finds a suitable fix for all of our problems...
August 2018 - last edited August 2018
I cant find something useful in a dump, but for some case there is some info from it:
Other suggestions:
1.
Try to crate new user account in ur Operation System with Admin rights and dont use local language symbols in a user name, use only latin symbols.
2.
Try to uninstall this software:
-- screenSHU "c:\program files (x86)\screenshu\screenshu.exe"
-- "NVIDIA 3D Vision" component
3.
Reinstall all Visual С++ components in this way:
a) delete all content of this folders (ignore any problems/errors): "C:\Windows\Temp\" and "C:\User\[UserName]\AppData\Temp\";
b) all installers run as Admin;
c) before install this, delete all already installed versions in order from 2005 to 2017;
d) if you have x64 OS, you'd install x32 (x86) and x64 packages of all versions:
VC2005 (хххххх80.dll), VC2008 (хххххх90.dll), VC2010 (ххххх100.dll), VC2012 (ххххх110.dll), VC2013 (ххххх120.dll), VC2017x86, VC2017x64 (ххххх140.dll).
There are no more ideas...
August 2018 - last edited August 2018
I dont talk about resolution, but refresh rate. u use 75Hz, when Native is 60Hz.
No any new info from dump for me. There is some info from a dump just for any case:
FAULTING_IP:
BurnoutPR+54c5b9a
058c5b9a 8b08 mov ecx,dword ptr [eax]
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 058c5b9a (BurnoutPR+0x054c5b9a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000
DEFAULT_BUCKET_ID: NULL_POINTER_READ
PROCESS_NAME: BurnoutPR.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000000
READ_ADDRESS: 00000000
FOLLOWUP_IP:
BurnoutPR+54c5b9a
058c5b9a 8b08 mov ecx,dword ptr [eax]
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
FAULTING_THREAD: 00000b28
PRIMARY_PROBLEM_CLASS: NULL_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ
LAST_CONTROL_TRANSFER: from 058c9688 to 058c5b9a
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
565afbe0 058c9688 00000780 00000440 00000006 BurnoutPR+0x54c5b9a
565afc00 058c0e3a 3e1e2098 00000780 00000440 BurnoutPR+0x54c9688
565afc20 055f53db a15cc300 565afd14 a11cbc80 BurnoutPR+0x54c0e3a
565afc40 007cb199 9f9cb304 565afd14 3e1e2098 BurnoutPR+0x51f53db
565afdb4 007c7286 00000100 007c7ad0 00f37378 BurnoutPR+0x3cb199
565afe7c 0569259b 565afe90 066193d9 9f9cb080 BurnoutPR+0x3c7286
565afe84 066193d9 9f9cb080 565aff4c 006cfaf2 BurnoutPR+0x529259b
565afe90 006cfaf2 007c7ad0 9f9cb080 7d097660 BurnoutPR+0x62193d9
565aff4c 727962a4 00f37378 73e6ce7a 00000000 BurnoutPR+0x2cfaf2
565aff88 754b338a 4ff632d0 565affd4 774d9902 ucrtbase!_crt_at_quick_exit+0x104
565aff94 774d9902 4ff632d0 21023b7a 00000000 kernel32!BaseThreadInitThunk+0xe
565affd4 774d98d5 72796250 4ff632d0 00000000 ntdll!__RtlUserThreadStart+0x70
565affec 00000000 72796250 4ff632d0 00000000 ntdll!_RtlUserThreadStart+0x1b
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: BurnoutPR+54c5b9a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BurnoutPR
IMAGE_NAME: BurnoutPR.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5b365b73
STACK_COMMAND: ~52s; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_BurnoutPR.exe!Unknown
BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_READ_BurnoutPR+54c5b9a
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/BurnoutPR_exe/1_0_0_0/5b365b73/BurnoutPR_exe/1_0_0_0/5b365b73/c...
So, I still think that ur main problem is ur CPU, so if it is true u can try find info in google about how run the new game on 2-cores CPU (there is some methods) and check it.
There are no more ideas...
August 2018
@MADrag0n Thank you for your help, really appreciate it.
Unfortunately I already tried uninstalling and repairing VCC and creating new user but it didn't help (
I guess I will have to wait till eventual patch...
August 2018
Thank you very much for your effort, will do! Otherwise I have to wait for the official patch :D
August 2018 - last edited August 2018
@MADrag0n THANK YOU.
Your suggestion to create a user account without diacritical marks in the name (my first name is José with an acute accent on the e and it is in my normal Windows User account name) turns out to be the solution to the non-camera related problem. I was online and everything under the new user account, but with my same Origin ID. Under my regular account, BPR would 100% of the time crash right as it was connecting to server. Under my rump account (A regular, no Admin Rights account even) NO PROBLEM.
How COLOSSALLY DUMB is that, in this international age, SERIOUSLY, EA.
So, pro-tip people, for now, until this stupid bug is fixed, that's how you take care of one of the CTDs, anyway--just plain old non-extended ASCII in your Windows User Account name. #smh.
August 2018
delete ur dumps file in previews post for security reasons
@PapagenoX good to hear it.
But u should understand that EA/Origin do not use 100% own software technology, some of it developed by different company or people and any problem can by on any side of any technology. And good test and quick patch can be only for 100% own product!