Still crashing in less than 2 mins.
Yup still a frickin mess and ofc every time you crash you lose all your buffs etc. I mean they could make those outlast a crash but then they’d have to admit their game is crashing constantly. Can’t do that we don’t want to admit we’re hopelessly incompetent
Still crashing / bug checking for me:
BUGCHECK_CODE: a
BUGCHECK_P1: ffffc2b16e1de2f0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff800a825e4d0
FILE_IN_CAB: 103124-26781-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
FAULTING_THREAD: ffffb08b8dba5080
READ_ADDRESS: fffff800a8fc34b0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffc2b16e1de2f0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Diablo IV.exe
TRAP_FRAME: ffffae8cdc486e60 -- (.trap 0xffffae8cdc486e60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff918000000028 rbx=0000000000000000 rcx=000000316e1de2f2
rdx=000000ffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800a825e4d0 rsp=ffffae8cdc486ff0 rbp=ffffae8cdc487040
r8=ffff918000000000 r9=0000000000000002 r10=ffffc28000000000
r11=ffffc28000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiLockProtoPoolPage+0x90:
fffff800`a825e4d0 498b1e mov rbx,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope
STACK_TEXT:
ffffae8c`dc486d18 fffff800`a868a9e9 : 00000000`0000000a ffffc2b1`6e1de2f0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffae8c`dc486d20 fffff800`a8685ca8 : 00000000`00000f00 ffffd600`76a5a180 ffffd600`76549180 ffffae8c`dc486f60 : nt!KiBugCheckDispatch+0x69
ffffae8c`dc486e60 fffff800`a825e4d0 : ffffd600`764a7180 fffff800`a8581718 00000000`00000047 00000000`00000000 : nt!KiPageFault+0x468
ffffae8c`dc486ff0 fffff800`a82583ed : 000062dc`3bc5e5af 00000000`00000001 00000000`00000000 00000000`00000000 : nt!MiLockProtoPoolPage+0x90
ffffae8c`dc487100 fffff800`a8258b9a : 00000191`21cca000 00000000`00000002 ffffae8c`dc4871d8 000062dc`3bc5e5af : nt!MiResolveProtoPteFault+0x85
ffffae8c`dc4871a0 fffff800`a8214b93 : 00000191`21cca000 fffff800`00000100 00000000`00001000 ffffb08b`7a76d080 : nt!MiDispatchFault+0x226
ffffae8c`dc4872f0 fffff800`a8685bcb : ffffb08b`8dba5080 00000000`00000000 00000191`0298f2c0 00000000`00000000 : nt!MmAccessFault+0x183
ffffae8c`dc487460 00007ff6`e35fd0fb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
00000073`be8ef448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`e35fd0fb
SYMBOL_NAME: nt!MiLockProtoPoolPage+90
MODULE_NAME: nt
IMAGE_VERSION: 10.0.26100.2161
STACK_COMMAND: .process /r /p 0xffffb08b7a76d080; .thread 0xffffb08b8dba5080 ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 90
FAILURE_BUCKET_ID: AV_nt!MiLockProtoPoolPage
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {27dc92b6-2b7e-5408-61ec-c60ff31082f0}
Followup: MachineOwner
It may be too much to ask.
Developers can put a way to keep the positions, elixirs, and incenses when we disconnect ?
Because every fall everything is lost…
Thank you
2 Likes
players. since D4 release, players are always the beta testers. D4 is still in Beta even now after expansion release
3 Likes
Still crashing / bug checking for me.
FAULTING_THREAD: ffffb08b8dba5080
FAILURE_BUCKET_ID: AV_nt!MiLockProtoPoolPage
PROCESS_NAME: Diablo IV.exe
Looks like a memory management issue.
Since Blizzard doesn’t even consider it necessary to provide an answer or transparency, i analyzed the BSOD myself.
Without going into great detail here is a short summary:
-
Error code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with the specific error code c0000005, which indicates an access violation error. Such errors usually occur when a program attempts to access memory that is no longer valid or inaccessible.
-
Error module: dxgmms2.sys, which suggests that the error occurred in the communication between Windows and the graphics driver.
-
Triggering function: VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress, which indicates a memory management function in the graphics API that may have failed in the address allocation for GPU data.
Since my graphics card (RTX 4090 Strix OC) has the following properties:
- Passes every stress test
- Nvidia drivers are up to date
- Temperatures at full load (60 °C, Hotspot delta <= 10 °C)
- No crashes in other games, and certainly no BSOD
These BSODs are most likely caused by an error in the code on the part of Blizzard.
The fact that Blizzard can’t get this bug under control after all these weeks since the release of VoH raises some questions. Also that patches are released in such a state.
Always only patches with “Various stability improvements.” instead of communication.
This is really very bad from you Blizzard. We are all customers here who have already paid.
11 Likes
Wowee guys.
Been quite awhile.
Wowee 
Thanks for the extra info.
The updates being rolled out are hitting on specific individual items but not all of them. We choose to roll out updates as fixes come in. We do have some other lingering stability bugs and so we do expect additional client patches. I know 2.0.4b is currently in the works and will have some details on that soon.
7 Likes
Game uninstalled, Battlenet launcher uninstalled. Problems all season so far, very poor communication/no solutions from Blizzard with people being told it is their rig despite a very large number of people all experiencing the same errors. Game balance is terrible, it is so difficult to get the new ancestral level aspects. Masterworking is so expensive and RNG based it is just not fun for me at least and the events are so lacklustre you would think it actually costs Blizzard money to be generous with the drops. I had never played a Blizzard game before and the clear lack of testing of the game which is evidenced by there being issues after every patch or new season tells me everything I need to know about these devs. How to get as much money as possible with the absolute minimum effort.
5 Likes
thank you so much for this level of information. wish blizz would be this transparent and open with us. we’re not dumb. just talk to us. please. the constant crashing is sickening and annoying and makes me want to uninstall.
1 Like
Stop doing this. Stop side stepping and giving unclear political type responses. It is time to give us FULL transparency on this issue. Tell us what is going on, what is causing this, and what specific steps are being taken towards a complete resolution.
1 Like
We demand real answers.
2 Likes
Please check out my related post - Game Periodically Crashes (Minidump Info).
my game crashed again today and i really hoped last patch fixed it. i also had zero issues and crashes before.
here is the error window i got
[prism] Device Removal - Win10/Dx12 BC:Hybrid False
Ah, soon…
Seriously?
Who will give us back the time we spent on an unplayable product?
If there were no such problems at the beginning of the season, and after some “patches” from the developers the game begin to crashing every time it is being played?
why should we remain calm and respect devs while they are not interested in fixing their screwups?
The causes of crashes and the difficulty of detecting and fixing them are absolutely irrelevant for the end user… Users did not pay for assistance in the development and refinement of the beta version with the devs… This approach could have been at the development stage. However, you preferred to methodically show us your unfinished versions of so long-awaited and beloved game series…
sorry for my english))))
4 Likes
I agree with the poster above me. It’s time your Team and your Company take full Responsibility and Accountability for Your Mistakes.
1 Like
No More Free Passes for Blizzard.
Things that will never happen for 100 please, Alex
1 Like