BSOD caused by Ntfs.sys

[KairosDialga]

Uploaded is the needed ZIP file from the instructions, I have no idea what else I need to post in this concerning details with trying to help with this BSOD of mine. (I'm sorry, I'm not very good with computers actually, so some things I may have to ask with clarifying on.

-Anyways, I ran Memtest through several passes, checked out with no errors.
-Used HDTune to make sure that it wasn't my hard drive failing, checked out entirely fine with no damaged sections.
-Chkdsk didn't help since it did still BSoD after running that. I have no idea if it repaired any errors or not when I ran it because I was away from the computer while it was running on bootup.
-I ran several virus, malware, and rootkit scans and all checked out ok.

This computer is a custom build, only 5 months old so I'm really wondering as to what it could be this early. I don't have a system repair disc at all, just the Windows Installation disc, I don't know if I would be able to do a repair from that.

And I don't want to do a clean install unless it is a last resort, and if I have to, I won't be able to do that until probably after Christmas because my external HD won't be here until then since I have a ton of important files to save and backup.

 

[Golden]

fffff880`0333fac8  fffffa80`00000002
fffff880`0333fad0  fffffa80`0c262001
fffff880`0333fad8  fffff880`07360201Unable to load image rtwlane.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="Red"][B]rtwlane.sys[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys
 rtwlane+0x123201
fffff880`0333fae0  fffffa80`00000000
fffff880`0333fae8  fffff8a0`1b328c70
.
.
.
    Loaded symbol image file: rtwlane.sys
    Image path: rtwlane.sys
    Image name: rtwlane.sys
    Timestamp:        Thu [COLOR="red"][B]Sep 26[/B][/COLOR] 12:34:22 [B][COLOR="red"]2013[/COLOR][/B] (5243A436)
    CheckSum:         002E5CA3
    ImageSize:        002ED000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the Realtek wireless driver from here:
Realtek

fffff880`0333e808  fffff880`00000000
fffff880`0333e810  fffff880`0904db40Unable to load image aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="red"][B]aswMonFlt.sys[/B][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
 aswMonFlt+0x1cb40
fffff880`0333e818  fffff880`0333e830
fffff880`0333e820  fffffa80`121a9010

Replace Avast with MSE.

DAEMON Tools Lite	"c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	Games\April	HKU\S-1-5-21-1359300711-755945027-3949031439-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Uninstall Daemon Tools - it uses the sptd.sys driver which is a well-documented cause of BSOD's.

 

[KairosDialga]

Alright, I did replace Avast with MSE, but I'm stuck on the other two things.

First off, I have no idea which wireless driver to use in the link you gave me. The wireless card I have installed isn't a realtek brand, what I have is an 'ASUS PCE-N10 11n Wireless LAN PCI-E Card' Looking on that list it shows a few options that have 11n for the list of things on there and thus I have no idea which one to use.

Also the Realtek network driver that seems to appear in my driver manager is 'Realtek PCIe GBE Family Controller' which when I did download the one for my OS and launched it, my only option were to either remove or repair. Which did the repair in hope that maybe it did update it?

As for Daemon Tools, would there be an alternative to that of which you recommend then that wouldn't cause BSOD's? Because I actually need to use that to play a game of which I lost the actual disc for (I play that game extremely often as well) and I can't find a physical copy of it anymore to allow me to play without using that.


Though as an update, I did run MalwareBytes through another scan last night and it did detect something of which I did get rid of, but I cannot confirm if maybe that was the cause of the BSoD. I'll update on when there is another one, though.

 

[Golden]

The Realtek and ASUS wireless device use the same driver:

Name	[00000007] [COLOR="red"][B]ASUS PCE-N10 11n Wireless LAN PCI-E Card[/B][/COLOR]
Adapter Type	Ethernet 802.3
Product Type	ASUS PCE-N10 11n Wireless LAN PCI-E Card
Installed	Yes
PNP Device ID	PCI\VEN_10EC&DEV_8176&SUBSYS_84B51043&REV_01\4&2A24CC02&0&0028
Last Reset	12/12/2014 5:02 PM
Index	7
Service Name	[COLOR="Red"][B]RTWlanE[/B][/COLOR]

Many disc mounting software use the sptd.sys driver - you'll have to do some research of alternative products to find something suitable, or you could risk using Daemon Tools.

 

[KairosDialga]

Alright, after a long long while of hunting around to figure out what sort of chipset or something of the wireless card to correspond with the realtek driver, I did finally find it and updated it.

Though I did end up having a bluescreen after doing the things in the prior post and before updating the realtek driver. But this time it was caused by ataport.SYS
I'll still attach the crash report just in case it might bring to light other things outside of that specific driver as well to possibly try since it appears to have a different cause as opposed to others.

I still have yet to uninstall daemon tools, but I'm searching into alternatives at this moment to replace that.

 

[KairosDialga]

Well, new BSoD, still same reason as the first, (caused by NTFS file system). Log is attached to this post.

The only thing I haven't done so far was uninstall Daemon Tools, but it was because I was still using it not too long ago as well and still have yet to find an alternative at the moment.

 

[Golden]

fffff880`0d6b8378  fffff880`019ae3c8 cdrom!WPP_ThisDir_CTLGUID_wppCtlGuid+0xf8
fffff880`0d6b8380  00000000`00000000
fffff880`0d6b8388  00000000`00001f80
fffff880`0d6b8390  00000000`00000001
fffff880`0d6b8398  00000000`00000000
fffff880`0d6b83a0  0000057f`f020b258
fffff880`0d6b83a8  fffff880`019a247e cdrom!RequestDispatchToSequentialQueue+0x1346
fffff880`0d6b83b0  fffffa80`0f6958d0
fffff880`0d6b83b8  fffffa80`0fdf4da0
fffff880`0d6b83c0  00000000`00000000
fffff880`0d6b83c8  fffff880`019a0e0e cdrom!RequestDispatchProcessDirectly+0x3a
fffff880`0d6b83d0  fffff880`019ae3c8 cdrom!WPP_ThisDir_CTLGUID_wppCtlGuid+0xf8
fffff880`0d6b83d8  0000057f`f020b258
fffff880`0d6b83e0  fffff880`0d6b8ac0
fffff880`0d6b83e8  00000000`00000024
fffff880`0d6b83f0  fffffa80`0c43b680
fffff880`0d6b83f8  fffff800`02dc130d nt!ExFreePoolWithTag+0x22d
fffff880`0d6b8400  0000057f`f020b204
fffff880`0d6b8408  fffff880`019a02a5 cdrom!WPP_RECORDER_SF_L+0xc5

Its not definitive enough, but there are lots of references to CDROM - may or may not be related to sptd.sys.

 

[KairosDialga]

Alright, I can make do without using that sort of program for the time being then since I would rather end the BSoDs first. So I'm uninstalling it right now. ^^

I'll keep updated on if there are any more in the future after this.

 

[KairosDialga]

New BSOD again, this time the reasoning stated in Blue Screen View is Cache_Manager and ntsf is still part of the culprit.

I did uninstall Daemon tools as well so it shouldn't have been that now, so I have no idea what it could be this time around.

 

[Golden]

Is your RAM over/under-clocked at all?

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Reference this tutorial to help you use MemTest86+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[KairosDialga]

I have no idea how to underclock or underclock, so I should be good on that front I guess?

I'll try to do Memtest again when I have another long stretch of time which may take at least week or so for me to acquire, Sadly it takes a long time for my computer I think due to how much memory it has to test on mine (Last time I did it I had it running for 6 hours and it only got 2 passes finished with no errors. This computer has 16 gigs of RAM if that affects anything)

Though, is it normal for it to take this long? Also I do have something that measures the MHz of the GPU and the memory, I haven't touched any settings from how it was set at default when my friend assembled this computer for me.
http://fc09.deviantart.net/fs71/f/2014/353/8/6/gpu_by_tailic-d8afyca.png
Those are the MHZ settings thingy for the GPU that I have, I actually don't touch that at all so I have no idea on if I need to after the settings of that or not.

 

[Golden]

Though, is it normal for it to take this long?

Yes, thats normal...mine takes the same length of time on 16Gb.

 

[KairosDialga]

Any attempts to run Memtest has been mostly fruitless, the most I have been able to get was 3 passes (12 hours) with 0 errors but my parents keep turning my computer off on me when it is partway through and keep telling me as to 'how I'm wasting power keeping it on while I'm not using it'

Even trying to tell them what I'm doing just goes right over their heads as well, so I won't be able to actually get the chance to do a full run until May at the soonest since then is when they would be gone for a few days. : /

And I have had 2 more blue screens again, I think both for different reasoning? I wonder if there are other things that could also be flagging them as well since I would rather replace the memory when I'm certain that it is that. (but the sticks were just bought about 7 months ago, brand spanking new...so it's not like they even had much use yet either.)

Also a question concerning Memtest, if I just ran it with only one of the 2 memory sticks inserted in, and then later ran it with just the other one, would it still get similar results on finding out if one of the sticks is faulty? Since doing it that way may help in trying to cut some of the time down and possibly be able to get 8 passes in during an overnight and get the computer off before they notice it as opposed to running it with both sticks in.

 

[Golden]

Yes, you can test each stick individually.

 

[KairosDialga]

Well, I was able to get the sticks through the 8 passes by doing them separately, but memtest reported to me 0 errors on each of them.

I apologize if this is becoming difficult to figure out and for sounding so needy too.

 

[Golden]

OK. Kets see what Driver Verifier finds.

Follow:
1. Log in as administrator, open Windows Explorer and go to C:\Windows\Minidump
2. Delete all .dmp files in that folder
3. Run Driver Verifier as follows:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[KairosDialga]

How do I know if Driver Verifier is working properly? I've followed the instructions to it EXACTLY and had it running for 2 days and I can't get my machine to BSoD on me. Instead if periodically crashes and locks up (but no BSoD) and the screen looks like a ton of coloured bars when it does so as well.
(This is what it looks like when it crashes -- http://fc07.deviantart.net/fs71/f/2015/004/f/c/hni_0070_by_tailic-d8ckcug.jpg )

I deleted the verifier settings and this hasn't happened yet after trying to induce the same load as when it was on, but when it was 'on' I couldn't notice any sluggish behavior from my computer at all, and there wasn't any sort of 'driver verifier' process in my task manager either if there should be one.

 

[KairosDialga]

I can't get it to blue screen still when in driver verifier (The computer just freezes up and crashes without bluescreening, so it doesn't make a dump), though I did have 2 blue screens when the driver verifier was off, though. : /

 

[KairosDialga]

I'm in desperate need of help still, when I use Driver Manager to force the computer to crash, I STILL can't get it to make a bluescreen, it still just only gives me the multi-coloured bars like in the image I put two posts above (Won't give me a blue screen image and WON'T create a bluescreen dump either). So trying to diagnose from that is apparently going to be a no-go if I can't get you a bluescreen dump created with driver manager on.

So I have no choice but to have to work from dumps with the driver manager off because of this. : /

Anywho, new bluescreen happened as well.

 

[Golden]

Sorry for the late reply. The image is a classic symptom of a problematic video card and/or drivers.

Try this:
1. Uninstall all the video card drivers and associated software.
2. Re-install the latest stable version of the drivers
3. Stress test the card by running this for 20 mins, noting the temperatures reached

http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html