Solved bsod caused by ntoskrnl.exe and Ntfs.sys

[AnPham]

hello, i've recently bought a new computer but finding it frustrating that i keep getting the bsod randomly as i use my computer. using blue screenview, its saying that the bsod was caused by ntoskrnl.exe and Ntfs.sys. i am in desperate need of help and would be very grateful for any solutions bought forward.

 

[koolkat77]

Welcome

Dumps indicate memory issue

Run memtest86+ on each stick for 8 passes preferably overnight http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Post back results

Analyze

STOP 0x0000001A: MEMORY_MANAGEMENT :: Usual causes: Device driver, memory, kernel :: BSOD Index

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Red"]BugCheck 50[/COLOR], {fffff7000d838588, 0, fffff80002ca170c, 2}


Could not read faulting driver name
Probably caused by : [COLOR="Red"]memory_corruption ( nt!MiUpdateWsle+35c )[/COLOR]

Followup: MachineOwner
---------

STOP 0x00000024: NTFS_FILE_SYSTEM Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure BSOD Index

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="red"]BugCheck 24[/COLOR], {c08a5, 0, 0, 0}

Probably caused by : [COLOR="red"]Ntfs.sys[/COLOR] ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]NTFS_FILE_SYSTEM (24)[/COLOR]
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.

To make sure that hard drive is good run disk check following this tutorial :ar: http://www.sevenforums.com/tutorials/433-disk-check.html then Hard drive scan usings SeaTools :ar: SeaTools | Seagate both long and short tests.

Let us know how it goes

 

[AnPham]

i ran memtest last night and i found a staggering 16mil+ errors
im going to ask the retailer for an exchange immediately

thank you so much for the suggestion

 

[koolkat77]

You're welcome

Let us know how it goes & good luck.

 

[karlsnooks]

i ran memtest last night and i found a staggering 16mil+ errors
im going to ask the retailer for an exchange immediately

thank you so much for the suggestion

Quite often such a multitude of errors is NOT due to a defective stick, but rather to a bad insertion of the memory stick.

Before you rush off, I suggest:
Unseat all boards.
Insert one board firmly and thorougly.
Run Microsoft's memory test which comes with your Win 7 by:
WIN | type MEM | ENTER key
WIN is the key with the Microsoft logo on top.

If memtest immediately starts showing errors, powerback down, check card seating.

Insert another stick, into the same slot.

If all sticks fail, then you have a bad slot and not a bad chip.

You get the idea, you work your way thru all of the sticks.

Now this all assumes that you have the correct ram installed.

Run Speccy which will show you the mfg, etc of the ram sticks.

Here is a snip of memory info on one of the sticks in my computer.


Then what you want to do is go the website of the manufacturer of your computer and see if the installed memory is on his list of approved memory.

 

[koolkat77]

Oh sure!
Thanks Karl
@ AnPham, you can follow suggestions by Mr. Karlsnooks before you get the memory sticks replaced.

 

[karlsnooks]

View attachment 231473

 

[AnPham]

thanks karl, i checked each slot and they all seem to be fine
it was one of my ram sticks that was totally screwed
i'm currently running my comp with the other working ram stick and all seems to be fine, no bsod so far, and programs are running smoothly

thanks for all your help

 

[AnPham]

thanks karl, i checked each slot and they all seem to be fine
it was one of my ram sticks that was totally screwed
i'm currently running my comp with the other working ram stick and all seems to be fine, no bsod so far, and programs are running smoothly

thanks for all your help

 

[karlsnooks]

glad to hear that problem identified and to be of assistance.

 

[koolkat77]

Thanks for the update An.
Feel free to mark this thread as solved.