Windows 7: Windows 7 AMustor.sys BSOD issues?

st0kEd · 21 May 2014

I have an ASUS N53SV-XV1 that has been getting BSOD during normal use. It goes BSOD at random whether in use or sitting idle. I ran driver verifier and AMustor.sys was showing up as a problem. AMustor.sys has to do with the SD card reader. Updated the driver for the card reader and still getting BSODs, as many as 10+ per day. Attached are my dump files.

Was running Corsair 8GB (2x 4GB) 1333mhz PC3-10666 204-pin DDR3 SODIMM, but switched to OEM stick.
NOTE: In 2012 I ran Memtest 10+ passes on each stick and there were no errors found.
I reinstalled the OEM RAM, which came up clean after a Memtest run, but that was a while back.

Below are my specs:

Make and Model
ASUS N53SV-XV1

Display
15.6-inch LED-backlit Full HD display (1920 x 1080)

Graphics Card
NVIDIA® GeForce® GT 540M with 1GB DDR3 VRAM and NVIDIA Optimus Technology

Processor
Type : 2nd gen Intel® Core™ i7-2630QM
Speed : 2.0 GHz (with Turbo Boost 2.0 up to 2.9 GHz)
Cache : 3 MB L3

Chipset
Intel® HM65

Memory
OEM 4Gb
Corsair 8GB (2x 4GB) 1333mhz PC3-10666 204-pin DDR3 SODIMM
NOTE: In 2012 I ran Memtest 10+ passes on each stick and there were no errors found.

Storage
Crucial M4 SSD 256GB, 2.5" SATA

Optical Drive
Super Multi DVD drive

Communication
LAN : 10/100/1000 Mbps Ethernet
WLAN : Integrated 802.11 b/g/n (@2.4GHz)

Bluetooth
Built-in Bluetooth™ 2.1

Audio
Bang & Olufsen ICEpower®
Built-in Speakers And Microphone
SonicFocus
(Realtek High Definition Audio)

Interface
1 x USB 3.0 ports
3 x USB 2.0 ports
1 x RJ45 LAN Jack for LAN insert
1 x HDMI
1 x Microphone-in jack
1 x Line-in Jack
1 x VGA port/Mini D-sub 15-pin for external monitor

Power
Output : 19 V DC, 6.3 A, 120 W (Quad Core) / 4.74 A , 90 W (Dual Core)
Input : 100 -240 V AC, 50/60 Hz universal

Thedoctor44 · 21 May 2014

Your Intel display driver is causing issues.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x67001

Code:

fffff880`04806000 fffff880`053b7180   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Tue May 24 02:17:00 2011 (4DDB070C)
    CheckSum:         00BB2D63
    ImageSize:        00BB1180
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's out of date, you can update it here:

https://downloadcenter.intel.com/Default.aspx

Can you uninstall your Alcor Micro SD Card Controller as it's causing issues.

Code:

Unable to load image \SystemRoot\system32\drivers\AmUStor.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AmUStor.SYS
*** ERROR: Module load completed but symbols could not be loaded for AmUStor.SYS

Although if you really need it you can update it (not recommended) here:

ALCOR MICRO - Storage Product > SD Card Controller

Code:

fffff880`011ef000 fffff880`011fe000   AmUStor  T (no symbols)           
    Loaded symbol image file: AmUStor.SYS
    Image path: \SystemRoot\system32\drivers\AmUStor.SYS
    Image name: AmUStor.SYS
    Timestamp:        Fri Aug 21 07:48:18 2009 (4A8E4332)
    CheckSum:         0000F912
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

st0kEd · 21 May 2014

Thanks, I'll try updating the Intel driver and disabling the card reader. It is unfortunate that I have to uninstall the card reader, I use it often, but the computer is worthless with the constant BSODs.

Thedoctor44 · 21 May 2014

I mean you can try updating the card reader and if it continues to BSOD then remove it.
At the end of the day it's up to you :)

st0kEd · 21 May 2014

I updated the Intel graphics driver without disabling the card reader and got a BSOD. I now have both disabled and haven't had a BSOD since disabling the card reader. I'm attaching the new dump file to confirm it was the card reader that caused the BSOD.

Thedoctor44 · 22 May 2014

Only pool corruption, can't identify the driver responsible.

Can you also enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no points, make a System Restore Point Manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

st0kEd · 22 May 2014

Thanks for the advice.

I'll start running Verifier again this evening when I'm off work and let you know what happens.