Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: bsod caused by ntoskrnl.exe and Ntfs.sys

10 Sep 2012   #1
AnPham

64
 
 
bsod caused by ntoskrnl.exe and Ntfs.sys

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.


My System SpecsSystem Spec
.
10 Sep 2012   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome

Dumps indicate memory issue

Run memtest86+ on each stick for 8 passes preferably overnight RAM - Test with Memtest86+

Post back results

Analyze

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

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff7000d838588, 0, fffff80002ca170c, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiUpdateWsle+35c )

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

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a5, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

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

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

NTFS_FILE_SYSTEM (24)
    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 Disk Check then Hard drive scan usings SeaTools SeaTools | Seagate both long and short tests.

Let us know how it goes
My System SpecsSystem Spec
12 Sep 2012   #3
AnPham

64
 
 

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
My System SpecsSystem Spec
.

12 Sep 2012   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

You're welcome

Let us know how it goes & good luck.
My System SpecsSystem Spec
12 Sep 2012   #5
karlsnooks

MS Windows 7 Ultimate SP1 64-bit
 
 

Quote   Quote: Originally Posted by AnPham View Post
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.
My System SpecsSystem Spec
12 Sep 2012   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Oh sure!
Thanks Karl
@ AnPham, you can follow suggestions by Mr. Karlsnooks before you get the memory sticks replaced.
My System SpecsSystem Spec
12 Sep 2012   #7
karlsnooks

MS Windows 7 Ultimate SP1 64-bit
 
 

My System SpecsSystem Spec
13 Sep 2012   #8
AnPham

64
 
 

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
My System SpecsSystem Spec
13 Sep 2012   #9
AnPham

64
 
 

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
My System SpecsSystem Spec
14 Sep 2012   #10
karlsnooks

MS Windows 7 Ultimate SP1 64-bit
 
 

glad to hear that problem identified and to be of assistance.
My System SpecsSystem Spec
Reply

 bsod caused by ntoskrnl.exe and Ntfs.sys




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD caused by Ntfs.sys
Uploaded is the needed ZIP file from the instructions, I have no idea what else I need to post in this concerning details with trying to help with this BSOD of mine. (I'm sorry, I'm not very good with computers actually, so some things I may have to ask with clarifying on. -Anyways, I ran...
BSOD Help and Support
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support
BSOD caused by ntfs.sys & ntoskrnl.exe
Hi Guys ... For some obscure reason my system keeps crashing when it is on idle mode. I keep gettin that darn infernal msg that the crash was caused by ntfs.sys I have tried each and everythin possible that I know of yet the issue is not resolved. The dump files are attached. Hopefully I...
BSOD Help and Support
BSOD ntoskrnl.exe and NTFS.sys
I recently formatted and did a full clean install of Windows 7 because of BSOD trouble, and now it is back to haunt me. For that reason, I think it is a hardware issue. I attached the 7 forum diagnostic tool report. Please help
BSOD Help and Support
BSOD probably caused by Ntfs.sys, ntkrnlmp.exe, win32k.sys
Hello! I'm working with a Dell OptiPlex 580 running 64-bit Windows 7 Professional in a domain environment. This PC is two years old and essentially started to crash out of the box. I put up with it for about a year-and-a-half because the crashes were somewhat infrequent, maybe occuring every two to...
BSOD Help and Support
BSOD on startup, code 24 caused by Ntfs.sys
I get the BSOD when restarting my machine (which I rarely do). It kicks in several seconds after my desktop comes up. After it restarts, it's usually fine (although sometimes it hits a second BSOD). But, once it's up and stable, no more BSOD. Thanks for any help tracking it down!
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:45.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App