Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

The Stub received bad data???


  • Please log in to reply
7 replies to this topic

#1 joker80

joker80

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:19 AM

Posted 25 September 2015 - 05:40 PM

What is this annoying window that pops up randomly? I can go into command prompt sometimes and other times it gives me that error.



BC AdBot (Login to Remove)

 


#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:01:19 AM

Posted 25 September 2015 - 07:15 PM

From the command prompt (when you can get it to run) type

sfc /scannow

It could take a while to run.

 

Better now?



#3 joker80

joker80
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:19 AM

Posted 26 September 2015 - 07:19 AM

I'm getting this everytime 

 

 

Microsoft Windows [Version 10.0.10240]
© 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>



#4 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:01:19 AM

Posted 26 September 2015 - 10:00 PM

Try this tool



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:19 AM

Posted 27 September 2015 - 05:05 AM

Here's a bunch of suggestions:  https://www.google.com/search?q=The+Stub+received+bad+data&ie=utf-8&oe=utf-8

Couldn't find any that specifically applied to W10 - but the W8 one's may be similar.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 joker80

joker80
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:19 AM

Posted 27 September 2015 - 10:51 AM

Here is what it did with the trick:

Welcome to SFCFix by niemiro and sysnative.com.

Checking for updates . . .
No new update is available at this time.

Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .

Attempting repair . . .
Stage 1
Stage 2
Stage 3

Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log



#7 joker80

joker80
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:09:19 AM

Posted 27 September 2015 - 05:27 PM

I istalled windows 10 again and problem was fixed. Thanks!

#8 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:01:19 AM

Posted 27 September 2015 - 05:29 PM

I was working on a reply, but I'm glad it worked out for you :thumbup2:






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users