Solved ntoskrnl.exe 0x0000001E BSOD

[writhziden]

Probably caused by : Ntfs.sys ( Ntfs!NtfsMapUserBuffer+28 )
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: explorer.exe

Run http://www.sevenforums.com/tutorials/433-disk-check.html with both boxes checked as the crash was hard drive related.

 

[justinbronze]

Attached is a txt file of the Chkdsk results.

No bad sectors, no kb in bad sectors, nothing wrong found.

 

[writhziden]

Attached is a txt file of the Chkdsk results.

No bad sectors, no kb in bad sectors, nothing wrong found.

Odd that you would get an NTFS.SYS crash with Verifier running and no disk problems. Have you had a chance to run the memory tests yet?

 

[justinbronze]

I have not, but I am going to as soon as I can.

Any idea as to what might be causing it all?

 

[writhziden]

Things seem to be pointing toward hardware, and most of your errors are hard disk related to some extent. If memory comes back clean, check your hard drive with diagnostics software such as CrystalDiskInfo - Software - Crystal Dew World or HD Diagnostic tools.

 

[justinbronze]

Ill be running the Memory check tonight. In the mean time, however, I ran Crystal disk info. The attached picture is the results.

 

[justinbronze]

I ran the windows memory diagnostic. No problems found.

 

[justinbronze]

Feedback?

 

[writhziden]

Feedback?

Nothing stands out to me... Have you at any time run a registry cleaning tool on your machine? And just to be clear, I do not recommend doing so. I was just wondering because I have seen registry cleaners cause unexplainable blue screen crashes.

 

[justinbronze]

I have not run any registry cleaning tools on my computer. I'm well aware of the damage they can cause, and refuse to use them in fear they might cause the problem I'm having now.

I also ran Memtest86 last night. No errors found. So it looks that so far all the tests show no problems.

Next step?

 

[writhziden]

Are you still running Verifier? If so, just keep running as normal and collecting .dmp files. Post back after you've collected a few more. Hopefully they will be more conclusive.

If not, re-enable Verifier for further testing.

 

[justinbronze]

So far, no BSOD's.

 

[writhziden]

So far, no BSOD's.

Odd that you get more blue screen crashes with verifier off than with it on.

 

[justinbronze]

So far, no BSOD's.

Odd that you get more blue screen crashes with verifier off than with it on.

It is odd.

 

[justinbronze]

2 days running verifier and no BSODs.

 

[writhziden]

2 days running verifier and no BSODs.

I guess just keep it running since it keeps your system stable. If you get another blue screen crash, let us know.

 

[justinbronze]

That I will. That I will.

But isn't Verifier supposed to CAUSE BSODs to help show the problem? So why is it keeping my system stable?

 

[writhziden]

That I will. That I will.

But isn't Verifier supposed to CAUSE BSODs to help show the problem? So why is it keeping my system stable?

Have you made sure that it is running? (Start Menu -> Type Verifier into Search programs and files (do not hit enter) -> Right click Verifier and click Run as administrator and follow directions from UAC -> Display information about the currently verified drivers -> Next -> Check the white box on the right side for the verified drivers)

 

[justinbronze]

It says that all drivers are loaded.

 

[writhziden]

Then just keep running it and post back if you have a crash. I have never seen behavior such as that on your computer, so this is new ground for me (and probably would be for anyone else helping you as it is very bizarre behavior).