Windows 7 Random BSOD when working, Error-Checking Drive Failure, Windows 7

S

sirjonathan

New Member
Joined
Jan 7, 2014
Messages
8
Hey Guys, first time posting here so hopefully this can be cleared up easily. ( I have Windows 7 64xBits Home Premium and More info is under my profile.)

I have been getting random BSOD's for quite a while now and I am at my wits end. Sometimes it occurs right away, say when I open up Photoshop when I am deep into work, at other times it will be quite a while before it happens, in either case, I mostly get either "Error Memory Management" or "page_fault_in_nonpaged_area", and sometimes I get other cases similar to that or non listed. I have run Memory Checks when I restart my computer but it turns up nothing, however, I have run SFC Checks that have yielded some files that I cannot fix, and I posted those below. I don't know what causes it because it comes out of nowhere most of the time.

When I try doing a Restart and Error-Check the Drive, it will give me a Blue screen of death around 4% mark, which a while back did not happen. This happens every time I schedule a disk check and it will go on a loop like that for hours. Any helped can be appreciated, thanks.
 

Attachments

Last edited:
Solution
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a01cf985c4, 0, fffff88001a21f80, 0}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memcmp+10 )

Followup: MachineOwner

Hi,
Ntfs.sys is a file system driver which I guess fits in with the possible failing drive. When you do a chkdsk...
Sort by date Sort by votes
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a01cf985c4, 0, fffff88001a21f80, 0}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memcmp+10 )

Followup: MachineOwner

Hi,
Ntfs.sys is a file system driver which I guess fits in with the possible failing drive. When you do a chkdsk do you tick both boxes to repair sectors? If not try that and run chkdsk again.. Normally if chkdsk fails to complete it's usually because the drive is failing. What type of drive you have?

Driver and Bios info:
BiosVersion = V17.3
BiosReleaseDate = 07/16/2013
Please update.
Link Removed

iaStorA.sys Tue Aug 07 16:43:10 2012: Intel RST (Rapid Storage Technology) driver
iaStorF.sys Tue Aug 07 16:42:20 2012: Intel RST (Rapid Storage Technology) Filter driver
Please update:
Link Removed (the driver utility should update your other Intel drivers too)

NTIOLib_X64.sys Thu Oct 25 11:27:58 2012: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
Please remove to test.

RTKVHD64.sys Tue Dec 04 13:28:37 2012: Audio driver
Please update:
Link Removed


rusb3hub.sys Tue Aug 21 05:14:52 2012: USB3 Driver: USB3 chip: NEC D720202
Your download is the third one down and try updating firmware too:
Link Removed

I also notice your running these too:

aswMonFlt.sys Mon Dec 16 22:28:29 2013: Avast AV

avgtpx64.sys Thu Aug 29 08:25:58 2013: AVG AV

SASDIFSV64.SYS Fri Jul 22 00:03:00 2011: Superantispyware.

Please remove and run MSE for the interim:
Link Removed
 
Upvote 0 Downvote
Solution
"Hi,
Ntfs.sys is a file system driver which I guess fits in with the possible failing drive. When you do a chkdsk do you tick both boxes to repair sectors? If not try that and run chkdsk again.. Normally if chkdsk fails to complete it's usually because the drive is failing. What type of drive you have?
"

Hi,

Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 931.41 GB (1,000,097,181,696 bytes)
Free Space 662.29 GB (711,124,066,304 bytes)
Volume Name Windows
Volume Serial Number C8527A26

this is what I found. And yes I check both boxes and it still did that and it caused a restart loop, that I can only get out of by Going into Safe Mode, Currently Updating all the drivers with your suggestion, will let you know when they are done.
 
Upvote 0 Downvote
Ran another SFC Chkdsk and after having one stop on me with a "windows resource connection could not perform requested operation" I managed to get the next one to work when I went into Safe Mode. Here is the newest CBS.Log file. I updated all the drivers like you suggested.

However, how do I Remove MSI Afterburner?

"NTIOLib_X64.sys Thu Oct 25 11:27:58 2012: MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
Please remove to test."
 

Attachments

Upvote 0 Downvote
If there is an icon in the Task bar for afterburner then it will still be running and need closing down. Try stopping it using Task manager and then uninstall it.
As for your HD looking at the 'SMART' data might help (post the results even). This web page tells you how:
Link Removed
 
Upvote 0 Downvote
I did get one BSOD when I first booted up after the test, but I will need keep it running a bit to see if it's all clear. Seems like things are moving forward though!
 
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0283572c8, 0, fffff8800f70af7e, 2}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+b9f7e )

Followup: MachineOwner

Hi,
this is the latest dmp file which points to the gpu driver. As you sent many more dmp files I could then have a good look at what was the issue. One thing which became apparent is that you have various dmp files pointing to totally different issues. This can at times mean that there might be a memory issue so please run memtest86:
http://www.memtest.org/

BiosVersion = V17.3
BiosReleaseDate = 07/16/2013
Please update.
Link Removed

Please uninstall Avast using this tool:
Link Removed
Please uninstall AVG using this tool:
Link Removed
Please uninstall SuperAntiSpyware using add and remove programs. Until bugchecking is over please run: Link Removed

It wouldn't surprise me that after all the bsoding thats been occurring you might have a corrupted os. If a SFC scan won't fix the files it might be time to re-install?
 
Upvote 0 Downvote
You must log in or register to reply here.