BSOD mostly NTFS.SYS errors (new system)

[bwpotter]

Hi:

I'm new to the forum and have been experiencing several BSOD's on a recent home-built AMD platform. After the initial build, I received a few MEMTEST86 errors and RMA'd the G.Skill memory. The replacements passed over 24 hours of MEMTEST testing. And then the whole system was burned in for 48 hours with PRIME95 with no errors. All drivers are up-to-date. System is not overclocked and the memory is running at 1333 MHz.

Now, during the last couple of weeks, I received eight BSOD's, (dumpfiles attached):

Six ea. NTFS_FILE_SYSTEM (24)
One ea. KMODE_EXCEPTION_NOT_HANDLED (1e)
One ea. PAGE_FAULT_IN_NONPAGED_AREA (50)

System specs:
GIGABYTE GA-770TA-UD3 AM3 Motherboard
AMD Athlon II X4 630 Propus 2.8GHz Processor
G.SKILL 2 x 2GB DDR3 1600 F3-12800CL9D-4GBNQ RAM
SAPPHIRE 100283-2L Radeon HD 5770 Video card
Western Digital Caviar Black WD6401AALS 640GB Harddrive
COOLER MASTER Elite 460 RS-460-PSAR-J3 460W Power Supply

The only other peculiarity is the monitor occasional goes black while typing; however, if I move the mouse, it comes right back!

I would be very grateful for any and all help!

Regards... Brian

 

[Johnathan Lyman]

Having SIX of the NTFS_FILE_SYSTEM BSODs lead me to believe you have some problems with your file system's integrity.

I would run FIXBOOT, FIXMBR, and CHKDSK /R on your hard drive and see if that helps.

With the monitor going black, it sounds like it's jumping into power save mode per the request of Windows. Check your power settings on that one.

Let me know how it goes!

Thanks!

 

[Jonathan_King]

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

BSOD Index

I suggest uninstalling Avira completely, and installing Microsoft Security Essentials instead.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

Run one of these diagnostics: HD Diagnostic

And please upload any new dmps that might come.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp5_minidump.zip\Seven Forums\Minidumps\040410-15022-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`0309ee50
Debug session time: Sun Apr  4 10:19:29.120 2010 (GMT-4)
System Uptime: 0 days 0:04:36.900
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008c526e8, fffff88008c51f40, fffff880012d2d06}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+26d3 )

Followup: MachineOwner
---------

 

[bwpotter]

Thanks guys... I'm getting the machine back this evening and will run your suggestions and report back my findings.

Regards... Brian

 

[bwpotter]

I wasn't able to run anything until this weekend but decided to first re-check hardware after getting the computer back.

MemTest86 was first and after about 15 min, it spat out multiple errors (>100) and actually froze up! I removed the two modules and proceeded to test each one individually. They both ran 5 passes perfectly! I then installed both sticks together and again, after 7 passes, everything was fine, no errors! I wonder if re-seating them helped?

Prime95 ran successfully for over 24 hours. Still no errors.

CHKDSK /R ran OK. A long test, HD diagnostics passed with no errors.

Hardware-wise, there area couple of items that are different than before. Currently, I'm testing with a standard analog mouse and keyboard input, no USB. My sister was using a very old keyboard, over 10 years old and I had read somewhere that old keyboards could potentially cause issues with new generation hardware. Her mouse is a USB wireless. And there is no printer or external USB harddrive connected. I could get the old hardware back from her if you think it's warranted?

I can still uninstall Avira but thought I'd report back first with these findings and see if you guys have alternate suggestions for the next course of actions?

It really seems to be running perfectly but I don't want to give it back until I know it's OK.

I've attached an amended dumpfile record including new dmps that occurred before I got everything back.

Thanks again for your help... Brian

 

[Jonathan_King]

RAM sounds like a likely cause. If you continue to have BSODs, follow the other suggestions.

 

[bwpotter]

Thanks Jonathan for the quick reply... do you think it was the re-seating that helped?

If so, should I test the RAM further and if everything passes, with no further BSOD's, pronounce it OK?

 

[Jonathan_King]

I don't think testing the RAM more is necessary. I'd say call it, unless you get another BSOD.