BSOD - Dump Files

[luffypotter]

I only have Windows 7 in my pc and without problems but since a few days ago, sometimes appears a BSOD that says:
Kernel_Data_Inpage_Error

Technical Information
***Stop: 0X0000007A (0XC05074E0, 0XC0000056, 0X6915EBE0, 0XA0E9C00)

Physical memory dump failed with status 0XC0000010

I know that the information which the dump file contain will help but i dont know where the dump file is located

 

[Night Hawk]

Many have simply reinstalled Vista when seeing the "Physical memory dump failed with status 0XC0000010" error repeatedly without any memory dumps being seen. Your next step would be looking in the event viewer logs which can sometimes point to a company name.

For the "Stop: 0X0000007A" error the MS information on that goes back as far as Windows 2000.

"This issue can occur if you have the UlraDMA66/ATA66 (80 wire/40 pin) IDE cable attached to the drive that you are trying to install Windows 2000 on. Windows 2000 does not fully support the UltraDMA66 controller."
Error Message "Stop 0x0000007A" Occurs During Setup on an ATA66-based Computer

An updated version of the same problem seen with Windows Server 2008 and Vista is found at Stop error message when you put a computer that is running Windows Vista or Windows Server 2008 into hibernation: "STOP 0x000000A0," "STOP 0x0000007a," or "STOP 0x00000077"

You'll find a link for a hotfix at the top of the page there that might help with 7. But still look the event viewer logs over to see what other information is shown there.

 

[Zidane24]

Many have simply reinstalled Vista when seeing the "Physical memory dump failed with status 0XC0000010" error repeatedly without any memory dumps being seen. Your next step would be looking in the event viewer logs which can sometimes point to a company name.

For the "Stop: 0X0000007A" error the MS information on that goes back as far as Windows 2000.

"This issue can occur if you have the UlraDMA66/ATA66 (80 wire/40 pin) IDE cable attached to the drive that you are trying to install Windows 2000 on. Windows 2000 does not fully support the UltraDMA66 controller."
Error Message "Stop 0x0000007A" Occurs During Setup on an ATA66-based Computer

An updated version of the same problem seen with Windows Server 2008 and Vista is found at Stop error message when you put a computer that is running Windows Vista or Windows Server 2008 into hibernation: "STOP 0x000000A0," "STOP 0x0000007a," or "STOP 0x00000077"

You'll find a link for a hotfix at the top of the page there that might help with 7. But still look the event viewer logs over to see what other information is shown there.

You beat me to it Night Hawk.... I have seen people bring in computers to me that they formatted because they couldn't get something to install on it....That could be the reason that OS manufactures don't send the discs with the new machine much anymore!

 

[Night Hawk]

You beat me to it Night Hawk.... I have seen people bring in computers to me that they formatted because they couldn't get something to install on it....That could be the reason that OS manufactures don't send the discs with the new machine much anymore!

Just about any new desktop or laptop these days has a specified key combination you use at post time for seeing the full restore take place. The manufacturers have been doing that since Vista came out for most simply to save on manufacturing costs as well as seeing a new restoration feature available.

A former neighbor brought up a Dell XPS laptop back in late 2007 when that line was first out with the full restore option seen then.

The one thing luffypotter can do there is go into the advanced system settings>startup/recovery section and disable the automatic restart on crash option to watch for any further BSODs and take down any other information that comes up as well. That could reveal whether this is a simple device driver error or hardware problem being realized.

 

[luffypotter]

well, for now the bsod stop appearing without doing anything.
NightHawk whick link you said that can help with 7?
I disable the automatic start and the information in the blue screen is that i psot here. I need to find the dump file that the OS create wih the bluescreen but i dont know where he was created

 

[Night Hawk]

The second link above is for Vista and Server 2008 which is much closer to 7. The first is for 2000 showing how this type of problem has come up on the older versions as well due to the NT core being present.

The best advice for you would be seen at the MS page covering the memory dump file processes all the way up from 2000 to Server 2008 seen at Overview of memory dump file options for Windows Vista, Windows Server 2008, Windows Server 2003, Windows XP, and Windows 2000

That also sees a few other reference links there along with the steps you need to take. The part you want to pay close attention to there has the title "Tools for the various dump types".

Another thing that could be a help for you is looking over how much disk space is taken up for system restore points. http://www.sevenforums.com/tutorials/335-system-protection-change-disk-space-usage.html

 

[luffypotter]

well, about system restore, the space i use is very low so its not that
i search at MS site like you said but all the tuturials that are there are for pcs over 4gb

 

[zigzag3143]

BSOD dump file

I only have Windows 7 in my pc and without problems but since a few days ago, sometimes appears a BSOD that says:
Kernel_Data_Inpage_Error

Technical Information
***Stop: 0X0000007A (0XC05074E0, 0XC0000056, 0X6915EBE0, 0XA0E9C00)

Physical memory dump failed with status 0XC0000010

I know that the information which the dump file contain will help but i dont know where the dump file is located

dump file is usually in c:\windows\minidump. If its not you can search c:for *.dmp which is the extension for the dump file
\
Ken

 

[Night Hawk]

Apparently that's limited to the 32bit 7 as seen in the left explorer window while the 64bit has no memorydump folder to begin with. The 64bit Windows handles crashes a little bit different there.

 

[luffypotter]

ya, but the problem is tha i dont have that folder called minidump and i search for dump files and find nothing

 

[Night Hawk]

If you are running the 64bit 7 you may not either. I found that on the 32bit installation presently on.

The event viewer logs are another place to start looking since you can often identify a company name pointing back to the drivers when seeing blue screens from a bad install of an update. It can be useful for tracking down the source of other problems with the information kept there as well.