{"id":103743,"date":"2020-05-12T07:00:00","date_gmt":"2020-05-12T14:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=103743"},"modified":"2020-05-12T06:43:07","modified_gmt":"2020-05-12T13:43:07","slug":"20200512-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20200512-00\/?p=103743","title":{"rendered":"When you start getting in-page errors on your hard drive, it’s time to go shopping for a new hard drive, redux"},"content":{"rendered":"

Some time ago, I explained that receiving a STATUS_IN_PAGE_ERROR<\/code> from your hard drive means that it’s time to go shopping for a new hard drive<\/a>. It means that the system needed to page in code or data from a storage device, but the storage device was unable to produce the data. This can happen if you are running a program from removable media or over the network, but if it happens for your hard drive, that’s bad news.<\/p>\n

Your hard drive is starting to die. Back up everything you can and replace it as soon as possible.<\/p>\n

Now, the STATUS_IN_PAGE_ERROR<\/code> code is used when the system could not page data in for a user-mode application, and the kernel is forced to terminate the program. But the I\/O failure could also occur if the system could not page data in for the kernel itself, and that’s a much more dire situation.<\/p>\n

There is no process to terminate when the kernel itself suffers an in-page error. The only thing it can do is terminate itself, and that gives you the infamous blue screen of death<\/a>.<\/p>\n

There are two different stop codes for in-page errors, depending on whether the thing that couldn’t be paged in was static data or stack data.<\/p>\n\n\n\n\n\n
Stop number<\/th>\nStop code<\/th>\n<\/tr>\n
0x77<\/tt><\/td>\nKERNEL_DATA_INPAGE_ERROR<\/tt><\/td>\n<\/tr>\n
0x7A<\/tt><\/td>\nKERNEL_STACK_INPAGE_ERROR<\/tt><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The difference between them is not really important. They both mean, “Back up all your data and get a new hard drive ASAP.”<\/p>\n","protected":false},"excerpt":{"rendered":"

The click-click-click of impending doom.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[104],"class_list":["post-103743","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-tipssupport"],"acf":[],"blog_post_summary":"

The click-click-click of impending doom.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/103743","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=103743"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/103743\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=103743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=103743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=103743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}