I'd argue that 64-bit versions of Vista are more stable and secure due to mandatory driver signing.There is no difference in stability between 64/32bit.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I'd argue that 64-bit versions of Vista are more stable and secure due to mandatory driver signing.There is no difference in stability between 64/32bit.
I'd argue that 64-bit versions of Vista are more stable and secure due to mandatory driver signing.
In practice, yes. But...in Vista 32 (or 7, AFAIK), protection isn't provided to kernel components' read/write memory from other kernel components, so an ill-written driver *could* overwrite something it shouldn't.I think for all intents and purposes, the 64 bit and 32 bit versions are about identical when it comes to stability.
Honestly they shouldn't have bothered with x86 version of Win7
For Windows 8 I will agree, but until then, netbooks aren't x64 compatible yet. That is the ONLY reason someone should be buying an x86 version of Windows 7.
64 is a bigger number, bigger is better
I think what I am going to do (to verify that it is NOT hardware) is format and install Windows XP Professional 32bit. We all know that drivers are stable for that OS. I'll test it out for a day or two....then move on to Windows Vista 64bit.......do the same with that OS.....and see where I stand after that.
Well to be frank, all the parts you have are fine in a 64 bit environment -- i.e. if they are all working properly (not faulty) then they work fine in a 64 bit environment. Beyond netbooks (and other 32-bit only processors), I can't think of a part that is incompatible with 64 bit Windows released in the past few years...
If you are able to get an OS running, I would run Prime95 + furmark (or something similar like RTHDRIBL) simultaneously to check stability (memtest 86 is something you can do prior to this). I would put money on it being a hardware issue.
This is definitely nothing to do with 32 vs 64 being better/worse. Just to clarify: you should definitely run 64.
Hardware issue being bad drivers or hardware issue being faulty hardware?
BSOD Message:
atikmdag.sys - Address FFFF8800463BFCC base at FFFFF88004629000, Datestamp 4a0e3895
Physical Memory Dump
Same thing every time...
You DO know that 32-bit apps can be used in 64-bit Windows as long as there's no driver attached to it, right?
Compatibility is a given, everything is guaranteed to work in 32bit, you don't necessarily have that guarantee in 64bit (as evident from the OP)
You DO know that 32bit apps in a 64bit OS don't run any faster, right?
And yes to all those asking, I've used both 32bit and 64bit Win 7 builds and through my use I've found 32 bit to be more stable.
Compatibility is a given, everything is guaranteed to work in 32bit, you don't necessarily have that guarantee in 64bit (as evident from the OP)
Some motherboards require you to flip a few options in the BIOS for 64bit operating systems to work correctly. Have you checked this yet?
Something like "64bit ACPI Table" may need to be enabled, and you might have to change the memory hole remapping mode.
If these aren't set correctly, you'll get all kinds of strange issues.
Ok....a bit of an update.
I reformatted and installed Windows 7 RC1 Build 7100 straight up....let it sit for an hour or so (since the majority of the time my computer BSOD on me, it was sitting idle)...and no BSOD's. This is with all Windows 7 drivers for everything. No updates, no drivers downloaded.
I am going to download the 9.6 ATI drivers in just a sec, install them and see how they work out. Any other suggestions?
Now, after looking at this page (http://www.amd.com/us/Pages/AMDHomePage.aspx) if I select either my video card or the motherboard / chipset (onboard HD3200) they both point to this page (http://game.amd.com/us-en/drivers_catalyst.aspx?p=win7/windows-7-64bit). So, apparently I did it this way before and downloaded drivers from Gigabytes page too....which could have screwed up everything from the beginning.
I am going to install the 9.6 drivers WITHOUT ccc (catalyst control center) and see how this does.
Update in about an hour!
What conditions lent 32-bit to being more stable?You DO know that 32bit apps in a 64bit OS don't run any faster, right?
And yes to all those asking, I've used both 32bit and 64bit Win 7 builds and through my use I've found 32 bit to be more stable.
Compatibility is a given, everything is guaranteed to work in 32bit, you don't necessarily have that guarantee in 64bit (as evident from the OP)
So far so good. Installing my Steam games as we speak! Anyone suggest any other drivers/software to install?
What conditions lent 32-bit to being more stable?
Bonsai has a history here with spreading FUD, just ignore it.
What conditions lent 32-bit to being more stable?
Presumably you've installed your chipset drivers, audio drivers, etc. I look forward to hearing how things are going now.
So you think that 64bit has better compatibility than 32 bit?
Small things mostly, a few random crashes, Explorer seizing up, programs starting slower on occasion, random errors, none of which I've experienced on 32bit. Not saying 64bit is a bad experience, I've just found on my particular hardware, with my particular drivers that 32bit is a bit more reliable. I've only got 4gb of RAM, and I don't have any 64bit hungry apps, so it's no real loss for me. Hopefully the issues will be sorted out for RTM, I'd love to support 64bit more fully, but until I have native 64bit apps I really don't see the point.
Sounds like you definitely need to let other people install your OS for you.
What's your system consist of?
Sounds like you definitely need to let other people install your OS for you.
What's your system consist of?
Seriously, just ignore bonsai.
Alright....I take it back....we are still having an issue.
I downloaded and ran Furmark 1.7.0. On 1900x1080 running defaut stability test, it ran decently, the temp reached 75c and then CRASH within 30 seconds.....screens went blank but no BSOD.
Ran again at 1280 x 1024, it lasted 116 seconds and same thing happened.
Can we now say "hardware issue" or is it still the lack of good drivers for Win7 64bit?
Alright....I take it back....we are still having an issue.
I downloaded and ran Furmark 1.7.0. On 1900x1080 running defaut stability test, it ran decently, the temp reached 75c and then CRASH within 30 seconds.....screens went blank but no BSOD.
Ran again at 1280 x 1024, it lasted 116 seconds and same thing happened.
Can we now say "hardware issue" or is it still the lack of good drivers for Win7 64bit?