Random freezes with windows 7 - 64 bit

Anonymous

I use to run Vista home premium x86 on a acer computer. This summer I downloaded Windows 7 rc x86. A month ago I bought all new parts and since I could use 64-bit system now I installed a 64-bit Windows 7. Then did the problem start. Every new and then the computer freezes, some days over 30 times. I thought it was hardware problem and tried a lot of hardware finders and nothing helped. I also installed windows 7 rc my mothers laptop (The same version I use to have that work fine) that used to run on Vista home basic.. But her computer didn’t freeze it just got a black screen now and then.

The I started to suspect that it was because it was a beta version so when windows 7 were released I bought two of them a 32-bit and a 64-bit. But the problem didn´t go away. It´s still there and It´s kind of frustrating and even more now when I’m trying to write a essay.

I used windows upgrade advisor and it didn´t see any problem with an upgrade to windows 7. What can I do?

original title: Random freezes with windows 7

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Guys,

I might have the answer to your problems. This might fix your sleep/suspend problems and your random freezing problems. Bottom line is that the default and "auto" values in Win 7 and your BIOS might not produce a stable computer...even with a virgin install.

RANDOM FREEZES FIX:

My computer used to freeze randomly until I fixed the memory timings. I suspected bad memory early on and tested it with MEMTEST, but it passed with flying colors. I even tried swaping memory out, trying to eliminate bad memory and/or slots. It turned out that it was a memory frequency/timings/voltage issue. No more freezes! If you have a similar setup, this will most likely fix it. If not, then check your memory and/or power supply.

The "AUTO" settings in BIOS *may not* produce a stable setting. You have to goto the ASUS support website and download the latest memory QVL and lookup the memory settings for your particular brand there. For my memory (OCZX1333LV6GK(XMP)) I had to make the following adjustments in the BIOS:

DRAM Freq:1066 (even though my memory is rated at 1333 frequency, the QVL guide recommended a lower freq!)

7-7-7-16 for the rest of the timings. The other settings I was able to leave in "AUTO"

DRAM BUS Voltage: 1.6

*warning: be sure to consult your memory/motherboard documentation...the wrong value could damage your components!

SUSPEND/SLEEP FIX:

My computer used to hang when coming out of sleep or wouldn't completely goto sleep. This solution may be partially dependent on you fixing a random freezing issue if you have one.

In your "advanced" power settings, disable "Hybrid Sleep". That's it! My motherboard doesn't like hybrid sleep.

*If you have a desktop with a UPS, Win 7 will treat it like a laptop and apply the battery settings....sooo make sure you adjust the "on battery" settings!

My setup:

Processor:Intel core i7 920

Motherboard:Asus P6T

Memory: OCZX1333LV6GK(XMP) (ie. 6GB in 3 sticks)

Harddrive: 3 x WD Caviar Black drives in RAID 5

PSU: X3 1000W

Video card: 2 x NVIDIA 9800 GTX+ SLI

*I have all of the ASUS overclocking/energy savings programs uninstalled

*I have the latest BIOS 0801 and all the latest drivers installed

Nick

0 comments

966 additional answers

Anonymous

2009-11-12T18:11:13+00:00

I'm not sure why svchost is running rampant at the same time as wmpnetwk but it may have something to do with networking or the fact that wmpnetwk is using so many .dll files to operate. I just noticed that it went right along with wmpnetwk when my physical memory was slammed at 90% and the system was freezing. But after I disabled wmpnetwk using services.msc from start>run, svchost has been behaving normally. It's the last of many different things I tried without success and so I clean booted and watched with ProcMon and wmpnetwk was going nuts after about 5-10 minutes of system running since it's on a delayed start. It ended up being my problem and now I have a blazing fast system. But to answer you Birket, Microsoft says that svchost.exe is a generic host process name for services that run from dynamic-link libraries (.dll) or in other words, svchost.exe is the executable process used to open .dll files.
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-12T16:03:07+00:00

Will certainly give it a try. Could you briefly explain svchost.exe, what the point is, what causes it and why it is a problem?
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-12T15:46:46+00:00

Guys, if you haven't tried disabling wmpnetwk.exe using services.msc, give it a try. I did it and now my system is blazing fast. I had all of the same problems that most of you are having and didn't think that my problem had anything to do with network sharing or WMP because I was not even using those programs. It was a bug in the Betas and at least for me is a bug now. Just give it a try and it might surprise you. I thought it was Catalyst or something relating to ATI and then I thought it was my sound card but nothing about either of those threw up flags. It was the delayed start process of wmpnetwk.exe that was the problem and it seamed that svchost.exe was working in tandem with it. Now svchost doesn't run nearly as many operations. Just try it out. I posted about it in more detail above and no one else has said that they even tried it.
Was this answer helpful?

0 comments No comments
Anonymous

2009-11-12T14:52:47+00:00

Creative X-Fi Fatality sound card (as I wanted SPDIF out to my amp). Not sure of drivers, but updated to latest through Creative Live Update thingymagig last night.

Posted further up my exact problems and full spec list (not sure why it hasn't appeared down at the bottom of this thread though!)

EDIT - ah: refreshed page and my post appears at the bottom.Phew.
Was this answer helpful?

0 comments No comments