Windows 10: Graphical glitch and BSOD on clean installed Windows 10.

Page 1 of 12 12311 ... LastLast
  1.    01 Aug 2015 #1

    Graphical glitch and BSOD on clean installed Windows 10.


    After installing my GPU driver I noticed my desktop background went fully black. I moused over my icons and they were all highlited. Eventually after I clicked it went away. Screenshot:

    Attachment 27346


    It then happened again and when I moused over the icons they graphically duplicated. Again, clicking on the Desktop fixed it. Screenshot:

    Attachment 27347


    I started up Edge and it didn't load up any webpages as if I was not connected to the internet, even though I was...Then I received a Critical_Process_Died blue screen after restarting for updates. Started back up and its working fine.

    UPDATE: Computer froze and received a MACHINE_CHECK_EXCEPTION error blue screen. I will add that log in aswell.
    Last edited by friendlybear; 01 Aug 2015 at 04:33.
      My ComputerSystem Spec


  2. Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       01 Aug 2015 #2

    A hard one to call here mate, you've encountered a 0x9C which isn't a supported crash after Vista and has been replaced by a 0x124. As you will see from reading the link it's hardware related but the dump isn't really giving anything away.

    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: fffff8020a5e1ba0
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    The other dump is a 0xEF which is making me question your hard drive but I can't be certain on that.

    Code:
    CRITICAL_PROCESS_DIED (ef)
            A critical system process died
    Arguments:
    Arg1: ffffe001b46fc840, Process object or thread object
    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    ----- ETW minidump data unavailable-----
    
    PROCESS_OBJECT: ffffe001b46fc840
    
    IMAGE_NAME:  svchost.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: svchost
    
    FAULTING_MODULE: 0000000000000000 
    
    PROCESS_NAME:  svchost.exe
    
    EXCEPTION_RECORD:  ffffd00025a6fb00 -- (.exr 0xffffd00025a6fb00)
    ExceptionAddress: ffffe001b4937840
       ExceptionCode: b4937840
      ExceptionFlags: ffffe001
    NumberParameters: 631700352
       Parameter[0]: 0000000000000000
       Parameter[1]: 00001fa202080000
       Parameter[2]: 00007ffed484dec8
       Parameter[3]: 002d0033002d0035
       Parameter[4]: 0000000000000000
       Parameter[5]: 000000cec0f6a6a0
       Parameter[6]: 000000cec12feef8
       Parameter[7]: 0000000000000001
       Parameter[8]: 000000cec0f69048
       Parameter[9]: 00007ff66114c000
       Parameter[10]: 0000000000000000
       Parameter[11]: 0000000000000000
       Parameter[12]: 0000000000000000
       Parameter[13]: 0000000000000000
       Parameter[14]: 0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0xEF
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xb4937840 - <Unable to get error code text>
    
    EXCEPTION_CODE: (NTSTATUS) 0xb4937840 - <Unable to get error code text>

    Running !process on Arg2 isn't particularly conclusive either from what I can see.


    Code:
    3: kd> !process ffffe001b46fc840 3
    GetPointerFromAddress: unable to read from fffff802155cc1c0
    PROCESS ffffe001b46fc840
        SessionId: none  Cid: 0710    Peb: 7ff66129f000  ParentCid: 02a0
        DirBase: 13af16000  ObjectTable: ffffc001de0d9940  HandleCount: <Data Not Accessible>
        Image: svchost.exe
        VadRoot ffffe001b47e6680 Vads 194 Clone 0 Private 1881. Modified 666. Locked 0.
        DeviceMap ffffc001ddd2d990
        Token                             ffffc001de0da060
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    fffff78000000000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         141096
        QuotaPoolUsage[NonPagedPool]      44216
        Working Set Sizes (now,min,max)  (5405, 50, 345) (21620KB, 200KB, 1380KB)
        PeakWorkingSetSize                22772
        VirtualSize                       2097267 Mb
        PeakVirtualSize                   2097821 Mb
        PageFaultCount                    70213
        MemoryPriority                    BACKGROUND
        BasePriority                      8
        CommitCharge                      2844
    
            *** Error in reading nt!_ETHREAD @ ffffe001b47e47c0

    So, coupling this with your BSODs over on Seven Forums I'm going to post a program of hardware stress and diagnostic checks so we can start rooting out the problematic piece of hardware. Read the instructions below carefully before running each step and if you have any questions feel free to ask, (you can use the User Tag feature to get my attention - @friendlybear ).




    Graphical glitch and BSOD on clean installed Windows 10. STOP 0x124 Troubleshooting Graphical glitch and BSOD on clean installed Windows 10.
    Read carefully before proceeding.


    warning   Warning
    If you're overclocking your system, revert back to stock clocks now.

    Note   Note
    Test the system once the overclock is removed before continuing with the steps outlined below.


    Part One: CPU Stress Test
    Part Two: MemTest86+ RAM Diagnostic
    Part Three: Hard Drive Diagnostics
    Part Four: GPU Stress Test




    Graphical glitch and BSOD on clean installed Windows 10. ONE Graphical glitch and BSOD on clean installed Windows 10.
     CPU TEST

    Run Prime95 to stress test your CPU. http://www.sevenforums.com/tutorials...t-prime95.html

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.





    Graphical glitch and BSOD on clean installed Windows 10. TWO Graphical glitch and BSOD on clean installed Windows 10.
     RAM TEST

    Run MemTest86+ to analyse your RAM. http://www.sevenforums.com/tutorials...memtest86.html

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.





    Graphical glitch and BSOD on clean installed Windows 10. THREE Graphical glitch and BSOD on clean installed Windows 10.
     HDD TEST

    Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html




    Graphical glitch and BSOD on clean installed Windows 10. FOUR Graphical glitch and BSOD on clean installed Windows 10.
     GPU TEST

    Run Furmark to stress test your GPU. http://www.sevenforums.com/tutorials...t-furmark.html

    Note   Note
    Run Furmark for around 30 minutes.
    warning   Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
      My ComputerSystem Spec

  3.    02 Aug 2015 #3

    @Boozad, I just ran the CPU stress test to start off and I noticed something peculiar...

    Attachment 27712

    My temperatures were normal although the fourth one was lower than the others. I decided to stop the test and await your advice.
      My ComputerSystem Spec


  4. Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       02 Aug 2015 #4

    I'm going to be out for most of today, I'll get someone to drop in to assist you further until I'm back.
      My ComputerSystem Spec


  5. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       02 Aug 2015 #5

    Hello, friendlybear, I will see if I can help. If you would, please fill out your system specs in as much detail as possible. Please include all components, including hard drives, PSU and CPU cooler. Also include the Manufacturer and model of the components. We occasionally have to look up components and need that info to do it. If you will look at your last post and click My System Specs in the bottom Left there will be a link to edit your system specs. Be sure to click save when finished. If you are unsure of what we would like, click my system specs at the bottom left of this post and see mine..

    If you are overclocking anything please set everything back to defaults.

    Prime95 acted the way it did because one of the cores shut down. If you will look at worker 4, you will see hardware failure detected. That does not necessarily mean the CPU. Several other things could be the cause. What was the highest temp you saw during the test? I trust you had a CPU Temp monitoring program open during the test. If not, do not run the test again until you get one. If you need some suggestions, I can provide a couple. Once I see your hardware specs, I will know more of what to advise you. If you have any questions, feel free to ask.
      My ComputersSystem Spec


  6. Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       02 Aug 2015 #6

    Thanks Steve, I'll drop back in when I'm back tonight. @friendlybear you're in more than capable hands with essenbe.
      My ComputerSystem Spec

  7.    02 Aug 2015 #7

    Hey there essenbe. I hope the information provided is now sufficient!

    As far as I know I am not overclocking anything, I remember checking the BIOS a while back to make sure my CPU wasn't OCed. I have checked Catalyst Control Center and my GPU is not overclocked at all.

    3 of the threads were running at ~55C but the fourth was just hitting 40C. I was running Real Temp to monitor temperatures

    EDIT: I just finished the SeaTools scan. Here is a screenshot. I think we're all clear in that department?

    Attachment 27755
    Last edited by friendlybear; 02 Aug 2015 at 08:12.
      My ComputerSystem Spec


  8. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       02 Aug 2015 #8

    OK, that looks good. We are just going to have to start doing some tests to see if we can find out what is going on. Hardware tests are long and tedious. I know, I have been there myself, too many times. So, if you are ready

    Please Run Memtest86+



    information   Information
    Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
    Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask
      My ComputersSystem Spec

  9.    02 Aug 2015 #9

    Ok I will run that before I go to bed and then get back to you tomorrow.

    One question, what will happen if it completes 3 hours before I wake up? Does it require a prompt so I can check if it discovered any errors? Thanks for your help!
      My ComputerSystem Spec


  10. Posts : 8,183
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       02 Aug 2015 #10

    No, it needs to run 8 complete passes, at a minimum. If you notice it has an error, stop the test. If it has an error and you don't notice it, it will be fine. It is just that even 1 error is a fail. So, no need to run it any longer. But if you do run it longer, it will hurt nothing. With 8 GB of ram, it should take 9-10 hours to run 8 passes. If you have any questions, feel free to ask.
      My ComputersSystem Spec


 
Page 1 of 12 12311 ... LastLast

Related Threads
Clean install - random BSOD in BSOD Crashes and Debugging
Hey guys Did a clean install this morning. I am getting the error INTERNAL_POWER_ERROR and it BSODs/reboots. This happens every 30-40 mins. I have installed and updated all drivers and installed the latest BIOS revision (which I don't normally do...
Clean install BSOD during sleep? in BSOD Crashes and Debugging
Just did a clean install of Windows 10 pro x64 last night. Everything was going well it seemed. Installed all my essentials and drivers. I put my PC to sleep last night. Woke up this morning and my PC was turned on for some reason, checked event...
25517 That's what I see on booting. I want to see the legacy screen. This is my BCDfile: Windows Boot Manager -------------------- identifier {bootmgr} device partition=C:
Hello! Today, I got a new monitor to add to my setup. After setting up the monitor, I noticed my old main monitor (now my secondary) has strange glitches. My monitors: Main: BenQ XL2420T @ 1920x180 145Hz on GTX 760 Secondary: Samsung T24C350...
Toolbar Glitch in General Support
Hi there If you've set the Auto hide on the bottom tool / taskbar it doesn't re-appear unless you point your mouse a little bit AWAY from the left hand corner. OK a Gripe but it is a bit irritating if you are used to pointing the mouse at the...
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:12.
Find Us