Access Violation

Support Technical Support
1

Hi All - I’m tying to figure out what exactly is causing my issue. It started last night where i had one random D/C and chalked it up new patch. Then this morning, I started to get all sorts of access violation errors in combat. The most recent one was when I was in LFR about to toss a shield at a bunch of Imps. It is a little frustrating. Everything was just fine prior to the new patch.

I made sure all the drivers for my video card were updated (clean installs) and there are no new drivers for any of my PC parts (that I’m aware). The system was just built in early July as I needed a new one as my old rig would not run TWW.

I’ve also tried uninstalling wow, removing WoWUp and the weak aura companion, deleting the wow folder after it was uninstalled, and starting a fresh install. I went add-on by add-on making sure all were up to date and none were flagged as outdated by the Game. It worked well for a bit and then I got the most recent combat crash. I turned off all add-ons and ran a dungeon and then just sitting in Valdraken, it just randomly had another access-violation crash.

The combat one:

Exception: ACCESS_VIOLATION - The instruction at “0x00007ff75786ddcd” referenced memory at “0xffffffffffffffff”.
The memory could not be “read”.
ProcessID: 100204
ThreadID: 100904

The crash in Val:

Exception: ACCESS_VIOLATION - The instruction at “0x00000000ffffffff” referenced memory at “0x00000000ffffffff”.
The memory could not be “executed”.
ProcessID: 105092
ThreadID: 106204

I do have a 4090, a ROG Maximus Z790 Dark Hero MB, 96G of RAM, and a 14900KS. I’m assuming the response will be the 14900KS. The CPU temps are within range (will spike up to about 70). The computer builder put it thought a 24 hours burn in, and there were no bad memory modules and no issues with any of the components. The from the task manager in windows the base is 3.2 and shows anywhere from Several of the other posts suggested to lower the voltage or possible reduce the turbo stuff from intel, but as far as I can tell it appears that was already done.

I’m at a loss here as the was no instability or any issues prior to the patch. Would it help to post the rest of the crash report?

2

The 13th and 14th gen intel chips appear to have major stability issues. Thats just an Intel fault at this time. Lots of info on the web, including some companies reporting a 100% fail rate on those chips with unreal engine.

1 Like
3

I understand there are stability concerns with that processor and lots of failures. I would presume that if the processor was going bad i would see other issues in using the computer. There are no other issues (no blue screen of death, no hang ups, etc) only on WoW. That is why I don’t want to 100% jump to just say ‘oh the processor’. When i look at the issue the only variable that has changed the WoW patch.

I’m hoping I can get some clarity in terms of the bug report to see if potentially it is patch related/WoW client or truly that it is the processor or possibly both.

1 Like
4

The only variable you have identified is the wow patch. MS updates windows on Tuesdays as well.

It could be the cumulative usage has now made the chip unstable.

Post a dxdiag or file an actual ticket with blizzard. The memory errors aren’t specific enough for diagnosis.

5

The last installed Microsoft update (outside of defender definitions) was a cumulative updated (not a cumulative preview). I’m really trying to find an answer as nothing is adding up and I’ve hit the ceiling of things i know to look and check.

The excerpts of the DXDiag (as it wont let me post the full text) does not show any problems found and does show a few WER items at the bottom. Outside of the WoW.exe ones I’m not 100% sure what any of that means. I have submitted a ticket to blizz and did ask the tech support of the folks that built my PC to see if there is anything I can try to see if it processor (trying to cover all bases). I do appreciate any suggestions.

DxDiag Notes

  Display Tab 1: No problems found.
  Display Tab 2: No problems found.
    Sound Tab 1: No problems found.
    Sound Tab 2: No problems found.
    Sound Tab 3: No problems found.
    Sound Tab 4: No problems found.
    Sound Tab 5: No problems found.
      Input Tab: No problems found.

Diagnostics

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1352890927756274138, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Get-AppxVersion.exe
P2: 1.7.5.0
P3: aa977faa
P4: clr.dll
P5: 4.8.9256.0
P6: 665a83c0
P7: c0000005
P8: 000c27a8
P9:
P10:

+++ WER1 +++:
Fault bucket 1721784278893547155, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Wow.exe
P2: 11.0.0.55824
P3: 66a0ace8
P4: StackHash_2264
P5: 0.0.0.0
P6: 00000000
P7: PCH_8A_FROM_unknown+0x0000000000000000
P8: c0000005
P9: 0000000000000008
P10:

+++ WER2 +++:
Fault bucket 1250779575600630842, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: powershell.exe
P2: 10.0.22621.3085
P3: aab1e5c4
P4: clr.dll
P5: 4.8.9256.0
P6: 665a83c0
P7: c000001d
P8: 00031d88
P9:
P10:

+++ WER3 +++:
Fault bucket 1673470298428199136, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: powershell.exe
P2: 10.0.22621.3085
P3: aab1e5c4
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_A9_FROM_ntdll+0x0007715C
P8: c0000005
P9: 00000008
P10:

+++ WER4 +++:
Fault bucket 1250779575600630842, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: powershell.exe
P2: 10.0.22621.3085
P3: aab1e5c4
P4: clr.dll
P5: 4.8.9256.0
P6: 665a83c0
P7: c000001d
P8: 00031d88
P9:
P10:

+++ WER5 +++:
Fault bucket 1673470298428199136, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: powershell.exe
P2: 10.0.22621.3085
P3: aab1e5c4
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_A9_FROM_ntdll+0x0007715C
P8: c0000005
P9: 00000008
P10:

+++ WER6 +++:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: powershell.exe
P2: 10.0.22621.3085
P3: aab1e5c4
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_A9_FROM_ntdll+0x0007715C
P8: c0000005
P9: 00000008
P10:

+++ WER7 +++:
Fault bucket 1548927743672654260, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Wow.exe
P2: 11.0.0.55824
P3: 66a0ace8
P4: StackHash_0000
P5: 0.0.0.0
P6: 00000000
P7: PCH_84
P8: c0000005
P9: 0000000000000008
P10:

+++ WER8 +++:
Fault bucket 2018705255464310314, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Wow.exe
P2: 11.0.0.55824
P3: 66a0ace8
P4: Wow.exe
P5: 11.0.0.55824
P6: 66a0ace8
P7: c0000005
P8: 00000000002fa408
P9:
P10:

+++ WER9 +++:
Fault bucket 1587783439422152192, type 5
Event Name: StoreAgentSearchUpdatePackagesFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;DSIC
P2: 803fb005
P3: 22631
P4: 3880
P5: Windows.Desktop
P6: M
P7:
P8:
P9:
P10:

6

Post the whole dxdiag to pastein and post the link here, using the preformatted text option if it won’t let you post a link.

`Tomshardware.com`

For instance

1 Like
7

That’s a lot of Windows errors. Curious to see the full report.

8

I was having this problem as well, 13900k cpu. Wow was the only game I played that had an issue. The only other software with issues was the occt power test, which would fail very quickly, sometimes with a blue screen or even a reset. Lowering my cpu multiplier would get things stable for a while, then wow would start crashing again. I got an rma and things are good so far. It might be a good idea to wait until the microcode update Intel says is coming soon to do an rma though as some people think the problem permanently damages CPUs.

9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.