Random freezes with windows 7 - 64 bit

I really hope a fix is found soon as this is becoming annoying as I am unable to use my computer properly and certainly am not making any use of my new quad core processor and Direct X11 gfx card, maybe I will stick with Linux if it is stable and use Wine until M$ eventually release a fix Win7 SP1 anybody?

if you have a hardware problem in your PC how exactly is a service pack going to help you to correct a hardware issue of incorrect memory timings in relation to your Mobo? I am not saying you have one but do u see how silly this statement is if ppl have their memory timings set wrong or incorrect voltages for the memory speed. Or even memory speeds too fast for the processor they have. A service pack wont do jack to help these issues.

What would help is if Microsoft creates error codes that are aren't meant to be read by ppl with Computer Science degrees but normal ppl who have some base to work off of to tackle these errors. THAT would help everyone.

Well, I agree in principle to the above statement, but I am using the timings as set out by Corsair for my ram and also the same as set out by Asus QVL for my Ram.

Something is certainly adrift somewhere as Bios only sees 4087MB not 4096MB of ram, but why? where has the other 9MB gone and why is this the case when using both Asus and Corsair recommended memory timings and voltages?

Also Linux running fine no freeze no crash and really puhing this to limits running two VM's inside of SUSE x64 compiling wxWidgets, playing music, surfing the web scrolling mouse and using drop downs on web pages, and to top it off playing Tux racer all at the same time, I admit this is only for one day so far but nether the less no problems, surely if this were incorrect timing issues with ram I would be experiencing the same problems in Linux?

Don't get me wrong I am not starting a Linux/Win7 is better debate, the web is full of these if you want to waste your life reading the flames, but it certainly helps me to pin point the cause of these problems logic dictates that if I am not getting these problems running identical hardware in Linux as Win 7 then it is either a driver issue or a Win7 issue or a combination of the two.

I am really peeved that I have forked out for Win7 after using RC and Beta without problems for most of this year and then when I buy a copy it turns out to be more unstable than the beta!

Laws on software licensing really need to change, I should be entitled to return Win7 for a full refund due to not being fit for purpose, if I bought a piece of hardware that behaved like this, I could return it for a refund or exchange, not so with software if you buy buggy software you are stuck with it and are at the mercy of the vendor to release a fix or not if they choose not to, they have your money and there is no way of getting it back!

Sorry but someone or many need shooting for this outrage and if I sound negative it is because I am! this really does not score well for me, especially after the Vista fiasco, I do not care who's fault it is, I want someone to take ownership of this problem and solve it.

ok, I too was running my memory with exact specs from Corsair. I went line by line in the BIOS settings with a Corsair tech rep to verify every single setting and it would still CTD/Freeze/BSOD, etc. Until I called the Mobo maker and found out that my CPU running memory exactly as specified was not specced to run at the current speed I had it at with the Processor I had. It takes a combination of working with the CPU, Memory and Mobo maker to get definitive answers that are not found on websites and not found in BIOS settings and not found in any other common sense place you think of but the actual knowledgeable tech support ppl to get the true specs to run your PC. This was my lesson.

In my situation and many others this was the exact same case with minor variances. To just discount this information is your choice. My Windows 7 is now running smooth and no problems and all along I was cursing Windows 7 for being a PITA. When it wasn't even the OS's fault.

I don't get paid anything for posting information here. If anyone chooses to not heed mine and others similar experiences its at their own peril. I can care less after being blasted and flamed in this thread and other in these Windows 7 forums to try and help ppl. So those of you with problems, too bad. My PC works and works great. You can flame and troll the great Satan Microsoft if you wish but this is a very misdirected and wasteful effort imo.

Don't listen to anything I say, what do I care my PC works and runs great under Windows 7 now =P

PS: I am not singling you out or anything just trying to help ppl with my knowledge and getting so flamed by ppl with superiority complexes on other threads here has left me with a very bad distaste for this entire forum and the immature jerks who post here. This will be my last post in this thread and probably in this entire forum because Elitist jerks who think they know it all about computers and yet still have problems whereas I do not have problems and have solved mine. I am very glad I bought Windows 7 and its the first OS in 20 years I am proud to run on my PC. It may not be "perfect" but show me something that is?

Sure, I've underclocked my RAM and things so far have been stable - but then again my system only froze about once a week - so I may have to wait awhile to verify the fix.

Even if this is a fix, it's not ideal.  My original RAM speed worked just fine under Vista 64-bit, and was working at a speed certified by the vendor.  I am now running my RAM slower than I should have to, because of the OS.  That's not an acceptable solution.

I totally agree with you and it does burn me to have to underclock my own high performance RAM chips to satisfy the OS and make it stable. This, I will be hammering Microsoft for. It is just ridiculous and we should not need to do this.

@Passion I'm not attacking anybody - it's just you are plain and simply wrong in most scenarios. I've already contributed possible solutions that have helped some people (i.e links to Windws 7 hotfixes for Windows 7 problems) which has resolved some people's issues - BUT NOT ALL. And like I say your fix will help some other people with their hardware issues which may be related to Windows 7. So good on you.

But you have a hardware issue and not a Windows 7 issue. It is important to distinguish this fact and understand you are coming up with any definitive solution here - you are not ... and if you read earlier this thread - you were not the first to mention this

• so it's hardly a revelation. Exactly the same cure could be used for Linux 64 or Vista 64 if you indeed had these issues. Then again Windows 7 might be allocating memory in certain scenarios badly.

I did not offer my input to the memory timings issue with the understanding that was the only solution to all of Windows 7 problems but it was one solution that myself and many many others have been able to use and move on to bigger and more challenging issues. But to discount that these solution does not exist and no one has used it is just false. I had a hardware issue, showed examples of how Win7 reacts to it and offered steps on what to do to overcome that problem. Many ppl have noticed the same thing and applied these steps and it worked for them too. You may not be one of them but it does work! You may have a different problem altogether which is why it may not. But if you ever have a memory timing issue with my steps you will at least have some place to come to for reference for what symptoms you may experience and how to address it. Concrete, tangible steps that do work and fix that specific problem.

Windows 7 is allocating commit memory badly in terms with the audiodg.exe. I have posted in this thread and others threads more specific to the audiodg.exe file, specific steps I have come across and done to overcome this problem. Until Microsoft releases a hotfix/patch/service pack to fully address this issue. Creative Labs is partly to blame for this in how it uses its "Creative" services to accelerate this issue and I am also working with them to make it known their service is not helping the poor commit memory allocation problem of the audiodg.exe as a whole.

If you are running other 64 bit operating systems fine that utilize all hardware then YOU DON'T have a hardware problem. It is silly to jump to conclusions. Not everybody has the same issue (that's why they should be logging their issue on seperate threads).... don't expect this thread to get anywhere (too much noise).

That's true but I did not experience sudden restarts until Win7 came about all along having a bad memory timing issue lurking in the background cause me to confront these hardware problems which Windows 7 detected rather violently. If Linux or XP are not showing the symptoms but Windows 7 does maybe its a sensitivity issue of the OS in detecting these off-kilter timings. But the short end of the story is I did have a hardware issue that once fixed made sudden restarts stop completely and my computer is running very nice and behaving and i love it!

If you think Linux is less sensitive that Windows 7 you've got another thing coming LOL :).

This probably fixes YOUR issue as YOU hard a hardware related issue and decided to visit a Windows 7 forum with your hardware issue ;)

I have no hardware issues thankyou (I've been building PC's since the early 1980's).

Not all the issues here are like yours if you read the thread carefully. And people have been going on about memory timings before. Again if they have hardware issues they should goto TomsHardware.com :).

If you have nothing usefull for ppl here , please leave. Noone need comments like yours " goto imdabest.com ".

U are a crack on hardware ? fine but if you can't resolve the whole bug for everyone , stay back and watch adult talk. And for your information my hardware was checked about 10 times by different people certified in IT.

The bug IS the OS.

so what is your input into the solution to the problem? or is name calling your best effort to resolve a problem? If you do not like it uninstall and be on your way. No one is holding a gun to your head saying you MUST use this OS or you will die is there?

Please offer constructive systematic process steps to overcome a problem and stop the childish antics, it really does not help those of us that want to see this resolved and WE CAN AND WILL!

I really hope a fix is found soon as this is becoming annoying as I am unable to use my computer properly and certainly am not making any use of my new quad core processor and Direct X11 gfx card, maybe I will stick with Linux if it is stable and use Wine until M$ eventually release a fix Win7 SP1 anybody?

if you have a hardware problem in your PC how exactly is a service pack going to help you to correct a hardware issue of incorrect memory timings in relation to your Mobo? I am not saying you have one but do u see how silly this statement is if ppl have their memory timings set wrong or incorrect voltages for the memory speed. Or even memory speeds too fast for the processor they have. A service pack wont do jack to help these issues.

What would help is if Microsoft creates error codes that are aren't meant to be read by ppl with Computer Science degrees but normal ppl who have some base to work off of to tackle these errors. THAT would help everyone.

My memory timings where wrong for Vista 64-bit?  Please explain that, I ran solid as a rock under Vista and my memory timings are the same now as they were back then.  

But then along comes Windows 7 and suddenly I am subject to random freezes.  The cause is Windows 7, not my hardware.

ok that's fine if its Windows 7 uninstall it, go back to whatever flavor of OS you want to have and stop posting on this thread if its not constructive in nature to help resolve the problem. Putting just blame out "The cause is Windows 7, not my hardware." does not solve the problem for those that ARE having a memory timing issue and how Win7 reacts to it. Discounting the fact that this problem DOES exist on a hardware layer for some but not you does not contribute to the whole. There are 4 areas that I have noticed will make Windows 7 react strongly and violently (whereas other OS's may not):

1. Hardware memory timings
2. Hybrid/Sleep modes
3. Audiodg.exe
4. Autoplay with USB Readyboost drives (thumb drives)

I have been able to knock all 4 of these issues out since the Oct timeframe that Win7 was released and my system now runs smoothly and stably day after day after day. Now you have a choice, you can either get mad, throw blame around, revert to a different OS or actually work with us to overcome and knockout these problems and be on your way in an OS that quite evidently is not perfect but can be made to act that way or you may not. Its your choice.

Will there be problems in the future. Quite possibly, but the thing is how do we overcome these obstacles in computing. Do we just throw blame and give up or actually work together to overcome this obstacle. How are we going to overcome our disagreements on a planetary scale if we can't even overcome a stupid OS freezing issue problem. What a travesty it would be to any of our forefathers to say we cant all even work together enough to overcome some stupid computer issue and then move on to bigger and better challenges that the world faces today.

I want to be part of the solution crowd not the problem/blaming/name-calling crowd. Which one do you want to be in?