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: Various 0x0000007A Stop Errors on Newly Installed Win7 and HD

16 Apr 2014   #31
Jahkepon

Windows 7 Home Premium x64
 
 

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.


My System SpecsSystem Spec
.
16 Apr 2014   #32
Jahkepon

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
16 Apr 2014   #33
Jahkepon

Windows 7 Home Premium x64
 
 

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

17 May 2014   #34
Jahkepon

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
17 May 2014   #35
derekimo

Microsoft Community Contributor Award Recipient

 
 

Here are the usual causes of that Bugcheck 7A,

Quote:
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 SFC /SCANNOW Command - System File Checker

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.
My System SpecsSystem Spec
17 May 2014   #36
Jahkepon

Windows 7 Home Premium x64
 
 

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

No Dumpfiles or Minidump folder for 0x0000007A Errors

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.
My System SpecsSystem Spec
17 May 2014   #37
Jahkepon

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
17 May 2014   #38
Jahkepon

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
17 May 2014   #39
derekimo

Microsoft Community Contributor Award Recipient

 
 

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.
My System SpecsSystem Spec
18 May 2014   #40
Jahkepon

Windows 7 Home Premium x64
 
 

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

 Various 0x0000007A Stop Errors on Newly Installed Win7 and HD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Sudden recurring BSOD, Win7 Ultimate64x (newly installed)
Hello friends, My name is Jonathan. Just recently formatted my HD on my Dell Inspiron 5521. Got rid of Win8 and installed 7. Two days past, and I have installed many previous software I had before, plus all win7 updates and offfice 2010 (haven't updated office). Suffering from sudden,...
BSOD Help and Support
BSOD with ks.sys, newly installed Win7 Ultimate x64(Log included)
Hi All, I have just re-installed my PC yesterday and left it on running for the night. This morning when I check, it shows the BSOD for ks.sys. I've been having similar issue even before re-install but since I don't have the log back then I might just ask you guys to please analyze this log and...
BSOD Help and Support
c0000005 errors when running newly installed games
Hi, I've been having problems with games crashing with c0000005 as soon as I run them. This isn't happening with games I've had installed for a while, it has only started when i've tried to install new games in the last month or so. I've attached my files from the SF tool. I was wondering if...
General Discussion
BSOD random stop : stop 0x0000007A
I have bluescreen with that stop 0x0000007A (0x0000000000000020, 0xFFFFFFFFc000009D, 0xFFFFFFFFA8007CEF7C8, 0x0000000000000000) It happens randomly after sometime half an hour one hour whatever i'm doing on my computer. Do you have any solution to solve this problem. Thanks windows7 64 bit...
BSOD Help and Support
BSOD on newly installed Win7 Home Premium - log included
Just installed Win 7 Home Premium x64 yesterday & still loading programs, tweaking etc. I have had two crashes today. Same message in event viewer.
BSOD Help and Support
Newly re-installed Win7, constant BSOD's
Hi! As the title states, I just reinstalled windows 7 on my machine. I installed all windows updates available as well as my GPU and Mobo drivers. Everything should be running smoothly, but I have been getting constant blue screens while doing just about anything. Any help in solving this...
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 01:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App