Various 0x0000007A Stop Errors on Newly Installed Win7 and HD

[Thedoctor44]

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.

www.sevenforums.com/tutorials/433-disk-check.html

Then scan to see if your HDD is failing by using Seatools.

http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Post the results.

 

[Jahkepon]

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.

 

[Jahkepon]

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.

http://www.sevenforums.com/bsod-hel...pfiles-minidump-folder-0x0000007a-errors.html

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.

 

[Thedoctor44]

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.

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[Jahkepon]

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.

 

[Thedoctor44]

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

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Jahkepon]

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.

 

[Jahkepon]

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 ...

 

[Thedoctor44]

Did you run Seatools? You should run it.

 

[Jahkepon]

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.

 

[Jahkepon]

Well, since it's typically been a week between BSODs for me, I've been leaving Driver Verfier on this whole time. I've been busy and not actually on this computer much, but the BSODs have never regarded actual time spent on the computer. I could leave it off for a whole week and come back and get a BSOD. Or I could have it on for a whole week, although I haven't, and get a BSOD about a week after the last in most cases. I'm hoping as I approach a week since Driver Verifier has been on, I'll see something I want like a dumpfile perhaps. Otherwise, I've not seen any errors. Things just seem to be running slower or not well in some select places as I described in my last post. I'm waiting for my next BSOD basically before moving on.

I doubt Seatools will tell me anything, but I simply don't know and I'm lacking in options. If this Driver Verifier thing doesn't work, I really don't have another suggestion as to how to get a dumpfile. My thread dedicated to the question of how to get a dumpfile since I can't has been ignored or people simply don't have answers apparently.

 

[Jahkepon]

I just followed the necessary steps to also have complete memory dump settings as well. Hopefully I can create a memory dump file now along with the help of Driver Verifier as soon as the next BSOD happens.

 

[Jahkepon]

Well, I just got another BSOD. This would be #9 now. My settings were on "complete memory dump" and Driver Verifier was running. It doesn't appear I have a dumpfile though. However, I restarted my comp earlier than I'd have liked because I was working on something that I wanted to recover and finish. I'd have left the BSOD on my screen longer in the hopes that the complete memory dump was making a dumpfile otherwise. Even so, the BSOD was on my screen for a good two minutes. Maybe it didn't work again and wasn't going to, but I'll keep the complete memory dump settings on just in case it would've. Not too encouraging I'll admit though.

Here's the transcribed photo of my BSOD as always...

*** STOP: 0x0000007A (0xFFFFF6FC400099C8, 0xFFFFFFFFC000000E, 0x000000011C1A3860, 0
xFFFFF88001339335)

*** Ntfs.sys - Address FFFFF88001339335 base at FFFFF8800122F000, DateStamp
52e1be8a

Collecting data for crash dump ...
Initializing disk for crash dump ...

 

[Jahkepon]

Just bumping this with an update....

Yes, I still get BSODs with no dumpfiles. I've gotten 3 since I posted here last. They come about once a week as usual although one of them took two weeks to come probably mainly because I avoided being on the comp for most of that time.

In any case, I'm kind of lost as to what to do next. I don't want to resort to reinstalling windows or something. I'd just like for my BSODs to have dumpfiles so I can move on to the next step.

I've been frustrated that I can't use my computer how I'd like since I want to stamp this issue out rather than compound it with more stuff. But I've gotten a bit impatient and today I installed my drawing tablet on my computer. It requires it's own driver so I installed that although I've been avoiding adding more drivers on for a long time now. It didn't take long before driver verifier gave me a BSOD. This could be because of how I set up driver verifer to perhaps help me catch the at fault drivers from the BSODs I've been getting, but this time it appears to have caught something new. This BSOD actually DID give me a dumpfile unlike the dozen previous one's. But it's not the same and a review of the dumpfile tells me the at fault driver has to do with the tablet I just installed. So it appears this is a new problem and not to do with my old ones, at least directly. I'm not sure if getting this dumpfile bodes well for the future, but for now I'm going to see if I can get this problem fixed specifically and perhaps if I'm lucky it'll help solve the problems I've continually had for the weeks and weeks before today.

I plan to start a new thread for this tablet issue just to see if there's anything in there that could tell me more than perhaps I can see on my own. Maybe there's data in there that could hint to the issues I've been having.

Something else that I should note is that today I also remembered that I had set my computer up to backup it's data to my external HD. Thing is, my external HD can't do this job because of O/I restrictions or whatever they're called. Basically, it's too big to be a backup as dumb as that sounds and I'd need to format it. It's got lots of stuff on it already though, and I'd rather not deal with that. Long story short, I scheduled my computer to make backups onto my external every month but then the external was incompatible and I don't leave it plugged in ever anyways, but the computer still had this as a schedules thing to do until I turned it off today. I wondered if that could've been causing me issues. I wondered if perhaps that's where my computers has been trying to send dumpfiles. The BSOD and the tablet install happened after I did this btw.

 

[derekimo]

Here are the usual causes of that Bugcheck 7A,

Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

You said you ran memtest86+ and it passed.

Paging file corruption, (What are your settings here, Virtual Memory Paging File - Change)

File system, Try running http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Hard Drive, you said you ran chkdsk /r, what about the seatools?

Cabling, Have you tried a new cable on the drive?

Virus infection, Have you ran full AV and Malware scans?

Improperly seated cards, try reseating and checking connections.

BIOS, worth looking into to see if a new one addresses any of your issues.

Bad Motherboard, that will take some testing of just about everything else first.

Missing Service Pack, Doesn't apply here.

Without any dump files, it's really hard to diagnose, since every crash you report is the same Bugcheck 7A

Work through and report back on each of the above probable causes.

 

[Jahkepon]

>Paging file corruption, (What are your settings here, Virtual Memory Paging File - Change)

Well, the last memory dump settings I tried were complete and I doubled my virtual memory page size for that as suggested in the instructions there when dealing with complete memory dumps. I was actually linked that exact page in the thread I made addressing my lack of dumpfiles...

http://www.sevenforums.com/bsod-hel...ump-folder-0x0000007a-errors.html#post2750510

I'll attach a screencap of my settings for convenience at the bottom of this post.

>File system, Try running SFC /SCANNOW Command - System File Checker

I can't remember if I've tried that or not. Think I did chkdsk instead and figured I'd learned what I would've one way or the other. It wouldn't hurt to try again. I'm thinking I'm thinking of another time before this newer HD that I used it and I haven't tried it recently with this new stuff in actuality. Noted.

>Hard Drive, you said you ran chkdsk /r, what about the seatools?

I was told about seatools, and again I thought it was more HD failure measures when I didn't think that was an issue for me. I was hoping to resolve my lack of dumpfiles problem first before taking this measure, but I've yet to encounter a way or reason I'd not be getting them for these 7A errors. I did get a dumpfile recently but for something seemingly unrelated. I'll see what I can learn about it here with a separate thread.

>Cabling, Have you tried a new cable on the drive?

No. I'm not sure what this means actually, but I do remember a friend telling me to check and see if the installed HD was properly plugged in. I went into detail about what I saw and thought, and I'll copy paste that part in a following post.

>Virus infection, Have you ran full AV and Malware scans?

I did, but it was a while ago. I'm using Avast as it's the security I chose for this fresh OS after installing the new HD at the suggestion of many. I have heard it can cause issues for the OS for some I guess.

>Improperly seated cards, try reseating and checking connections.

I did open up the back like I said to check my HD's connection, but I didn't check my RAM cards if that's what you're talking about. If you're not talking about these, than I don't know what you mean. I'm not clear on some technical terms.

>BIOS, worth looking into to see if a new one addresses any of your issues.

Yeah, I figure this is something to try after I eliminate other possibilities. I don't even know where I'd begin with this, but I figure it's not to different from just plain doing a reinstallation of the OS.

>Bad Motherboard, that will take some testing of just about everything else first.

I seriously hope not.

>Missing Service Pack, Doesn't apply here.

Okay.

>Without any dump files, it's really hard to diagnose, since every crash you report is the same Bugcheck 7A

>Work through and report back on each of the above probable causes.

Got it.

 

[Jahkepon]

Well, my description of the HD's connection isn't nearly as detailed as I remember. It's likely my detailed description was something I gave in private to the the friend that suggested I check in the first place. Here's what I said here though copy pasted like I said I would...

I should also note that after the third BSOD, a friend suggested I look to see if my new internal HD is even plugged in securely. I shut everything down, pulled the battery and all that and opened it up to have a look. The HD seemed in there plenty securely, but I'll admit that the connector seemed like it could move around a bit on the board end of the connection - the little metal box with the plastic tab on top. I'm not sure if that's normal and I'd like to exhaust all other options before potentially putting money down for a replacement connector if that's really an issue.

 

[Jahkepon]

Just waiting on an analysis of my paging file settings and seeing if I can learn anything in a separate thread I just made about this seemingly unrelated BSOD I got early today.

Then I'll move on to SCANNOW accordingly.

 

[derekimo]

Please do the SFC /scannow, full scans with Avast and the free version of https://www.malwarebytes.org/ report back the results of each.

Please run the seatools whether you think it's valid or not, these troubleshooting steps are all we have right now.

Your page file looks fine, we can leave that for now.

The cable I mentioned was the one from the hard drive to the mobo, just make sure it it is plugged in securely. It would be nice to have a new one to test with since we are grasping for causes here.

Forget about the card reseating, it slipped my mind this is a laptop. I was just covering all the probables.

I do see an updated version of your BIOS but let's wait till you report back on the above steps.

 

[Jahkepon]

Scannow was run and no problems were found.

Next I will run an Avast scan. The malewarebytes program won't interfere with Avast or vise versa, correct?

I suppose I will run a full system scan unless a quick scan would suffice. I just have the free Anti-virus software as opposed to a larger Avast package requiring payment, but the scan settings for quick scan says that it will check places on my computer most susceptible to maleware. Not sure if that implies it'll do the job that the malewarebytes program is meant to do. Regardless, I think I'll try a full system scan in the hopes I don't miss anything.