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

Windows 7 Embedded


  • Please log in to reply
34 replies to this topic

#1 likuid99

likuid99

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 17 May 2015 - 09:20 PM

Hello, 

 

I built a new HTPC using a trial copy of Windows 7 Embedded. I have had 3 blue screens. I have not been present for any, they have happened while my girlfriend was watching netflix. 

I have Coretemp installed, highest recorded temp is 49C. 

 

It says a problem has been detected and windows was shutdown to protect the computer.

Under technical info it has this line:

Stop: 0x00000024 (0x001904FB, 0xB4D878F0, 0xB4D874D0, 0x81D3287B)

 

The PC is built as follows:

Pentium G3258 Devils Canyon

Gigabyte GA-B85-Gaming 3 MOBO

8gb 1600 DDR3 RAM

Samsung 850 EVO

Corsair 430 PSU

 

The memory is currently running at 1400mhz. I don't know why it chose that speed. I thought I would be able to change the memory timing to 1600mhz. I can't figure that out.

 

When I installed the OS, I chose to install everything it let me. It was a little hard to get all the drivers installed as some didn't want to work right away. But I got the basics down and Intel HD graphics as well. 

 

Any help appreciated, if only to direct me to the right place to ask if this is not appropriate. 

 

Thanks.

 

 



BC AdBot (Login to Remove)

 


m

#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 17 May 2015 - 09:51 PM

Hi there,

 

This is an ntfs file system error. It's pretty easy to fix.

 

:step1: open an elevated command prompt

 

:step2:  enter "chkdsk /r" without the quotes and press enter.

 

This process can take some time so please be patient

 

TsVk!



#3 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 17 May 2015 - 11:25 PM

Thanks for replying. 

 

I had to reply Y (yes) for it to run on the next restart because the disk was in use. Is that correct?

 

I then restarted and after the motherboard logo screen , the screen has stayed blank for some time.

 

I previously tried a checkdisk but using the accessory utility. This was 1-2 blue screens ago.

 

How does an error like this happen. Was it something I possibly did while installing the OS?

 

Thanks

 

EDIT: Ok so it just took a few minutes, then windows booted up. Is there a way to see if anything was changed/corrected?


Edited by likuid99, 17 May 2015 - 11:28 PM.


#4 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 17 May 2015 - 11:46 PM

That's correct, you would need to restart to run the utility. The changes created by chkdsk can be see through the event viewer.

 

You can access the event viewer by

  1. Click the Windows start button
  2. right click "Computer"
  3. select "Manage" from the list.
  4. Select Event Viewer > Windows Logs > Application
  5. then find the chkdsk event in the list for more details.

This type of error is a file system error that is generally not user caused. It's just one of those things. Drivers can cause it, updates can cause it, bad disks can cause it, faulty cables, sudden power offs, little invisible gremlins have been fingered more than once as the culprit...

 

You could also run

 

sfc /scannow

 

From an elevated command prompt to ensure that any Windows files that may have been damaged by the problem are repaired.

 

There can be other causes of this issue also. But let's see how the most likely fix goes, first.

 

TsVk!



#5 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 18 May 2015 - 12:13 AM

I checked the event viewer but I don't know where to look because I didn't find the chkdsk entry. I did find this though:

The COM+ Event System could not remove the EventSystem.EventSubscription object {F55E4282-CE4F-4785-B5C8-29D60709F8AF}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.
Object name: SENS Logon Subscription
Object description: 
The HRESULT was 80070005.
 
However, when I ran the sfc /scannow command it said 
Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log
 
I tried to open the logs in that location, but I couldn't. I didnt have permission on the main one with a current timestamp. And the others didn't work either.
 
On a different note, while in the event viewer, I found an entry that said

The disk defragmenter successfully completed boot optimization on C:

I have disk derangementer turned off, because I have an SSD. Should I be concerned about this message?

 

 

Thanks again for the help.



#6 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 18 May 2015 - 01:14 AM

80070005 is an Access Denied error. I wouldn't worry about it too much at this stage, but there may be other pieces to this puzzle...

 

Are you running as an administrator? or as a local user account?

 

The defrag running on boot is of concern. Please download and run the attached batch file by double clicking on it. What was the returned message?

 

TsVk!

Attached Files



#7 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 18 May 2015 - 01:29 AM

According to the user accounts section of control panel, the account is an Admin. I've often wondered why on this pc as well as my personal pc where I am also an admin, I had to right click and choose to "run as admin" if im already an admin....

 

Anyway. This is the only user account on this pc. 

 

When I run the .bat file, I see the cmd prompt show up for a second, then it goes away. Nothing seems to actually happen.



#8 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 18 May 2015 - 01:35 AM

Thank you for your time. I do have to get to bed though so it will be a few hours before I am able to respond.

#9 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 18 May 2015 - 01:36 AM

The "run as admin" function is a built in protection that's part of the UAC, to stop unauthorised system changes.

 

I forgot a bit of syntax on the batch... it probably worked but didn't give the readout. Try this one for a readout.

Attached Files


Edited by TsVk!, 18 May 2015 - 01:36 AM.


#10 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 18 May 2015 - 01:41 AM

Even better than that you could disable the service though... would stop it reactivating itself. (for some unknown to me reason)

 

Here's a how to.



#11 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 18 May 2015 - 10:39 AM

Alright. Even though I checked the defrag settings through defragmenter when I installed the OS, it did have a schedule to run. The defragmenter said it had never been run on C:. I disabled the service, and deleted the schedule.

 

So since the disk scan said that it repaired the issue. Now I just wait and see if the issue is resolved. 

 

I decided to run sfc /scannow on my personal PC just now, and an error was found but unable to be repaired. How can I view this error?



#12 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 18 May 2015 - 01:13 PM

Alright I got it open. 

 

This is the error that was not able to be repaired.

 

2015-05-18 10:33:47, Info                  CSI    000003dc [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-18 10:33:47, Info                  CSI    000003de [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-18 10:33:47, Info                  CSI    000003e0 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-18 10:33:47, Info                  CSI    000003e1 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
2015-05-18 10:33:47, Info                  CSI    000003e3 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-18 10:33:47, Info                  CSI    000003e4 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
2015-05-18 10:33:47, Info                  CSI    000003e7 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
2015-05-18 10:33:47, Info                  CSI    000003ea [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted


#13 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 18 May 2015 - 04:41 PM

Credit to "Go The Power" for this fix.

 

To repair these two corruptions is rather straight forward, it is important to know if you need the x86 or the x64 version of these files. If you are unsure please stop here and ask for help.

 

SFCFix Script

Warning: this fix is specific to the above corruptions only, do not run these fixes if you do not have these corrupt files.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download SFCFix.zip from one of the below links, and save this to your Desktop. Ensure that this file is named SFCFix.zip – do not rename it.
  3. If you have a x64 machine download this version: SFCFix (x64 fix)
  4. If you have a x86 machine download this version: SFCFix (x86 fix)
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  7. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. The results should return as Fixed:

SFC /SCANNOW

  1. Click on the Win7Orb_zps4dae3b32.jpg button. Inside the search box type in CMD
  2. Right click on CMD => Choose Run as Administrator
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with the rest of the steps.


#14 likuid99

likuid99
  • Topic Starter

  • Members
  • 49 posts
  • OFFLINE
  •  
  • Local time:08:33 PM

Posted 18 May 2015 - 06:23 PM

Alright, ran sfc fix, then performed another sfc /scannow and it returned no errors.

 

Thanks!

 

BTW how is this site supported. I have gotten help many times in the past, and with this issue you have been very prompt and spot on. How do I show my appreciation? Donation or subscriptions or what?



#15 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:10:33 AM

Posted 18 May 2015 - 06:30 PM

I'm glad your issues are sorted :thumbup2:

 

The forums are supported by volunteers... like myself.

 

Some helpers accept donations, most of us just do it for love and knowledge.

 

The appreciation we have is in knowing we have helped someone.  :hug:






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users