Page 1 of 3 123 LastLast

  1. Joined : Oct 2016
    Posts : 13
    windows 10
       31 Oct 2016 #1

    BSoD's while playing WoW and forum trawling


    I had a few BSoD's while doing many different thing's such as reading forums and playing world of Warcraft.

    while searching the web for solutions for the BSod's none of them seem to work they normally suggest scanning the computer for both virus's and malware. updating drivers, I have even tried things like using the driver verifier, memory diagnostics tool and the scf scannow command and nothing has been picked up. i have even tried reinstalling windows 10 but while keeping my personal files this did't work either.

    I'm hoping that some one can have a look at the dump files i have attached to help me determine the source of the problem problem
    BSoD's while playing WoW and forum trawling Attached Files
      My System SpecsSystem Spec


  2. Joined : Apr 2014
    Space coast of Florida
    Posts : 4,062
    Windows 10 Pro X64 14393.105
       01 Nov 2016 #2

    Latest dump indicates a problem with aswMonFlt.sys, which belongs to your Avast anti-virus software.
    Code:
    BugCheck A, {0, 2, 1, fffff8033a4cd693}
    *** WARNING: Unable to verify timestamp for aswMonFlt.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
    Please uninstall it and run with the built-in Windows Defender for now and see if that resolves the problem. If it does, you can stay with Windows Defender, which is what I use, along with Malwarebytes amti-malware and anti-exploit or try the latest Avast or a different AV program.
      My System SpecsSystem Spec


  3. Joined : Oct 2016
    Posts : 13
    windows 10
       01 Nov 2016 #3

    thanks for that i'll try that hope it works.

    could you tell me what error that was making as i got a 2 blue screens today both of with the same stopcode wjich was machine check exception.


    if this was not the one that was caused by avast i'll happily get another attachment for you.

    if necessary here is the attachment with the two dumps form today
    BSoD's while playing WoW and forum trawling Attached Files
    Last edited by allan2; 01 Nov 2016 at 18:14.
      My System SpecsSystem Spec


  4. Joined : Apr 2014
    Space coast of Florida
    Posts : 4,062
    Windows 10 Pro X64 14393.105
       02 Nov 2016 #4

    Uninstall Avast then see if you get any more BSODs. If yes, re-run DM_Log_collector and post the zip.
      My System SpecsSystem Spec


  5. Joined : Oct 2016
    Posts : 13
    windows 10
       02 Nov 2016 #5

    after uninstalling avast i got 2 more blue screens tonight attaching the log files now

    because of the times its the 2 dated 02/11/16 and 03/11/16
    BSoD's while playing WoW and forum trawling Attached Files
      My System SpecsSystem Spec


  6. Joined : Apr 2014
    Space coast of Florida
    Posts : 4,062
    Windows 10 Pro X64 14393.105
       02 Nov 2016 #6

    The 11/3 dump shows a problem with nvlddmkm.sys
    Code:
    BugCheck 19, {20, ffff940e4adeb450, ffff940e4adeb4f0, 40a001b}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+82f26 )
    Remove and install latest Nvidia drivers:
    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    You have 375.63 while there is a 375.70 available.
    See if that gets rid of the problem.
      My System SpecsSystem Spec


  7. Joined : Oct 2016
    Posts : 13
    windows 10
       03 Nov 2016 #7

    ok ill do that what about the 11/2 dump as its the same stop code as the other 3 dumps there?
    Last edited by allan2; 03 Nov 2016 at 17:15.
      My System SpecsSystem Spec


  8. Joined : Oct 2016
    Posts : 13
    windows 10
       03 Nov 2016 #8

    ok this is really frustrating 2nd time tonight i've had this machine_check_exception im praying that it isn't speeding up. i mean the amount of times i get this error per day
    BSoD's while playing WoW and forum trawling Attached Files
      My System SpecsSystem Spec


  9. Joined : Apr 2014
    Space coast of Florida
    Posts : 4,062
    Windows 10 Pro X64 14393.105
       03 Nov 2016 #9

    Both of the latest dumps indicate a hardware failure, Machine Check Exception, as does the 11/2 and one of the 11/1 dumps.
    Code:
    MACHINE_CHECK_EXCEPTION (9c)
    A fatal Machine Check Exception has occurred.
    KeBugCheckEx parameters;
        x86 Processors
            If the processor has ONLY MCE feature available (For example Intel
            Pentium), the parameters are:
            1 - Low  32 bits of P5_MC_TYPE MSR
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of P5_MC_ADDR MSR
            4 - Low  32 bits of P5_MC_ADDR MSR
            If the processor also has MCA feature available (For example Intel
            Pentium Pro), the parameters are:
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
        IA64 Processors
            1 - Bugcheck Type
                1 - MCA_ASSERT
                2 - MCA_GET_STATEINFO
                    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
                3 - MCA_CLEAR_STATEINFO
                    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
                4 - MCA_FATAL
                    FW reported a fatal MCA.
                5 - MCA_NONFATAL
                    SAL reported a recoverable MCA and we don't support currently
                    support recovery or SAL generated an MCA and then couldn't
                    produce an error record.
                0xB - INIT_ASSERT
                0xC - INIT_GET_STATEINFO
                      SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
                0xD - INIT_CLEAR_STATEINFO
                      SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
                0xE - INIT_FATAL
                      Not used.
            2 - Address of log
            3 - Size of log
            4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
        AMD64 Processors
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    Arguments:
    Arg1: 0000000000000000
    Arg2: fffff8037115cba0
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    I can't find much info on it. just this so far: Bug Check 0x9C: MACHINE_CHECK_EXCEPTION - Windows 10 hardware dev
    This may or may not be a CPU problem. Try running PRIME95 to stress the CPU, see if that forces a failure. ==================================================
    Follow this tutorial to stress test your CPU:
    Prime95 - Stress Test Your CPU - Windows 10 Forums
    If that doesn't show us anything try enabling Driver Verifier: ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.
    Driver Verifier - Enable and Disable in Windows 10
    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.
    Warning: It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.
    Always create a Restore Point prior to enabling Driver Verifier.
    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My System SpecsSystem Spec


  10. Joined : Oct 2016
    Posts : 13
    windows 10
       4 Weeks Ago #10

    i tryed running prime last night i didnt get a blue screen but one of the cores of my cpu failed in the first minuet and the motherboard temp was to high it was running at about 84-89c dipping at periods to 75 where it should be for a second then going back up currently have the verifier running in the background. will update once the verifier is done
      My System SpecsSystem Spec


 
Page 1 of 3 123 LastLast


Similar Threads
Thread Forum
BSOD While playing BF1
Hey guys. Ive been getting alot of BSODs while playing bf1. Doesnt seem to happen with any other game. I cant seem to finish a match without it crashing. Thanks for any help107421
BSOD Crashes and Debugging
Solved BSOD playing playing Tom Clancy's Division
happens when im play division and when coping files from one HDD to another
BSOD Crashes and Debugging
BSOD While playing lol
Hello, My names Tristen and I've been getting BSOD ever since I built my computer about a month ago. First I got them all the time, but now not so much but still gets annoying. Happens when I play League of Legends and I continue to get Bugsplats...
BSOD Crashes and Debugging
Solved BSOD playing video games such as Cs:Go etc. Error, Random BSOD's
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that. System Information Bellow Intel Core i5-6600K 3.5Ghz @ 3.5 GeForce GTX960 2gb GDDR5, Physx CUDA 1TB Harddisk 7200RPM 8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
BSOD Crashes and Debugging
BSoD while playing ARK
I can usually play for a couple hours and then it will just randomly crash. I used whocrashed and it said the problem was probably a driver and not a hardware problem.41772
BSOD Crashes and Debugging
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 21:00.
Find Us
Twitter Facebook Google+



Windows 10 Forums