New
#1
Various 0x0000007A Stop Errors on Newly Installed Win7 and HD
Hello SevenForums. I've come here like many I'm sure after not being able to fix or figure out my own problems and seeing the knowledgeable user base here as I've explored for solutions. I'll get to my issue, but first I'll provide some context...
Some months ago now the computer I'm currently on, a Dell Studio XPS 1647, had a hard drive failure. I don't know what brought it on, but fortunately with some help from friends I was able to recognize the failure early on. I shut down my computer and didn't touch it until I could acquire a new backup external HD. Once I did, I backed up all I could from my laptop's dying hard drive. Most of the files came across alright but I had to use a recovery program to retrieve some off of some bad sectors. Once most everything that was important to me minus some things I knew I could get again was backed up, I ran a chkdsk and during that long process the HD died entirely as all the sectors went sour evidently and the chkdsk stopped. Windows could not be booted from the HD any longer.
Time went by as I shopped for a replacement for my failed internal HD. I finally stumbled upon a sale for the Seagate 1TB Hybrid. I couldn't say no after reading good reviews and researching hybrids. I wasn't entirely certain it would be compatible but was told that most all computers with SATA connections would accept it, so I ordered the thing. I grabbed a copy of Windows 7 Home Premium as that's what I'd run previously and used a program to copy the OS onto a flashdrive. When the HD arrived, I carefully removed my old bad HD and installed the new one. My old one was also a Seagate but just the normal 500 GB HD that came with the comp so I also doubled my storage capacity. I installed Windows from the flashdrive and verified with my product ID.
Windows was up and running but there was still a lot to be done to get my comp back to normal. Drivers, for one. I didn't even realize I couldn't use wireless internet until I installed a driver for instance. I used Windows Update and the Device Manager to pick up what I could. Some things Windows couldn't resolve on it's own though and I had to leave. Over the next couple weeks I was picking up other things I needed as needed including .NET stuff. Had to actually get the x64 and the x86 since the x64 wasn't functioning for all my needs and I'll admit I didn't like having to do that since I'm not sure if it's really helpful to have two of these things on the comp. In fact, there were a couple times where I was searching for a driver and finding the one I grabbed didn't work and had to get another. I tried not to make too many mistakes like this but I do worry driver conflicts could be part of my current issue.
So yeah, "my current issues"... or more appropriately "issues" I suppose. For the last three weeks I've been getting BSODs about once a week. Yes, I've only had three. But the laptop is newly setup and I really didn't want to think anything could be broken again already. I figured I must be missing a driver or having a driver conflict. I talked to some friends who know more than me about these things. I showed them my BSODs. The look of it had them thinking it was an HD problem which I didn't want to hear after just installing the new one. I was told to run chkdsk and memory tests just to be sure. Everything came up a-okay. Still, the BSODs have happened. Between the second and third BSOD is when I ran most of these tests and it's also when I thought I'd found a solution. It was a hotfix for computers that were trying to use a large HD to wake up after sleep mode. Both my first two BSOD happened shortly after the computer had been woken up from idle. It was probably premature to jump to conclusions but it seemed like too perfect of an explanation. Didn't matter though since upon downloading it and trying to use it, I was told that the hotfix could not apply to my computer. So that was a failure. The second BSOD happened about a week ago, and then just earlier today, my third BSOD. The third one happened after the computer had been on for a while too, which just raised more questions.
I should note that although I grabbed Blue Screen Viewer, I've not been able to get any info from it and it could just be an installation issue, but I'm not sure. I've gotten info from the BSOD themselves though since each one has stayed on my monitor until I pushed the power button - (it wasn't a hold down shut down but a simple push to shut down or restart... can't remember if I was shutting down or restarting admittedly but I think it's been shut down). In any case, I took photos of each one of my BSODs with my phone and transcribed them into Notepad. The first one is the entire BSOD and the second and third just include what's under "Technical information:" as that's the only thing that's different from the first. These are pasted in below.....
----------------------------------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 ...
-------------------------------------------------------------------------------------
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.
Any advice or instruction is appreciated. The suggested debug tool file is attached.
Last edited by Jahkepon; 11 Mar 2014 at 02:20.