BSOD + Repair Install Failure 0x80070241


  1. Posts : 4
    Windows 7 64 Bit Home Premium
       #1

    BSOD + Repair Install Failure 0x80070241


    I've had many BSOD crashes, which I thought were caused by bad memory, but I thoroughly checked the memory and could not isolate any problems. Then I found this forum, and tried Driver Verifier, which also didn't show any specific problems (at least not that I could tell). Then I tried Blue Screen View, as shown in the report below, and saw that the problems are related to core windows system files. Then I tried SFC /SCANNOW, and it showed some missing/corrupt system files, as shown in the report below.

    After all this, I tried to do a repair install to replace the corrupt/missing windows system files. The repair install stopped and said "Windows cannot copy files required for installation. The files may be corrupt or missing. Make sure all files required for installation are available, and restart the installation. Error Code: 0x80070241".

    I checked the forum, and it seems that this error was common when people were burning downloaded Beta ISO images of Win 7. But I'm installing from an original store-bought Windows 7 disc, so I can't understand what the problem would be. I tried to download a new copy from Microsoft, but it seems that you need a $500 Technet subscription to do so.

    I'd like to avoid a clean install if possible, but it looks like that is where I am heading. Any help would be very much appreciated. Thank you!
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    We need the actual .dmp file for analysis ... [1 - Novice] How to ask for help with a BSOD problem
      My Computer


  3. Posts : 4
    Windows 7 64 Bit Home Premium
    Thread Starter
       #3

    Thanks Tews - sorry, I missed that one. Here it is.
      My Computer


  4. Posts : 11,840
    64-bit Windows 8.1 Pro
       #4

    51 dump files ... This is going to take a while and I may need to call in some reinforcements... The first few that Ive looked at are blaming corrupted memory ... Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes ...

    Code:
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 15cd5, 2, 15cd0}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 0000000000015cd5, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 0000000000015cd0, 0
    
    Debugging Details:
    ------------------
    
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 4
    Windows 7 64 Bit Home Premium
    Thread Starter
       #5

    Ok, thanks. Will do. I'll let MemTest run overnight now and see what it says. I tried it before, with various combinations of the 4 DIMMs installed, but I couldn't get MemTest to consistently show an error. I'm sure you'll be able to interpret the results better than I could. The memory is the same manufacturer and type, but 2 DIMMS are 1.6v and 2 are 1.65v. I still got the BSODs with only the same voltage DIMMs installed, so that didn't seem to be the problem.

    Looking at the DMP files, it kind of seemed like the early errors were memory-based, and the later ones were more system file based... I tried taking out the memory and using only 1 DIMM, but it still kept crashing.

    Thanks again - really appreciate your help. :)
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #6

    Tom has asked for help running the dmps...that will take a while. Running them now.
      My Computer


  7. Posts : 13,354
    Windows 7 Professional x64
       #7

    I suspect Semantic (Norton). Several of the dmps point to that as the cause. Pleaes uninstall it, then run this removal tool: ftp://ftp.symantec.com/public/englis...moval_Tool.exe

    Then download and install Microsoft Security Essentials.

    Code:
    
    BugCheck 4E, {99, 1e08e6, 2, 1311e7}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 1A, {41790, fffffa8003964260, ffff, 0}
    Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck C4, {f6, 3fc, fffffa800513f060, fffff88003f62c12}
    Probably caused by : elrawdsk.sys ( elrawdsk+5c12 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck BE, {fffff80002caf1f2, 2caf121, fffff880062c2600, b}
    Probably caused by : SRTSP64.SYS ( SRTSP64+11f8 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck C4, {f6, 3fc, fffffa80054d2060, fffff8800436bc12}
    Probably caused by : elrawdsk.sys ( elrawdsk+5c12 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 4E, {99, 15cd5, 2, 15cd0}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 4E, {99, 77a00, 2, 15c1b}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 50, {fffff89fcce5d6f4, 0, fffff80003118231, 5}
    Probably caused by : ntkrnlmp.exe ( nt!PfSnPrefetchSections+351 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 1A, {3452, 3380000, fffff7000108cfe8, d00000014d9e4c66}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a23 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 19, {20, fffff8a00e488930, fffff8a00e4889e0, 50b0403}
    Probably caused by : BHDrvx64.sys ( BHDrvx64+6c1eb )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 24, {1904fb, fffff8800b93eca8, fffff8800b93e510, fffff880012e4c27}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 1A, {5003, fffff70001080000, 774, 77600020ee8}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 24, {1904fb, fffff88003338818, fffff88003338080, fffff880012dd42e}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownStructures+22e )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 1A, {41790, fffffa8003964530, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a08 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 50, {fffffa800c5ff4d8, 0, fffff8800418301d, 0}
    Probably caused by : IDSvia64.sys ( IDSvia64+3801d )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
      My Computer


  8. Posts : 4
    Windows 7 64 Bit Home Premium
    Thread Starter
       #8

    I uninstalled Norton and installed MS Security Essentials, and left the computer running all day today when I was at work, and it didn't crash at all. Usually it would crash at least once during the day, even with noone using it.

    I also ran MemTest overnight last night, and it showed there is definitely a problem - 80,000+ errors in 4 passes. I was able to isolate it to one of the 4 DIMMs. I took that DIMM out and MemTest finds no errors with the other 3, so I'm running with 3x2GB for now. Not sure why the results were less conclusive the last time I tried MemTest, but it's definitely clear now.

    I reran SFC /SCANNOW, and it still found some corrupt files - new report attached below. Do you think I need to do anything about this?

    I'll see how things go tonight...

    Tom & Jonathan - thank you very much for your help - this is a great service you provide to those of us who can't figure this stuff out by ourselves.
      My Computer


  9. Posts : 13,354
    Windows 7 Professional x64
       #9

    I'd suspect maybe you had a bad OS install, due to the unfixable files. However, the RAM errors suggest either bad RAM or a bad motherboard slot.

    Test each one of your sticks individually in slot #1, and if you get a good one, test it in all the slots.
      My Computer


 

  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 02:47.
Find Us