Hi,

I've recently started to have BSODs at least once a day and it's starting to take it's toll on me

What I get is a Kernel Inpage Error most of the time, can't remember if I've had any other type of error messages. I've seen once that the bluescreen referes to ataport.sys though.

I have not made any hardware upgrades or driver changes for several months before the issue with BSODs appeared. Before the BSODs I had been on vacation for two weeks and can't remember if I did any heavy software installations just before the problems started occuring.

Also tried checking the event viewer to see what that says. The most recent error I got were:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xc0416a60, 0xc000000e, 0x2fbfa860, 0x82d4ca9c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071810-20342-01.

Most of those error messages are about "rebooted from a bugcheck", what does that mean?

Attaching the most recent minidump file as well (both the dmp and the debug log from debugwiz).

Thank you, hope you can help.

Blue screen with this error code: KERNEL_DATA_INPAGE_ERROR, STOP: 0x0000007A

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

Use check disk command for any errors on hard disk -

Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.

Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.

NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.

You may refer to the below mentioned link for more details -
Content Removed (Windows)

Your log also indicated in several places that there are disk errors. I would back up your personal files to prepare for the worst. Diskcheck might fix it but I suspect that your drive is dying.

Thanks for the help. What sucks is that the harddrive is like 3-4 months old. Maybe the warranty will cover this?

its should. with it that new I would rma it. it shouldn't be doing that.

I've run chkdsk now but no errors were found. It told me I had a clean disk. I know BSODs can be a little hard to figure out what the underlying problem really is. How sure can I be that it is actually a harddrive problem, versus a harddrive controller problem? (The logfile said the controller could also be at fault...) Or any other system problem for that matter, with the harddrive controller only being the symptom of an underlying problem?

I've already done a Memtest86+ test and it passed with flying colors. I'm thinking of doing like a superpi test also, but that only tests the processor though I'm told. I've gotten bluescreens in idle mode though (had the comp on overnight and woken up to a BSOD for example), or while only playing some music, can't be such a toll on the processor me thinks..)

I recommend that you get the manufacturer's diagnostic tools and scan the drive. Be sure to use the comprehensive scan. You'll probably have to scan the drive with them before you'll be allowed to rma it anyway.

As for the drive vrs drive controller, I'm not sure. However It might be more of a possibility if either you used another drive on that computer and still had problems or that drive in another computer without problems. However you just can't plug that drive into another computer and not expect to have problems. If you run windows in another computer than the one it was installed with you are more than likely to have driver and/or registry conflicts so it would have to be used as a secondary drive.

If you're questioning the CPU you might want to read this: http://www.smartcomputing.com/editor...2r04/22r04.asp

As you can see, if it is the CPU the problems are more than likely to be worse than the symptoms that you are having. Besides, did you not read that post?

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

There is a reason why there are so many different error codes--to help you determine the cause. From http://technet.microsoft.com/en-us/l.../cc957628.aspx

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

So it is more than likely the drive or memory. Other than that I would suspect a problem with windows or a virus over the CPU.