BSOD while playing Skyrim, other graphics heavy programs. Error 0x07a

First of all, this is going to be quite the tl;dr, so a big thanks to anyone who even takes time to read it.

I built my first rig in May, a mid to high grade gaming machine. Got it running successfully, everything seemed great until I started trying to play games. Oblivion was the first one. I started getting random blue screens from time to time. I thought it was my graphics card, so I sent it in for a replacement. Boom. Problem solved. Not another issue.

Several months later Skyrim comes out. Now I'm running into the same issue. Random blue screens. I've started investigating the error codes (I did not do this the first time around, just assumed it was a hardware issue and solved the problem.) Usually, it is a 0x07a error, KERNAL_DATA_INPAGE_ERROR, the offending file seeming to be ntoskrnl.exe. Sometimes other files will be in error as well, or I'll get a 0x0f4 CRITICAL_OBJECT_TERMINATION, but ntoskrnl.exe is always the error. Disk check goes fine, no error. Every test I do on the hard drive turns out okay. I have not tested both sticks of my ram, but I tested one of them with no errors and tried running the system on the one good stick, still getting a blue screen when I play Skyrim. I thought my graphics card or CPU might be overheating, so I bought a couple more fans. Keeping the system cooler has not helped either. Sometimes I would get a ntsf.sys error in my BSOD, so I wondered if my hard drive was bad, even though it passed the tests. I was also hearing what could have been some suspicious noises from it (though now I think it was the fan just cutting out in front of the hard drives). Regardless, I ordered a new hard drive and did a fresh install of Windows on it, in case that was the problem. I'm STILL getting errors. I'm wondering now if it's my mobo, because on occasion before the blue screen I'll hear the usb unplugged, then plugged back in noise.

Break down:

• Random blue screens only while doing something graphics heavy
• Replaced graphics card
• Replaced hard drive
• Tested RAM, tried switching their slots, or just using one at a time
• Purchased new fans to keep system cooler, didn't help
• Fresh install of windows on new hard drive
• Tried unplugging all usb devices
• All drivers up to date
• File ntoskrnl.exe is always in error, even on fresh install
• Sometimes ntfs.sys
• Error codes 0x0000007a and 0x000000f4
• Game freezes before BSOD
• Fan cuts out for a fraction of a second, USB restarts (I think only usb in the back restarts, front ones seem to be okay)

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? Retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? Some parts from May this year, some brand new
- What is the age of OS installation (have you re-installed the OS?) Just did it today


Hardware:
AMD Phenom II X4
2 x 2GB Transcend JETRAM DDR2 ram
Coolmax 650 watt PSU
ASUS M4A785-M Motherboard
EVGA Geforce gts 450 GPU
Seagate 1TB hard drive

I thought I would ask for help before I went ahead and replaced my mobo... Thanks in advance for anyone who takes the time to try to help. Let me know if you need any more info.

Most recent crash


KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error.

I would

1-run chkdsk

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.



2- Run a system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before sucessful

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Chkdsk:

221145545 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
91784100 KB in 83671 files.
56536 KB in 18855 indexes.
0 KB in bad sectors.
234587 KB in use by the system.
65536 KB occupied by the log file.
884582184 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
221145546 allocation units available on disk.

Internal Info:
00 91 01 00 89 90 01 00 e9 fc 02 00 00 00 00 00 ................
67 24 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 g$..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................



System file check:

Windows Resource Protection did not find any integrity violations.

Siesna said:

Chkdsk:

221145545 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
91784100 KB in 83671 files.
56536 KB in 18855 indexes.
0 KB in bad sectors.
234587 KB in use by the system.
65536 KB occupied by the log file.
884582184 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
221145546 allocation units available on disk.

Internal Info:
00 91 01 00 89 90 01 00 e9 fc 02 00 00 00 00 00 ................
67 24 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 g$..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................



System file check:

Windows Resource Protection did not find any integrity violations.

Ok CHKDSK passed


Is you paging file on the same HD as the OS? What size is it?

Is UAC turned off?


Ok lets also download cpu-z and gpu-z and find out what the absolute temps are.



Lets also run these two tests (yes I saw you ran "a" memory test. Did you run memtest for 7-8 passes?)


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-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/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.

Driver Verifier - Enable and Disable

I am checking the hard drive the OS is on. It's a 1TB drive. I have another 250gb hard drive, but I have it unplugged for now as I try to narrow down the problem. UAC is off.

I have been monitoring my temperatures during this whole ordeal, so I have a good baseline of information. My GPU idles around 31C, CPU at around the same temperature. When playing a game, my GPU climbs to about 70 and usually peaks there, every once and a while blipping up to 71C but I've never seen it go more than that. My CPU doesn't usually get over 55C when under load. Before I purchased two more fans to go on the side of my case, my CPU was getting up to 65C. The fans have helped it a lot. They've only helped my GPU by a few degrees, unfortunately.

The memory test I used was that program you have directed me to. I ran it for 10 passes with no errors. I have not tested both sticks, but I have been running the system on the one stick that did check out and am still getting the BSOD.

I will post again when I have completed the Driver Verifier.

Well, I just got a blue screen. However, it did not produce a dump file. I suppose I will continue use with Driver Verification running to see if it happens again. I was playing Skyrim when it happened.

Another blue screen, this one generated a dump, which I have attached.

Siesna said:

Another blue screen, this one generated a dump, which I have attached.

Still blaming memory corruption.

It could be hardware (RAM) or software ( driver)

What were the results of the memtest re-run?

Have you tried driver verifier? The current DMP was not verifier enabled.

I am rerunning the tests now. The first stick came out clean with no issues. The second stick is through 2 passes with no errors so far. I tested this before, and using the one stick I knew tested clean, still got blue screens, so I'm not sure if this is a simple hardware problem. Perhaps a more annoying hardware problem, lol.

I thought I had enabled the driver verification. I went through the steps and it seemed to be enabled. When I restarted though, my computer would not make it past the windows logo. I restarted again, and the second time it got through. Don't know if it disable it the second time or if I just did it wrong. I will try again when this memtest it done.

Thank you for your help!

Siesna said:

I am rerunning the tests now. The first stick came out clean with no issues. The second stick is through 2 passes with no errors so far. I tested this before, and using the one stick I knew tested clean, still got blue screens, so I'm not sure if this is a simple hardware problem. Perhaps a more annoying hardware problem, lol.

I thought I had enabled the driver verification. I went through the steps and it seemed to be enabled. When I restarted though, my computer would not make it past the windows logo. I restarted again, and the second time it got through. Don't know if it disable it the second time or if I just did it wrong. I will try again when this memtest it done.

Thank you for your help!

You can turn off verifier and upload the verifier enabled dmps