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

Froze/black screen, debug report appears.


  • Please log in to reply
1 reply to this topic

#1 i0bject

i0bject

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 29 October 2012 - 06:35 PM

I am running Windows 7 Ultimate on an MSI X320 netbook.

This is the second time this happened.

What happened the first time, was that the computer froze and was completely unresponsive. I waited for about four minutes and listened for any sort of activity coming from the computer (noise from the hard drive) I heard virtually nothing, and decided to force a reboot. After the reboot, and once i had logged in to my profile, it immediately displayed a debug text file. I did not save it, because everything seemed to be running fine again otherwise. I ran it yesterday with no problems at least over 24 hours.

Just a moment ago, it happened again, only this time the screen went entirely black. The computer was still on, but completely unresponsive, so again, I forced a reboot. This time, however, before taking me to the login screen, it recommended I run a check disk. I allowed it to do so, and it found no disk errors, but I was unable to read the entire thing before it it closed and loaded windows. Once again, after logging in, it popped up the debug text file again.

The file is EXTREMELY long, and I couldn't fit the entire thing in here, but this is the beginning:

[1025/155403:WARNING:backend_impl.cc(1609)] Messed up entry found.
[1025/155403:WARNING:backend_impl.cc(1895)] Destroying invalid entry.
[1025/155410:WARNING:backend_impl.cc(1895)] Destroying invalid entry.
[1025/191103:WARNING:dns_config_service_win.cc(481)] Failed to read DnsConfig.
[1025/191113:WARNING:dns_config_service_win.cc(481)] Failed to read DnsConfig.
[1025/191116:WARNING:dns_config_service_win.cc(481)] Failed to read DnsConfig.
[1026/124023:WARNING:dns_config_service_win.cc(481)] Failed to read DnsConfig.
[1026/124038:WARNING:dns_config_service_win.cc(481)] Failed to read DnsConfig.
[1026/124040:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124042:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124043:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124043:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124044:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124044:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124045:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124045:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124045:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124045:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124045:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167
[1026/124046:ERROR:proxy_resolver_winhttp.cc(79)] WinHttpGetProxyForUrl failed: 12167


I'm rather concerned about this problem, and would really appreciate some input, as I'm just not that good with computers.

BC AdBot (Login to Remove)

 


#2 Jimbob85

Jimbob85

  • Members
  • 308 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:VA, USA
  • Local time:09:11 PM

Posted 31 October 2012 - 08:35 AM

This may be a corrupt OS but lets try a scan and see if there is any malware present.

Download

ESET online scanner

Install it

Click on START, it should download the virus definitions
When scan completes, click on LIST of found threats

Export the list to desktop, copy the contents of the text file in your reply
You may not get a listing if nothing is found




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users