Various 0x0000007A Stop Errors on Newly Installed Win7 and HD

Jahkepon · 11 Mar 2014

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.

derekimo · 11 Mar 2014

Hi there,

There aren't any .dmp file in your attachment. These are required to analyse the BSOD.

Follow these steps:
Dump Files - Configure Windows to Create on BSOD

Then, when the system next BSOD's, follow this:

1. Download this .BAT file to your desktop

Download

2. Right-click the .BAT file and 'Run as Administrator'
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

Jahkepon · 11 Mar 2014

Under startup and recovery settings I have both "Write an event to the system log" and "automatically restart" checked. I didn't do anything. This is just their settings. The "Write debugging information" is default set to "Kernel Memory Dump" as well.

I used the .bat to create the file I attached and followed the instructions in the thread at the top of the BSOD Subforum's front page.

The trouble is I think my BSODs just aren't getting dumped or something. In my OP I described how the BSOD would sit on my monitor until I shut down. I had plenty of time to snap a photo of each one and transcribe it into Notepad to later paste here.

Should I have been waiting several minutes for the BSOD to disappear and finish it's dump and such? It didn't look like it was doing anything each time it's happened and I was anxious to look it up and see if I could determine the problem.

I'll be sure to attach another .bat created zipped file to a reply if and when I get another BSOD. Any more instructions as to how to get dump data at all would be appreciated. Thanks for the reply.

Edit: I suppose I should try all these options? Is there any harm in trying them all since the first one seems not to work for me at least.

derekimo · 11 Mar 2014

Can you see anything in C:Windows\Minidump folder?

You haven't run any cleaner programs or disk cleanup have you?

Jahkepon · 11 Mar 2014

I don't see that I even have a "minidump" folder on my C Drive at all after a search. Maybe I'm not totally clear on where to look though, but trying that in the address bar gives nothing either.

My settings for Startup and Recovery look exactly like what's shown under 7. in Option 1 of the link you gave me earlier.

I've not run any disk clean up programs at all to my knowledge. My Avast is basic virus protection and I doubt chkdsk and the hard disk sentinel I used would do anything like that. I'm not sure what could do anything like what you're describing purposefully or otherwise.

Edit: Going to bed, but I'll check this place in the morning and periodically while I'm busy tomorrow.

derekimo · 11 Mar 2014

If there isn't a folder it may not be configured for that.

Number 7 is a Kernel memory dump so the folder would be different.

What's preferred is small memory dump, try the reg file under number 2 in option two.

We will have to wait for another crash after you do that.

Jahkepon · 11 Mar 2014

I followed your instructions and used the option 2 means to change my settings to acquire small memory dumps now. Hopefully I get the dump files you need to tell me better what's going on when the next BSOD happens.

The actual blue screen text I copied isn't telling you anything though? Or do you just don't want to speculate on incomplete data until you see the actual dump files?

It's odd to actually want a BSOD right now, heh. I'd be fine if it never happened again, but if it must happen, I'd like it to be soon so I can diagnose with help here and hopefully fix my issue.

I'll attach the dump files here if and when they come. Thanks again.

derekimo · 11 Mar 2014

I can give you some stuff to try, the bugcheck 7A is more than likely a Disk issue.

Following option two in this tutorial,

Disk Check

Run a chkdsk /R

Here is another test you can run,

SeaTools for DOS and Windows - How to Use

Jahkepon · 11 Mar 2014

I just got my fourth BSOD moments ago shortly after opening up my laptop and getting on the browser. I let it sit on my monitor for about 10 minutes and was going to post about it on my phone but I couldn't use the message field for some reason with it. So I just pushed power and can confirm that doing so restarts the system and does not shut it down. It's worrying that it's just been a day since the last one when previously it was happening once a week, but this fourth one is like the first and second since it happened shortly after I woke it up from being closed. It was proceeded by the browser freezing during a refresh if that's any help either. Hopefully I have dump files this time to help figure this out.

I'll run the .dat thing and attach the results.

I ran a chkdsk /r just last week after my second BSOD, at a friend's suggestion. It took a while and there appeared to be no errors. Soon after it was done a lot of text I was unable to read flashed by and there was no information I could find on my comp about what if anything it found. I assumed everything was fine since up until moments before it was complete not a single error had been found and hard disk sentinel had said I was a-okay already.

I'll try the other test you linked though since it seems new to me.

Edit: Seems this second test is just to confirm whether I have bad sectors like a chkdsk would. Looks like it could be risky too so I'll wait on your advice before jumping in here. So far all the tests I've run have said there's nothing wrong with the HD, which I'd expect since it's brand new. If anything, I'm increasingly feeling it may be a compatibility issue. Could be my model of laptop just doesn't like this new large hybrid HD and perhaps needs a firmware update or drivers or something. I really don't know though.

derekimo · 12 Mar 2014

There is still no dump file in there,

Can do this tutorial here,

Speccy - Publish Snapshot of your System Specs

Without the dump files all I can do is speculate,

Here is some info on that Bugcheck,

Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR (Windows Debuggers)

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:
0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.
0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration.
These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
A virus infection can also cause this bug check.

Try testing your RAM as well,

Information

MemTest86+

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with MemTest86+

Have you scanned for Virus's or Malware?