BSOD - Running out of ideas

Sirik said:

Hi Dave,

I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.

There is your clue. It runs fine with only one card, either card. With two, it crashes. I conclude that there is something wrong with, conflicting in your dual setup. Setting up dual cards is outside of my realm of experience.

I will leave this to the graphics card gurus and wish you the best in figuring out the problem. :)

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

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800124ce95 to fffff80002e7f740

STACK_TEXT:  
fffff880`096196b8 fffff880`0124ce95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`096196c0 fffff880`0124cae8 : 00000001`00000000 00000000`00000000 00000000`00000000 000001fb`00001000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`096197c0 fffff880`0109623f : fffffa80`094428d0 fffffa80`09442530 fffffa80`05acec30 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89
fffff880`09619870 fffff880`010946df : fffffa80`064de950 fffffa80`09442530 fffffa80`064de900 fffffa80`09442530 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`09619900 fffff800`02e711f2 : fffffa80`09442550 fffffa80`0645f9a0 00000000`00000043 fffff683`ff7b48c0 : fltmgr!FltpDispatch+0xcf
fffff880`09619960 fffff800`02e714f5 : fffffa80`09d97601 fffffa80`09d97601 fffff880`09619a60 00000000`00000000 : nt!IoPageRead+0x252
fffff880`096199f0 fffff800`02e9a8bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`09ba92a8 : nt!MiIssueHardFault+0x255
fffff880`09619ac0 fffff800`02e7d82e : 00000000`00000008 00000000`00000051 ffffffff`ffb3b401 00000000`000001f4 : nt!MmAccessFault+0x14bb
fffff880`09619c20 000007fe`f6918d60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`1bb3f938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f6918d60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+155
fffff880`0124ce95 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsPagingFileIo+155

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

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

The dump does not tell us very much. I have to admit to admit that I am baffled by this. You have run chkdsk and well as Memtest. And you have run Driver Verifier. At the moment, the only thing I can suggest is to make sure your RAM is seated properly and that your connections to your hard drive are good.

I believe it is a hardware issue; I just can't put my finger on it.

You need to test with another graphics card to be able to rule this out or confirm it's the cause.

If you need to find a shop that can do this for you, it will confirm the cause instead of guessing, then you'll know if it's the graphics cards and not RAM related or motherboard faults.

Glad to hear that it's running stable.

Let us know if there are any other issues.

That is good news! Thank you for posting back with the solution. Happy computing. Don't be a starnger to the forum.