BSOD 0x0000007a ntoskrnl.exe

[Holty10]

This has happened a couple of time today, it also happened a few weeks ago but didn't create a dump file. Since then it hasnt happened until now. So I have attached the requested files. Not sure what information you may need, but this is an Acer 5738zg laptop.

 

[koolkat77]

Welcome

Problematic Software

Start Menu\Programs\Advanced SystemCare 6	Public:Start Menu\Programs\Advanced SystemCare 6	Public
Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public
Start Menu\Programs\ESET\ESET NOD32 Antivirus	Public:Start Menu\Programs\ESET\ESET NOD32 Antivirus	Public
Start Menu\Programs\IObit Malware Fighter	Public:Start Menu\Programs\IObit Malware Fighter	Public

Please uninstall these softwares including Eset Antivirus and install MSE while we are troubleshooting with your computer. Multiple antivirus programs may also cause blue screens. Please uninstall IObit as well. Programs like advance system care cause a damage to windows 7 system that is beyond repair.

:ar: Microsoft Security Essentials - Free Antivirus for Windows

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR BSOD Index

Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack.

To make sure that hard drive is good run disk check following the tutorials:

Disk Check
Hard drive scan usings SeaTools:

SeaTools | Seagate both long and short tests.

You should run memtest86+ on each stick for 8 passes preferably overnight:

Memtest86

Run the system file checker to repair damaged windows files
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html


Post back results

 

[Holty10]

Well so far I've uninstalled the programs, however got a different BSOD error when installing the Seagate software. I've attached it to this post.

 

[Holty10]

Just ran the Seatools short test and it passed, then ran the long test and it failed.

The test had only for a few minutes and the progress bar had moved maybe 1/32 of the way.

Edit, they were both the 'generic' tests, I have just run the short DST, and that failed. I have no option for a long one, but I assume that would fail too.

Edit 2, ran chkdsk /r as this helped me a couple of weeks ago, re done the short dst test and it still failed, although made more progress.

also just performed scannow, and attached results. Looks as though there has been some problems, but the scan did finish.

I will do the memory test when i can if its needed but it looks like this may be my problem as far as i can tell

 

[koolkat77]

The new dump does not give correct information.
So we'll wait for the memory test result.

 

[Holty10]

I ran the memory test last night and when i woke up this morning the laptop had shut down. I dont know if it's meant to or not.

 

[koolkat77]

Sounds like hard drive failure.
Whats the age of the hardware?
Is it under its warranty?

 

[Holty10]

The laptop is about 2 years old now, so I dont think it is still under warranty. Is it likely that I am going to need to buy a new one?

 

[koolkat77]

Most likely. Take a back-up of all your important data just in case.

It could be heat related also. Do you have a cooler?
Does your laptop feel warm? Were you able to see any results from the memory test?

CPU burn test with:
:ar: http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

Hardware Stress test with:
:ar: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

During these tests use Speccy to monitor your hardware temps:
:ar: Speccy - System Information - Free Download

Also tell me your temps during normal usage.

 

[Holty10]

CPU is at 55 at launch of the program, motherboard is at 60 and hard drive is 48. No I dont use any cooler, I have considered the fact that my laptop has seemed to be getting warm, and have noticed high temps.

Running the IntelBurnTest on standard my laptop just reached 88 CPU and 96 Motherboard.

 

[koolkat77]

Any BSoD? Freezes?

 

[Holty10]

Sorry missed the reply as it was on the next page. No nothing, I havent run the other test yet as i wasnt sure how high these values were. In fact i havent had a BSOD since that last one i mentioned in this thread. It did this last time I ran chkdsk though too, I had a period where everything seemed better, then after a while it happened again.

 

[koolkat77]

Alright, use your computer the way you do and keep a check on the temps
If the BSoDs/freezes/ happen again, let us know. It'll take a while till we find out what the problem actually is.

 

[Holty10]

Okay, thanks for the help so far.

 

[koolkat77]

Sure, come back and update this thread when needed.

 

[Holty10]

Didn't last too long. Just got another BSOD, looked very much the same as the first 2. I can upload the dump if needed.

 

[koolkat77]

Please upload them

 

[Holty10]

Here you go, put all 4 in.

 

[koolkat77]

Well yes, same error.

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data 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/Windows 7 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 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.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

 

[Holty10]

I havent had a BSOD whilst running this yet. Should I just keep waiting?