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 Freezes/hangs after clean reinstall


  • Please log in to reply
11 replies to this topic

#1 Smikis

Smikis

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 27 September 2012 - 04:32 PM

Ill try to make this short and simple, i had same pc for around 3 years now, finally managed to ruin my first win 7 instalation by being lazy, that resulting in long needed reinstall, no problem there,
But after everything was done, my pc started randomly freezing for around 1-5 mins ( depends, usually around 3 mins ) then it just comes back alive like nothing happened, sometimes video driver crashes

My first thought was that my hdd finally dying on me, but after numerous test found nothing wrong on any of them and freezes doesnt always occur on hdd usage i ruled that out, some googling blamed it on new video drivers, got other ones, same, still freezing, reseted my bios to default, still same, sometimes i can turn on a game and play 2 hours straight and nothing will happen, next time i can startup movie and it will freeze 2 times in 5 mins, already reinstalled coddecs and video players

i am just running out of ideas here, never had this issue before, using same windows 7, same install, same pc and all of my drivers/programs are same ones i used

BC AdBot (Login to Remove)

 


#2 Textbook

Textbook

  • Members
  • 89 posts
  • OFFLINE
  •  
  • Local time:10:27 PM

Posted 27 September 2012 - 05:48 PM

If the computer has ever crashed (BSOD), there should be a minidump log. You can check by going to C:\Windows\Minidump

If there are dump files, attach them to this post. You can also try using a software like whocrashed but it's not as good as using WinDbg.

How to read the small memory dump files that Windows creates for debugging

In addition, review your event log by opening Event Viewer.

How to use event viewer

Just type event viewer into the Windows 7 start menu search bar. Or, get to it by going to Control Panel > View Small Icons > Administrative Tools > Event Viewer. View your error events.

#3 Smikis

Smikis
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 27 September 2012 - 08:29 PM

nothing that stands out or have same time frame as freezes in event viewer, disabled system restore ( again, was first thing idid after reinstall, not sure how or why it was active again ) so far 2h+ without freeze, hope it was that one

#4 MDTechService

MDTechService

  • Members
  • 303 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Maryland
  • Local time:09:27 PM

Posted 28 September 2012 - 09:30 AM

Have you recently added any hardware or installed any new programs?
If I am helping you and I haven't replied to your thread in 3 days, please PM me or bump it

Mike D, BS, A+, HPSP, MCTS
I <3 Linux
The Airline Open source airline simulation game
Check the power cable to the wall first!

#5 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:27 PM

Posted 28 September 2012 - 10:27 AM

Hello Smikis,

If your computer is an OEM (i.e. Dell, HP, etc.), what is the make and model number?


To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • During installation, uncheck "Install the free Google Toolbar along with Speccy."
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.

Finally, please download MiniToolBox by farbar, save it to your Desktop, then run it.

Put a check in the following checkboxes:
  • List last 10 Event Viewer log
  • List Installed Programs
  • List Devices
    • Only Problems
  • List Users, Partitions and Memory size
  • List Minidump Files
Click Go and post the result (Result.txt). A copy of Result.txt will be saved in the same directory the tool is run.

Regards,
Brooks



 


#6 Smikis

Smikis
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 28 September 2012 - 08:33 PM

still freezing ocasionaly, no new hardware and no new software that i can think of..

anyway here is new info

http://speccy.piriform.com/results/hHTWxkSoxyabzixI3KfUuCw



o MiniToolBox by Farbar Version: 23-07-2012
Ran by Ssmikis (administrator) on 29-09-2012 at 02:30:43
Microsoft Windows 7 Ultimate Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (09/25/2012 01:30:12 AM) (Source: Application Error) (User: )
Description: Faulting application name: Borderlands2.exe, version: 1.0.35.4705, time stamp: 0x5059137d
Faulting module name: Borderlands2.exe, version: 1.0.35.4705, time stamp: 0x5059137d
Exception code: 0xc0000005
Fault offset: 0x0089e536
Faulting process id: 0x10c4
Faulting application start time: 0xBorderlands2.exe0
Faulting application path: Borderlands2.exe1
Faulting module path: Borderlands2.exe2
Report Id: Borderlands2.exe3

Error: (09/25/2012 01:30:03 AM) (Source: Application Error) (User: )
Description: Faulting application name: Borderlands2.exe, version: 1.0.35.4705, time stamp: 0x5059137d
Faulting module name: Borderlands2.exe, version: 1.0.35.4705, time stamp: 0x5059137d
Exception code: 0xc0000005
Fault offset: 0x0011b6d5
Faulting process id: 0x1f0
Faulting application start time: 0xBorderlands2.exe0
Faulting application path: Borderlands2.exe1
Faulting module path: Borderlands2.exe2
Report Id: Borderlands2.exe3

Error: (09/23/2012 10:08:55 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance(CLSID_VSSCoordinator). hr = 0x800401f0, CoInitialize has not been called.
.

Error: (09/23/2012 10:08:55 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x800401f0, CoInitialize has not been called.
]

Error: (09/23/2012 10:08:55 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance(CLSID_VSSCoordinator). hr = 0x800401f0, CoInitialize has not been called.
.

Error: (09/23/2012 10:08:55 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x800401f0, CoInitialize has not been called.
]

Error: (09/23/2012 10:08:55 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance(CLSID_VSSCoordinator). hr = 0x800401f0, CoInitialize has not been called.
.

Error: (09/23/2012 10:08:55 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x800401f0, CoInitialize has not been called.
]

Error: (09/23/2012 10:07:56 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance(CLSID_VSSCoordinator). hr = 0x800401f0, CoInitialize has not been called.
.

Error: (09/23/2012 10:07:56 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name Coordinator cannot be started. [0x800401f0, CoInitialize has not been called.
]


System errors:
=============
Error: (09/29/2012 00:12:10 AM) (Source: Service Control Manager) (User: )
Description: The HomeGroup Provider service depends on the Function Discovery Provider Host service which failed to start because of the following error:
%%1058

Error: (09/28/2012 11:10:01 PM) (Source: Service Control Manager) (User: )
Description: The O&O Defrag service terminated unexpectedly. It has done this 1 time(s).

Error: (09/28/2012 09:57:26 AM) (Source: Service Control Manager) (User: )
Description: The HomeGroup Provider service depends on the Function Discovery Provider Host service which failed to start because of the following error:
%%1058

Error: (09/27/2012 10:16:30 PM) (Source: VDS Basic Provider) (User: )
Description: Unexpected failure. Error code: 490@01010004

Error: (09/27/2012 09:55:05 PM) (Source: NetBT) (User: )
Description: The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.0.2.
The computer with the IP address 192.168.0.3 did not allow the name to be claimed by
this computer.

Error: (09/27/2012 09:49:55 PM) (Source: NetBT) (User: )
Description: The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.0.2.
The computer with the IP address 192.168.0.3 did not allow the name to be claimed by
this computer.

Error: (09/27/2012 09:10:12 PM) (Source: Service Control Manager) (User: )
Description: The HomeGroup Provider service depends on the Function Discovery Provider Host service which failed to start because of the following error:
%%1058

Error: (09/27/2012 09:10:00 PM) (Source: BugCheck) (User: )
Description: 0x0000000a (0x0000100000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80001ececf2)C:\Windows\MEMORY.DMP

Error: (09/27/2012 09:10:00 PM) (Source: BugCheck) (User: )
Description:

Error: (09/27/2012 10:21:47 AM) (Source: Service Control Manager) (User: )
Description: The HomeGroup Provider service depends on the Function Discovery Provider Host service which failed to start because of the following error:
%%1058


Microsoft Office Sessions:
=========================
Error: (09/25/2012 01:30:12 AM) (Source: Application Error)(User: )
Description: Borderlands2.exe1.0.35.47055059137dBorderlands2.exe1.0.35.47055059137dc00000050089e53610c401cd9ab4ec7c4ba0D:\games\2K Games\Borderlands 2\Binaries\Win32\Borderlands2.exeD:\games\2K Games\Borderlands 2\Binaries\Win32\Borderlands2.exe2a995b30-06a8-11e2-b23a-002215f8ea0b

Error: (09/25/2012 01:30:03 AM) (Source: Application Error)(User: )
Description: Borderlands2.exe1.0.35.47055059137dBorderlands2.exe1.0.35.47055059137dc00000050011b6d51f001cd9ab4e3be7100D:\games\2K Games\Borderlands 2\Binaries\Win32\Borderlands2.exeD:\games\2K Games\Borderlands 2\Binaries\Win32\Borderlands2.exe255b5880-06a8-11e2-b23a-002215f8ea0b

Error: (09/23/2012 10:08:55 PM) (Source: VSS)(User: )
Description: CoCreateInstance(CLSID_VSSCoordinator)0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:08:55 PM) (Source: VSS)(User: )
Description: {e579ab5f-1cc4-44b4-bed9-de0991ff0623}Coordinator0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:08:55 PM) (Source: VSS)(User: )
Description: CoCreateInstance(CLSID_VSSCoordinator)0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:08:55 PM) (Source: VSS)(User: )
Description: {e579ab5f-1cc4-44b4-bed9-de0991ff0623}Coordinator0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:08:55 PM) (Source: VSS)(User: )
Description: CoCreateInstance(CLSID_VSSCoordinator)0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:08:55 PM) (Source: VSS)(User: )
Description: {e579ab5f-1cc4-44b4-bed9-de0991ff0623}Coordinator0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:07:56 PM) (Source: VSS)(User: )
Description: CoCreateInstance(CLSID_VSSCoordinator)0x800401f0, CoInitialize has not been called.

Error: (09/23/2012 10:07:56 PM) (Source: VSS)(User: )
Description: {e579ab5f-1cc4-44b4-bed9-de0991ff0623}Coordinator0x800401f0, CoInitialize has not been called.


=========================== Installed Programs ============================

Adobe Flash Player 11 Plugin (Version: 11.4.402.278)
Advanced SystemCare 5 (Version: 5.4.0)
Agama (Version: 1.10.000)
µTorrent (Version: 3.2.1.27972)
Battlefield 3™ (Version: 1.3.0.0)
Borderlands 2
CPUID CPU-Z 1.61.5
Creative ALchemy (Version: 1.43)
Creative Audio Control Panel (Version: 2.00)
Creative Console Launcher (Version: 2.61)
Creative Software AutoUpdate (Version: 1.40)
Creative Sound Blaster Properties x64 Edition
DAEMON Tools Lite (Version: 4.45.4.0316)
EVEREST Ultimate Edition v5.50 (Version: 5.50)
EVGA Precision X 3.0.3 (Version: 3.0.3)
Faster Than Light
Foxit Reader
Hawken
K-Lite Codec Pack 9.3.0 (Full) (Version: 9.3.0)
Kaspersky Internet Security 2013 (Version: 13.0.1.4190)
Microsoft .NET Framework 4 Client Profile (Version: 4.0.30319)
Microsoft Visual C++ 2005 Redistributable (x64) (Version: 8.0.59192)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 (Version: 9.0.21022)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022 (Version: 9.0.21022)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 (Version: 9.0.30729)
Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 (Version: 10.0.40219)
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 (Version: 10.0.40219)
Might & Magic Heroes VI (Version: 1.7.1)
mIRC (Version: 7.25)
Mount&Blade Warband
Mozilla Firefox 15.0.1 (x86 en-GB) (Version: 15.0.1)
Mozilla Maintenance Service (Version: 15.0.1)
Nexus Mod Manager (Version: 0.20.0)
NVIDIA 3D Vision Controller Driver 306.63 (Version: 306.63)
NVIDIA 3D Vision Driver 306.63 (Version: 306.63)
NVIDIA Control Panel 306.63 (Version: 306.63)
NVIDIA Drivers (Version: 1.10.57.35)
NVIDIA Graphics Driver 306.63 (Version: 306.63)
NVIDIA Install Application (Version: 2.1002.85.551)
NVIDIA PhysX (Version: 9.12.0604)
NVIDIA PhysX System Software 9.12.0604 (Version: 9.12.0604)
NVIDIA Update 1.10.8 (Version: 1.10.8)
NVIDIA Update Components (Version: 1.10.8)
O&O Defrag Professional (Version: 16.0.139)
OpenAL
Origin (Version: 9.0.13.2141)
PlanetSide 2 Beta
Skype™ 5.10 (Version: 5.10.116)
Speccy (Version: 1.18)
Torchlight II © Runic Games version 1 (Version: 1)
Ubisoft Game Launcher (Version: 1.0.0.0)
Update for Microsoft .NET Framework 4 Client Profile (KB2468871) (Version: 1)
Update for Microsoft .NET Framework 4 Client Profile (KB2533523) (Version: 1)
Update for Microsoft .NET Framework 4 Client Profile (KB2600217) (Version: 1)
War Thunder Launcher 1.0.1.83
Wargame European Escalation (Version: Wargame European Escalation)
Winamp (Version: 5.623 )
WinRAR 4.20 (64-bit) (Version: 4.20.0)

========================= Devices: ================================


========================= Memory info: ===================================

Percentage of memory in use: 30%
Total physical RAM: 4094.55 MB
Available physical RAM: 2858.98 MB
Total Pagefile: 8187.3 MB
Available Pagefile: 6175.5 MB
Total Virtual: 4095.88 MB
Available Virtual: 3978.45 MB

========================= Partitions: =====================================

1 Drive c: () (Fixed) (Total:49.75 GB) (Free:20.48 GB) NTFS
2 Drive d: () (Fixed) (Total:416.01 GB) (Free:118.49 GB) NTFS
3 Drive e: () (Fixed) (Total:232.88 GB) (Free:7.63 GB) NTFS
4 Drive f: () (Fixed) (Total:298.08 GB) (Free:3.78 GB) NTFS

========================= Users: ========================================

User accounts for \\SMIKIS-PC

Administrator Guest Ssmikis
UpdatusUser

========================= Minidump Files ==================================

No minidump file found


**** End of log ****

#7 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:27 PM

Posted 28 September 2012 - 10:14 PM

Hello,

sometimes video driver crashes


NVIDIA Graphics Driver 306.63 (Version: 306.63) is a beta driver. Were you trying the beta because the newest stable version (306.23 WHQL) was giving you problems?


Graphics
L226W (1680x1050@60Hz)
SyncMaster (1680x1050@60Hz)
512MB GeForce 9600 GT (XFX Pine Group): 63 °C
512MB GeForce 9600 GT (XFX Pine Group): 61 °C
ForceWare version: 306.63
SLI Enabled

If those are idle graphics temps, they seem a bit high. If you were stressing the cards previously, then possibly not. When was the last time you blew the dust out of the fans on the cards and made sure that the tower airflow was maximized?

You might want to install the free HWMonitor. Keep it open on the desktop and watch graphics temps with general computing and while gaming.


You said that you have tested your hard drives. Did you run the Dos version of SeaTools for your system (C: ) Seagate drive? The other two are Western Digital. WD has a DOS version that can be run from a bootable CD as well.

From the event viewer, on 9/25, it looks as if Borderlands 2 was having problems. I'm not sure what the Volume Shadow Copy Service (VSS) errors are all about.

Regards,
Brooks



 


#8 Smikis

Smikis
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 29 September 2012 - 03:58 AM

those aer idle temps, they do look high, but load temps are 80-100,so its pretty normal, it been this way for a long time and inst reason causing freezes, ye not sure about borderlands 2 problems, but considering windows freezes outside borderlands too, i doubt thats the problem , i did try 306.23 drivers, had same issue

i have everest and evga precision for temps and its not overheating issue ;), its one of those dont buy sli again issue,
Didnt do seagate and wd tests, might do latter

#9 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:27 PM

Posted 29 September 2012 - 06:43 AM

You can run SeaTools for DOS from a bootable CD. It should work on all of your drives. Run both Short and Long tests; both tests should "Pass." A "Fail" in either test means a failing hard drive.


Since a bad memory module can cause varied BSODs or computer freezing, you should also test memory. It is best to test memory outside the Windows operating system, so please follow this post: Windows 7 - RAM - Test with Memtest86+ to either create a bootable CD (Method 2) or USB flash drive (Method 1) to run the test.
  • Once the computer is booted from the CD or USB flash drive, MemTest86+ with start automatically and continue until you stop it.
  • My recommendation would be to run MemTest86+ overnight; 12 hours rather than just 7 passes.
  • There should be NO errors reported.
  • The test can be stopped (press ESC key) as soon as an error is reported.
  • See Part 3: If you have errors.

Regards,
Brooks



 


#10 Smikis

Smikis
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 06 October 2012 - 07:09 AM

been a while since i posted, after second windows reinstall,which i had to do because my mouse and kb wouldnt work in windows 7 after boot,for reason i cant figure out ( trust me took me half day of attempts fixing it to reinstall again )

anyway because of windows reinstall i was able to track down what was causing freezing ( better be so... ) and that was windows update driver for my wireless network card

after uninstalling that one and installing one from cd that came with adapter , freezing disappeared hopefully for good this time

#11 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:10:27 PM

Posted 06 October 2012 - 09:20 AM

Smikis,

That's for the update.

There are many of us who believe that the only place to get stable hardware driver updates is from the manufacturer of that hardware or the website of the computer manufacturer in the case of an OEM (Dell, HP, etc.).

I hope that your good luck continues. :)

Regards,
Brooks



 


#12 Smikis

Smikis
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:02:27 AM

Posted 06 October 2012 - 09:41 AM

Smikis,

That's for the update.

There are many of us who believe that the only place to get stable hardware driver updates is from the manufacturer of that hardware or the website of the computer manufacturer in the case of an OEM (Dell, HP, etc.).

I hope that your good luck continues. :)



well in this day and age, drivers apart video and sound, are pretty nonexistent such things as installing 10+ drivers after windows reinstall is thing of the past ,so i didn't pay much attention to suggested driver update from windows update, not to mention my wireless was already working right after installing windows and before said driver update
but in the end it screwed me over :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users