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

usasma · Sep 28, 2017

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?

axe0 · Sep 28, 2017

Same here, I stay with 10.0.14321.1024.

jcgriff2 · Sep 29, 2017

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

usasma · Sep 29, 2017

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!!!

axe0 · Sep 29, 2017

Download of 10.0.14321: <removed>

usasma · Sep 29, 2017

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)

Search

Search

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

usasma

Retired Admin

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

usasma

Retired Admin

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst

usasma

Retired Admin

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

usasma

Retired Admin

axe0

Administrator, BSOD Academy Instructor, Security Analyst

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

usasma

Retired Admin

axe0

Administrator, BSOD Academy Instructor, Security Analyst

usasma

Retired Admin

Administrator,
BSOD Academy Instructor,
Security Analyst

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Administrator,
BSOD Academy Instructor,
Security Analyst