Windows 7: BSODs and games not responding ( 0x0f4, 0x07a "ntfs.sys" )

Hello all,
So I've had a list of current problems that have been driving me up the wall lately. I have a sager np9150 notebook with the following specs

gtx 680m
core i7 3630qm
16gb ram @ 1600mhz
windows 7 64-bit home edition
750gb mechanical drive
bigfoot wireless N


So as some of you may be aware, i've cycled through various problems over the past year, which most are short lived. Most have consisted of BSOD errors and driver issues.
After having WoW crash on me countless times I decided that the newer drivers from nvidia were complete garbage and went back to 306.02 . I havent had any problems whatsoever in WoW with that driver, however I've been trying to play battlefield 3 for the past couple days and the game will stay up for anywhere from 1 minute to 20 mins before the game stops responding. This also just happened in a clean install of Crysis 2. The game stopped responding during the opening cinematic. The other issue is if i leave my computer alone for a little while ( lets say 20 mins ) i've come back to BSODs that failed to make minidump files. I've tried running disk defrag but it has resulted in 2 BSODs before finishing. I've cleaned out my vents almost weekly, tried all sorts of different drivers, ran CHKDSK in command prompt. and now im at a loss. I would love some insight. And to anyone who can just help me play games again, i would gladly buy you a virtual drink.

Hi GrimmCat,

The virtual drink sold it for me

Check to see if windows is configured to collect the correct info?
You want small memory dumps - "MiniDumps"

https://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Run the SF Tool which will collect info needed to analyse your issue (and hopefully any dump files):

https://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html




F4 and 7A are usually storage related /disk controller error, but can be related
to RAM and virus infection also.

Ntfs.sys is the driver file that allows the system to read and write to NTFS drives.


So I would say a good starting point is to test your HDD's.

Download CrystalDisk and post up a screenshot.

Test your hard drive. Perform a Hard Drive Diagnostic Procedure

Scan the system for possible virus infection:

https://www.sevenforums.com/tutorials/166445-windows-defender-offline.html
http://support.kaspersky.com/5350?vs=s88446#s88446

Test the memory:

I would firstly try re-seating the RAM, ensure they are free from dust, and seated properly.
Then run memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight, pay particular attention to #3 in tutorial if errors occur

Cheers

Dave

Hey thanks for the reply!
While grabbing all the stuff from SF diagnostic tool, I got this little error message..Found it a bit off.


The document it put out will be in my attachments.

After running crystal disk I came up with this, which doesnt look good at all:


I'm guessing thats my entire problem right there...I would go about resetting the RAM but it's under my keyboard, so that will be a pain in the butt, but its doable.

I've had avast and malware bytes running and havent come up with anything. I've also cleaned my registry with Ccleaner.

Memtest will happen while I'm in class in a few hours.

P.S. it turns out I've had minidumps on this entire time. I've posted some BSOD problems before. But for some reason it's almost like the BSOD itself is locking up, which is double fail. It just sits there saying its initializing, or that its failed putting out the dump file...Never seen that before.

Hi,

I would suggest to back up your data and test the HDD:

Run chkdsk in an elevated command prompt in order to check for file
system errors and bad sectors on your HDD:

• Click on Start>Type in search cmd
• Right click cmd and Run as Administrator
• At the command prompt please type: chkdsk /f/r
  (There is a space between chkdsk and /f/r)

Also test the hard drive if chkdsk does not find any errors:

http://carrona.org/hddiag.html

cheers

Dave