Solved BSOD 0x0007A kernel_inpage_err, 0x00F4 and operating system not found

[MvdB]

Please try running this link: Page file must be on OS drive
http://sysnative.com/0x8/WMIC_Recoveros_Pagefile_04-2010_jcgriff2_html.exe

 

[srinpraveen]

pagefile.sys is on my C drive (OS drive). And attached here is the screenshot after running the link that you gave. So any clues can be gathered from that?

 

[MvdB]

I think that now looks ok. When you have another BSOD, check that minidump dir.

 

[srinpraveen]

But though it mentions that the dump files are gonna be stored on that Minidump folder, when I go and visit that directory (C:\Windows) I don't see any such folder nor any *.dmp files even if I enable "see hidden files and folders".

This means that the minidump folder is gonna be created only if a bsod occurs and at the same time if a dump file is written successfully. Since the bsods has happened, but I don't see the folder, that leads me to believe that the dump files are not written.

Is my inference correct?

 

[srinpraveen]

@Mvdb,
The BSODs are getting menacing. I just now got a kernel_data_inpage_error. I couldn't even catch a glimpse of the bsod as the settings is set to restart the system upon the system failure. And I still don't see the dump folder or any *.dmp file. Do you reckon I give it for a service to check the RAM and hard disks for any ailments and probably get them replaced?

 

[MvdB]

Try some testing yourself first:
SFC /SCANNOW Command - System File Checker - Windows 7 Forums

and memory testing:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[srinpraveen]

I have done the former. But am yet to do the latter ie.memtest+. I will do it and let you know as soon as possible.

 

[srinpraveen]

I did the memtest for 2 passes. And there are no errors. So what next? And I have had no success with dumps so far.

 

[MvdB]

I did the memtest for 2 passes. And there are no errors. So what next? And I have had no success with dumps so far.

Memtest needs to run for a long time, 6 to 7 passes. It will take all night... Only then can you be relatively sure...

 

[srinpraveen]

Oh that's news to me. I will do that tonight then. Will do it for 7 passes. Will report back tomorrow.

 

[srinpraveen]

@Mvdb,
I ran memtest all night. And doesn't seem to show up any error. So what is the next step now?

 

[MvdB]

Lets be sure(r) and do CPU and HD tests too:

For a full diagnostic of your HD that goes beyond Chkdsk, see:
HD Diagnostic

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then when it really looks like it is not HW... we'll use Driver Verifier...

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[srinpraveen]

@Mvdb,
The free GIMPS link for windows 7 64 bit did not work. Is there an alternate link for that? By the way, I am going through the other link that you have given.

 

[MvdB]

@Mvdb,
The free GIMPS link for windows 7 64 bit did not work. Is there an alternate link for that? By the way, I am going through the other link that you have given.

??? just tried it (yours is the 64B...) and it works fine : ftp://mersenne.org/gimps/p64v266.zip

 

[srinpraveen]

It was not working in internet explorer. But I was able to download it through firefox with internet download manager. Thanks and I will check it out and report back.

 

[MvdB]

Hello Srinpraveen, did it work? You ok now?

 

[srinpraveen]

I didn't know exactly what I needed to do with GIMPS. But all I did was just started the Prime95.exe file and it started running some "threads". I started monitoring the temperature simulaneously with CPUID Hardware Monitor. At idle conditon the temperature was 57 degrees. But when I ran gimps, the temperature kept rising to the eighties and then the 90s..And then I got alarmed. I closed the application out of fear. Here is the screenshot of the temperatures. Maybe if I hadn't closed gimps, the temperature of the core may have even gone upto 100 degrees. Who knows!!

Sorry that I couldn't respond back sooner.

 

[MvdB]

Ok, thx for posting back. Prime tests your system 'harder' than most normal software would. We use it to see if, by forcing hard work in the system, we can identify the source of problems that we have. In your case, I'm still unsure to be honest, but it sounds to me as if 57 idle is a bit on the high side and tested you certainly want to keep it below 90, even 85. Are you sure all airways, fans etc are clean/no dust choking things up?

 

[srinpraveen]

As far as I can see, there seems to be no dust on the airways and vents. But whether there is dust on the fan--That I guess can be determined by dismantling and opening and examining the laptop and I am not too good at removing stuff and examining...But I think hopefully there shouldn't be any dust internally. For running my normal apps/work, the core temp hovers between 50 to 58 degrees as can be seen in the screenshot. (Am running mozilla firefox, gom player and ms sticky notes)

 

[MvdB]

Don't know what your ambient temp is but that seems to be a bit high