BSOD 90% on first start up unless I "cycle" ram locations

Page 1 of 2 12 LastLast

  1. Posts : 8
    Win 8 64, Win 7 64, Ubuntu various
       #1

    BSOD 90% on first start up unless I "cycle" ram locations


    Hello,
    I am receiving a BSOD on boot up. The weird part is, if I physically move location of each ram into a different slot I no longer receive the BSOD. I have run MEMTest and it did not indicate any errors. Attached is the MEMORY.dmp. I am away from that computer at the moment but can also download and run the SF "grab all" tool if needed.

    Running !Analyze -v shows:

    Code:
    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: 000000b50019060b
    Arg2: fffff880009a7d18
    Arg3: fffff880009a7550
    Arg4: fffff8008c337f5f
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff880009a7d18 -- (.exr 0xfffff880009a7d18)
    ExceptionAddress: fffff8008c337f5f (nt!FsRtlReleaseEofLock+0x00000000000000e3)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff880009a7550 -- (.cxr 0xfffff880009a7550)
    rax=fffff8a000f5d1a8 rbx=fffff8a000f5d1a0 rcx=fbfff8a000f5d1a8
    rdx=0000000000002ff4 rsi=0000000000000000 rdi=fffffa8009126d88
    rip=fffff8008c337f5f rsp=fffff880009a7f50 rbp=0000000000000000
     r8=fbfff8a000f5d1a8  r9=fffffa80090fdc01 r10=0000000000000000
    r11=fffff880009a7f98 r12=fffff880009a8220 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
    nt!FsRtlReleaseEofLock+0xe3:
    fffff800`8c337f5f 488b09          mov     rcx,qword ptr [rcx] ds:002b:fbfff8a0`00f5d1a8=????????????????
    Resetting default scope
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS:  ffffffffffffffff 
    
    FOLLOWUP_IP: 
    CI!CipMinCrypK_OpenFile+79
    fffff880`00d90a28 8bd8            mov     ebx,eax
    
    FAULTING_IP: 
    nt!FsRtlReleaseEofLock+e3
    fffff800`8c337f5f 488b09          mov     rcx,qword ptr [rcx]
    
    BUGCHECK_STR:  0x24
    
    LAST_CONTROL_TRANSFER:  from fffff880014d1e82 to fffff8008c337f5f
    
    STACK_TEXT:  
    fffff880`009a7f50 fffff880`014d1e82 : fffffa80`06a5db00 fffff880`009a81b0 00000000`00000000 fffffa80`08cf06e0 : nt!FsRtlReleaseEofLock+0xe3
    fffff880`009a7fa0 fffff880`014d21c6 : 00000000`00000000 fffff880`009a81b0 00000000`00000000 fffffa80`08cf06e0 : Ntfs!NtfsCleanupIrpContext+0x342
    fffff880`009a7ff0 fffff880`01582580 : fffffa80`08cf06e0 fffff880`009a81b0 00000000`00000000 fffffa80`08cf06e0 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd6
    fffff880`009a8030 fffff880`0158753a : fffff880`009a81b0 fffffa80`08cf06e0 00000000`00000000 00000000`00000038 : Ntfs!NtfsCommonQueryInformation+0xe07
    fffff880`009a8110 fffff880`015826a6 : fffff880`009a81b0 fffffa80`08cf06e0 fffffa80`08cf06e0 00000000`00000001 : Ntfs!NtfsFsdDispatchSwitch+0xda
    fffff880`009a8190 fffff880`0121c4ee : 00000000`00000005 fffff880`0121ba6c fffff880`009a8480 fffffa80`081f3505 : Ntfs!NtfsFsdDispatchWait+0x47
    fffff880`009a83c0 fffff880`0121a0b6 : fffffa80`081f3540 fffff880`009a8880 fffffa80`08cf06e0 00000000`000007ff : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25e
    fffff880`009a8460 fffff800`8c6e6d98 : 00000000`00000001 fffff880`009a8730 fffff880`009a8880 fffff800`8c57e180 : fltmgr!FltpDispatch+0xb6
    fffff880`009a84c0 fffff800`8c2df453 : fffffa80`09144180 fffff880`015976e2 00000000`00000000 fffffa80`07638bc0 : nt!NtQueryInformationFile+0x783
    fffff880`009a8640 fffff800`8c2e4630 : fffff880`00d90a28 00000000`00000000 ffffffff`000c000a fffff880`00d97af0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`009a8848 fffff880`00d90a28 : 00000000`00000000 ffffffff`000c000a fffff880`00d97af0 00000000`00000000 : nt!KiServiceLinkage
    fffff880`009a8850 fffff880`00d9728b : fffff8a0`00000002 00000026`00000003 ffffde02`3fe26101 fffff880`009a8c10 : CI!CipMinCrypK_OpenFile+0x79
    fffff880`009a8900 fffff880`00d97509 : ffffffff`800001a8 00000000`00000002 fffff8a0`01a1a540 00000000`00000000 : CI!I_MapAndSizeDataFile+0x73
    fffff880`009a89c0 fffff880`00d97d8f : fffff8a0`01a1a540 00000000`00000000 fffff880`009a8a90 fffff880`000022bd : CI!I_MapCatalog+0x161
    fffff880`009a8a70 fffff880`00d97c78 : 00000000`00000008 00000000`00000000 fffff8a0`01ffc500 00000000`00000000 : CI!I_RemapCatalog+0x37
    fffff880`009a8b50 fffff880`00d97a7f : 00000000`00000000 fffff880`009a8c29 fffff880`009a8d30 fffff8a0`01ffc580 : CI!I_ReloadCatalog+0x17c
    fffff880`009a8b90 fffff880`00d96abe : 00000000`c0000428 00000000`00000000 00000000`00000000 ffffffff`800001ac : CI!I_ReloadCatalogs+0x16f
    fffff880`009a8c90 fffff880`00d96968 : fffff880`009a8fd0 00000000`00000001 00000000`0000800c fffff880`00000000 : CI!I_FindFileOrHeaderHashInCatalogs+0x14e
    fffff880`009a8d10 fffff880`00d94549 : 00000000`00000000 00000000`00000000 00000000`c0000428 fffff880`00d963e1 : CI!MinCrypK_FindPageHashesInCatalog+0x64
    fffff880`009a8d90 fffff880`00d94f42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!CipGetPageHashesForFile+0xfe
    fffff880`009a8ea0 fffff880`00d92fc7 : 00000000`0000045b fffff880`009a9131 00000000`00000002 00000000`000007ff : CI!CipValidatePageHash+0x35b
    fffff880`009a9060 fffff800`8c6585d9 : fffffa80`09040b50 fffff880`07690000 00000000`00000000 00000000`00000002 : CI!CiValidateImageHeader+0x49f
    fffff880`009a9180 fffff800`8c71aae3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000004 : nt!MiValidateSectionCreate+0x2d1
    fffff880`009a9300 fffff800`8c700e2f : fffffa80`09040b50 fffff880`01000000 00000000`00000212 00000000`00000210 : nt!MiCreateNewSection+0x213
    fffff880`009a9400 fffff800`8c716970 : fffff880`009a99b8 00000000`00100020 fffff880`009a9928 fffff800`8c6ecec4 : nt!MiCreateSection+0x8eb
    fffff880`009a9620 fffff800`8c2df453 : fffffa80`06a5db00 fffff880`009a98d8 fffff880`009a96c8 00000000`00000001 : nt!NtCreateSection+0x1af
    fffff880`009a96b0 fffff800`8c2e4630 : fffff800`8c77e221 00000000`c0000034 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`009a98b8 fffff800`8c77e221 : 00000000`c0000034 00000000`00000000 00000000`00000000 fffff800`8c97f6a1 : nt!KiServiceLinkage
    fffff880`009a98c0 fffff800`8c77e0fe : 00010000`002a0028 00000000`00000000 00000000`00780076 ffffffff`800000f0 : nt!PspLocateSystemDll+0xd1
    fffff880`009a99a0 fffff800`8c9816cd : 00000000`00000000 fffff880`009a9a99 fffff800`8c560580 fffff800`8ae76430 : nt!PsLocateSystemDlls+0x5a
    fffff880`009a99e0 fffff800`8c989913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!IoInitSystem+0x8dd
    fffff880`009a9b00 fffff800`8c78f259 : ff0f0000`00000000 fffffa80`06a5db00 fffff800`8ae76430 fffffa80`06a2c308 : nt!Phase1InitializationDiscard+0xde3
    fffff880`009a9d20 fffff800`8c2b2fd9 : 00000000`00000000 00000000`00000000 e0ffffff`ffff0f00 00000000`00000080 : nt!Phase1Initialization+0x9
    fffff880`009a9d50 fffff800`8c3677e6 : fffff800`8c57e180 fffffa80`06a5db00 fffff800`8c5d8880 fffffa80`06a2c040 : nt!PspSystemThreadStartup+0x59
    fffff880`009a9da0 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  b
    
    SYMBOL_NAME:  CI!CipMinCrypK_OpenFile+79
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: CI
    
    IMAGE_NAME:  CI.dll
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5153b962
    
    STACK_COMMAND:  .cxr 0xfffff880009a7550 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  79
    
    FAILURE_BUCKET_ID:  0x24_CI!CipMinCrypK_OpenFile
    
    BUCKET_ID:  0x24_CI!CipMinCrypK_OpenFile
    
    Followup: MachineOwner
    ---------
    Thank you


    Update: I'm having trouble uploading the zipped .dmp file. Is there file size limit?
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Welcome to SF :) .
    Yes there is a size limit on attachments, Usually the file generated by the SFDT is sufficient enough
    use the Grab All option.

      My Computer


  3. Posts : 8
    Win 8 64, Win 7 64, Ubuntu various
    Thread Starter
       #3

    Thanks

    Apparently I can't see the listing of the file sizes in the attachment window

    Will update tonight.
      My Computer


  4. Posts : 3,056
    Windows 10
       #4

    For future reference, you scroll down the attachment window for the file key.
    Attachment 283717
      My Computer


  5. Posts : 22
    Windows 7 x64
       #5

    Well it is a bit flip, which is a typical hardware error. The referenced address (in RCX) starts with fbfff instead of fffff.
      My Computer


  6. Posts : 3,056
    Windows 10
       #6

    Right but in-order to establish that it is the situation we need to see consistent
    errors of that particular register.
      My Computer


  7. Posts : 8
    Win 8 64, Win 7 64, Ubuntu various
    Thread Starter
       #7

    Sorry YoYo my sarcasm was lost in text. I saw it,but choose to ignore the file size info .


    Here is the updated "grab all"
      My Computer


  8. Posts : 3,056
    Windows 10
       #8

    Your bugchecks are indicative of hardware issues.

    Flipped Bits:
    Code:
    Usual Culprits: CPU | PSU | Motherboard

    Code:
    CONTEXT:  fffff880009a7550
    rax=fffff8a000f5d1a8 rbx=fffff8a000f5d1a0 rcx=fbfff8a000f5d1a8
    rdx=0000000000002ff4 rsi=0000000000000000 rdi=fffffa8009126d88
    rip=fffff8008c337f5f rsp=fffff880009a7f50 rbp=0000000000000000
     r8=fbfff8a000f5d1a8  r9=fffffa80090fdc01 r10=0000000000000000
    r11=fffff880009a7f98 r12=fffff880009a8220 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    Code:
    0: kd> .formats fbfff8a000f5d1a8
    Evaluate expression:
      Hex:     fbfff8a0`00f5d1a8
      Decimal: -288238485033856600
      Octal:   1757777612000075350650
      Binary:  11111011 11111111 11111000 10100000 00000000 11110101 11010001 10101000
      Chars:   ........
      Time:    ***** Invalid FILETIME
      Float:   low 2.25749e-038 high -2.65816e+036
      Double:  -1.94731e+289
    0: kd> .formats fffff8a000f5d1a8
    Evaluate expression:
      Hex:     fffff8a0`00f5d1a8
      Decimal: -8108882144856
      Octal:   1777777612000075350650
      Binary:  11111111 11111111 11111000 10100000 00000000 11110101 11010001 10101000
      Chars:   ........
      Time:    ***** Invalid FILETIME
      Float:   low 2.25749e-038 high -1.#QNAN
      Double:  -1.#QNAN
    Code:
    FAULTING_IP: 
    nt!FsRtlReleaseEofLock+e3
    fffff800`8c337f5f 488b09          mov     rcx,qword ptr [rcx]
    The routine faulted on FsRtl (File System Runtime Library) I believe this is the reason
    this bugcheck code is 0x24 or NTFS_FILE_SYSTEM.
    Other bit-flipped bugchecks:
    Code:
    CONTEXT:  fffff8801da2feb0 -- (.cxr 0xfffff8801da2feb0)
    rax=000d0000000379ec rbx=fbfff8a004300520 rcx=fffffa80079b2680
    rdx=fffff8801da30910 rsi=fffff8801da30910 rdi=fffffa80079b2680
    rip=fffff8800152ac73 rsp=fffff8801da308b8 rbp=0000000000000745
     r8=fbfff8a004300540  r9=0000ffffffffffff r10=fffff880018dd000
    r11=0000000000000689 r12=fffff8a009bca010 r13=0000000000000700
    r14=fffff8a009bca000 r15=0000000000000000
    Code:
    CONTEXT:  fffff880009a7770 -- (.cxr 0xfffff880009a7770)
    rax=0000000000000702 rbx=fffffa8009127180 rcx=0000000000000001
    rdx=000000000000a3e2 rsi=0000000000000000 rdi=fbfff8a000760010
    rip=fffff880014d9a61 rsp=fffff880009a8170 rbp=fffff880009a8251
     r8=000000000000a3e2  r9=0000ffffffffffff r10=0000000000000000
    r11=0000000000000002 r12=fffff8a0012eb870 r13=fffff8a0004f3990
    r14=fffff880009a8450 r15=0000000000000001
    Code:
    CONTEXT:  fffff88000bfbf90 -- (.cxr 0xfffff88000bfbf90)
    rax=fffff8a00079d1a8 rbx=fffff8a00079d1a0 rcx=fbfff8a00079d1a8
    rdx=00000000000028ad rsi=0000000000000000 rdi=fffffa8009002ab8
    rip=fffff802c66bbf5f rsp=fffff88000bfc990 rbp=0000000000000000
     r8=fbfff8a00079d1a8  r9=fffffa80091fca01 r10=0000000000000000
    r11=fffff88000bfc9d8 r12=fffff88000bfcc60 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    The consistency of the r8 and rcx registers lead me to believe that there is either
    a power issue with the PSU or the CPU is faulty.

       Note
    If any component in the system is overclocked STOP.
    reset all clocks back to their respectable stock speeds.


    Remove AMD Over-Drive
    Code:
    AODDriver4.2.0    \??\c:\program files\ati technologies\ati.ace\fuel\amd64\aoddriver2.sys
    Test the CPU:




    Go into the BIOS (consult your manual), note the Voltages and post them back here.
    If you are comfortable poking around a PC and you have a multimeter handy follow this tutorial
    to check your Voltages while stress testing the CPU.





    To eliminate the possibility other hardware errors:

       Warning
    This methode should in no way be performed on an SSD!

    Testing the HDD:

    1. Perform a Disk Check | Disk Check
    2. Then Post the results following | THIS METHOD
    3. Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).



    Test the RAM:


    koolkat77 said:
    Test and Diagnose RAM Issues with Memtest86+:

       Tip

    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.





    Post back with the results!
      My Computer


  9. Posts : 8
    Win 8 64, Win 7 64, Ubuntu various
    Thread Starter
       #9

    Bios Readings:
    Vcore 1.360V
    DDR3 1.5V 1.488V
    +3.3V 3.264V
    +12V 11.921V

    Sys Temp 30C
    Cpu Temp 29C
      My Computer


  10. Posts : 8
    Win 8 64, Win 7 64, Ubuntu various
    Thread Starter
       #10

    MB Power Connector
    Actual Expected Color Color Expected Actual
    3.337 3.41 Orange Black 0 0
    12.06 12.35 Yellow Red 5.05 5.14
    12.06 12.35 Yellow Red 5.05 5.14
    5.00 5.07 Purple Red 5.05 5.14
    4.27 5.09 Grey White 0 0
    0 0 Black Black 0 0
    5.13 5.05 Red Black 0 0
    0 0 Black Black 0 0
    5.13 5.05 Red Green 0.06 0.04
    0 0 Black Black 0 0
    3.337 3.41 Orange Blue 11.34 11.83
    3.337 3.41 Orange Orange 3.41 3.331


    Power Supply is a Corsair CX430
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:02.
Find Us