topic Re: battlefield 5 0x887a0006 - crash question in Mobile and Desktop Processors

battlefield 5 0x887a0006 - crash question

SLitw — Sun, 23 Jun 2019 04:53:36 GMT

Hi.

Hello. I left running Battlefield 5 in singleplayer campaign for hours,by standing in the same place in game. I go to sleep.

When i woke up i met desktop and Windows 10 message:"we've got an update for you"and it hangs because mouse cursor was a turning circle and unable to click anything,so i just ctrl alt delete and log out.

Event viewer said:"display driver stopped responding and has recovered".

This is exception code of crash:"0x887a0006 "according to MDMP WinDbG.

Also in background have only gpuz and msi afterburner + rivatuner.

My pc:9900K 4.7 stock

2x16GB DDR4 GSKILL 3000mhz XMP

Corsair 850 RmX

Rtx 2080 Ti Aorus Xtreme ( stock ,no oc )

I am using the newest drivers.

Also i tested Unigine Heaven ,3dmark firestrike and other games for hours and no crashes.

Memtest86 no errors. RAM TEST no errors. Realbench ok.

My question is that was related to hardware or maybe due that Windows update notification,or that doesnt matter? Also i cant reproduce this crash anymore. Some EA dude told me that is hardware crash. But i am not sure so i ask here.

Re: battlefield 5 0x887a0006 - crash question

AlHill — Sun, 23 Jun 2019 05:02:27 GMT

Newest drivers means nothing.

Confirm that you are using no intel graphics.

What operating system AND VERSION are you running? Be very specific.

Have you discussed this with your rtx manufacturer?

Have you run the https://downloadcenter.intel.com/download/19792

Doc

Re: battlefield 5 0x887a0006 - crash question

SLitw — Sun, 23 Jun 2019 05:07:40 GMT

I am using nvidia drive the newest. Win 10 1809 ver. Also it happened once after 14 hours being in game. Nothing more i am testing again and no crash.

CPu passing all stresstest and programs,apps. Ram the same.

Re: battlefield 5 0x887a0006 - crash question

AlHill — Sun, 23 Jun 2019 06:08:50 GMT

After 14 hours in the game, you probably crashed and just did not realize it.<G>

So, everything is ok, right?

Doc

Re: battlefield 5 0x887a0006 - crash question

SLitw — Sun, 23 Jun 2019 06:09:45 GMT

now its fine but why it crashed/.?

Re: battlefield 5 0x887a0006 - crash question

AlHill — Sun, 23 Jun 2019 06:12:47 GMT

who knows? Could be the game, could be the OS...

Doc

Re: battlefield 5 0x887a0006 - crash question

SLitw — Tue, 25 Jun 2019 00:21:30 GMT

Hello.

I get 2 crashes in Battlefield 5 with exception 0x887a0006. Event viewer said: display driver recovery.

This is exception code of crash:"0x887a0006 "according to MDMP WinDbG.

One time it crashed after 14 hours being in game,now it crashed after 2 minutes after started game.

And again its fine its running.

Also in background have only gpuz and msi afterburner + rivatuner.

My pc:9900K 4.7 stock

2x16GB DDR4 GSKILL 3000mhz XMP

Corsair 850 RmX

Rtx 2080 Ti Aorus Xtreme ( stock ,no oc )

I am using the newest drivers nvidia.

Also i tested Unigine Heaven ,3dmark firestrike and other games for hours and no crashes.

Memtest86 no errors. RAM TEST no errors. Realbench ok.

Is my hardware faulty?

Re: battlefield 5 0x887a0006 - crash question

SLitw — Tue, 25 Jun 2019 22:52:59 GMT

Hey. Its crash log. Can you analyze for me?:)

*** WARNING: Unable to verify timestamp for bfv.exe

*** WARNING: Unable to verify timestamp for dbdata.dll

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec

Value: 2

Key : Analysis.Elapsed.Sec

Value: 10

Key : Analysis.Memory.CommitPeak.Mb

Value: 198

Key : Timeline.Process.Start.DeltaSec

Value: 373

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start

Name: <blank>

Time: 2019-06-25T15:22:01.435Z

Diff: 178818435 mSec

Timeline: Dump.Current

Name: <blank>

Time: 2019-06-23T13:41:43.0Z

Diff: 0 mSec

Timeline: Process.Start

Name: <blank>

Time: 2019-06-23T13:35:30.0Z

Diff: 373000 mSec

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

MODLIST_WITH_TSCHKSUM_HASH: 5d4f03f892eff03a1c5435114ab49261724f087b

MODLIST_SHA1_HASH: f64fcc738ab2590fc75d22b7abdd1329c1d0ce06

COMMENT: Frostbite MiniDump. Address: 00007FFE80B39129 (In Windbg type: .ecxr)

[EOF]

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

DUMP_FLAGS: a2

DUMP_TYPE: 11

CONTEXT: (.ecxr)

rax=00000000887a0006 rbx=000000003824ac40 rcx=000000003490bf38

rdx=0000000141ff1718 rsi=00000000887a0006 rdi=0000000000000000

rip=00007ffe80b39129 rsp=000000003490c6a0 rbp=000000003490c880

r8=0000000000000000 r9=000000003490bf3a r10=000000003490c059

r11=000000003490c337 r12=000000003825e460 r13=0000000038247dd0

r14=0000000038247dd0 r15=0000000143b9a7e8

iopl=0 nv up ei pl nz na po nc

cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206

KERNELBASE!RaiseException+0x69:

00007ffe`80b39129 0f1f440000 nop dword ptr [rax+rax]

Resetting default scope

FAULTING_IP:

KERNELBASE!RaiseException+69

00007ffe`80b39129 0f1f440000 nop dword ptr [rax+rax]

EXCEPTION_RECORD: 000000003490d290 -- (.exr 0x3490d290)

ExceptionAddress: 0000000000000000

ExceptionCode: 00000000

ExceptionFlags: 00000000

NumberParameters: 1285050106

Parameter[0]: 000073fd8db5e4c0

Parameter[1]: 0000000000000000

Parameter[2]: 00009ffd0010004f

Parameter[3]: 0053002b002b0033

Parameter[4]: 00000206002b002b

Parameter[5]: 00007ffe4c8681a5

Parameter[6]: 000000005bc926e0

Parameter[7]: 000000003490d410

Parameter[8]: 000000003490e170

Parameter[9]: 0000000000000000

Parameter[10]: 000000005bc926e8

Parameter[11]: 000000005be906e0

Parameter[12]: 000000005be90678

Parameter[13]: 0000000000001000

Parameter[14]: 00000000887a0006

DEFAULT_BUCKET_ID: APPLICATION_FAULT

PROCESS_NAME: bfv.exe

ERROR_CODE: (NTSTATUS) 0x887a0006 - Jednostka GPU nie odpowie na wi cej polece prawdopodobnie z powodu nieprawid owego polecenia przekazanego przez aplikacj wywo uj c .

EXCEPTION_CODE: (HRESULT) 0x887a0006 (2289696774) - The GPU will not respond to more commands probably due to an incorrect command given by the calling application.

EXCEPTION_CODE_STR: 887a0006

WATSON_BKT_PROCSTAMP: 5089d1b5

WATSON_BKT_MODULE: KERNELBASE.dll

WATSON_BKT_MODSTAMP: aee8f822

WATSON_BKT_MODOFFSET: 39129

WATSON_BKT_MODVER: 6.2.17763.592

MODULE_VER_PRODUCT: Microsoft® Windows® Operating System

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_HOST: DESKTOP-RVP2EUM

ANALYSIS_SESSION_TIME: 06-25-2019 17:22:01.0435

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

THREAD_ATTRIBUTES:

OS_LOCALE: PLK

BUGCHECK_STR: APPLICATION_FAULT

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

ID: [0n320]

Type: [APPLICATION_FAULT]

Class: Primary

Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)

BUCKET_ID

Name: Add

Data: Omit

PID: [Unspecified]

TID: [Unspecified]

Frame: [0]

LAST_CONTROL_TRANSFER: from 0000000000000000 to 0ffda817418d0000

IP_ON_HEAP: 0ffda817418d0000

The fault address in not in any loaded module, please check your build's rebase

log at <releasedir>\bin\build_logs\timebuild\ntrebase.l og for module which may

contain the address if it were loaded.

UNALIGNED_STACK_POINTER: 000003e6830f02fd

STACK_TEXT:

00000000`3490c6a0 00000001`41ff1405 : 00000000`38247dd0 00000000`3824ac40 00000000`3490c880 00000000`887a0006 : KERNELBASE!RaiseException+0x69

00000000`3490c808 6e6f7361`65526465 : 64656c69`61662022 58442068`74697720 524f5252`455f4947 5f454349`5645445f : 0x766f6d65`52656369

00000000`3490c810 64656c69`61662022 : 58442068`74697720 524f5252`455f4947 5f454349`5645445f 0000202e`474e5548 : 0x6e6f7361`65526465

00000000`3490c818 58442068`74697720 : 524f5252`455f4947 5f454349`5645445f 0000202e`474e5548 00007ffe`83c25bd0 : 0x64656c69`61662022

00000000`3490c820 524f5252`455f4947 : 5f454349`5645445f 0000202e`474e5548 00007ffe`83c25bd0 00000000`0003ffff : 0x58442068`74697720

00000000`3490c828 5f454349`5645445f : 0000202e`474e5548 00007ffe`83c25bd0 00000000`0003ffff 00000000`3490c930 : 0x524f5252`455f4947

00000000`3490c830 0000202e`474e5548 : 00007ffe`83c25bd0 00000000`0003ffff 00000000`3490c930 000004e8`fffffb30 : 0x5f454349`5645445f

00000000`3490c838 00007ffe`83c25bd0 : 00000000`0003ffff 00000000`3490c930 000004e8`fffffb30 000004d0`fffffb30 : 0x0000202e`474e5548

00000000`3490c840 00007ffe`83cafd99 : 00007ffe`80d377b4 00000000`00000001 00000000`3490dbb0 00007ffe`4be4f3ec : ntdll!RtlUnwindEx+0xe0

00000000`3490ca50 00007ffe`80b8ace2 : 00007ffe`80d377e4 00000000`3490daf0 00000000`3490dbb0 00000000`00000000 : ntdll!_C_specific_handler+0xd9

00000000`3490cac0 00007ffe`83cc477f : 00000000`00000000 00000000`3490d060 00000000`00000000 00007ffe`80b00000 : KERNELBASE!_GSHandlerCheck_SEH+0x6a

00000000`3490caf0 00007ffe`83c24bef : 00000000`3490d060 00000000`00000000 00000000`00000000 00007ffe`80b00000 : ntdll!RtlpExecuteHandlerForException+0xf

00000000`3490cb20 00007ffe`83c289e6 : 00000000`3490d290 00007ffe`83c287d1 00000000`3490d290 00000000`00000000 : ntdll!RtlDispatchException+0x40f

00000000`3490d250 00000000`00000000 : 00002ad9`73fdb78d 00007ffe`80b257a3 00000000`00000002 00007ffe`80b1f3bd : ntdll!RtlRaiseException+0x316

THREAD_SHA1_HASH_MOD_FUNC: ca5f3522079e743716170cd795f24abc64e1f51f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e2ba14bcf6f206fef64b7592b863a120b5a897f0

THREAD_SHA1_HASH_MOD: fd3993ac99a0867a95fe80a5898c8d0920148e13

FOLLOWUP_IP:

bfv+1ff1405

00000001`41ff1405 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: bfv+1ff1405

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bfv

IMAGE_NAME: bfv.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ce71974

STACK_COMMAND: ~15s ; .ecxr ; kb

BUCKET_ID: APPLICATION_FAULT_bfv+1ff1405

FAILURE_EXCEPTION_CODE: 887a0006

FAILURE_IMAGE_NAME: bfv.exe

BUCKET_ID_IMAGE_STR: bfv.exe

FAILURE_MODULE_NAME: bfv

BUCKET_ID_MODULE_STR: bfv

FAILURE_FUNCTION_NAME: Unknown

BUCKET_ID_FUNCTION_STR: Unknown

BUCKET_ID_OFFSET: 1ff1405

BUCKET_ID_MODTIMEDATESTAMP: 5ce71974

BUCKET_ID_MODCHECKSUM: f2f46ca

BUCKET_ID_MODVER_STR: 1.0.73.12205

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: bfv.exe!Unknown

FAILURE_BUCKET_ID: APPLICATION_FAULT_887a0006_bfv.exe!Unknown