Please help me... Getting CONSTANT Error 132s back to back

Haniina-steamwheedle-cartel · July 30, 2020, 6:19pm

You can check my previous posts on the errors I have been having. I have been having them for a while now.

I was in a Horrific Vision and was getting constant crashes (Error 132s and then Error 123s). I installed the newest graphics driver for my Nvidia card (451.67) and then I started getting Error 123 crashes. I somehow finished the horrific vision completely by closing and re-opening repeatedly over 10+ times it seems after every crash…

I am only getting crashes in Horrific Visions and sometimes in the open world while I am flying or doing some world quest. I really need a fix for this please. It’s… beyond frustrating now.

By the way, all of these crashes started happening AFTER I had installed Windows 10 and started playing WoW on it. I never had crashes on Windows 7.

Here is the pastebin for my dxdiag and msinfo:

DxDiag
https ://pastebin.com/KdSGpk2r

MSInfo (Was too long so I had to half it and make two of them)
https ://pastebin.com/bNgGnP7t
https ://pastebin.com/v9PjEJrr

Please let me know what else you guys need from me.
Thank you.

EDIT 1:

I just realized that there is an error report folder in the WoW folder. From today only (2020/07/30), there are 15 error reports. Is there any way for me post or show you guys the txt docs for those error reports?

EDIT 2:

I will try to post all the txt docs (partials) from the error reports here if possible:

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020 12:45:02.929 AM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #123 (0x8510007b) This memory block has been corrupted by an out-of-bounds memory write.

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	13028
ThreadID:	12328

Memory corrupted -- d:\buildserver\wow\7\work\shared-checkout\branches\wow-patch-8_3_7-branch-fastpatch-0\wow\source\db\dbctypes.h 132

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception. Summary:>
ERROR #123 (0x8510007b) This memory block has been corrupted by an out-of-bounds memory write.
 Memory corrupted -- d:\buildserver\wow\7\work\shared-checkout\branches\wow-patch-8_3_7-branch-fastpatch-0\wow\source\db\dbctypes.h 132
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  2:02:32.183 AM
User:    
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	3648
ThreadID:	9664
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff7e4d4ae1f" referenced memory at "0x0000000000000090".
The memory could not be "read".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff7e4d4ae1f>("Wow.exe") <- DBG-ADDR<00007ff7e4d55fad>("Wow.exe") <- DBG-ADDR<00007ff7e5add177>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff7e4d4ae1f" referenced memory at "0x0000000000000090".
The memory could not be "read".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  8:35:05.323 AM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	6532
ThreadID:	4752
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff7e4d4ae1f" referenced memory at "0x0000000000000019".
The memory could not be "read".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff7e4d4ae1f>("Wow.exe") <- DBG-ADDR<00007ff7e4d55fad>("Wow.exe") <- DBG-ADDR<00007ff7e5add177>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff7e4d4ae1f" referenced memory at "0x0000000000000019".
The memory could not be "read".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020 12:28:30.880 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	8548
ThreadID:	4932
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff7e4d4add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff7e4d4add9>("Wow.exe") <- DBG-ADDR<00007ff7e4d55fad>("Wow.exe") <- DBG-ADDR<00007ff7e5add7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff7e4d4add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020 12:30:47.564 PM
User:    
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	13056
ThreadID:	13288
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff7e4d4add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff7e4d4add9>("Wow.exe") <- DBG-ADDR<00007ff7e4d55fad>("Wow.exe") <- DBG-ADDR<00007ff7e5add7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff7e4d4add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020 12:31:15.498 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	5728
ThreadID:	13352
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff7e4d4add9" referenced memory at "0x0000000000000019".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff7e4d4add9>("Wow.exe") <- DBG-ADDR<00007ff7e4d55fad>("Wow.exe") <- DBG-ADDR<00007ff7e5add7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff7e4d4add9" referenced memory at "0x0000000000000019".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:32:14.076 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #123 (0x8510007b) This memory block has been corrupted by an out-of-bounds memory write.

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	5052
ThreadID:	356

Memory corrupted -- d:\buildserver\wow\7\work\shared-checkout\branches\wow-patch-8_3_7-branch-fastpatch-0\wow\source\db\dbctypes.h 132

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ERROR #123 (0x8510007b) This memory block has been corrupted by an out-of-bounds memory write.
 Memory corrupted -- d:\buildserver\wow\7\work\shared-checkout\branches\wow-patch-8_3_7-branch-fastpatch-0\wow\source\db\dbctypes.h 132
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:40:10.665 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	7960
ThreadID:	1344
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:41:00.079 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	9148
ThreadID:	3692
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:41:55.729 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	2928
ThreadID:	4784
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:44:30.563 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	4420
ThreadID:	384
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:46:11.380 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	9648
ThreadID:	7508
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:49:21.480 PM
User:    
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	1376
ThreadID:	4424
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:50:13.782 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	5248
ThreadID:	6428
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

==============================================================================
World of Warcraft: Retail Build (build 35284)

Exe:      E:\World of Warcraft\_retail_\Wow.exe
Command:  "E:\World of Warcraft\_retail_\Wow.exe" -launcherlogin -uid wow
Time:     Jul 30, 2020  1:50:59.430 PM
User:     
Computer: DESKTOP-KQKIIBT
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program:	E:\World of Warcraft\_retail_\Wow.exe
ProcessID:	3480
ThreadID:	6368
Exception:	ACCESS_VIOLATION

The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".

<Exception.IssueType> Exception
<ExceptionType> Crash
<Exception.Summary:>
ACCESS_VIOLATION
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff6ee90add9>("Wow.exe") <- DBG-ADDR<00007ff6ee915fad>("Wow.exe") <- DBG-ADDR<00007ff6ef69d7ea>("Wow.exe") DBG-OPTIONS<>)
The instruction at "0x00007ff6ee90add9" referenced memory at "0x0000000000000090".
The memory could not be "written".
<:Exception.Summary>
------------------------------------------------------------------------------

Marionette-whisperwind · July 31, 2020, 1:09pm

I’m getting constant popups about Application Errors but the game continues to run. Blizz will eventually fix their F UP. They do it every Tuesday. Blame us on Wednesday. Finally admit they did on Thursday.

Haniina-steamwheedle-cartel · August 1, 2020, 4:36pm

Are you getting the Error 132s/123s by any chance? Or are the application errors different than those? I had these happen in Horrific Visions repeatedly every minute or so… It’s really annoying. I can’t do them 'cause of fear of my WoW crashing everytime I do it even though I really wanna do them.

Yindar-andorhal · August 1, 2020, 4:39pm

This is a bit out of my wheelhouse but since you haven’t gotten any other responses i’ll take a stab at a start.

While error 132 is pretty common and can be caused by lots of things, error 123 is pretty unusual. The only reference I can find to it suggested making sure any overlays you have are turned off, like discord, nvidia, windows game mode/game overlay are off. Then I’d also try switching the game to directx 11 or directx11 legacy mode.

Haniina-steamwheedle-cartel · August 1, 2020, 8:43pm

Thank you for replying.
I checked the error logs from my WoW folder and counted only one instance of where it showed Error 123. The rest are Error 132s. I assumed that I was getting multiple Error 123s but I was mistaken. Sorry about that.
When the multiple Error 132s were happening, they were occurring back to back, like only a minute or even less than a minute had gone by before WoW crashed with that error. And they all happened in a Horrific Vision. I don’t know why.
Today, there were 5 instances of Error 132s and all of them occurred while I was doing something else other than a Horrific Vision like I was flying, or was afk for a minute or two. Since I started getting the errors during the Horrific Visions, I have stopped doing them 'cause I don’t want to go through that again. And it’s extremely disruptive when it happens in the Horrific Visions. Even though I can start up WoW and log in to my character within 15 seconds, it’s still very annoying and frustrating… And I just dreaded every time I logged in again that it would crash again. Right now, the crashes are still in random time intervals, like it happens after an hour or after 10 minutes or after 30 minutes, something like that.

EDIT 1:

I forgot to mention that I also have DirectX 11 Legacy enabled and I still got the Error 132 crash.

EDIT 2:

I have been getting minor freezes as well while in-game. Like my screen would freeze for like 5 seconds and then everything would speed up to kind of “catch up” with the actual current time or state. It’s not due to overheating I think because I recently blew out the dust from my computer like a few weeks ago. And I have seen that the temperature doesn’t reach too high while playing when I have the temperature monitors running.

Yindar-andorhal · August 1, 2020, 11:50pm

Hmm. Ok so I read a bit about your issue from your other thread - seems like this isn’t too straightforward!

Anyway, error 123 is specifically indicating an issue with ram. So a couple of things to try. I would first check your windows install files - https://support.microsoft.com/en-ie/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system Then, northernlite has a few suggestions in this thread, I would try those 3. Please, what does this mean?!

Haniina-steamwheedle-cartel · August 2, 2020, 3:24am

I have done the DISM command in cmd and sfc /scannow and they didn’t find any problems as per your advice.

I have done the scan and repair through the Battle.net App and there were no problems found.

I have done the renaming of the folders and will see how it goes. Will run a horrific vision to see if I get any crashes. Can I download the add-ons that I was using or should I wait to see if I get any crashes without any add-ons first?

I will run the memory diagnostic tool overnight 'cause I think the extended one takes a really long while to do. I remember running it a few weeks ago and it getting stuck or maybe taking like a few minutes to even move 1% or something like that.

Also, for the RAM, I bought new RAM sticks (2x8 gb) like 2 weeks ago I believe 'cause I had only one 8 GB and it was some random ram stick I took from an old computer. I bought the Corsair ones, I forgot which model. Also, I only got the Error 123 crash only once… The rest were Error 132s.

Thank you though for all the advice .

Elocin-mugthol · August 2, 2020, 9:24am

Yeah, it’s best to test without them.

It will take a long time, yeah. You have the right idea

Haniina-steamwheedle-cartel · August 2, 2020, 1:10pm

I checked without add-ons after renaming the folders and I still got the Error 132 crash. So it rules out the add-ons I guess.

I forgot to do the memory diagnostic tool overnight so I’ll do it tonight before I go to bed.

I wanted to ask though… Even though I got new RAM sticks and installed them, would they be causing the Error 132s now? I intiially thought the old ones were causing issues so I bought new ones instead. Also, I was due to buying new ones since I didn’t like having only 8gb RAM.

EDIT 1:

I have tried DirectX 11 as the Grahpics API and now I am getting random 5-second minor freezes in-game. When it happens, my screen freezes and then 5 seconds after, everything gets sped up and catches up to what it would be after 5 seconds. I can still move my mouse around though but can’t do anything else with it.
I am gonna see if I am only getting minor freezes or if I get both freezes and Error 132 crashes and report back. Then I will try and test out DirectX 11 Legacy.

EDIT 2:

So I had DirectX 11 enabled. I kept on getting 5-second freezes after every few minutes it seemed. One time it happened when I took a portal in the druid class order hall and then it froze for a while. I had to alt-f4 and then try to re-open WoW. When I tried to, it said that my computer has run out of memory. I restarted Battle.net but closing it and then re-opening and I got a different error this time. It kept saying this error when I tried to relaunch WoW: “Your 3D accelerator card is not supported by World of Warcraft. For more information, please see the system requirements site.”
I am gonna try DirectX 11 Legacy now and see if that works. It’s really disappointing though that the only reason I upgraded from Windows 7 to Windows 10 was to use DirectX 12 so I can get a boost in FPS but I guess that is not happening now…

Caterpepi · August 2, 2020, 9:37pm

Hey, Haniina! Thank you for the details provided here! Checking on our end, there has been 9 different crashes which is a sign of system stability issues.

Checking over the system there were recent bluescreen crashes calling out specifcally the “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” error. This error could mean that there is a driver issue, hardware/firmware issues, memory issues, incompatible hardware with the current version of Windows, or hardware issues.

Because of these concerns and the bluescreen crashes recently, our support will be limited here and it’s recommended to contact a local technician to have them check out the system and these errors.

I think everyone here has already suggested what we would suggest in this situation. As a few personal suggestions, that are worth checking for overheating, overclocking that may have come factory overclocked or set in the BIOS, and checking the BIOS for any timing issues since it could cause similar issues like HPET or Speedstep settings.

Haniina-steamwheedle-cartel · August 3, 2020, 6:54pm

Thank you for replying, Caterpepi.
How do I check which hardware I have is overclocked or came factory overclocked? What do I check in the BIOS in regards to that?
Also, what are timing issues? How do I know if I have them?
And what is HPET and Speedstep settings?
Sorry I do not know much about these things.

I do want to say though that I haven’t had bluescreen crashes or BSODs for a while now (It’s been a few weeks now). I am only getting Error 132s now. I don’t know what I did to stop getting those BSODs but I haven’t gotten any for some time now.
I feel like DirectX is maybe causing some issues since Windows 7 only used DirectX 11 and I never had any crashes or BSODs while playing WoW but now, since I installed Windows 10 and been using DirectX 12, I started getting these errors. But that could be just coincidence. I have already tried all 3 options in the Graphics API settings (DirectX 12, DirectX 11 and DirectX 11 Legacy). I got the Error 132s still with all 3 settings. I did get a CTD (Crash to Desktop) without any error messages on DirectX 11 Legacy and for an hour or so, I didn’t get any Error 132 crashes so I thought maybe that fixed it but it didn’t unfortunately.

EDIT:

There is something else that has been happening but I don’t know if it is something related or not. I have been getting these “ding” sounds while playing WoW and a pop-up or a Windows notification happens on the bottom right corner saying something like that I can now safely remove the removable hard drives that I have and it mentioned my HDD which is drive D: for me. Is this something concerning or related by any chance?

Caterpepi · August 3, 2020, 9:00pm

The windows pop up error is usually for USB devices. If the D drive isn’t a removable HDD and it has WoW installed, it can definitely be a concern. This could indicate some issues with the drive, motherboard, sata cables, or windows. The hardware concerns and BIOS configurations are not within Blizzard’s technical support, but some suggestions to check out if you feel comfortable with doing so. As recommended before, you’ll want to discuss this problem and address the bluescreen crashes with a local technician to find the culprit thats causing these issues.

Haniina-steamwheedle-cartel · August 3, 2020, 9:12pm

The D drive (HDD) isn’t a removable drive I think, like it’s inside the computer connected to the motherboard through one of those wide and thin cables. My WoW is installed on a SSD (E: Drive) while Windows 10 is installed on another SSD (C: Drive).

I am not having any bluescreen crashes anymore. I am only getting Error 132s for at least 3 weeks now I think. Are you saying that the Error 132s are a type of bluescreen crash? Sorry, I am confused a bit on this.

EDIT:

I am remembering now that I did overclock my Intel Processor but it was many years ago, like maybe 5(?) years ago but I don’t remember if I restored it back to default setting or not. I went into BIOS and opened the overclock tab… Here is a picture of it:

https ://ibb.co/cyrbmSq

Is there anything there that I should change? I remember and at the same time don’t remember what I exactly did on there.

I do wanna ask though… Does installing Windows 10 use my hardware in a different way than Windows 7 was using? The reason I ask is because I did not have any crashes whatsoever on Windows 7 and everything ran fine in regards to playing WoW but once I installed Windows 10 and installed WoW on it after, I started having problems.

Caterpepi · August 3, 2020, 10:09pm

Hey, Haniina! The error#132 is not a type of bluescreen crash. However, when we do see multiple different types of Error#132 crashes as seen here. It does indicate system stability issues like bluescreen crashes, live kernel events, windows level issues, etc. In this situation, with the bluescreens that happened recently on the system, it definitely does point to some concerns with the system’s stability. It may run just fine in the mean time, but there is an underlying issue that should be addressed.

We cannot assist with BIOS settings, you will need to contact a local technician in regards to hardware, BIOS settings, bluescreen crashes, and so on. Windows 10 does have different requirements than Windows 7, so it’s entirely possible that it may function or work different than it did on Windows 7. There may have been some issues upon installation as well with the Windows installation.

These concerns and troubleshooting the issue is outside of our scope though. You may have better luck and clear answers with Microsoft support or a local technician once they can check out the system in depth or check for event logs or dump files created with the errors the system shows.

Haniina-steamwheedle-cartel · August 4, 2020, 11:46am

Oh ok. Well, thank you so much for replying back again and for the advice.

I believe I have found the problem that is causing the Error 132s. I played WoW for almost an hour on my iGPU instead of my Nvidia graphics card by changing the in-game setting to using the iGPU that I have instead of my Nvidia card. I ran two instances (Mythic+s) and found that I did not get any crashes at all. I would usually get one or sometimes two crashes in the same one instance run but after running on the iGPU, I didn’t get any. I am guessing you remember my previous thread I made regarding the BSODs and they were mostly pointing towards a Nvidia driver file I think. It turns out that my Nvidia card is the issue even though it is not as old as my motherboard or CPU. I now need to buy a new graphics card and decide whether to buy a Nvidia one or an AMD one. Am I right in this conclusion or assumption? I mean that is the only logical explanation I can think of at the moment and I was also hoping not to go out looking for a local technician to look into my system 'cause of the whole pandemic thing.

Caterpepi · August 4, 2020, 9:57pm

Hey, Haniina! Thanks again for the details! Glad that you were able to find the source of the issue and hopefully, its a solid workaround until the problem with the Nvidia graphics is found

We can’t really comment on hardware replacements or if you may need a new one. I completely understand wanting to try to figure this out on your own given the current situation. It is a last resort kind of situation worth looking into and I’m sure there are some places who have specific guidelines or steps to make sure they abide by social distancing for safety reasons.

As a few additional suggestions from me personally, since these are not all supported, it may be worth seeing if a CMOS reset may help if its just some silly motherboard issue recognizing the PCI-E slots properly. Do be careful as this can brick the motherboard if not done correctly. Some newer motherboards just have a battery that can be taken out and placed back in, but older ones do require jumper pins which is a bit risky. I’d also see if the debug mode may help in this situation if the card is factory overclocked. A DDU may be worth a try as well, if not done so already, and seeing if rolling back the drivers is an option. It may also help to check out an HWMonitor to make sure the system isn’t overclocked or overheating.

Hardware issues are quite tricky to determine the exact cause without having the device in our hands physically, so we’re a bit limited here. If anyone else in the household has a graphics card or a friend who can drop off a spare, you could temporarily place in your system and see if you run into similar problems. This should help determine if there is a hardware issue with the graphics card, or if it may be something on the motherboard like the PCI-E slots. Remember to use the DDU tool to cleanly remove the current drivers after you try the temporary one if you can.

You can also see if Nvidia, Microsoft support or other hardware forums may be able to take a look at any event logs or dump files to give you a better idea if the GPU may be malfunctioning. It may be something really simple like the BIOS is set to some sort of gaming or performance setting to increase the overclocking.

Sorry that we’re a bit limited here for this issue, but hopefully some of this will help with narrow down the cause a bit further for you or give you some direction.

Zungar-silver-hand · August 4, 2020, 10:47pm

You should check the warranty on the card you have before buying anything. Some manufacturers have really good warranties, and then you might only be out shipping instead of a new card. See what your options are there, since you have an igpu and the computer will remain functional.

Abena-area-52 · June 21, 2021, 10:53pm

I agree it is on nvidia’s end so gonna see what they can do