Random freezes with windows 7 - 64 bit

Anonymous
2009-10-28T19:01:43+00:00

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

Windows for home | Previous Windows versions | Windows update

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 No comments
Answer accepted by question author
Anonymous
2009-11-14T19:44:19+00:00

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

Was this answer helpful?

80+ people found this answer helpful.
0 comments No comments

966 additional answers

Sort by: Oldest
  1. Anonymous
    2010-05-18T02:25:19+00:00

    Opetero is obviously more tech savvy than I... but... the ONLY change that has been made to my computer has been stopping the use of a particular wireless mouse, and this fixed it, totally, permanently, a couple months ago.

    I also have my data in a separate physical drive, but of course I agree that its a problem in the system drive... obviously the system drive is required to access the other drive if Windows is loaded so I am not sure what significance is being placed on this? Of course if you use 3rd party software to access the data drive instead of Windows you are going to avoid any problems with Windows?

    Everyone is blaming particular programs, events etc.. but everyone has a different problem. I maintain, despite the many expert opinions and experiments in this forum, that the problem is a driver, at least in my case.  Its only the MS V5000 mouse that is an issue with my system.. no other mouse, wireless or otherwise, causes the problem, and this mouse causes the problem instantly in other 7x64 machines.

    I believe there are a selection of various devices that people are running into that dont have decent drivers to go with them. In my case, it was a V5000 mouse. If this isnt the case, then somebody, anybody, tell me they are using THIS MODEL mouse without problems? I am betting no-one is.

    If you arent using a V5000 mouse, and you are having problems, then I strongly suggest you start disconnecting hardware and see if you can discover a different problem.. its worth a try isnt it?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-05-18T19:16:50+00:00

    I believe there are a selection of various devices that people are running into that dont have decent drivers to go with them. In my case, it was a V5000 mouse. If this isnt the case, then somebody, anybody, tell me they are using THIS MODEL mouse without problems? I am betting no-one is.

    If you arent using a V5000 mouse, and you are having problems, then I strongly suggest you start disconnecting hardware and see if you can discover a different problem.. its worth a try isnt it?

    I am pretty sure that 1. There is  problem in W7, 2. There are multiple triggers that will bring it on, 3.  They may be hardware, drivers, or settings.

    So, I say that 1. Check virtual memory setting (automatic too small) and Bios memory speed.   2. Drivers up to date, especially audio/visual.     3.   Disconnect hardware.  (that was the first thing I did, my wireless mouse is Logitech, also I had a crash in my XP boot, that appears to have been an old parallel cable next a power cord)

    Knock on wood, think I am fixed since Virtual memory and Realtek driver, both were done same day, so who knows which.      (the driver was a "recommended" MS  update.)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-05-21T01:32:24+00:00

    I've been dealing with this problem since Windows Vista came out. I have even had fresh installs lock up on me, without even allowing any drivers beyond the generic defaults to install. I have used many different software and hardware combinations. I have two desktops in my possession, a new gaming computer and an older one with the old parts from the first computer. The new computer always has windows 7 lockups, but the one with the older parts (which had the same lockups when it was in my gaming computer) doesn't ever lock up. Not even one. I have tried dozens of things, most of which seemed to help for a day but then the problem returned.

    Now, seeing as most of us have tried to fix something after having a working windows install, has anyone tried putting different drivers in the windows 7 install disk itself? Perhaps the Windows 7 disk doesn't have the right hard drive driver or something, causing it to install correctly but act as if everything is peachy. Or, perhaps a bundled driver could be causing these lock-ups, but nothing happens to people without that specific hardware.

    I would really like to see some more developer action on this issue. This is a big problem. In my IT department, we are having problems with Dell laptops crashing yet Dell says that windows 7 runs fine on Latitude E4200's. (Although I think the E4200 is just a big failure of a laptop - don't tell anyone!).

    The most fascinating thing for me is that running more than one application quadruples the chance of windows crashing. I've had it crash while idle on the desktop though, so no clue what's up there. Playing music/video raises the chances significantly, as well as flash or java web pages. yet this is also inconclusive, because I've run every single program on my computer simultaneously (and there's some big stuff like Autocad and photoshop on there), and it ran for 12 hours like that with no issues. With Vista I always had it crash while playing games (I got a bluescreen and it locked up while on the bluescreen!), but with Windows 7 it never crashes while in a fullscreen game unless I'm also playing music. Oh, and it doesn't matter what game or music/music player.

    P.S. Uninstall Quicktime, if you have it installed. Quicktime made it crash way, way more often. Get K-Lite codec pack or something to replace it, come on people.

    P.S.S It's definitely NOT memory, as I've had this on 2 different motherboard/memory combinations where the memory was completely fine AND it was on the motherboard memory compatibility list. Also, I can run Ubuntu just fine on this computer.

    EDIT: I have searched the forums for every manufacturer of every bit of software and hardware currently on my computer. There are several things that people are getting the freezes with:

    -Nvidia drivers (Especially the newer 195.XX-197.XX drivers)

    -Steam

    -AVG

    -Firefox

    -Foobar2000 (just a handful, and most claimed to be using Firefox as well)

    Most of the people on the Nvidia forums believe that running video or playing games exacerbates the frequency of the crash. If you have an Nvidia graphics card, I highly recommend grabbing one of the archived drivers on the Nvidia website.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-05-22T19:07:06+00:00

    I would like to know if anyone from Microsoft reads these forums? Does anyone know if it is possible to contact Microsoft and how to do it?  I just can't work out what the problem is and I think people should be able to contact Microsoft about such problems. The whole thing sucks!!!

    Was this answer helpful?

    0 comments No comments