I have a Windows 7 PC that can boot, work normally and hibernate/restart all well, except whenever I open a file explorer and CLICK on "My Documents" , "Pictures", "Music" or "Videos" I get a BSOD:

STOP ntoskrnl 0x000001e

Also if I navigate from C: to My Documents, upon entering My Documents, the same BSOD occurs.

Using BlueScreenView I found that ntoskrnl.exe is always in the stack's top 2, sometimes alone sometimes the first one will be something else: I've had dozens of this crash and it's pretty variable what the other driver is alongside ntoskrnl.

The very first crash was with the string "PAGE_FAULT_IN_NONPAGED_AREA" and since then they are all "KMODE_EXCEPTION_NOT_HANDLED".

I can go into My Documents from a cmd window, and list files there. I ran sfc /scannow and it found no corruption. I have removed recently installed applications, and still this persists. chkdsk finds no corruption , and the bsod does not happen in safe mode.

This system is pretty generic, it had been hibernating on and off succesfully for months as I remember, I can't think of anything really big that changed recently (Firefox 13, Skype 5.9, Avast which I've now got rid of).

Any ideas would be much appreciated: My Documents is actually a place I like to visit often!

  • Official documentation for your STOP code: Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED Jun 18, 2012 at 11:27
  • Please see Crash Dump Analysis if you want to retrieve further information from the generated crash dump. Jun 18, 2012 at 11:29
  • Thanks!I will run chkdsk and test memory just in case. However: the fact that it occurs at specific actions and not randomly makes me think it's not a physical problem with RAM? The fact that I can do dir in My Documents in the cmd window makes me think it's not a disk problem?
    – imateapot
    Jun 18, 2012 at 11:37
  • I am inclined to believe there is some corruption the hard drive (more specifically MFT) since it only happens with some directories. If chkdsk does not work see if you can open the folder from a different computer (though still win-7)
    – soandos
    Jun 18, 2012 at 11:42
  • @imateapot: The most promising results are always obtained by loading the crash dump into a debugger like WinDBG. It allows you to analyze the dump and gain further insight into what may have caused the issue. Jun 18, 2012 at 11:56

1 Answer 1


Sounds like it's a faulty HDD, following on from Oliver's comments above I would recommend running a full hard disk diagnostic (Hiren's Boot CD is good for this).

Once you are sure your HDD is healthy next check would be a RAM test (because it's quick, easy and worth doing - use memtest, also on Hirens).

As you've run SFC then the filesystem should be intact, but (as also mentioned by Oliver) a full chkdsk will check this for you (like a memory test, it's worth doing for peace of mind).

After all these tests are done, if the problem persists the next stages would be a complete low level format and reinstall of Windows, quite obviously a last resort!

  • Sounds like a Virii or Root Kit to me
    – Jay
    Jun 18, 2012 at 12:32
  • Could be, but why would it only occur when entering any Win7 library and nothing else odd happening?
    – HaydnWVN
    Jun 18, 2012 at 14:55
  • Because of the rootkit, by virtue of the same question how come he can access the convents via CMD?
    – Jay
    Jun 19, 2012 at 0:56
  • Windows UI/API being unable to read additional file information/attempting to view corrupted info due to a faulty area of disk. Neither of us is correct (or incorrect) as both are valid and need further diagnostics! :)
    – HaydnWVN
    Jun 19, 2012 at 10:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.