BSOD after copying files from one hard drive to another

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Professional 64 bit
       #1

    BSOD after copying files from one hard drive to another


    Hello. I hope you can help as this problem is very frustrating. Just built a new PC:
    - Gigabyte Z97X Gaming 7 mobo
    - 8 gig Corsair Vengance 1866 mhz
    - EVGA GTX 770 video
    - Intel 4770K CPU
    - two 1 Tb WD black hard drives as RAID 1
    - one ADATA 256 Gb SSD as OS drive
    - one 1 Tb Toshiba drive
    - Windows 7 64 bit Professional
    - Rev F3 bios

    System can run fine for days but when I copy large number of files from one drive to another (i.e., 70,000 files, 80 Gb), shortly afterwards (10 - 30 mins) I get a bugcheck BSOD.

    I ran MEMTEST86 for hours with no errors. I can run PRIME95 with max heat with no errors. ANd like I said it seems to be fine until I do a large file copy. It doesn't seem to matter what drive I copy to/from. Booting WIndows I don't see any CHKDISK activity. Ideas?
      My Computer


  2. Posts : 4,161
    Windows 7 Pro-x64
       #2

    It's best to run Memtest for at least seven passes and overnight.
    The error is 0x124 which is a hardware error but the ErrRec didn't provide much since it was a total memory collapse. What it does show is a fault occurs right after a memory move. What's in memory at the time is a process called ubssrv-oc-only. This program is identified as a trojan virus by many antivirus scanners.

    I'll see if one of our AV guys can check this out. In the meantime, run the System File Checker using Option Two in the tutorial. Report back any console messages from SFC.

    Code:
     
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8008788028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  ubssrv_oc_only
    CURRENT_IRQL:  f
    STACK_TEXT:  
    fffff880`009d7b58 fffff800`03217a3b : 00000000`00000124 00000000`00000000 fffffa80`08788028 00000000`bf800000 : nt!KeBugCheckEx
    fffff880`009d7b60 fffff800`033da463 : 00000000`00000001 fffffa80`084feea0 00000000`00000000 fffffa80`084feef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`009d7ba0 fffff800`03217700 : 00000000`00000728 fffffa80`084feea0 fffff880`009d7f30 fffff880`009d7f00 : nt!WheaReportHwError+0x263
    fffff880`009d7c00 fffff800`03217052 : fffffa80`084feea0 fffff880`009d7f30 fffffa80`084feea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`009d7d50 fffff800`03216f0d : 00000000`00000008 00000000`00000001 fffff880`009d7fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`009d7d90 fffff800`0320ae88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`009d7dc0 fffff800`032c24ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`009d7df0 fffff800`032c2313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`009d7f30 fffff800`032ba7b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`07715638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memmove+0x208
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: hardware
    IMAGE_NAME:  hardware
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 4,566
    Windows 10 Pro
       #3

    Download DDS:

    DDS.com

    Save the file to your pc. Then open the dds icon to run the tool.
    When done, DDS will open two (2) logs:
    DDS.txt
    Attach.txt

    Save both reports to your desktop.
    Include the contents of both logs in your next post by using the paperclip




    ___________________________________________________________________________________________

    1.) Download herdprotect: (choose the portable version)

    Download herdProtect - Free Anti-Malware Platform

    2.) Run the scan.

    3.) When the scan finishes, save the results per the screenshot below. Then upload the log here.

    DO NOT REMOVE ANYTHING YET. I will advise if anything needs removed when I receive the log.

    Attached Images
      My Computer


  4. Posts : 7
    Windows 7 Professional 64 bit
    Thread Starter
       #4

    Hello and thank you for your quick reply. Attached are the 2 log files your requested from DDS and one from herdprotect. I ran SFC and it found no problems.

    I did uninstall the Gigabyte app center because I think that is where that usbssrv came from. As I said last time I ran MEMTEST86 overnight, 10 passes, no problems. I also ran it at other times with no problems.

    Joe
      My Computer


  5. Posts : 21,007
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
       #5

    No probs under control it would seem.
    Last edited by ICIT2LOL; 26 Jun 2014 at 23:34.
      My Computer


  6. Posts : 4,161
    Windows 7 Pro-x64
       #6

    I'm not sure what I'm looking at in those uploads so we'll see what Andrew has to say about that. If there's any cleaning to do, I'd rather wait until after that's done before continuing with more dumps.

    Did you get any more dumps (BSODs) after removing the Gigabyte app?
      My Computer


  7. Posts : 7
    Windows 7 Professional 64 bit
    Thread Starter
       #7

    I have tried moving large amounts of files between drives after removing Gigabytes apps and so far I have not had any BSOD. Of course only time will tell but right now it is looking good...

    Joe
      My Computer


  8. Posts : 4,161
    Windows 7 Pro-x64
       #8

    Keep us posted.
      My Computer


  9. Posts : 4,566
    Windows 10 Pro
       #9

    I keep seeing things popping up in your temp folders. Lets clear them:


    Make sure your data is backed up either on an external hard drive or somewhere else before proceeding:

    1.) Please download and save the file TFC by Old Timer. Again, save the file to your downloads folder or your desktop. Do not run it.

    Downloading TFC


    2.) Close your programs before running this tool. TFC will close ALL open programs.

    3.) Browse to where you saved tfc. Right click on tfc.exe and choose Run As Administrator.

    4.) Click the Start button to begin the cleaning process and let it run uninterrupted to completion. When it finishes it will say total files cleaned, and the start button will be grayed out. Click exit.
    Important! If TFC prompts you to reboot, please do so immediately. If not prompted, manually reboot the machine anyway to ensure a complete clean.
    Last edited by andrew129260; 27 Jun 2014 at 20:23.
      My Computer


  10. Posts : 4,566
    Windows 10 Pro
       #10

    CARWIZ, you may be interested in the following:

    Code:
    ==== Event Viewer Messages From Past Week ========
    
    6/25/2014 8:50:04 PM, Error: Service Control Manager [7026]  - 
    The following boot-start or system-start driver(s) failed to load:  
    UsbCharger
    Code:
    6/25/2014 7:55:51 PM, Error: Microsoft-Windows-WHEA-Logger [18]  - 
    A fatal hardware error has occurred. Reported by component: 
    Processor Core Error Source:
     Machine Check Exception Error Type: Internal Unclassified Error 
    Processor ID: 4 
    The details view of this entry contains further information.
    Code:
    6/25/2014 7:55:50 PM, Error: Microsoft-Windows-WER-
    SystemErrorReporting [1001]
      - The computer has rebooted from a bugcheck.  
    The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8008788028, 
    0x00000000bf800000, 0x0000000000200401). 
    A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062514-6692-01.
    Code:
    6/25/2014 7:32:06 PM, Error: Microsoft-Windows-WHEA-Logger [18]  - 
    A fatal hardware error has occurred. Reported by component: Processor Core
     Error Source: Machine Check Exception Error Type: Internal Unclassified Error 
    Processor ID: 2 The details view of this entry contains further information.
    Code:
    6/25/2014 7:32:06 PM, Error: Microsoft-Windows-WER-SystemErrorReporting
     [1001]  - The computer has rebooted from a bugcheck.  
    The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800884b028,
     0x00000000bf800000, 0x0000000000200401). A dump was saved in: 
    C:\Windows\MEMORY.DMP. Report Id: 062514-7300-01.
    Code:
    6/22/2014 8:44:41 PM, Error: Service Control Manager [7000]  - 
    The cpuz137 service failed to start due to the following error:  
    The system cannot find the path specified.
    Code:
    6/20/2014 9:14:23 PM, Error: Microsoft-Windows-Directory-Services-SAM [12291] 
     - SAM failed to start the TCP/IP or SPX/IPX listening thread
    Code:
    6/20/2014 7:49:01 PM, Error: Microsoft-Windows-WHEA-Logger [18]  - 
    A fatal hardware error has occurred. Reported by component: Processor Core 
    Error Source: Machine Check Exception Error Type: Internal Unclassified Error 
    Processor ID: 6 The details view of this entry contains further information.
    Code:
    6/20/2014 7:48:52 PM, Error: Microsoft-Windows-WER-SystemErrorReporting
     [1001]  - The computer has rebooted from a bugcheck.  The bugcheck was: 
    0x00000124 (0x0000000000000000, 0xfffffa8008537028, 0x00000000bf800000, 
    0x0000000000200401). A dump was saved in: C:\Windows\MEMORY.DMP. 
    Report Id: 062014-6130-01.
    Code:
    6/20/2014 7:21:20 AM, Error: Microsoft-Windows-WER-
    SystemErrorReporting [1001]  - The computer has rebooted from a bugcheck. 
     The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8008548028, 
    0x00000000bf800000, 0x0000000000200401). A dump was saved in: 
    C:\Windows\MEMORY.DMP. Report Id: 062014-6302-01.
    Code:
    6/20/2014 6:20:30 AM, Error: Microsoft-Windows-WER-SystemErrorReporting
     [1001]  - The computer has rebooted from a bugcheck.  The bugcheck was: 
    0x00000124 (0x0000000000000000, 0xfffffa8011a3d028, 0x00000000bf800000, 
    0x0000000000200401). A dump was saved in: C:\Windows\MEMORY.DMP. 
    Report Id: 062014-6349-01.
    Code:
    6/20/2014 12:06:15 PM, Error: Disk [11]  - 
    The driver detected a controller error on \Device\Harddisk3\DR3.
    Code:
    6/19/2014 6:52:34 PM, Error: Microsoft-Windows-WER-SystemErrorReporting
     [1001]  - The computer has rebooted from a bugcheck. 
     The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8008829028,
     0x00000000bf800000, 0x0000000000200401). 
    A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061914-7082-01.
    Code:
    6/19/2014 4:53:42 PM, Error: Microsoft-Windows-WHEA-Logger [18]
      - A fatal hardware error has occurred. Reported by component: Processor 
    Core Error Source: Machine Check Exception Error Type: Internal Unclassified
     Error Processor ID: 0 The details view of this entry contains further information.
    Code:
    6/19/2014 4:53:34 PM, Error: Microsoft-Windows-WER-SystemErrorReporting 
    [1001]  - The computer has rebooted from a bugcheck.  The bugcheck was: 
    0x00000124 (0x0000000000000000, 0xfffffa8008c10028, 0x00000000bf800000, 
    0x0000000000200401). A dump was saved in: C:\Windows\MEMORY.DMP. 
    Report Id: 061914-7004-01.
    Code:
    6/19/2014 4:29:31 PM, Error: Microsoft-Windows-WER-SystemErrorReporting
     [1001]  - The computer has rebooted from a bugcheck.  
    The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8011d62028,
     0x00000000bf800000, 0x0000000000200401). A dump was saved in: 
    C:\Windows\MEMORY.DMP. Report Id: 061914-7316-01.
    .
      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 01:55.
Find Us