Event viewer help - game crashes

[Kaned Dragon]

So I just tried the game with event viewer and afterburner up to see if I can find out why my PC keeps crashing when playing the game. I don't really understand the details I'm looking at so I'm hoping someone can give me some advice. The game crashed and came back to the desktop.

The event viewer had this warning-
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Internal parity error
Processor APIC ID: 0
WHEA-Logger

Does anyone who what I should be looking for.
I did notice on MSI that on the fan section there's a temperature limit of 79c and my system did get to 80c, but it was staying there for about 5 mins and then the crash happened.

[Kaned Dragon]

Sorry just seen this might be more relevent.
Faulting application name: theHunterCotW_F.exe, version: 0.0.0.0, time stamp: 0x619bc2f1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000000001de
Faulting process ID: 0x8d68
Faulting application start time: 0x01d816ec55dd67de
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\theHunterCotW\theHunterCotW_F.exe
Faulting module path: unknown
Report ID: 9d940597-9342-49b9-b01a-458d82e88377
Faulting package full name:

[yogisgoat]

I'm no expert but the fact that event viewer calls it a hardware error and a parity error in particular leads me to believe it's a memory problem. 80c is hot but not hot enough to cause problems UNLESS there's an issue with the vram.

[JeDagelijkseIntrovert]

Sorry about my previous comment, I copy pasted the wrong message as I was multitasking.

Internal parity error usually relates to an issue with the CPU's memory(a.k.a. L1 Cache, L2 Cache, etc.)
Which brand is the processor?

If it is from Intel, and if you're willing to do a stress test; Then you could check those caches with IPDT(Intel Processor Diagnostic Tool), which you can find on the site of Intel.
Once installed, on the first run, IPDT will do a quick stress test, which usually will be enough to see if there's any fault.

You also might want to test your RAM, you can do so by running "Windows memory diagnostic tool", which is present on all windows devices.
Just type in the search function of your taskbar "MdSched" without the quotes.

[Kaned Dragon]

Originally posted by INFP-T Slagroompje:

Sorry about my previous comment, I copy pasted the wrong message as I was multitasking.

Internal parity error usually relates to an issue with the CPU's memory(a.k.a. L1 Cache, L2 Cache, etc.)
Which brand is the processor?

If it is from Intel, and if you're willing to do a stress test; Then you could check those caches with IPDT(Intel Processor Diagnostic Tool), which you can find on the site of Intel.
Once installed, on the first run, IPDT will do a quick stress test, which usually will be enough to see if there's any fault.

You also might want to test your RAM, you can do so by running "Windows memory diagnostic tool", which is present on all windows devices.
Just type in the search function of your taskbar "MdSched" without the quotes.

Thanks for the advice, Yes it's an intel processor - Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
I did both tests. The processor test was a pass on all tests, it was just the start up test, and the ram test detected no errors.

[JeDagelijkseIntrovert]

Originally posted by Kaned Dragon:

Thanks for the advice, Yes it's an intel processor - Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
I did both tests. The processor test was a pass on all tests, it was just the start up test, and the ram test detected no errors.

Then it's likely not to be a hardware issue, how many WHEA entries are in your event viewer?

WHEA internal parity errors usually correct themselves, however should not cause any crashes.
It still was worth to check the memory modules, just to be safe.

It's more likely you're having the same issues as a lot of other people right now with the game just randomly crashing.
Just to be sure, did you overclock anything at all or have you recently updated some drivers(incl. BIOS)?

[Kaned Dragon]

Originally posted by INFP-T Slagroompje:

Then it's likely not to be a hardware issue, how many WHEA entries are in your event viewer?

WHEA internal parity errors usually correct themselves, however should not cause any crashes.
It still was worth to check the memory modules, just to be safe.

It's more likely you're having the same issues as a lot of other people right now with the game just randomly crashing.
Just to be sure, did you overclock anything at all or have you recently updated some drivers(incl. BIOS)?

Yes I believe my cpu is over clocked, but not by much, and the guy who helped me set up my machine did stress tests on it and it was stable. It's not water cooled, I got 2 fans that cool it down. One is going all the time the other activates when the system gets hot.

I cleared my log and tried playing the game tonight. I tried playing 3 times. 2 times the system crashed to blue screen of death and once it crashed to desktop.

Upon checking the event viewer I've got loads of WHEA logs - 177. There all milliseconds apart from each other, as in there are 15 that have a time stamp of 03:34:55.

There are also some major ones.

Error - volmgr - Crash dump initialization failed!

Critical - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

And 2 Errors NetBT - Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.

I do have 4 stick of ram installed but the only time they seemed to be an issue was irronically after a crash while playing COTW. My system went to blue screen of death and when it restarted it got stuck in the bios load up screen. I waited for an hour and nothing happend. So i emergency restarted the system and it caused a corruption of the windows system. I tried doing a repair but it just wouldn't work. I contacted my mate who made the system with me and he suggested take all but 1 ram stick out. I took 2 out leaving 2 and the system repair went smoothly. So having 4 sticks of ram in while trying to do a windows repair definately was a no no. But apart from that it's been fine.

On a side note - I have NordVPN installed, Agent UI, and quite a few music programs installed. Ableton / Reason / IK products include Amplitube and I have an AXE I/O usb audio interface installed.

I mention the AXE I/O in case that solves something but also because the first crash this evening knocked that audio interface out. It's done it before but only after a crash while playing COTW. I had to unplug it and restart before my pc recognised it was connected.

I can't help but feel like I'm having the crashes like some other players. Only COTW crashes so frequently and it seems more of the crashes go to blue screen of death. I got Minecraft and that isn't as stable as it used to be, but it always crashes to the launcher. and none of my other programs kill the system, just COTW. And I'm really starting to get worried it'll cause damage to my system.

I think if the patch that's meant to be coming round the corner doesn't stop the crashes I might uninstall the game for quite a while. While it's installed I can't help but want to play and it's just getting so frustrating. Such a massive downer

Again thanks for any help you can suggest I really appreciate the time and info :)

[Kaned Dragon]

Also just realised this might shed some light maybe perhaps, but I've got a Logitech G203 Mouse and G213 Keyboard. There was also soemthign else I was going to emtion but it's very late and my brains is mush and I can't remember what the other thing was I was goin to mention

[JeDagelijkseIntrovert]

Since you mentioned 2 bluescreens, can you check if there's a .dmp file located in "C:\Windows"?

If there is, you can open that file by installing "WinDbg Preview" on Microsoft Store.
Once opened click the hyperlink that appears in the information box that says '!analyze -v'.
Once it is done analyzing, post the very first block that comes after bugcheck analysis.
It will look something like this:

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffd888007d9080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

Also check your motherboard's manual to see which memory slots are the primary.
Windows shouldn't get stuck on bios boot up, it's especially odd it worked by removing 2 DIMM cards.

[Kaned Dragon]

Originally posted by INFP-T Slagroompje:

Since you mentioned 2 bluescreens, can you check if there's a .dmp file located in "C:\Windows"?

If there is, you can open that file by installing "WinDbg Preview" on Microsoft Store.
Once opened click the hyperlink that appears in the information box that says '!analyze -v'.
Once it is done analyzing, post the very first block that comes after bugcheck analysis.
It will look something like this:

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffd888007d9080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

Also check your motherboard's manual to see which memory slots are the primary.
Windows shouldn't get stuck on bios boot up, it's especially odd it worked by removing 2 DIMM cards.

Okay after some digging and hair pulling i got the DMP file checked, it came back with the below.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8006e03dd5b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8004a03dd54, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

"LOADS OF" Page 174bf8 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 4124

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5171

Key : Analysis.Init.CPU.mSec
Value: 546

Key : Analysis.Init.Elapsed.mSec
Value: 14648

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

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


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 50
BUGCHECK_P1: fffff8006e03dd5b
BUGCHECK_P2: 0
BUGCHECK_P3: fffff8004a03dd54
BUGCHECK_P4: 2
READ_ADDRESS: fffff8006e03dd5b
MM_INTERNAL_CODE: 2
BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: theHunterCotW_F.exe

TRAP_FRAME: fffff680c5467a50 -- (.trap 0xfffff680c5467a50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=0000000000000001
rdx=ffff818189579410 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004a03dd54 rsp=fffff680c5467be0 rbp=ffff818189579410
r8=ffff818180ec7d10 r9=0000000000000000 r10=0000000000000003
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlAvlRemoveNode+0xc4:
fffff800`4a03dd54 851501000024 test dword ptr [fffff800`6e03dd5b],edx ds:fffff800`6e03dd5b=????????
Resetting default scope

MISALIGNED_IP:
nt!RtlAvlRemoveNode+c4
fffff800`4a03dd54 851501000024 test dword ptr [fffff800`6e03dd5b],edx

STACK_TEXT:
fffff680`c54677a8 fffff800`4a24a56f : 00000000`00000050 fffff800`6e03dd5b 00000000`00000000 fffff680`c5467a50 : nt!KeBugCheckEx
fffff680`c54677b0 fffff800`4a09f4d0 : 00078405`bd9bbfff 00000000`00000000 fffff680`c5467ad0 00000000`00000000 : nt!MiSystemFault+0x18d07f
fffff680`c54678b0 fffff800`4a20545e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffff680`c5467a50 fffff800`4a03dd54 : ffffab03`1f6b4390 00000000`00000001 00000000`00000000 fffff800`5ac63398 : nt!KiPageFault+0x35e
fffff680`c5467be0 fffff800`5ac64cff : 00000000`00000000 00000000`00000001 ffffab03`1f6b4358 ffff8181`80ec7d10 : nt!RtlAvlRemoveNode+0xc4
fffff680`c5467c30 fffff800`5ac669f0 : ffff8181`80ec7d10 00000000`00000001 ffff8181`89573510 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP::RemoveMultirangeFromTree+0x5f
fffff680`c5467c60 fffff800`5ac66127 : 00000298`8b000000 ffff8181`80ec7d10 ffff8181`89357ce0 ffff8181`89358520 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::MergeWithNeighborsIfPossible+0x5b0
fffff680`c5467d00 fffff800`5ac659b1 : ffffab03`1f6b4358 ffffab03`1f6b4398 ffff8181`80ec7dd8 00000298`89440000 : dxgmms2!VIDMM_RECYCLE_HEAP::IntegrateMultirangeIntoTrees+0x587
fffff680`c5467db0 fffff800`5ac886b5 : ffffab03`22138f10 ffff8181`7a566e30 ffff8181`809834e0 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Free+0xb1
fffff680`c5467df0 fffff800`5ac73eea : ffffab03`22138f10 00000000`00000004 ffffab03`22138f10 ffff8181`809834e0 : dxgmms2!VIDMM_GLOBAL::UncommitLocalBackingStore+0x171
fffff680`c5467e80 fffff800`5ac73bd5 : 00000000`00000000 ffff8181`00000000 00000000`40043d80 ffffab03`22138f10 : dxgmms2!VIDMM_GLOBAL::CloseOneAllocation+0x27a
fffff680`c5467fc0 fffff800`5ac11eaa : 00000000`00000000 ffff8181`7fad2de0 fffff680`c5468150 fffff680`00000003 : dxgmms2!VIDMM_GLOBAL::CloseAllocation+0xc5
fffff680`c5468010 fffff800`5a2373b9 : 00000000`00000000 fffff680`c5468150 00000000`00000000 00000000`00000000 : dxgmms2!VidMmCloseAllocation+0x1a
fffff680`c5468050 fffff800`5a236e0f : 00000000`00000000 fffff800`5a1f48fa ffff8181`801ae010 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x4c5
fffff680`c54681f0 fffff800`5a1f5020 : fffff680`c5468190 ffff8181`801ae010 00000000`00000000 ffff8181`801ae1f0 : dxgkrnl!DXGDEVICE::DrainAllocations+0x5f
fffff680`c5468250 fffff800`5a1f471c : ffff8181`801ae010 ffff8181`7f792ae0 00000000`0000000b 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState+0x148
fffff680`c5468290 fffff800`5a2246c8 : 00000000`00000000 fffff680`c54683c0 ffff8181`801ae010 ffff8181`801ae010 : dxgkrnl!ADAPTER_RENDER::DestroyDevice+0xd8
fffff680`c54682c0 fffff800`5a2254f9 : ffff8181`7fad2de0 00000000`00000000 ffff8181`7fad2de0 00000000`00000000 : dxgkrnl!DXGPROCESS::Destroy+0x494
fffff680`c5468530 fffff800`5a116841 : 00000000`00000000 ffffab03`22f04ed0 00000000`00000000 fffff800`4e46a2a8 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105
fffff680`c5468680 fffff800`4a402a4f : 00000000`00000000 ffffab03`1441af30 ffffab03`20bd2080 ffffab03`12897570 : dxgkrnl!DxgkProcessNotify+0x1a1
fffff680`c54686d0 fffff800`4a41d664 : ffffab03`20bd2000 ffffab03`20bd2080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
fffff680`c54687a0 fffff800`4a4b0fa2 : ffffab03`21fc54b8 00000000`00000000 fffff680`c5468990 00000000`00000000 : nt!PspExitProcess+0x70
fffff680`c54687d0 fffff800`4a4f5b88 : 00000000`c0000005 00000000`00000001 fffff680`c54689e0 000000ec`11230000 : nt!PspExitThread+0x5b2
fffff680`c54688d0 fffff800`4a00ef67 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`4a0a1836 : nt!KiSchedulerApcTerminate+0x38
fffff680`c5468910 fffff800`4a1fb880 : 00000000`00000000 fffff680`c54689c0 fffff680`c5468b80 00000297`00000000 : nt!KiDeliverApc+0x487
fffff680`c54689c0 fffff800`4a208d5f : ffffab03`21fc5080 ffffab03`21850de0 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff680`c5468b00 00007ffa`eb1ccdf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000ec`136ef9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`eb1ccdf4

SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_HEAP::RemoveMultirangeFromTree+5f
IMAGE_NAME: hardware
IMAGE_VERSION: 10.0.19041.1466
STACK_COMMAND: .cxr; .ecxr ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}
Followup: MachineOwner

[JeDagelijkseIntrovert]

Originally posted by Kaned Dragon:

Okay after some digging and hair pulling i got the DMP file checked, it came back with the below.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8006e03dd5b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8004a03dd54, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

This is the only information you need.
However this dump file was created in 2019 as indicated by Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z as well as the OS version being outdated.
Have you had any issues back then?

Given it also says "IMAGE_NAME" and "MODULE_NAME" hardware, even though it's about 2 years ago, and the crashes occurring more often.
It's most likely a memory card going faulty, and I would suggest having the guy get those checked.
You can do it yourself, but I would get those cards getting stress tested for about a hour on another rig that supports that amount of memory.
It is very important that the supply enough power as well as the motherboard being able to handle the amount of memory.

Before doing so however, if the crashes still occur without those memory cards, reinstall all drivers(do a clean install if possible).
If you have had a recent update with windows, rollback your computer to the previous state (if possible).
Also check your hard drives for a corrupt NTFS volume, you can do so by running(in command prompt as administrator): chkdsk <disk drive letter> /f /r
Replace '<disk drive letter>' with the disk you want to scan, most of the time you want to scan the one that has windows installed on it, so it would be: chkdsk c: /f /r

This can schedule a restart as the parameter /f requires the drive to be locked, meaning it may not be used.
/r Has the same functionality as /f, with the addition of checking physical disk errors.
/r Also has the functionality of recovering data if it finds any in a bad sector.

[Kaned Dragon]

Originally posted by INFP-T Slagroompje:

Originally posted by Kaned Dragon:

Okay after some digging and hair pulling i got the DMP file checked, it came back with the below.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8006e03dd5b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8004a03dd54, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

This is the only information you need.
However this dump file was created in 2019 as indicated by Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z as well as the OS version being outdated.
Have you had any issues back then?

Given it also says "IMAGE_NAME" and "MODULE_NAME" hardware, even though it's about 2 years ago, and the crashes occurring more often.
It's most likely a memory card going faulty, and I would suggest having the guy get those checked.
You can do it yourself, but I would get those cards getting stress tested for about a hour on another rig that supports that amount of memory.
It is very important that the supply enough power as well as the motherboard being able to handle the amount of memory.

Before doing so however, if the crashes still occur without those memory cards, reinstall all drivers(do a clean install if possible).
If you have had a recent update with windows, rollback your computer to the previous state (if possible).
Also check your hard drives for a corrupt NTFS volume, you can do so by running(in command prompt as administrator): chkdsk <disk drive letter> /f /r
Replace '<disk drive letter>' with the disk you want to scan, most of the time you want to scan the one that has windows installed on it, so it would be: chkdsk c: /f /r

This can schedule a restart as the parameter /f requires the drive to be locked, meaning it may not be used.
/r Has the same functionality as /f, with the addition of checking physical disk errors.
/r Also has the functionality of recovering data if it finds any in a bad sector.

Okay so got an update. In short my hardware was the problem. I recently got myself an SSD card, instead of sticking with the old disk drive. I Played all day today and so far no issues. Thanks for all you help Slagroompje !!!!.