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: No Dumpfiles or Minidump folder for 0x0000007A Errors

31 Mar 2014   #1
Jahkepon

Windows 7 Home Premium x64
 
 
No Dumpfiles or Minidump folder for 0x0000007A Errors

Hello again Sevenforums. I'm starting a new thread here dedicated to a problem I'm facing that's keeping me from solving my greater BSOD issue... I'm not getting any dumpfiles. Here's my original thread detailing all the problems I've had so far as well as specs and evidence of tests I've run...

Various 0x0000007A Stop Errors on Newly Installed Win7 and HD

For convenience sake, I'll run down some quick details as well as everything I've done so far...

My computer is a Dell XPS Studio 1647 that just a month and a half ago had a new HD installed to replace the one that died some months ago now. The new HD is a 1TB Hybrid Seagate. I installed Windows 7 Home Premium x64 on it since that was it's OS on the old HD. I used the product key found on the laptop to verify.

My first BSOD came 10 days after my fresh install. I've had them about once a week since with the exception of the third and fourth BSODs happening within a day of each other. All are 0x0000007A stop errors with various sub info I'm not adept at interpreting. There's been six BSODs now since the fresh install. I'll copy paste all my BSOD screens in a following post so as to not make this post overly long and broken up.

Since I've come here and even before then, I've run various tests. I've used "Hard Disk Sentinel" to do a quick check of my hard drive as well as a full chkdsk at the suggestion of a friend. I also ran a basic memtest at a friends suggestion before running a much more thorough memtest 10 times at the suggestion of derekimo on my original thread. All things passed. Also at derekimo's suggestion I checked how my dumpfiles were being "written". I checked and saw that I was using the default kernel memory. Following the clear instructions on a linked thread I changed my debug settings to "small memory dump". I've still gotten no dumpfiles at all since then. I also shared with him my Speccy data and there was apparently nothing of note. He was basically the only person helping me but disappeared after I shared my Speccy data and passed the 10 memtests. He was quite helpful for a while though. Also, I'll add that at a friend's suggestion I even checked how well my components are plugged into each other by taking my laptop apart. This was something I did between the third and fourth BSODs, so it changed nothing. The next BSOD just taking a day is probably unrelated. The notion was that my HD or RAM could have a loose connection. Everything seemed solid although the connection between the SATA connector and the board seemed a bit floaty I guess, but I don't know how normal that is. Besides, BSODs possibly caused by a loose connection would be more frequent or would be followed by a totally disconnected HD I'd think.

The important stuff.... I don't get dumpfiles after my BSODs and I don't even have a minidump folder. I've used the tool provided in the sticky on the front page of this sub forum as well as "Blue Screen View". I've also just plain searched my "Windows" folder with no luck either. I've had my settings use "kernel memory" and "small memory". I asked if I should use "complete memory" but never got an answer and the process for that seems much more tricky potentially. If that is an answer, I'd like direction on how to do that right. Any help in any way would be very welcome.


My System SpecsSystem Spec
.
31 Mar 2014   #2
Jahkepon

Windows 7 Home Premium x64
 
 

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

Windows 7 Home Premium x64
 
 

I've been really busy lately and not on my comp much anyways, but I'd still like to solve this problem as the fact that it still exists is keeping me from wanting to move on and get programs and do things on my computer in general. So basically this is a "bump" just to remind the front page that I still am having troubles in the hope of attracting people with answers.
My System SpecsSystem Spec
.

16 Apr 2014   #4
Jahkepon

Windows 7 Home Premium x64
 
 

...and I'm bumping this again because I feel it's what's holding me back from fixing my problem and I find it hard to believe that no one here would have a solution or at least a suggestion for me.
My System SpecsSystem Spec
16 Apr 2014   #5
Callender

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
Suggestion

Well here's my thoughts on this. I'm no expert on BSOD's so can't give step by step instructions or advise on specific steps needed to resolve the issue.

Check through the following reasons why crash dumps might not be written out:

Resplendence Software - WhoCrashed, automatic crash dump not written


Also check the other documentation for more tips.

BSOD's on my own machine have historically been caused by either:

Running unsigned drivers

Running buggy or out of date drivers

Other causes to investigate are listed here:

Resplendence Software - WhoCrashed, Troubleshooting System Crashes

If you can narrow it down a bit - maybe start another thread. Like I said it's not my area of expertise so I can't help - only provide some information.
My System SpecsSystem Spec
16 Apr 2014   #6
Jahkepon

Windows 7 Home Premium x64
 
 

Thanks for the suggestions. There's more here addressing this issue of mine specifically than I've gotten in a long while. I feel if I could just get a crash dump file following a BSOD I might actually be able to fix the BSODs. I think I'll start with setting my computer up to do complete memory dumps rather than just kernel or small. Then I'll just go through the other items listed on that webpage if I need to.




Edit: Ah, I can't make a complete memory dump, I'd forgotten about that. I need to do something with a page file or something. I never did understand that but I'll dig around to see if I can find some instruction.
My System SpecsSystem Spec
16 Apr 2014   #7
Jahkepon

Windows 7 Home Premium x64
 
 

I set my virtual memory page file to twice the size of my RAM. RAM is 4 GB, so I made the page file 8. Then I acquired a complete dump memory setting via a reg download available in a thread here dedicated to helping one change their memory dump settings. I still have Driver Verifier going as that's supposed to help create dumpfiles as well. Now I just wait for the next BSOD I suppose.
My System SpecsSystem Spec
16 Apr 2014   #8
Jahkepon

Windows 7 Home Premium x64
 
 

Below is the report of my last BSOD, copy pasted from my original thread into this one...

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
Reply

 No Dumpfiles or Minidump folder for 0x0000007A Errors




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
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...
BSOD Help and Support
BSOD using Sage 300 CRE, errors 0x000000f4, 0x0000007a
This computer gave a BSOD and restarted while using accounting software. This has happened twice, a few days apart. See attached debug file. Thank you for your assistance. System Specs: Computer type PC/Desktop System Manufacturer/Model Number Dell Precision T3400 OS Windows 7 Professional...
BSOD Help and Support
BSOD after every boot up, errors 0x000000f4 and 0x0000007a
Hello all, First off, thanks for taking the time to read this posting. Been meaning to get around to this, but it's always been more of an annoying (if chronic) inconvenience than anything system-breaking at this point. The problem has been occurring for almost a year, shortly after I...
BSOD Help and Support
BSOD Randomly and Under Load, Errors 0x000000F4 and 0x0000007a
A few days ago, my computer BSOD'd while I was playing a game. The error code was 0x0000007a. I ran CHKDSK C: /F /R, Norton Antivirus Scan, and Spybot: Search and Destroy, and now whenever my computer is under load I receive a blue screen with this error message: 0x000000F4 I've uploaded my dmp...
BSOD Help and Support
Random BSODs - Errors 0x00000101 and 0x0000007A
My computer has crashed twice today, giving me error code 0x00000101. The first time was while watching Netflix, and the second time was while playing Minecraft. Additionally, I got an error code 0x0000007A (ataport.sys) while surfing the internet. Perfmon and Dump files attached below. Thanks...
BSOD Help and Support
Repeating BSOD, never get minidump file, always 0x0000007A
hi all, i keep getting BSOD crashes, always with the same information (0x0000007A code), KERNEL_DATA_INPAGE_ERROR, and the last two lines on the BSOD are always" "Collecting data for crash dump.... Initializing disk for crash dump..." After that, it stops, and i have to force a reset. ...
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:24.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App