1. #1

    Join Date
    Feb 2012
    Posts
    2,085
    Blog Entries
    7

    Unable to get current machine context, Win32 error 0n30 GetContextState failed, 0x800

    I get this a lot recently when debugging dumps:
    Unable to get current machine context, Win32 error 0n30
    GetContextState failed, 0x8007001E
    It seems mostly when I debug dumps with AMD processors - but today I got it with a system that had an i5
    I'm using 10.0.15063.468 WinDbg and kd.exe
    When using the new Windows Store version of WinDbg Preview (10.0.16365.1002) I get what I presume to be the correct results

    Not much helpful on the web, and ntdebugging blog hasn't posted anything since January of 2016


    From this topic: IRQL NOT LESS OR EQUAL with Netgear Wifi adapter - Windows Crashes, BSOD, and Hangs Help and Support
    OP identified USB WiFi device as being the problem
    Netgear scmndisp.sys dates from 2007 - and I often see this when there are USB WiFi device problems.

    kd.exe (10.0.15063.468) finds nt to be at fault (using writhziden's app)
    WinDbg Preview (10.0.16365.1002) finds scmndisp.sys to be at fault


    Thoughts/ideas/suggestions/discussion?


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Age
    21
    Posts
    315
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        1920 x 1080 @ 60 Hz
      • Operating System:
        Windows 10 Pro

    Re: Unable to get current machine context, Win32 error 0n30 GetContextState failed, 0

    Same here, I stay with 10.0.14321.1024.

  3. #3
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,465
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: Unable to get current machine context, Win32 error 0n30 GetContextState failed, 0

    Does it happen with both Mike's app + Windbg GUI?

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  4. #4

    Join Date
    Feb 2012
    Posts
    2,085
    Blog Entries
    7

    Re: Unable to get current machine context, Win32 error 0n30 GetContextState failed, 0

    Yes it does. The only "solution" that I've found from others is to revert to a previous version haven't tried it myself yet.

    EDIT: I'm having problems finding older versions. Any ideas/links?

    EDIT2: Currently ripping out all WDK/SDK/Debugging Tools for Windows installations. I didn't realize how much crud I'd accumulated!!!

  5. #5
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Age
    21
    Posts
    315
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        1920 x 1080 @ 60 Hz
      • Operating System:
        Windows 10 Pro

    Re: Unable to get current machine context, Win32 error 0n30 GetContextState failed, 0

    Download of 10.0.14321: <removed>
    Last edited by axe0; 09-29-2017 at 09:23 AM. Reason: Removed link
    usasma and MichaelB say thanks for this.

  6. #6

    Join Date
    Feb 2012
    Posts
    2,085
    Blog Entries
    7

    Re: Unable to get current machine context, Win32 error 0n30 GetContextState failed, 0

    Solved it! Now running kd.exe v10.0.14321.1024 and it doesn't have the problem
    Had to download the WDK for 1607 from here: Download the Windows Driver Kit (WDK) and related tools – Windows 10 Hardware Dev Center
    Then had to install the entire WDK (I didn't want to install Visual Studio again - as it started my problems with WinDbg/kd.exe)
    jcgriff2 says thanks for this.

Similar Threads

  1. [SOLVED] [Win7SP1 x64] I still have current issues on my machine
    By mclovis in forum Windows Update
    Replies: 8
    Last Post: 09-12-2017, 04:19 PM
  2. Replies: 12
    Last Post: 08-08-2013, 08:08 AM
  3. please Windows 7 SFC Unable to Fix Files in a work machine
    By a8nsli in forum Windows 7 | Windows Vista
    Replies: 12
    Last Post: 08-08-2013, 08:08 AM

Log in

Log in