BSODs occuring daily, Ntfs.sys or SYSTEM_SERVICE_EXCEPTION errors.

parraman · 26 May 2012

For a few weeks now I've been using my custom-made computer, put together with parts purchased by a trustworthy man that, unlike me, actually knows what he's doing with computers. About one week ago, when using YouTube on Google Chrome I experienced my first BSOD but didn't take any note of it expecting it to be a one-time thing. Unfortunately, it continued to occur to the point of it happening daily. In fact, the last one happened only a few hours ago which was the thing that convinced me to register on this site and ask the experts.

System specs (others can be found on my profile):

System: Microsoft Windows 7 Ultimate 64bit
Motherboard: Asus P8H61-M Le/USB3

Because I'm new, please forgive me if I don't do something right or I don't know how to do something but as long as you can help me fix this issue, I'll try to do anything you need.

Due to the BSODs occuring most when using Chrome, I have since uninstalled and stuck to Internet Explorer but I am still recieving at least one a day (twice today so far). I have attempted to solve this multiple times but simply lack the experience and knowledge. Every time a BSOD occurs, it contains the usual "if this happens again..." advice and it either has up the top "SYSTEM_SERVICE_EXCEPTION" and some codes down the bottom or nothing with caps at the top but says below:

Ntfs.sys - Address FFFFF8800123B5CE base at FFFFF 88001209000, Datestamp 4a5bc14f

I've followed the instructions as to how to make a dump file and have attatched it (not sure if it's right but I hope so). If you need me to upload anything else, feel free to tell me. As long as you think you can help me and simplify it to the point that a (relatively knowledgable) dummy could understand, I'd be extremely thankful. :)

parraman · 26 May 2012

Oh, one last thing, something suspicious occured a few days ago. A BSOD occured when I tried to perform a virus scan with Avast!. I later retried the complete scan and results came up with no threat detected. It may have just been a coincidence but I couldn't tell.

usasma · 26 May 2012

You've done quite well. Thank you for the reports and the concise description of your issues.

The first issue that I note is that you don't have Service Pack 1 installed.
SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

Next, I notice that you have a NETGEAR WNA1100 N150 Wireless USB Adapter. Win7 doesn't like these devices, and when combined with Vista-era drivers, will spit out BSOD's faster than you can shake a stick at it. Here's my rant about these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Unfortunately (for me, fortunately for you! :0) there's only 4 memory dumps. This makes it hard to discern a pattern of hardware failure. But with the 4 memory dumps, you have 3 different BSOD error codes and 2 different causes blamed.

This could be the beginning of a pattern that says "hardware issue". Hardware issues include:
- borked (broken) hardware
- overclocking
- compatibility issues (such as Service Pack 1 being missing)
- low-level driver problems (such as the wireless USB drivers)
- malware

The driver for your StorageCraft Volume Snap-Shot or Symantec/Norton Backup Exec/Norton Ghost (symsnap.sys) dates from 2009 and should be updated or uninstalled from your system.

The drivers for your Netgear wireless USB device (scmndisp.sys Wed Jan 17 02:48:03 2007 (45ADD4B3) and jswpslwfx.sys Thu May 15 06:28:50 2008 (482C1062)) date from 2007/8 and must be updated. If no more current driver is available, uninstall the software and physically remove the device from your system. If you need internet connectivity, either try a built-in wireless PCI/PCIe card - or a very, very long wire!

If all these steps don't stop the BSOD's, then please run the free hardware diagnostics listed here: http://www.carrona.org/hwdiag.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys      Tue May 19 13:56:59 2009 (4A12F2EB)
symsnap.sys      Tue Sep 15 17:02:11 2009 (4AB000D3)
scmndisp.sys     Wed Jan 17 02:48:03 2007 (45ADD4B3)
athurx.sys       Mon Oct 11 05:10:57 2010 (4CB2D4A1)
aswFsBlk.SYS     Tue Mar 06 19:01:31 2012 (4F56A55B)
aswTdi.SYS       Tue Mar 06 19:01:56 2012 (4F56A574)
aswrdr2.sys      Tue Mar 06 19:02:19 2012 (4F56A58B)
jswpslwfx.sys    Thu May 15 06:28:50 2008 (482C1062)
aswSnx.SYS       Tue Mar 06 19:04:05 2012 (4F56A5F5)
aswSP.SYS        Tue Mar 06 19:04:03 2012 (4F56A5F3)
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
GenericMount.sys Mon Jan 18 08:50:40 2010 (4B546730)
asmtxhci.sys     Wed Nov 02 23:00:22 2011 (4EB203C6)
GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
Rt64win7.sys     Tue Sep 27 10:50:33 2011 (4E81E2B9)
igdkmd64.sys     Sun Jun 26 21:55:42 2011 (4E07E31E)
aswMonFlt.sys    Tue Mar 06 19:01:51 2012 (4F56A56F)
RTKVHD64.sys     Tue Dec 13 05:24:54 2011 (4EE727F6)
asmthub3.sys     Wed Nov 02 23:00:32 2011 (4EB203D0)
SASKUTIL64.SYS   Tue Jul 12 17:00:01 2011 (4E1CB5D1)
usbaapl64.sys    Tue Jan 10 19:56:04 2012 (4F0CDE24)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-35427-01.dmp]
Built by: 7600.21179.amd64fre.win7_ldr.120330-1504
Debug session time: Sat May 26 04:02:52.377 2012 (UTC - 4:00)
System Uptime: 0 days 1:21:46.313
Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+93 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlDeleteNoSplay+93
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02c964bb fffff880`094d0d50 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-15553-01.dmp]
Built by: 7600.21179.amd64fre.win7_ldr.120330-1504
Debug session time: Fri May 25 20:00:10.817 2012 (UTC - 4:00)
System Uptime: 0 days 0:30:49.754
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteScb+108
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0319a548 fffff880`03199db0 fffff800`02c98452
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052512-19578-01.dmp]
Built by: 7600.21179.amd64fre.win7_ldr.120330-1504
Debug session time: Fri May 25 06:47:37.405 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:09.342
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  InstStub.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAllocatePoolWithTag+53d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02df290d fffff880`0944a950 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052512-18049-01.dmp]
Built by: 7600.21179.amd64fre.win7_ldr.120330-1504
Debug session time: Fri May 25 06:41:00.832 2012 (UTC - 4:00)
System Uptime: 0 days 10:45:19.159
Probably caused by : Ntfs.sys ( Ntfs!NtfsMcbCleanupLruQueue+7e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_Ntfs!NtfsMcbCleanupLruQueue+7e
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0123b5ce fffff880`0317e8a8 fffff880`0317e110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``