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

Random stalling and unresponsiveness Windows 7 pro 64bit


  • Please log in to reply
3 replies to this topic

#1 crossfirez-28

crossfirez-28

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:48 AM

Posted 04 June 2015 - 06:42 PM

Hi, I have an HP EliteBookw OS Windows 7 pro 64bit, Intel ® Core™ Duo CPU T9400 @ 2.53 and 3.16 GHz, 4GB memory, Invidia Quadro graphics...Not sure if it's relevant, but then again, I pretty new at this.  The problem, as stated, is that the computer seems to become unresponsive at random intervals forcing a hard reboot. I never get a BSOD it just stalls. I have run the sfc /scannow and as I have read here, It will find corrupted files, but will be unable to fix. So, as suggested, I checked the CBS log and have included a piece of it below.

 

 

2015-05-26 17:28:25, Info                  CSI    000001bf [SR] Verify complete
2015-05-26 17:28:25, Info                  CSI    000001c0 [SR] Verifying 100 (0x0000000000000064) components
2015-05-26 17:28:25, Info                  CSI    000001c1 [SR] Beginning Verify and Repair transaction
2015-05-26 17:28:26, Info                  CSI    000001c2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-26 17:28:26, Info                  CSI    000001c3 [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-26 17:28:26, Info                  CSI    000001c4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:YhEYLI1Sx86AiwUXEaBDtkHon3TQfdR97nHR0QuCUEQ=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-26 17:28:26, Info                

 

Although, again, I am just learning (teaching myself due to necessity) After reading some of your tutorials, as I read through this line it has a reference to amd64 processor architecture, as my system runs an Intel product, I can't help but wonder if this is somehow responsible for tangling everything up and creating an issue. To give some history of the computer. It had run WITHOUT a hiccup since being purchased in November of 2014. It started having issues after what I believe was an automatic update, I'm just sure when. After going to microsoft knowledge base, all of the files that cannot be repaired (and what I assume have absolutely nothing to do with my processor) have something to do with reporting Microsoft 10 bugs automatically from developers. Again, I'm not sure how I ended up with this update, but I would sure like to know how to fix the issue. Just to put it out there, I have already tried a restore but unfortunately I hadn't set up to retain recovery points for more than a week. I have also tried to repair with a recovery disc, but again, it has not worked. Also, just so I give you as much info as I can, The computer will boot in safe mode and be stable, and it also seems to be stable for the most part if I'm at the Microsoft site or in regular utility programs. Although it will become unresponsive most times if I try to run programs. There doesn't seem to be any particular process that locks it up, but then again, I can't honestly be sure of that. If you need, I will attempt to post the entire CBS log. Thanks for any help you can give

 

POQ 78 ends.
2015-05-26 17:28:25, Info                  CSI    000001bf [SR] Verify complete
2015-05-26 17:28:25, Info                  CSI    000001c0 [SR] Verifying 100 (0x0000000000000064) components
2015-05-26 17:28:25, Info                  CSI    000001c1 [SR] Beginning Verify and Repair transaction
2015-05-26 17:28:26, Info                  CSI    000001c2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-26 17:28:26, Info                  CSI    000001c3 [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-26 17:28:26, Info                  CSI    000001c4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:YhEYLI1Sx86AiwUXEaBDtkHon3TQfdR97nHR0QuCUEQ=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-26 17:28:26, Info                  CSI    000001c5 [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-26 17:28:26, Info                  CSI    000001c6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-26 17:28:26, Info                  CSI    000001c7 [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-26 17:28:26, Info                  CSI    000001c8 [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-26 17:28:26, Info                  CSI    000001c9 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:YhEYLI1Sx86AiwUXEaBDtkHon3TQfdR97nHR0QuCUEQ=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-26 17:28:26, Info                  CSI    000001ca [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-26 17:28:26, Info                  CSI    000001cb [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-26 17:28:27, Info                  CSI    000001cc Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-26 17:28:27, Info                  CSI    000001cd Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-26 17:28:27, Info                  CSI    000001ce [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-26 17:28:27, Info                  CSI    000001cf Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:YhEYLI1Sx86AiwUXEaBDtkHon3TQfdR97nHR0QuCUEQ=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-26 17:28:27, Info                  CSI    000001d0 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:YhEYLI1Sx86AiwUXEaBDtkHon3TQfdR97nHR0QuCUEQ=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-26 17:28:27, Info                  CSI    000001d1 [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
2015-05-26 17:28:27, Info                  CSI    000001d2 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope

 

 

 

Thanks Again



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:48 AM

Posted 05 June 2015 - 07:09 AM

The 64 bit version of Windows will sometimes be referred to as AMD64

 

Built by: 9600.17736.amd64fre.winblue_r9.150322-1500

 

I'm not real good w/CBS logs, and prefer to use the following reports:

 

1)  Even though you're not getting BSOD's, please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

 

2)  Also, please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

This one probably doesn't apply to you - but I left it in just in case you'd like to read about it.

While waiting for a reply, please monitor your temps with this free utility:  http://www.cpuid.com/softwares/hwmonitor.html

 


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.

#3 crossfirez-28

crossfirez-28
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:48 AM

Posted 05 June 2015 - 02:07 PM

Good Morning, Thank you so much for your quick response. As I explained in the first post, I have been teaching and learning from the tutorials here and they have proved to be very helpful. I was able to install the "GodMode" icon on the desktop in safe mode. What an AWESOME tool. I'm not sure why, but as I was checking out all the different options I now had for diagnostics, I found that the UAC in Microsoft Security had been disabled. Also, I had a  device that was disabled. (turedo tunneling device) After again going to the knowledge base and running down ALL of the corrupted files and finding out exactly what a turedo tunneling device was. I uninstalled the device, and re enabled the UAC to default setting. Then rebooted from the recovery disc. After doing this, I updated a packet that had been released yesterday afternoon from Microsoft Security and rebooted again. Then there was a couple of new packet releases from Windows Update. After downloading those and rebooting, now everything seems to be fine. Again, I'm not sure what initially caused the problem, but being as I hadn't had a problem previously and the only files that seemed to be causing an issue with the SFC was anonymous bug reporting for windows 10 for developers. I can only assume that it was a glitch there that was the problem. Thank You very much again for the time you spent responding to my problem. I will certainly keep reading and learning from this site. I hope soon enough that I will also be able to offer help.



#4 crossfirez-28

crossfirez-28
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:48 AM

Posted 05 June 2015 - 04:20 PM

Well, I guess I spoke too soon. The computer ran fine for about 12 hours....now it's back to stalling. I will follow your instructs above and see where that may take us.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users