Windows 10: BSOD while playing World of Warcraft

When playing World of Warcraft my game crashes randomly. Sometimes resulting in a BSOD like this.

Minidump https://1drv.ms/u/s!AkRIjjX48IYVgo1-AZWkmnlKdvisYQ?e=YXrNJD

Please help me resolve this! I do not know which driver is causing this issue.

1. I have checked windows memory diagnostics
2. I have checked the disk diagnostics
3. I have reinstalled windows
4. I have reinstalled gpu driver manually multiple times clean install

Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 18362 MP 12 procs Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff800`35400000 PsLoadedModuleList = 0xfffff800`35848190 Debug session time: Fri Jul 10 11:11:55.768 2020 UTC + 2:00 System Uptime: 0 days 23:04:02.439 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ Loading User Symbols PEB is paged out Peb.Ldr = 00000000`00f76018. Type ".hh dbgerr001" for details Loading unloaded module list .................... For analysis of this file, run !analyze -vnt!KeBugCheckEx: fffff800`355c23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff585`427afc60=000000000000001e 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED 1e This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffff80000003, The exception code that was not handled Arg2: fffff8003550c0c8, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000fffff8003559, Parameter 1 of the exception Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5905 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOPPMCSMOLD Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 9357 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffff80000003 BUGCHECK_P2: fffff8003550c0c8 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8003559 EXCEPTION_PARAMETER2: 0000fffff8003559 BLACKBOXBSD: 1 !blackboxbsd BLACKBOXNTFS: 1 !blackboxntfs BLACKBOXPNP: 1 !blackboxpnp BLACKBOXWINLOGON: 1 PROCESS_NAME: Battle.net.exe STACK_TEXT: fffff585`427afc58 fffff800`3561a02b : 00000000`0000001e ffffffff`80000003 fffff800`3550c0c8 00000000`00000000 : nt!KeBugCheckEx fffff585`427afc60 fffff800`355d431d : fffff585`427b03e0 fffff585`427b0361 00000000`00040293 fffff800`35450d8d : nt!KiDispatchException+0x18c3ab fffff585`427b0310 fffff800`355cdcd6 : 00000000`00000001 fffff585`00001f80 00000000`427b0c10 fffff585`427b0b70 : nt!KiExceptionDispatch+0x11d fffff585`427b04f0 fffff800`3550c0c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBreakpointTrap+0x316 fffff585`427b0680 fffff800`3559d325 : 00000000`00000000 fffff585`427b1900 00000000`00000000 fffff585`427b0ca0 : nt!KeCheckStackAndTargetAddress+0x49 fffff585`427b06b0 fffff800`355cb192 : fffff585`427b1900 fffff585`427b0c90 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0x45 fffff585`427b0720 fffff800`35489855 : 00000000`00000017 00000000`00000000 fffff585`427b0c90 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12 fffff585`427b0750 fffff800`3548ddee : fffff585`427b1688 fffff585`427b13d0 fffff585`427b1688 ffffdc87`936c2860 : nt!RtlDispatchException+0x4a5 fffff585`427b0ea0 fffff800`355d431d : ffffd56a`b55aa000 fffff585`427b1730 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e fffff585`427b1550 fffff800`355d0503 : ffffdc87`91a59080 ffffdc87`8dbf7d50 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d fffff585`427b1730 00000000`00000000 : fffff585`427b1b80 fffff800`35499ef7 00000000`00000004 00000000`00000004 : nt!KiPageFault+0x443 SYMBOL_NAME: nt!KeCheckStackAndTargetAddress+48 MODULE_NAME:nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 48 FAILURE_BUCKET_ID: 0x1E_80000003_nt!KeCheckStackAndTargetAddress OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {8bf4701b-5b4d-2023-a998-fc7dbbdaa46f} Followup: MachineOwner --------- 6: kd> !blackboxbsd Stream size mismatch expected = 192, read = 168

:)

 

Constant BSODs while playing World of Warcraft

I have constant BSODs while playing World of Warcraft. I do not have BSODS at any other time.

Sometimes the BSOD message is: IRQL NOT LESS OR EQUAL
Other times: KERNAL SECURITY CHECK FAILURE

Any help is appreciated. Ive been having this problem for month and I'm at my wits end.

Thanks in advance for the help!

 

BSOD while playing world of warcraft

I have been getting ingame crashes in world of Warcraft for a few weeks now and also chrome is crashing the blizz techs have told me it may be a corrupt windows instillation so I did a fresh reinstall of windows 10 the other day and I have had a few BSOD they seem fairly random and not only when I'm playing games I missed the error code on the last crash but I will get it if I BSOD again I have attached the file with dxdiag etc
Thanks in advance for any help on this issue

 

[SOLVED] Multiple random BSODs, all pointing to the kernel


No BSODs yet but I haven't been playing World of Warcraft which I suspect to be a possible cause.

Was the driver verifier step necessary or just a suggestion?