Well, ntfs.sys is Windows New Technology File System. These bugchecks or "BSODs" are generaly caused by corrupt critical files on your HDD or a failing HDD. I would run a disk check by following these instructions.
Disk Check
Then scan to see if your HDD is failing by using Seatools.
SeaTools for DOS and Windows - How to Use
Post the results.
I have run chkdsk with no errors found at all, /r as I recall. Hard Disk Sentinel also has my HD at 100%.
I suppose I should try Seatools even with these other tests passing? It appears they recommend Option 2 even though the process seems much more lengthy.
Also, I should mention that I did start a new thread directly related to my lack of dumpfiles. If I could get an answer there I might be able to finally produce a dumpfile and make diagnosing and fixing much less just guess work.
No Dumpfiles or Minidump folder for 0x0000007A Errors
Second post has more transcribed BSODs. Including not just a couple "ntfs.sys" related errors, but also a "partmgr.sys" related error I had some time ago now. None of these errors have created a dumpfile.
Hmm, partmgr.sys is the windows Partition Management Driver. It sounds like a partition hasn't been created properly or Windows is damaged. normally repairs for Windows using the installation CD isn't a great idea as they never seem to work.
However in this case it is advised.
Repair Install
Sorry for the late response to your suggestion. Just have been quite busy and haven't even used my computer in a while.
I'm a bit hesitant to be reinstalling Windows just from what the BSOD itself is telling me. I hopeful I can get answers to why I'm not getting dumpfiles at all first. That way, if I can get that issue solves, I can at least diagnose why I'm getting the BSODs more accurately and take appropriate action instead of perhaps needless action that'll do nothing for me in the end. The suggestion is certainly on the table no doubt, however. I just want to wait a bit and see if the "lack of dumpfiles" problem can be worked out first.
Also, I got another BSOD just now. The first in a while, but I've also not been on the computer much anyways. It's more of the same basically and I doubt sharing the code expressed in the BSOD itself would be much help as the previous 6 BSOD posts here haven't really been. I did take a picture of the BSOD as usual though, so I can post it whenever if I so choose.
Post the pictures anyway, you might want to try and enable driver verifier as that can help create a dump file, especially if it's a driver at fault.
Follow these instructions
Driver Verifier - Enable and Disable
And I just got another. This is my 8th now. My BSODs usually come around once a week give or take a day like clockwork, but this is the second time I've had a BSOD happen the day after another. The pattern so far is... BSOD>week>BSOD>week>BSOD>day>BSOD>week>BSOD>week>BSOD>week>BSOD>day>BSOD. I experienced my first BSOD roughly a week and a half after I installed this new HD and got my OS again via product key.
I'll try this Driver Verifier thing. I saw it suggested in another thread about an issue similar to what I've been experiencing. I didn't follow it up though and when I asked Derekimo if he needed data from it he told me it was in my Speccy data I shared here earlier in this same thread. He never mentioned about it though. Thanks again Doctor.
I'll follow this post up with one that'll basically be a copy/paste of my BSOD photo transcriptions post that's in the thread I made about my lack of dumpfiles. Only difference will be that it'll include my latest two BSODs.
Below are my all my BSODs to date transcribed from photos I took of each of them when they appear. They stay on my screen like this for a long time. I've waiting as much as 20 minutes with no change. Plenty of time to take a picture with my phone. The first BSOD is the full screen. All the following BSODs only include what's after "Technical information:" since that's the only part that changes between them.
----------------------------------First Crash Info----------------------------------
A problem has been detected and windows has been shut down to prevent damage
to your computer.
KERNEL_DATA_INPAGE_ERROR
If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any windows updates you might need.
If the problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical information:
*** STOP: 0x0000007A (0x0000000000000020, 0xFFFFFFFFC000009D, 0xFFFFFA8005AC27C8, 0
x0000000000000000)
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Second Crash Info----------------------------------
*** STOP: 0x0000007A (0xFFFFF6FC40009A48, 0xFFFFFFFFC000000E, 0x00000000368E1860, 0
xFFFFF88001349D18)
*** Ntfs.sys - Address FFFFF88001349D18 base at FFFFF8800125B000, DateStamp
5167f5fc
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Third Crash Info----------------------------------
*** STOP 0x0000007A (0xFFFFF6FC40007270, 0xFFFFFFFFC000000E, 0x000000008B7C3860, 0
xFFFFF88000E4E630)
*** partmgr.sys - Address FFFFF88000E4E630 base at FFFFF88000E40000, DateStamp
4f641bc1
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Fourth Crash Info----------------------------------
*** STOP: 0x0000007A (0x0000000000000020, 0xFFFFFFFFC000009D, 0xFFFFFA80059727C8, 0
x0000000000000000)
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Fifth Crash Info----------------------------------
*** STOP: 0x0000007A (0x0000000000000020, 0FFFFFFFFC000009D, 0xFFFFFA80058E17C8, 0
x0000000000000000)
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Sixth Crash Info----------------------------------
*** STOP: 0x0000007A (0xFFFFF6FC40009968, 0FFFFFFFFC000000E, 0x0000000069FF4860, 0
xFFFFF8800132D758)
*** Ntfs.sys - Address FFFFF8800132D758 base at FFFFF8800123F000, Datestamp
5167f5fc
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Seventh Crash Info----------------------------------
*** STOP: 0x0000007A (0xFFFFF6FC40037128, 0xFFFFFFFFC000000E, 0x000000006B0F0BE0, 0
xFFFFF88006E25000)
Collecting data for crash dump ...
Initializing disk for crash dump ...
----------------------------------Eighth Crash Info----------------------------------
*** STOP: 0x0000007A (0xFFFFF6FC40041A00, 0xFFFFFFFFC000000E, 0x00000000A0F17BE0, 0
xFFFFF88008340000)
Collecting data for crash dump ...
Initializing disk for crash dump ...
Did you run Seatools? You should run it.
So I've had the Driver Verifier on and verifying all the drivers on my computer that aren't listed as provided by "Microsoft Corporation" as suggested in thread you linked. Things seem a bit less responsive perhaps, like they don't happen immediately or seem partially frozen at times. The chime that happens at start up and when you plug something into the USB port comes out broken sounding, or just "unsmoothly". I've not been on this computer much since I started the verifier, being busy, but these are just some little things I've noticed. Fan seems to kick on and kick into high gear more easily as well. Not had a BSOD since I started it and as I recall from the instructions I should be expecting error messages or something more frequently. Nothing like that has happened in the nearly 24 hours I've had it on. Again, however, I've maybe used the computer here only 3 or 4 of those 24.
I'd forgotten about the Seatools suggestion. I suppose I don't have much else to try and could do it. I recall being hesitant to try it however since it seems like all it does is tell you whether your HD is failing or not. I've done chkdsk and use a HD Sentinel to monitor and test my HD and I've only ever gotten back that it's 100% fine. Plus it's a brand new HD that I doubt is actually having trouble. If anything, I think it might be this comp just having compatibility issues with the new HD, not the HD failing. However, Derekimo said he never saw that my HD needed a firmware update for my computer. I think he figured this after looking at the Speccy data. I'll still try it though since you feel it's an important thing to do and I don't have too many other things to even try at this point... just stating that if this is meant to tell me whether my HD is failing or not and nothing more, I doubt I'll get much out of it after what I've already done.
Quote