HUGE 134GB .Sys File on C Drive

Page 1 of 2 12 LastLast

  1. Posts : 13
    Windows Server 2008 r2 32-bit
       #1

    HUGE 134GB .Sys File on C Drive


    I hope I've picked the right forum but apologize in advance if I didn't.
    I'm running Win7 64-bit. My SSD drive (128GB) died and I am waiting for a replacement so I decided to reconstruct the OS drive and transfer the image when I get my SSD back in a week or so. I decided to partition a drive of approx. 128 GB after I finished configuring Win7. However, There is a HUGE .sys file on my C drive. The name looks like some sort of system generated name ({aed8a510-a6d5-11e1-94ce-806e6f6e6963}.sys). It looks like a GUID and it is 134GB. I can't get into the file because it's a sys file and I'm sure if I delete it there will be terrible consequences. It has todays date on it. Does anyone know what this could possibly be? I've used Disk Cleanup and CCleaner and a few other utilities and Googled it like crazy to see if it can be safely deleted but none of these even list it.
      My Computer


  2. Posts : 687
    Microsoft Windows 10 Professional / Windows 7 Professional
       #2

    Cant you right click over it and select properties / details?
      My Computer


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

    Possibly either pagefile.sys, or hyberfil.sys (page file, and hibernation file respectively). You can disable hibernation to see if it disappears.

    Hibernate - Enable or Disable

    Or, download Space Sniffer and see how it identifies the file. A Guy
      My Computer


  4. Posts : 5,941
    Linux CENTOS 7 / various Windows OS'es and servers
       #4

    Hi there

    Unlikely to be a page file (134 GB ????) or even a hiber.sys file. Hibernate files are rarely more than a few GB -- remember all a HIBERSYS file is is just a "Snapshot" of the current state of your system like taking a snapshot of a Virtual machine.

    As it's a GUID it might be some sort of old Windows install data or Windows Updates details .
    It might also contain memory dumps or whatever -- but I'm sure this file can be safely got rid of.

    My gut feel would be to just delete the file.

    I don't see how it would be an integral part of the running windows system. If Windows needed or used 134GB sized files I'm sure people would have had something to say on the issue before !!!.

    Cheers
    jimbo
      My Computer


  5. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #5

    I agree with Jimbo on all points.

    Delete the file.
      My Computer


  6. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #6

    Rename it and see if it has consequences
      My Computer


  7. Posts : 13
    Windows Server 2008 r2 32-bit
    Thread Starter
       #7

    Thanks for all the suggestions. No, it's not a pagefile as I can see that. I disabled and deleted the hibernation file as well. I only install Win7 64 on Friday and as I said it has todays' date on it. Looking at the properties doesn't give any clues either. It's a huge .sys file with only admins allowed to manipulate it. I'm going to do Kaktussoft said and see if I can rename it. If you don't hear back in a while you'l know I crashed my machine again :)
      My Computer


  8. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #8

    Do you see any other stuff on machine with aed8a510-a6d5-11e1-94ce-806e6f6e6963 in name? And check registry as well. Maybe this give you a clue what it is
      My Computer


  9. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #9

    Larry,
    Well, did you crash your machine again?
    karl
      My Computer


  10. Posts : 13
    Windows Server 2008 r2 32-bit
    Thread Starter
       #10

    It's ALIVE!!


    Sorry for not posting what happened. How else do we learn from other's mistakes?

    Like I said, it wasn't a pagefile or a hibernation file. When I tried to rename or delete it W7 reported it was in use. I dropped to safe mode copied it to a backup and rebooted. No complaints. It's gone and it looks like my system is running smoothly again. I'm still not sure what it was but I've been playing extensively with a backup program (EaseUS - Don't buy) so I think it was related to that. I'm awaiting the arrival of my replacement SSD so I can get my machine off the dining room table and back to my office.

    Thanks for asking,

    Larry
      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 05:26.
Find Us