Driver BSODs on Windows 8 and 7

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 24
    Microsoft Windows 7 Professional 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #11

    I went through the list of resolutions, and these two look plausible:
    -Operating system intermittently crashes with a "0x0000007E" Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2
    -Stop error message in Windows 7 or Windows Server 2008 R2: "Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)" or "Stop error code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)"

    How can I know if I should install the hotfixes associated with those articles? Also, is there any probable cause that I should update the BIOS? The current version I have installed is from 10/13/2009.
      My Computer


  2. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #12

    3. Running a regular hard drive, so no trimming.
    So the CORSAIR CMFSSD is is wrong in your system specs?


    Your most recent .dmp points to memory corruption:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000014, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 830ba2cb, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 8318884c
    Unable to read MiSystemVaType memory at 83167e20
     00000014 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiFindNodeOrParent+5
    830ba2cb f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  9c82569c -- (.trap 0xffffffff9c82569c)
    ErrCode = 00000000
    eax=00000000 ebx=86dbff38 ecx=00000000 edx=00000000 esi=86dbff38 edi=807c3120
    eip=830ba2cb esp=9c825710 ebp=9c825710 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!MiFindNodeOrParent+0x5:
    830ba2cb f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h ds:0023:00000014=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 830ba2cb to 8305fb7f
    
    STACK_TEXT:  
    9c82569c 830ba2cb badb0d00 00000000 9c8256bc nt!KiTrap0E+0x1b3
    9c825710 830bae5d 9c825724 9c82573c 830d7254 nt!MiFindNodeOrParent+0x5
    9c82571c 830d7254 00000000 86dbff10 86dbff80 nt!MiLocateAddressInTree+0x11
    9c82573c 830a806e 86dbff10 00000000 00000000 nt!MiGetSharedProtos+0x5d
    9c82575c 830c127b 96422788 846601f8 84660200 nt!MiComputeStartingOffset+0x61
    9c8257a0 83050bdc 85b3db60 85b3d000 9c825844 nt!MiIdentifyPfn+0x29e
    9c8257c8 8329f295 00b3d060 b5c8104c 9c825858 nt!MmQueryPfnList+0xa6
    9c825810 83254b6c 91007001 b5c810cc 00000000 nt!PfpPfnPrioRequest+0xde
    9c825890 83240837 00000000 91007001 9c825cd0 nt!PfQuerySuperfetchInformation+0xea
    9c825d00 8324ffbb 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x2477
    9c825d1c 8305c8c6 0000004f 0133ed90 00000014 nt!NtQuerySystemInformation+0x76
    9c825d1c 778170f4 0000004f 0133ed90 00000014 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0133cc50 00000000 00000000 00000000 00000000 0x778170f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiFindNodeOrParent+5
    830ba2cb f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiFindNodeOrParent+5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  521e9cb6
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5
    
    BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5
    
    Followup: MachineOwner
    ---------
    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL (Windows Debuggers)


    Okay on the CHKDSK. Thank you for the disk management and SFC snips they're helpful.

    Usually to open system files you need to copy them to your desktop, then you should be able to open them. I applaud your initiative in uploading the CBS. logs.

    'bout that SFC scan, I believe we found your problem. Hold off on running those hotfixes. I know enough about CBS logs to be dangerous, but I'm going to see if I can get NoelDP to stop by and take a look at them, he may be able to write a batch file that would fix your SFC scan problem and having those CBS logs ready is very helpful.

    Until Noel does stop by Have you tried to run the SFC scan at least three times or more with restarts in between?

    See Note after Option Two step #4:

       Note

    • If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
    • If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.
    • If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
    • If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix.




    • Only do the first bullet.
    • Noel may instruct you to run the System Update Readiness Tool (SURT) and then upload the newer CBS logs.
    • Ignore the third bullet.
    • The fourth bullet is where he might be able to write up the batch file to make replacement easier.
    • Let us know if running SFC 3x's helps.


    The old BIOS? Well, 4years is starting to get a little long in the tooth, but hold off on that also. Our goal is to see if we can get your present setup running once we get the system files straightened out and when your OS is steady you could consider updating the BIOS.
      My Computer


  3. Posts : 53,363
    Windows 10 Home x64
       #13

    You can also upload just the sfcdetails.txt as per OPTION THREE of the tutorial

    How to See and Read Only the "SFC" Scan Results from the CBS.LOG
    SFC /SCANNOW Command - System File Checker

    A Guy
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #14

    The SFC results are unusual...
    Here's the brief summary
    Code:
     Line 3370: 2014-01-17 21:22:34, Info                  CSI    0000029c [SR] Repairing 4 components
     Line 3371: 2014-01-17 21:22:34, Info                  CSI    0000029d [SR] Beginning Verify and Repair transaction
     Line 3374: 2014-01-17 21:22:34, Info                  CSI    0000029f [SR] Cannot repair member file [l:24{12}]"keyboard.drv" of Microsoft-Windows-NTVDM-System32, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3377: 2014-01-17 21:22:34, Info                  CSI    000002a1 [SR] Cannot repair member file [l:20{10}]"mmtask.tsk" of Microsoft-Windows-NTVDM-System32, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3380: 2014-01-17 21:22:34, Info                  CSI    000002a3 [SR] Cannot repair member file [l:24{12}]"keyboard.drv" of Microsoft-Windows-NTVDM-System, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3383: 2014-01-17 21:22:34, Info                  CSI    000002a5 [SR] Cannot repair member file [l:20{10}]"mmtask.tsk" of Microsoft-Windows-NTVDM-System, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3386: 2014-01-17 21:22:35, Info                  CSI    000002a7 [SR] Cannot repair member file [l:18{9}]"l2057.ngr" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3389: 2014-01-17 21:22:35, Info                  CSI    000002a9 [SR] Cannot repair member file [l:18{9}]"l2057.smp" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3392: 2014-01-17 21:22:35, Info                  CSI    000002ab [SR] Cannot repair member file [l:18{9}]"l2057.phn" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3395: 2014-01-17 21:22:35, Info                  CSI    000002ad [SR] Cannot repair member file [l:18{9}]"l2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3398: 2014-01-17 21:22:35, Info                  CSI    000002af [SR] Cannot repair member file [l:18{9}]"l2057.wwd" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3401: 2014-01-17 21:22:35, Info                  CSI    000002b1 [SR] Cannot repair member file [l:22{11}]"AI032057.am" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3404: 2014-01-17 21:22:35, Info                  CSI    000002b3 [SR] Cannot repair member file [l:20{10}]"wp2057.bin" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3407: 2014-01-17 21:22:35, Info                  CSI    000002b5 [SR] Cannot repair member file [l:18{9}]"s2057.ngr" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3410: 2014-01-17 21:22:35, Info                  CSI    000002b7 [SR] Cannot repair member file [l:18{9}]"s2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3413: 2014-01-17 21:22:35, Info                  CSI    000002b9 [SR] Cannot repair member file [l:18{9}]"p2057.ngr" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3416: 2014-01-17 21:22:35, Info                  CSI    000002bb [SR] Cannot repair member file [l:18{9}]"p2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3419: 2014-01-17 21:22:35, Info                  CSI    000002bd [SR] Cannot repair member file [l:22{11}]"AF032057.am" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3422: 2014-01-17 21:22:35, Info                  CSI    000002bf [SR] Cannot repair member file [l:22{11}]"AM032057.am" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3425: 2014-01-17 21:22:35, Info                  CSI    000002c1 [SR] Cannot repair member file [l:22{11}]"c2057dsk.fe" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3428: 2014-01-17 21:22:35, Info                  CSI    000002c3 [SR] Cannot repair member file [l:16{8}]"l2057.cw" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3431: 2014-01-17 21:22:36, Info                  CSI    000002c5 [SR] Cannot repair member file [l:20{10}]"tn2057.bin" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3434: 2014-01-17 21:22:36, Info                  CSI    000002c7 [SR] Cannot repair member file [l:22{11}]"ai031033.am" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3437: 2014-01-17 21:22:36, Info                  CSI    000002c9 [SR] Cannot repair member file [l:22{11}]"lsr1033.lxa" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3440: 2014-01-17 21:22:36, Info                  CSI    000002cb [SR] Cannot repair member file [l:18{9}]"l1033.ngr" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3443: 2014-01-17 21:22:36, Info                  CSI    000002cd [SR] Cannot repair member file [l:18{9}]"l1033.dlm" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3446: 2014-01-17 21:22:36, Info                  CSI    000002cf [SR] Cannot repair member file [l:22{11}]"c1033dsk.fe" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3449: 2014-01-17 21:22:36, Info                  CSI    000002d1 [SR] Cannot repair member file [l:22{11}]"af031033.am" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3452: 2014-01-17 21:22:36, Info                  CSI    000002d3 [SR] Cannot repair member file [l:22{11}]"am031033.am" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3455: 2014-01-17 21:22:37, Info                  CSI    000002d5 [SR] Cannot repair member file [l:16{8}]"l1033.cw" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    I'll post a fix protocol a bit later (maybe tomorrow, now )
      My Computer


  5. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #15

    NoelDP said:
    A Guy said:
    You can also upload just the sfcdetails.txt as per OPTION THREE of the tutorial

    How to See and Read Only the "SFC" Scan Results from the CBS.LOG
    SFC /SCANNOW Command - System File Checker

    A Guy
    The SFC results are unusual...
    Here's the brief summary
    Code:
     Line 3370: 2014-01-17 21:22:34, Info                  CSI    0000029c [SR] Repairing 4 components.........
    .......Line 3455: 2014-01-17 21:22:37, Info                  CSI    000002d5 [SR] Cannot repair member file [l:16{8}]"l1033.cw" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    I'll post a fix protocol a bit later (maybe tomorrow, now )
    Thank you A Guy, I forgot to mention that.

    A big thank you Noel, your efforts are appreciated.

    moromis, Noel should give you the procedure to run the fix, please read the instructions carefully before you try, then let us know the results.



       Warning
    I have noticed other members viewing this thread.


    The fix protocol that Noel will post later only applies to moromis's situation / problem.

    Any attempt to try it on your own system would result in irreparable harm to the extent that you would have to re-install your operating system (OS).
      My Computer


  6. Posts : 24
    Microsoft Windows 7 Professional 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #16

    Oh, I did do step three to see it for myself, although to me it's all gobbledygook. Here's the .txt. file:
    Attachment 302250

    I'll run 3 more sfc /scannow now, with restarts inbetween each, as per request.
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #17

    I've uploaded a file - mmsaa.zip - to my SkyDrive at Noel's SkyDrive

    (note - this may take a while to finish uploading - it's a large file, and I have a slow connection today)

    Please download and save it.
    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)
    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.
    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\mmsaa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\mmsaa
    or
    DIR E:\mmsaa

    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

    XCOPY <drive>:\mmsaa <drive>:\windows\winsxs /y /i /s /v /h

    (e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

    run the command (it should take almost no time)and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply.
    Last edited by NoelDP; 19 Jan 2014 at 03:56. Reason: add size warning
      My Computer


  8. Posts : 24
    Microsoft Windows 7 Professional 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #18

    While I wait for it to finish uploading, here's the results of the original sfc scan, as well as the three subsequent scans.
    Attachment 302275

    Also, here's the last three BSODs, one or two of which I got today.
    Attachment 302276

    None of them came back with positive results.
    I'll follow your directions once the file shows up in your SkyDrive.

    Thanks for all your help so far.
      My Computer


  9. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #19

    Your SFC logs are an expanded version of what Noel posted earlier in his code box.

    Of the two .dmps from yesterday the 18th; The first one wouldn't open for me and the second referred to NETIO.
    If you have any type of card that facilitates or program that measures network speeds you may want to consider removing it after you run Noels fix protocol.

    The one for today the 19th refers to athur.sys and USB ports.

    I wouldn't do anything right now until you finish with Noel's fix protocol and instructions to post a new CBS log. You have to get that straightened out first.
      My Computer


  10. Posts : 24
    Microsoft Windows 7 Professional 32-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #20

    Interestingly enough, I got a BSOD after I booted into the Repair Environment and opened up the command prompt. A minidump wasn't made, so I don't have anything for you, unfortunately. I rebooted and performed all the steps, and then as requested, ran a scannow, and it still was not able to repair all problems.

    I also want to mention I've previously gotten BSODs recently when I was on the Windows CD performing repairs. That just seemed odd to me, and this reminded me of that.

    Here's the log file:
    Attachment 302316
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... 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 09:01.
Find Us