Page fault in non... BSOD (but not limited to this only)

[Kinothas]

First off, sorry if the thread title is badly named, couldn't think of any other title really.

My machine is less than a year old, been having issues with BSOD's for a little while now and I've been trying to fix them myself but I'm finally at my wits end. I'm not usually a forum guy but I always end up at this forum reading related posts, so thought you guys could help me out!

Anyway, I'm using...

Windows 7 Home Premium x64 full retail version.

Fresh install since I got a new HDD the other week.

Had graphics card related BSOD's, so I re-installed the drivers in the appropriate manner, even though they were up to date, those BSOD's have ceased happening now. I have CPU-Z if you need anything from that let me know.

Also I've ran memtest for 7 passes and everything came back clean..

Without any more rambling here's there crash dumps and report. (Sorry I can only post them in RAR format)

Thanks a lot guys, and if I've done anything wrong (broken thread rules etc) sorry in advance, been a long time since I been on a forum.

 

[Vir Gnarus]

The crashdumps I see are dated back to the 11th, which is pretty much around the time you did the fresh install on the new drive (actually, the log says you first installed at March 31st). All the crashdumps are disk-related issues such as failures during NTFS operation, plus one of your minidumps was created with it being 0 bytes in size which typically occurs when KeBugCheckEx managed to successfully initiate the dump procedure but nothing got dumped due to an I/O issue (most likely the drive was not responsive at the time).

I don't think it's coincidence that the only crashdumps that you provided us started during the time you started using the new drive, and considering that this started occurring even after a fresh install of Windows, then it has to be hardware related. The only exceptions would be if Windows failed to properly install or the partition Windows sits on was corrupt during installation. Yet most likely this is hardware failure, which I point finger at the disk.

In addition to the crashdumps, I did see in the syslog a single instance early on that there was NTFS corruption. Did you run chkdisk any this past month? Preferably do the full chkdsk (both options). In addition, I did see transaction errors reported by NTFS. Hopefully all of this is just because your NTFS partition is corrupt and a fix of it would do the trick, and that there isn't any underlying problem like the disk itself causing the corruption. You can run all basic and self tests on Seatools to see if it is the disk or the controller causing woes, but it's not a 100% guarantee it'll find hardware problems if they exist.

 

[Kinothas]

Nope, haven't run chkdsk at all, so will do that now. Thought it might be of note that some of these crashes did happen before the new HDD was installed, I was also concerned that maybe my PSU has slightly too low power to run what I have inside the machine, if you need further specs than whats posted in my profile I'm more than happy to provide. I'll report back once I've finished chkdsk and seatools tests.

Many thanks.

 

[Vir Gnarus]

PSUs can cause any various symptoms, and this would be no exception. If you believe your PSU might be too low for your hardware, then it probably is. Best way to look for a PSU is go for one that's 100W above what you anticipate it'll need. This is especially considering that any PSU running at 80% load or higher for any amount of time will start wearing out its parts quickly, so you want to avoid it as much as possible by going for higher. Also brand names and model series are actually very important in determining reliability of PSUs, since when you purchase a PSU you aren't paying for "performance" but rather reliability.

As for the crashdumps, I do notice in the syslog that while the BSODs did start at April 11, unexpected system shutdowns do occur frequently all the way back to even the first day of Windows installation on March 31. Have you been manually turning off the system for whatever reason? If not, then the system has been restarting forcefully, which could be caused by a heat sensor detecting an overheating CPU, a motherboard failure, or a PSU failure (PSU being most common).

 

[Kinothas]

Well chkdsk finished, i've attached a jpeg of it's results, hopefully it maybe of use to you. System is currently stable but then again thats how it goes every time, it'll be stable for a couple of days and then bam it hits again.

Hmmm manual shut downs? Only time I've ever done that is when the system literally hangs on the bluescreen or gets stuck on the windows start screen, it also tends to restart itself a lot on the windows start screen after the first BSOD happens.

Also I've ran all the seatools tests bar the long one, which I'll start soon. All results were clean. If there's anything else you need from me to help out with this just ask away

Thanks again.

EDIT: Also if you could suggest some decent brands of PSU, I'd be grateful, I'm holding off of buying one, in case it isn't necessary but been eying up a corsair one for a while, are they a reputable brand?

 

[Kinothas]

Every test came back as a pass. Any other ideas?

 

[cyclic]

For the original problem (page fault) make sure all your drivers are completely up to date
Sevenforums tutorial link
Also run a memtest, for a minimum af an hour.

Post any results, let's see how far we get.

 

[Vir Gnarus]

By default Windows is set to restart on BSODs as soon as it completes creating the crashdump. If for whatever reason KeBugCheckEx initializes the dump generation procedure but holds up during I/O due to some sort of failure, it will cause the BSOD to hang permanently until restarted.

I'd like to check a couple more things. Please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get your system to crash during a logging session, even better. It'll retain what was logged prior to the crash. Understand that this is rather dependent on your chipset drivers and stuff. Make sure all drivers for your motherboard are up to date as well as updating the BIOS. If you have any software that came with your motherboard installed, please uninstall all of them. They can conflict with HWInfo sensor readings and they often harbor nasty bugs.