Solved Some problems with random BSODs ntfs.sys

Discussion in 'Win 7/Vista BSOD' started by AguyInNeed, Aug 17, 2012.


Thread Status:
Not open for further replies.
  1. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    So i had yesterday downloaded Starcraft 2 which was a fake version just to try out the campaign, the result was with 2 blue screens, then downloaded starter version, and it went fine however i ran on a overclocked Intel HD 4000 but it still did blue screen after it went on normal (2nd BSOD), so those 2 errors showing ntoskrnl.exe is probably solved but i'm dropping them here, today when i was playing league of Legends the error from ntfs.sys appeared, and i have no idea why :/

    Edit : Another BSOD, now it says Memory_Management and error is 0x0000001a instead, this is weird but i believe it's memory related, please help =/

    Dumps : (Attachments)

    PC specs :

    Asus Z77 V-Pro
    Corsair GS 800W
    3770k
    Intel HD 4000
    16GB LP Ram at 1600Mhz Vengeance
    Samsung SSD 830 128GB
    And a old hard drive Sata 1 160GB at 7200rpm

    Running windows 7 ultimate x64



    Note : This PC is just 1week or so old.

    It has run fine for 3days, and then this appeared, yesterday when i downloaded a safe file, and today but not by any of the files i did download. (I was just playing LoL), then another BSOD did happen with Memory_Management when playing LoL

    I have microsoft security essentials and it didn't detect anything.
    Attached Files

    Attached Files:

  2. samuria Network Specialist

    PCHF Staff
    Message Count:
    16,404
    Likes Received:
    975
    My System
    Loading...
    Welcome to the forum. Have you done a system restore the Fake game may have changed the system files so a restore may fix it or from a cmd prompt type

    sfc /scannow
  3. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    Thanks.
    I did a full scan today on microsoft essentials and nothing was found, the file i downloaded though was highly trusted or seemingly, i did a scan and then before did the hard drive scan that required a reboot, nothing found, i'm running memtest86+ on each RAM module now though, i'm unsure on which place to run it, i saw somewhere to test every RAM stick on the closest blue place to the CPU, is this correct? what if the motherboards RAM place is the problem? Shall i test every RAM module on the closest one to the CPU (Blue one)?

    So far Module 1 has completed 1 pass without errors...
  4. Google Advertisement

  5. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,600
    Likes Received:
    360
    My System
    Loading...
  6. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    Here you go, i also ran Memtest86+ on each stick for atleast 4 passes each with no errors found, it runs on ivy bridge however and 4.2 only supports Sandy bridge apparantly should i be worried? Or could the voltage be too low? my all DIMM slots are occupied, running with these, Running on 1600Mhz XMP setup.
    http://www.corsair.com/memory-by-pr...annel-ddr3-memory-kit-cml16gx3m4a1600c9.html/

    Each RAM Stick boots windows fine, if there's a RAM problem my guess would be voltage, since people say that if all RAM spots are occupied 1.5volts is too low, XMP runs on 1.5 though, i dunno...:(

    Attached Files:

  7. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,600
    Likes Received:
    360
    My System
    Loading...
    Rerun the PCHF tool with option 1.
  8. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...

    Attached Files:

  9. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,600
    Likes Received:
    360
    My System
    Loading...
    You have a few of these
    Code:
    081712-8049-01.log
    Debug session time: Fri Aug 17 20:38:36.953 2012 (UTC + 2:00)
    System Uptime: 0 days 16:28:16.734
    IRQL_NOT_LESS_OR_EQUAL (a)
    Arg1: fffffc000368edbb, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    Arg4: fffff80002cdb959, address which referenced memory
    IMAGE_NAME:  memory_corruption
    PROCESS_NAME:  League of Lege
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkPageFromLockedList+169
    fffff880`08494038 fffff800`02cca769 : 00000000`0000000a fffffc00`0368edbb 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08494040 fffff800`02cc93e0 : 00000000`00000000 fffffa80`180fd500 fffffa80`180fd580 fffffa80`00015570 : nt!KiBugCheckDispatch+0x69
    fffff880`08494180 fffff800`02cdb959 : 4eb00002`3a00d921 00000000`00000005 fffff800`02efdd48 00000000`00000005 : nt!KiPageFault+0x260
    fffff880`08494310 fffff800`02ce08b5 : fffff6fc`c00eb3e8 00000000`00000000 fffffa80`00015570 fffffa80`056895f0 : nt!MiUnlinkPageFromLockedList+0x169
    fffff880`08494390 fffff800`02cb94ce : fffff980`1d67c000 00000000`00002000 fffff880`00000000 fffffa80`11a1bb50 : nt!MmCheckCachedPageStates+0x295
    fffff880`08494540 fffff800`02fb0a00 : 00000000`00000000 00000000`028bceaa fffffa80`0ca6f070 00000000`33b40010 : nt!CcFetchDataForRead+0x10e
    fffff880`084945a0 fffff880`016aaf08 : fffff880`00000000 00000000`00000005 fffffa80`00003156 fffffa80`00001001 : nt!CcCopyRead+0x180
    fffff880`08494660 fffff880`01488098 : fffffa80`0ca6f070 fffffa80`11a1bae8 fffffa80`1655c1f8 fffffa80`0ca6f001 : Ntfs!NtfsCopyReadA+0x1a8
    fffff880`08494840 fffff880`0148b8ba : fffff880`08494910 00000000`33b40003 00000000`33b40000 fffffa80`0ca6f000 : fltmgr!FltpPerformFastIoCall+0x88
    fffff880`084948a0 fffff880`014a9630 : fffffa80`0ca6f070 00000000`00000000 fffff880`08494a00 00000000`00001000 : fltmgr!FltpPassThroughFastIo+0xda
    fffff880`084948e0 fffff800`02fb0539 : fffffa80`0ca6f070 00000000`00000001 fffffa80`0c7b4400 fffffa80`0ca6f070 : fltmgr!FltpFastIoRead+0x1d0
    fffff880`08494980 fffff800`02cca453 : 00000000`73902450 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
    fffff880`08494a70 00000000`73902e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`1eb9f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73902e09
    which usually means you either need to update the BIOS or test memory. Since your BIOS is already up to date, I'd follow one extra precaution and go to bios setup and load safe defaults.

    As for testing memory, I suggest taking out all memory modules and inserting only module 1 into slot 1. Test the PC for a while and see if you restored some stability. Afterwards, take out that one module and insert module 2 into slot 1 and again use the PC for a while. Test all modules like that.
    If you get problems with only one module, that RAM stick is probably damaged.
    If more then one modules give you problems in slot 1, it may be possible the slot on the motherboard is faulty, so try repeating the process in slot 2.
  10. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    BIOS is up to date, i tested memory today with every stick into the first blue one with no errors, the thing is i use memtest86+ 4.2 which is said to support only Sandy Bridge, i run on Ivy :S, regarding RAM my manual says to insert blue ones first then black ones, it goes like this Black/Blue/Black/Blue on DIMMs.

    What exactly should i do now since memtest86+ has given 0 errors with really many passes on single stick mode, it however does freeze sometimes when running all 4 sticks it did that in the first time of running memtest86+, should i simple take out all RAMs, test 1day with Ram 1 on DIMM 1, then next day RAM 2 on DIMM 2 etc, and eventually if a blue screen is found on any DIMM i test all RAMs on that DIMM and if just 1 RAM does BSOD it's the RAMs fault and i better RMA?
  11. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,600
    Likes Received:
    360
    My System
    Loading...
    memtest is inconclusive.
  12. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    Okay, ever since i did take out the RAM and re-insert i haven't had the blue screens, i tested all 4 on memtest as said then re-insert all and no blue screen...yet, if it does i will test every RAM when playing LoL, and 4Gb should be enough. I'll report back if it does BSOD with all the 4 sticks.

    Also, how do you see those errors, what program do you use? I know Bluescreenviewer helps but it doesn't show the info like memory_Corruption etc
  13. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,600
    Likes Received:
    360
    My System
    Loading...
    It also may be probable that some of the modules wasn't sitting right, so when you swapped it in and out you effectively fixed the issue.
  14. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    Alright, it did BSOD now with all Ram sticks, i did run the program u sent, here's the dump, can you confirm the last BSOD i had was a memory error? So now i can run with 1 stick each and test.
    Also, can this be a voltage error? Does Memory_Corruption or errors like that happen because the voltage is too low?
  15. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,600
    Likes Received:
    360
    My System
    Loading...
    You haven't attached anything.
    That RAM is rated at 1.5V and I wouldn't change it for now.
  16. AguyInNeed Bronze Member

    Bronze
    Message Count:
    41
    Likes Received:
    0
    My System
    Loading...
    Sorry, here's the attachment

    Is the latest BSOD a memory error? Sorry, just wanna be sure :S

    Attached Files:

Some problems with random BSODs ntfs.sys

Thread Status:
Not open for further replies.