Windows 7: BSOD - ntfs.sys 0x50

tmad · 06 Apr 2013

I understand this could be a memory/hard drive problem, just want to be totally sure and get a second opinion before I start buying stuff or could be something very simple

Playing Call of Duty 4, game crashed a first time, restarted game and started playing again, 2 mins into game PC BSOD with:

PAGE_FAULT_IN_NONPAGED_AREA
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+75c40

Para1:fffffc00`03014c08
Para2:00000000`00000000
Para3:fffff880`012b5b1f
Para4:00000000`00000007

ntfs.sys 0x00000050

I have attached my dump files.

koolkat77 · 06 Apr 2013

Code:

fffff880`0884b158  fffff880`03cf469eUnable to load image \SystemRoot\system32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
 cmdguard+0x1969e

http://carrona.org/drivers/driver.php?id=cmdguard.sys
Comodo seems to be contributing to your crashes. As a test please uninstall it using its removal tool from here:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials is recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free
Good and Free system security combination

Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Is the firmware for your SSD up-to-date?

Check for one and see if the stability returns.

Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file.

To do this, follow these steps:

Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
At the command prompt, type the following command, and then press ENTER: sfc /scannow
The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. SFC /SCANNOW Command - System File Checker

Check a drive for errors:
1. Check a drive for errors
2. Check your hard disk for errors in Windows 7
3. Disk Check

Let us know the results.

tmad · 07 Apr 2013

Just a heads up, this is a fresh install of Win7 Home Premium 64bit

Unistalled Comodo

MSE - Scan found nothing
Malware Bytes: Found cookies, removed
SuperAntiSpyware: Found cookies, removed

SSD Firmware: Up-to-date
System File Checker: Nothing, cleared fine.

Check Drive: Both SSD came back fine, no errors
Hard Disk Errors: Nothing
Disk Check: No Errors

tmad · 07 Apr 2013

Just received 2 bsods within the last two hours

Posted dump files

the ndis.sys is for my nic so I can fix that hopefully.

Received both while playing cod4

koolkat77 · 07 Apr 2013

The following is for information purposes only. Any drivers in red should be updated/replaced/removed.

AiChargerPlus.sys Mon Nov 8 12:48:26 2010 (4CD79D3A)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys

The following information contains the relevant information from the blue screen analysis:

Code:

Debug session time: Sun Apr  7 13:33:12.126 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\040713-10389-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 1:02:58.297
Probably caused by : ntkrnlmp.exe ( nt!AlpcpMessageDestroyProcedure+75 )
BugCheck 3B, {80000003, fffff800031dae85, fffff88009c6de30, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 0000000080000003, Exception code that caused the bugcheck
Arg2: fffff800031dae85, Address of the instruction which caused the bugcheck
Arg3: fffff88009c6de30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpMessageDestroyProcedure+75
BiosVersion = 1604
BiosReleaseDate = 10/16/2012
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
RAM - Test with Memtest86+

Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

tmad · 08 Apr 2013

Alright, confirmed it was my RAM, thanks for the help!

koolkat77 · 08 Apr 2013

You're welcome.

Be sure to post should you have further issues.