Jump to content

gotthimself

Member
  • Posts

    18
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by gotthimself

  1. I deleted the whole BootExecute entry and voilà: Windows is booting fast again. Thanks for your help Andre
  2. Oh, I remember that i switched also to ahci, but everything went well (i guess). I can't really remember if this was the exact time the booting went so slow.
  3. I had that Idee before I wrote here, so I wrote already in the registry that C and D shoudln't be checked at all.
  4. Nope, I tried 8gb on C, 4, none and 500mb, but nothing changed at all.
  5. I could only boot in safe mode without network drivers, everything else started the bluescreen. After restarting normally, it worked again and the boot trace save option popped up. IPv& is now deactivated. new trace
  6. ok, new error, happend about 2 seconds after the login screen appeared: no name, but the technical information says "msrpc.sys - Address "someHEXnumber" base at "HEX"; DateStamp "HEX" " dumps Now the System restore..
  7. I updated the firmware, but no change. Then I started the new trace, but while booting, it shows me everytime a blue screen o.O. Right now the error is "SYSTEM_SERVICE_EXCEPTION", sometimes it's a blue screen without a name.
  8. It looks like fltmgr.sys scans my whole c-drive, I can't tell. I extracted every line with fltmgr.sys, maybe it make sense to you. link
  9. chkdsk didn't find any errors on all drives and smart didn't either. I run the boot trace a second time and the autochk.exe disappeared, but the fltmgr.sys was still running the exact same time.
  10. Hi, my WIndows 7 takes forever to boot, so I found this howto. The boot trace says that fltmgr.sys delays the start about 50s. I searched for hours, but couldn't find anything related to my problem. Any suggestions? Thank you in advance!
×
×
  • Create New...