BSOD while playing world of warcraft

Page 1 of 2 12 LastLast

  1. Posts : 9
    windows 10
       #1

    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
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    No symbols available for build 14393.447 unfortunately so I can't get any useful info out of the dump. This is a Microsoft problem that they need to fix.

    Code:
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*G:\Symbols
    Symbol search path is: SRV*G:\Symbols
    Executable search path is: 
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 10 Kernel Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
    Machine Name:
    Kernel base = 0xfffff803`cd691000 PsLoadedModuleList = 0xfffff803`cd996060
    Debug session time: Sat Nov 12 07:47:08.375 2016 (UTC - 5:00)
    System Uptime: 0 days 18:21:56.062
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
      My Computers


  3. Posts : 9
    windows 10
    Thread Starter
       #3

    I did a fresh install of windows 10 and have crashed twice since here is a who crashed report i hope this helps find the issue

    On Thu 17/11/2016 5:05:32 PM your computer crashed
    crash dump file: C:\Windows\Minidump\111716-3875-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
    Bugcheck code: 0x1 (0x7FFF25B357A4, 0x0, 0x2033, 0xFFFFC90159482B00)
    Error: APC_INDEX_MISMATCH
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that there has been a mismatch in the APC state index.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 17/11/2016 5:05:32 PM your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1 (0x7FFF25B357A4, 0x0, 0x2033, 0xFFFFC90159482B00)
    Error: APC_INDEX_MISMATCH
    Bug check description: This indicates that there has been a mismatch in the APC state index.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My Computer


  4. Posts : 9
    windows 10
    Thread Starter
       #4

    also here is a new DM log done today
      My Computer


  5. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #5

    The file reveals the following:
    Code:
    BugCheck 1, {7fff25b357a4, 0, 2033, ffffc90159482b00}
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExitPico+194 )
    Bugcheck 1 is an APC_INDEX_MISMATCH (1) but I am not very familiar with this.

    All I can suggest is that you try to run Driver Verifier to see if it will reveal any drivers that are misbehaving. This is not for the faint-hearted so if you are not familiar with this read through the following tutorial and note all the warnings. Make sure you have created restore points and backups. Do not run for more than about 24 hrs as that should be long enough to pick up any driver errors and then post back with the results.

    https://www.tenforums.com/tutorials/5470-driver-verifier-enable-disable-windows-10-a.html
      My Computers


  6. Posts : 9
    windows 10
    Thread Starter
       #6

    thanks Phil i will run that later today when i get home
      My Computer


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #7

    Phil, are you able to read the dump and get good symbol resolution? All I get is symbol erros.
      My Computers


  8. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #8

    Ztruker said:
    Phil, are you able to read the dump and get good symbol resolution? All I get is symbol erros.
    The symbol server was playing up at first but eventually I started to get some meaningful results.
      My Computers


  9. Posts : 9
    windows 10
    Thread Starter
       #9

    i've been running driver varifier for 12 hours so far no crash i'm about to go to bed ill leave it running overnight, is there anything else i can try if this doesn't help?
      My Computer


  10. Posts : 9
    windows 10
    Thread Starter
       #10

    I ran driver varifier for 20 hours no BSOD at all
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:07.
Find Us




Windows 10 Forums