{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibbunghgb2ms6zko4j26jowcei5dbgfl2d3dbgo4ue6lknfpcviwq",
    "uri": "at://did:plc:gptjj5dl4jidf7yvcx4gexxy/app.bsky.feed.post/3mm4g54vkfk32"
  },
  "path": "/threads/bugcheck-points-to-ntoskrnl-exe.3896104/",
  "publishedAt": "2026-05-18T06:22:06.000Z",
  "site": "https://forums.tomshardware.com",
  "tags": [
    "Windows 10",
    "Read more"
  ],
  "textContent": "I had a bugcheck yesterday to this day 0x1E. I think it started after that power outage. That BlueScreen Viewer program seems to point the finger towards ntoskrnl.exe.\n\n\n* * *\n\n==================================================\nDump File : 051626-20765-01.dmp\nCrash Time : 5/16/2026 10:50:53 PM\nBug Check String : KMODE_EXCEPTION_NOT_HANDLED\nBug Check Code : 0x0000001e\nParameter 1 : ffffffff`c0000005\nParameter 2 : fffff800`80652d04\nParameter 3 : 00000000`00000001\nParameter 4 : 00000000`000000a5\nCaused By Driver : ntoskrnl.exe\nCaused By Address : ntoskrnl.exe+3fdde0\nFile Description : NT Kernel & System\nProduct Name : Microsoft® Windows® Operating System\nCompany : Microsoft Corporation\nFile Version : 10.0.19041.7291 (WinBuild.160101.0800)\nProcessor : x64\nCrash Address : ntoskrnl.exe+3fdde0\nStack Address 1 :\nStack Address 2 :\nStack Address 3 :\nComputer Name :\nFull Path ...\n\nRead more",
  "title": "BugCheck points to ntoskrnl.exe ?"
}