BSOD 0x3B and 0x1E

Had 2 BSOD's while using driver viewer although it may not be related. Eventually had to use Start up repair again then boot into Safe Mode with Networking. Uploading the requested driver View File and a current Grab all. Below is from WHoCrashed. Note: Weird occurrences on reboots such as MBAM disabled and instead of a home network internet conn I had a public one. Restarted MBAM manually and disabled the public network then restarted a Home network. I don't know if these are related to the issues but figured I would mention them. I am guessing this was because I used the restore option in Start up repair.

Driver Verifier is still running.

On Wed 1/1/2014 6:56:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010114-21762-01.dmp
This was probably caused by the following module: mpfilter.sys (0xFFFFF88001019309)
Bugcheck code: 0x50 (0xFFFFF8A0281952D8, 0x0, 0xFFFFF88001019309, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\mpfilter.sys
product: Microsoft Malware Protection
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 1/1/2014 6:47:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010114-24538-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800124821C)
Bugcheck code: 0x50 (0xFFFFF10007874F48, 0x0, 0xFFFFF8800124821C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I think that the MpFilter.sys issue may be a glitch. But still we need to be totally cautious, as it is a continuing issue. Scan the system for possible virus infection with the following programs; for one more time please.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Also uninstall MSE. Download and install a fresh copy.

Though it is still the storage filter driver, from the part of MSE.

And the next one .... you notice the WhoCrashed output ... another ntfs error.

And here my question is ..... your motherboard is GA-P55M-UD2. Am I right???

If so, it is Intel® P55 Chipset. How this driver may come here????????

Code:

==================================================
Driver Name       : amdxata.sys
Address           : 00000000`010F5000
End Address       : 00000000`01100000
Size              : 0x0000b000
Load Count        : 1
Index             : 23
File Type         : System Driver
Description       : Storage Filter Driver
Version           : 1.1.2.5
Company           : Advanced Micro Devices
Product Name      : Storage Filter Driver
Modified Date     : 3/11/2011 12:41:12 AM
Created Date      : 12/28/2013 8:34:07 AM
Filename          : C:\Windows\system32\drivers\amdxata.sys
File Attributes   : A
Service Name      : amdxata
Service Display Name: 
Digital Signature : 
==================================================

And, I am seeing that it is running, too! It activates with every windows boot.

Code:

amdxata    amdxata    c:\windows\system32\drivers\amdxata.sys    Kernel Driver    Yes    Boot    Running    OK    Normal    No    Yes

Sekita, I hope you understand it. There is no scope of having a Storage filter driver by AMD in a system which is having an Intel Chipset motherboard.

And it is the most bona fide reason of this continuous storage related issues.

I think you need start afresh. Do a Clean Reinstall - Factory OEM Windows 7 .... the procedure works similarly for retail too.

Still, as it a situation I havent seen earlier, I think I need to consult with the members who are more experienced than me .... and who always guide me.

This might help letting us know about you system.

This would help us to understand the System Specs.

By andrew129260:

Speccy - Advanced System Information Tool

Hi there Layback, I had already published a Speccy a few posts back but here is another.
*Removed*

I made the mistake of uninstalling MSE thinking it would reinstall, it won't. It won't install under limited loadout or Safe MOde. THIS makes me nervous.

On Thu 1/2/2014 12:56:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010114-20638-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008C2EA18, 0xFFFFF88008C2E270, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

SekitaLuna if you use the tutorial correctly you won't have to send us off the Forum to see the results.
For security reasons I don't care to go off site to see the results of Speccy.

Attachment 299910

It wasn't meant to be snippy.
This Forum has the best Tutorials on the Web they will serve you well.
I looked at your log and I didn't see anything AMD but it could be hiding.

SEKITA-PC.txt (176.3 KB, 0 views)

I did find this that might be helpful for you and Arc.

amdxata.sys Windows process - What is it?

You are right about that! Some of the best written tutorials I have seen, and over the past month I have seen too many to count (sadly lol). You have EVERY right to be snippy, even if you weren't, as I know a lot of effort was put into those tutorials, and the least I could do is take the time to read it through and not just TL;DR *picture grazes*.

I was able to complete a system restore, and I am glad I am faithful about manually setting these whenever I uninstall something, and restored the computer to before I uninstalled MSE. It is currently running! This takes a big load off my shoulders.

AMD? Is amdxata.sys something I need to update, remove, or simply do more research on?
I have driverscanner installed already, and it does say I have 30 outdated drivers.



A friend has suggested Driver Navigator.

SekitaLuna said:

AMD? Is amdxata.sys something I need to update, remove, or simply so more research on?
I have driverscanner installed already, and it does say I have 30 outdated drivers.

amdxata.sys is the storage filter driver for AMD chipset motherboards. There is no logical reason for you to have that driver in your system, as yours is Intel chipset. Also when I noticed the place where this driver should be listed, it is not there under your storage controllers. I checked those controllers over and over, as it is an ongoing storage related issue.

Like all other storage controllers, it is also available as an windows update, but not for a system that is not AMD chipset.

It is not sure how you obtained it. But it should be removed. Only a deletion would not be enough, because some drivers are auto-configured at restart if the source is left; and for it we dont know th source. You need to format teh partition and perform a clean reinstall as I suggested earlier.

Thank you Layback Bear for all your valuable inputs