unexpected shutdown in my windows 7!

i got 4 BSODs this morning!

the first one:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff683ff7e9748, fae00002fa001025, fffff8a00591d722}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f72 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff683ff7e9748
Arg3: fae00002fa001025
Arg4: fffff8a00591d722
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_403
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff8000308a228 to fffff800030d4f00
STACK_TEXT:  
fffff880`0b241678 fffff800`0308a228 : 00000000`0000001a 00000000`00000403 fffff683`ff7e9748 fae00002`fa001025 : nt!KeBugCheckEx
fffff880`0b241680 fffff800`03105b51 : 000007fe`fd3e5000 fffff683`ff7e9f28 fffffa80`09ce97b0 000007fe`fd3debe6 : nt! ?? ::FNODOBFM::`string'+0x31f72
fffff880`0b241830 fffff800`031085d9 : 00000000`00000000 000007fe`fd3e6fff fffffa80`00000000 fffff800`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0b2419f0 fffff800`033eae50 : fffffa80`0c771820 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0b241b10 fffff800`033eb25b : fffff880`00000000 000007fe`fd210000 fffffa80`00000001 fffffa80`0b2586d0 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0b241bd0 fffff800`030d4153 : fffffa80`0c943760 fffff880`0b241ca0 fffffa80`09ce97b0 fffffa80`0bcc8960 : nt!NtUnmapViewOfSection+0x5f
fffff880`0b241c20 00000000`76e0015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0022ba98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e0015a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31f72
fffff800`0308a228 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+31f72
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f72
BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f72
Followup: MachineOwner

the second one:

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
---------
0: 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:  WerFault.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff8800120fe95 to fffff8000307af00
STACK_TEXT:  
fffff880`0c1e96b8 fffff880`0120fe95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c1e96c0 fffff880`0120fae8 : 00000001`00000000 00000000`00000000 00000000`00000000 000005d0`00000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`0c1e97c0 fffff880`010e323f : fffffa80`09bb59d0 fffffa80`09bb5630 fffffa80`09bcdd30 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89
fffff880`0c1e9870 fffff880`010e16df : fffffa80`0a7508b0 fffffa80`09bb5630 fffffa80`0a750800 fffffa80`09bb5630 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0c1e9900 fffff800`0306ca52 : fffffa80`09bb5650 fffffa80`0bba8b20 00000000`00000043 fffff800`031f3e80 : fltmgr!FltpDispatch+0xcf
fffff880`0c1e9960 fffff800`0306cd55 : 00000000`00000001 00000000`00000001 fffff880`0c1e9a60 fffff880`0c1e9ae0 : nt!IoPageRead+0x252
fffff880`0c1e99f0 fffff800`0309609b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff680`00005040 : nt!MiIssueHardFault+0x255
fffff880`0c1e9ac0 fffff800`03078fee : 00000000`00000001 00000000`00000000 00000000`00000401 fffffa80`09bf5140 : nt!MmAccessFault+0x14bb
fffff880`0c1e9c20 00000000`77c41afe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`001dc578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c41afe
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+155
fffff880`0120fe95 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 third one:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41201, fffff6800004f420, 90d0000173001867, fffffa800b404150}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6800004f420
Arg3: 90d0000173001867
Arg4: fffffa800b404150
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41201
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff800030ed1ee to fffff8000308cf00
STACK_TEXT:  
fffff880`0c16c9b8 fffff800`030ed1ee : 00000000`0000001a 00000000`00041201 fffff680`0004f420 90d00001`73001867 : nt!KeBugCheckEx
fffff880`0c16c9c0 fffff800`0305b40e : fffff880`00000000 00000000`00000000 00000000`00000000 90d00001`73001867 : nt! ?? ::FNODOBFM::`string'+0x13bf2
fffff880`0c16ca00 fffff800`0305b0aa : fffffa80`0b404150 fffffa80`0c6a4060 fffffa80`0c6a4060 00000000`09e84000 : nt!MiQueryAddressState+0x2ae
fffff880`0c16ca50 fffff800`03371798 : fffff880`00000004 00000000`09e85000 fffffa80`0b404150 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`0c16cac0 fffff800`0308c153 : 00000000`00000168 fffffa80`0b3d2760 fffff880`0c16cbc8 00000000`001aaa08 : nt!NtQueryVirtualMemory+0x386
fffff880`0c16cbb0 00000000`77b100ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001aa9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b100ea
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13bf2
fffff800`030ed1ee cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13bf2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2
BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2
Followup: MachineOwner
---------

and the fourth one :

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41201, fffff680003f7f18, 89d00002f9001025, fffffa8009d6b3b0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff680003f7f18
Arg3: 89d00002f9001025
Arg4: fffffa8009d6b3b0
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41201
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff8000311f1ee to fffff800030bef00
STACK_TEXT:  
fffff880`095c09b8 fffff800`0311f1ee : 00000000`0000001a 00000000`00041201 fffff680`003f7f18 89d00002`f9001025 : nt!KeBugCheckEx
fffff880`095c09c0 fffff800`0308d40e : 00000000`40c90200 fffffa80`0c85d7a0 00000000`00000000 89d00002`f9001025 : nt! ?? ::FNODOBFM::`string'+0x13bf2
fffff880`095c0a00 fffff800`0308d0aa : fffffa80`09d6b3b0 fffffa80`0aa83760 fffffa80`0aa83760 00000000`7efe3000 : nt!MiQueryAddressState+0x2ae
fffff880`095c0a50 fffff800`033a3798 : fffff880`00000002 00000000`7efe4000 fffffa80`09d6b3b0 fffff880`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`095c0ac0 fffff800`030be153 : 00000000`00000b7c fffffa80`0c85d7a0 fffff880`095c0bf8 00000000`0aa5e468 : nt!NtQueryVirtualMemory+0x386
fffff880`095c0bb0 00000000`776d00ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0aa5e448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776d00ea
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13bf2
fffff800`0311f1ee cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13bf2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2
BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bf2
Followup: MachineOwner
---------

for more details, please refer to the attached.

(sorry guys if i'm not following the rules here. I'm just trying to get rid of all these problems once and for all.)

I think i found the problem.

my RAMs are of OCZ3G1333LV2G type and when I looked at the list of RAMs supported by my motherboard, the type that I have is not listed!


As I said, mine are of OCZ3G1333LV2G type, please click this link: http://www.gigabyte.com.tw/FileList/...a-x58a-ud7.pdf


However, I just want to be 100% sure about what i found. I don't want the vendor whom i bought the RAMs from to have any execuse not to give me back my money or provide me with something compatible with the motherboard.

please, confirm that guys: are those all BSODs I got are possibly because my RAM is not compatible with the motherboard?
(you see, I remember i told him about this, i clearly remember i told him does the frequency of the RAMs go smoothly with the motherboard? And he Said yes, it does?!?!)

it's been 5 hours and the machine is stable so far!

found it!


the problem has been discovered after running memtest. 3 of my modules failed the test. i replaced them and it's been 3 days and everything is running smoothly.


thank you guys for you help.:)