Solved Frequent BSOD Kernel Input Data Error 0x07a on Win7 64bit ptBR

[lpachec]

Frequent BSOD Kernel Data Inpage Error 0x07A on Win7 64bit ptBR

I'm getting this system error when my computer does multiple things or runs specific aplications. I used to have Win7 for years straight flawless since these errors started to happen about 3 weeks ago. Differently from others users from this forum experiencing same error as mine I don't get this error when returnining from hibernation or restarting. It just happens on a regular basis. The behavior before the crash: first the aplication I'm running stop responding, then mouse cursor freezes, then the computer itself stop and finally after a few minutes the blue screen. Things that i've done so far:

1 Re-installed Win7 (all Windows Updates as well) / All drivers were updated
2 Replaced the lithium battery from mobo, checked all cables and memory connections
3 Ran Full virus scan
4 Ran Chkdsk /r (x2)
5 Ran CCCleaner, Advanced System Care, Spy bot search and destroy, TSSSKiller full scans
6 Ran Windows® Malicious Software Removal Tool (KB890830) x 64
7 Ran Scf /scannow

Needless to say items 3 to 7 didn't show any issue. Somehow I can't make Windows create the dmp files (yes I've enabled it in Startup and Recovery Settings and on and followed all the instructions said on this forum) but it didn't even create the Minidump folder in C:\Windows. Not sure if updating the BIOS would help. Yesterday Microsoft lanched an update on Windows Update and I thought it would solve it, but didn't. Attached the zip file from SF Diagnose Tool below.

Any ideas please?

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any kind of disc cleanup program before you upload the data.

 

[lpachec]

Thanks for your prompt reply Arc!
As soon as i get the stop error i'll let you know.

 

[lpachec]

The system crashed again and no Minidump or dmp file was created even after following (merging) the registry. =/

 

[Arc]

Ok ... then we may try it ... but a crash dump helps to to be precise.

According to Carrona.org, STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

Let us discuss those one by one ....

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Try to clear Page Files.
How to Clear the Windows Paging File at Shutdown

Do some Disc checks.

1. Re-seat the sata and power.
   
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
4. Tkke the WD Data LifeGuard for your HDD and test. http://support.wdc.com/product/download.asp?level1=6&lang=en

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Dismantel the PC and make it sure that all the hardware components and cables are properly fixed.
Dont forget to apply thermal paste while re-seating.

The BIOS is very old ....

Versão/data do BIOS    American Megatrends Inc. 080012, 25/02/2008

But no proper updates are available at ECS Web Site > 945GCT-M2 (V1.0) . You may search it, too.

Service pack is installed, so we can overlook that point.

Unfortunately a motherboard cannot be tested. If all the above faile, the issue will be narrowed down to the motherboard.

 

[lpachec]

I'm trying Windows Defender now. Meanwhile, any idea why my Windows is unable to create the minidump ?

 

[Arc]

If the dump recording is properly configured, there should not be any reason to not record a dump.
If a BSOD takes place before the desktop appears, it might not record a dump, but I guess it is not your case?

So I am also out of idea at this point.

BTW, you should uninstall Advanced System Care. Its a crap that causes various range of issues.

 

[lpachec]

Windows Defender Offline causing extreme BSOD when making the boot dvd. I can't use that tool for now. Ran TDSSSkiller and nothing found.

Going for chkdsk now.
Thanks again!

 

[lpachec]

Windows Defender Offline causing extreme BSOD when making the boot dvd. I can't use that tool for now. Ran TDSSSkiller and nothing found.

Going for chkdsk now. Tried it twice already but ill give it 1 more try.
Thanks again!

 

[Arc]

Windows Defender Offline causing extreme BSOD when making the boot dvd.

Is it the situation whenever you use the DVD drive? Check the cabling first then.

EDIT: These programs have bearings on cdrom.sys. For a test .... uninstall those and and check if the CD drive (Both D and E ?) are working the same way or not.

• Matroska Pack
• Nero 12
• PowerISO

Due to lack of a crash dump, the search becomes a lot of trial and error

 

[lpachec]

Windows Defender Offline causing extreme BSOD when making the boot dvd.

Is it the situation whenever you use the DVD drive? Check the cabling first then.

EDIT: These programs have bearings on cdrom.sys. For a test .... uninstall those and and check if the CD drive (Both D and E ?) are working the same way or not.

• Matroska Pack
• Nero 12
• PowerISO

Due to lack of a crash dump, the search becomes a lot of trial and error

No. It crashes when before burn the dvd so i think it is not the dvd device. Ok I'm uninstalling all the applications you're telling me. ^^

 

[lpachec]

Hello again Arc.
Did everything you said... but I'm still getting the BSOD with the same code error. =(
Any new idea?

 

[Arc]

And still there is no crash dump?

 

[Vir Gnarus]

I wouldn't doubt crashdumps aren't being made. If the issue is a kernel inpage error, it almost always means the drive was not accessible at the time due to an error retrieving data from it, and perhaps continued to be inaccessible even during the bugcheck. I recommend you look at replacing your drive, updating your BIOS when running Safe Mode on Windows, and checking your RAM as well just to make sure (if you haven't already). If you have an SSD, look for firmware updates for that too.

 

[lpachec]

I wouldn't doubt crashdumps aren't being made. If the issue is a kernel inpage error, it almost always means the drive was not accessible at the time due to an error retrieving data from it, and perhaps continued to be inaccessible even during the bugcheck. I recommend you look at replacing your drive, updating your BIOS when running Safe Mode on Windows, and checking your RAM as well just to make sure (if you haven't already). If you have an SSD, look for firmware updates for that too.

Hello Vir Gnarus, thanks for your reply.
Earlier today before Bios startup a disk error ocurred (Error reading disk - press Ctrl+Alt+Del to restart). After I restart Windows loaded normally. Maybe a the HD's cables causing the BSOD?? Something I've also noted is: Windows always crash with the error on this error - Kernell Data Inpage - when trying to copy large amont of files into hard disk (ie: copying photos from camera to hd).

Yes I've checked Ram and I don't have SSD and as far as i know, I have the latest Bios update (even it is from 2008). I'll double check Hds cables now.

 

[lpachec]

And still there is no crash dump?

Nope!

 

[Vir Gnarus]

Yes, check those cables (both power and data) before considering replacing the drive.

 

[lpachec]

finally managed to find where the problem was!
The sata cable i was using was damaged!
After replacing it for a new one my system is now working properly.
Thanks!

 

[Arc]

Ah! Its very good to know that you have caught the issue and removed it.

For any further issue, let us know

 

[lpachec]

Thanks Arc. really appreciate it.
changing the cabe was indeed the last thing i tried. never seen this happen to anyone else though. best wishes ^^