Windows 7: BSOD on newly built PC (0x24, 0x7E, 0x1A)

Sylo · 10 Mar 2011

I have been facing this problem ever since I first assembled my pc. I am not an expert but I don't think I have messed my hardware. The PC is 10 days old.
I am not sure but maybe there is some sort of incompatibility with my hardware and Windows 7.
I am currently running Windows 7 Ultimate x64. My pc spec are as follow:
MoBo: GA-X58A-UD5 (Link)
CPU: Intel i7 970 (Link)
RAM: G.Skill 8GB (2x4GB) (Link)
GPU: Nvidia GTX 580 (Link)
PSU: Corsair TX950 (Link)
SSD: Crucial C300 128GB (Link)
HDD: WD Caviar Black 1TB (Link)
Optical Drive: LG Blu-ray (Link)

As for my Windows 7 installations, I did about 3 clean installations on my SSD. Last one was yesterday.
I really need to know if I am having incompatibilities with my hardware or am I facing driver errors.
I attached the log of my BSODs, the last three happened while I was trying to install Windows 7 SP1.
I will try a CHKDSK

Maguscreed · 10 Mar 2011

Well they are file system errors.
Have you looked for new firmware for you ssd?
Crucial.com Product Downloads - Firmware Updates
it's apparently at version 6 now.

Code:

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:  des2svr.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880070bb930 -- (.trap 0xfffff880070bb930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800c673250 rbx=0000000000000000 rcx=0000000002831000
rdx=0000000002830000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000338edf2 rsp=fffff880070bbac0 rbp=fffff880070bbca0
 r8=fffffa800d0a9b10  r9=0000000000000155 r10=fffffa800673cc90
r11=000000000012019f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!NtReadFile+0x142:
fffff800`0338edf2 0fb602          movzx   eax,byte ptr [rdx] ds:0001:00000000`02830000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff88001210e95 to fffff80003073740

STACK_TEXT:  
fffff880`070bb3c8 fffff880`01210e95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`070bb3d0 fffff880`01210ae8 : 00000001`00000000 00000000`00000000 00000000`00000000 00000410`00000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`070bb4d0 fffff880`0101c23f : fffffa80`0abfc570 fffffa80`0abfc260 fffffa80`0c7ef010 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89
fffff880`070bb580 fffff880`0101a6df : fffffa80`06fb1990 fffffa80`0abfc260 fffffa80`06fb1900 fffffa80`0abfc260 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`070bb610 fffff800`030651f2 : fffffa80`0abfc280 fffffa80`0729a1f0 00000000`00000043 fffff800`031ede80 : fltmgr!FltpDispatch+0xcf
fffff880`070bb670 fffff800`030654f5 : fffffa80`048e6200 fffffa80`048e6200 fffff880`070bb770 fffff800`030abee2 : nt!IoPageRead+0x252
fffff880`070bb700 fffff800`0308e8bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`098b3740 : nt!MiIssueHardFault+0x255
fffff880`070bb7d0 fffff800`0307182e : 00000000`00000000 fffffa80`0c673250 00000000`02830f00 00000000`00000004 : nt!MmAccessFault+0x14bb
fffff880`070bb930 fffff800`0338edf2 : fffffa80`0c673200 fffff800`00000001 fffffa80`0673cc90 fffffa80`0c673201 : nt!KiPageFault+0x16e
fffff880`070bbac0 fffff800`03072993 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x142
fffff880`070bbbb0 00000000`74f02dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`002ef0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f02dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+155
fffff880`01210e95 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
---------

Sylo · 10 Mar 2011

I heard one of the firmware updates messes you SSD, so I didnt bother trying to update.
I will try this firmware update, hopefully everything will settle.

Thanks for the advice

Maguscreed · 10 Mar 2011

Was this one case of someone complaining or a lot of people?
if a firmware update fails it can cause problems. Failure like that is not very common though.

Sylo · 10 Mar 2011

Well here: RealSSD C300 Series Firmware Version 006 Release - Crucial Community
Some users seem to be having some problems with flashing.

Sylo · 10 Mar 2011

Ok. Just checked my SSD and it seems to have FW 0006 pre-installed. so no need to update.
Can my RAM cause this problem? because it seems to be made for P55 chipsets and I am using X58.

Edit:
My system crashed, MEMORY_MANAGEMENT 0x1A 10 minutes after reinstalling Norton Internet Security 2011. I guess its causing some problems here.

Maguscreed · 10 Mar 2011

Norton does not seem to like certain systems.
You could also have a memory issue though it would explain everything we're seeing here.

RAM - Test with Memtest86+

You'll want to let it run for 5-7 passes, unless it just starts spamming errors right off the bat.
This is usually something I recommend doing overnight.

Sylo · 10 Mar 2011

Alright then, I guess I'll start memtest.

Thanks

Sylo · 10 Mar 2011

OK. Did memtest and surprisingly, I got around 5000 errors in my first pass.
I guess I will test them 1 by 1.

My bad, 15K Errors and going up.

Edit:
Tested one stick alone and it spammed error like hell.
Currently testing the other stick, so far so good.

Sylo · 11 Mar 2011

I've been running my pc for hours now using 1 healthy RAM stick without any BSODs.
Guess the problem was with the defective RAM. Going to RMA it.

Can't thank you enough Maguscreed, you saved me a lot of trouble.

Windows 7: BSOD on newly built PC (0x24, 0x7E, 0x1A)

BSOD on newly built PC (0x24, 0x7E, 0x1A) problems?