Random freezes with windows 7 - 64 bit

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!

This would also explain why occasionally XP BSOD for some cryptic reason now that I look back at it although at a much longer stretch of time then Win7 does. I would get a cryptic sudden BSOD every few months or so under XP and passed it off as one of those weird "Microsoft" issues but now I can see if was a more forgiving OS running on top of hardware not being tuned to run within industry specs.

I repeat again it's not a hardware issue it's an MS issue

clean boot does same thing

xp works not 7

If you want to run Windows 7 on your PC, here's what it takes:

• 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
• 1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
• 16 GB available hard disk space (32-bit) or 20 GB (64-bit)
• DirectX 9 graphics device with WDDM 1.0 or higher driver '

AM I MISSING SOMETHING

i think NOT !

WE NEED THAT FIX AND WE ARE NOT BUYING new PC it's new just like every ones here

yes it is a hardware issue and I can show you how it may very well be. Lets break it down:

a) clean boot does same thing - ok, if your hardware is broken and its a clean boot does this not tell you something about the hardware problem you may be having and are unaware? next...

b) xp works not 7 - that is correct, with bad memory timings your XP OS can run for years and occasionally BSOD whereas Windows 7 BSOD right away because of the software architecture that works so closely with the hardware to run the PC at peak speed and efficiency. If you have a bad memory timing issue in relation the the Motherboard or CPU, XP will continue to plug away whereas a more hardware inconsistency OS, like Windows 7, will break fast. Windows OS's rely on the understanding your hardware is correctly specced and installed so as to run the OS as it should be. If the hardware is out of sync how in the world is the OS supposed to factor in every possible INCORRECT contingency the world can throw at it? The OS needs to have correct hardware for it shine. Software always conforms to the hardware without exception. You can not have software coded for every single contingency that can possibly be applied to it in the world and have it run smoothly. Its very existance is based on the fact the hardware is installed and running at specified industry specs correctly not incorrectly. If your hardware specs are off (heat, timings, voltage, etc) the whole crashes down like a house of cards. Is this the OS's fault? Ok, the error codes for crashes could be better in terms of using natural language to determine the problem as opposed to having some error code be 43 or 124. What am I a Mathematician all of a sudden to decipher these asinine code-speak errors? next...

c) If you want to run Windows 7 on your PC, here's what it takes:

• 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
• 1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
• 16 GB available hard disk space (32-bit) or 20 GB (64-bit)
• DirectX 9 graphics device with WDDM 1.0 or higher driver '

if your having a problem that is hardware in nature all these specs mean is that they need to work intercooperatively with each other. Yes, you can run certain memory module and certain CPU's but if the specs for the hardware to work correctly TOGETHER are not met then is that the OS's fault? The DirectX portion of this spec is irrelevant if you do not meet the hardware requirements just to boot a run the PC with no OS installed, so that point is moot. next...

d) AM I MISSING SOMETHING - i think NOT ! - if you are having a sudden restart problem (and I am assuming you are if you are posting in this thread) and having seen this problem enough personally and in many forums, having seen the solution as stated so eloquently by the 2nd poster in this thread about memory timings. And I myself have covered in many posts in this and other threads, have you tried these suggestions? Have you actually verified the memory timings of the BIOS are set correctly as Memtest shows based on the correct speed that memory needs to run at for that CPU and motherboard (all 3 in conjunction working in harmony). Again, I ask, how is this the OS's fault or a lack of a service packs fault or anything in the software layer if the hardware is messed up due to lack of knowledge on how to correctly set these settings?

Don't get me wrong I am NOT a Microsoft fanboy or want to be confrontational with you just merely using you post as an example of a how silly posts like this sound if the problem is hardware in nature and due to lack of knowledge ppl always assume its Microsoft's fault. In many cases it may be and I do hammer them hard when it is. But in the case of sudden restarts and Windows 7 this is an issue of the hardware industry not being very cooperative with making the memory timings and the Motherboards and CPU talking to each other with more tolerance as the speeds start to ramp up in our PC's. Microsoft's Memory Diagnostic is very basic and does not even show timings or voltage its testing at. This is something I am hammering at them to fix to give us a tool that is more robust and informative then just "you have an error". Ok great, I have an error, WHY??? It could be better.

Please, stop blaming Microsoft for stuff that is not entirely their fault. When it is, I will be first to lay the hammer down and let em have it but in this case I can honestly say it is not. Ok, this sentence sounds a bit harsh but you get what I mean.

Please do not flame me for this post. I am passionate about computers and I may not know everything but I'm trying to to! lol Its our job to teach each other in this crazy world of evolutionary computing we live in. Its a lifelong class if you are involved in it.

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).

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.