Vista 32 crashes a lot on a tri-core.

Post Reply New Topic

I recently built a computer, intending to get Vista 64 bit, accidently ordered 32 bit, I have an AMD Phenom II x3 710 2.6 GHZ stock, Oced to 3ghz, the temp holds at 110-120F though, and 4 Gigs of RAM, I was thinking that 4 gigs on 32 bit was a bad idea, I know that a tri-core is a defective quad core, overclocking is not always reliable, so does anyone have any other ideas on how to prevent this from happening again. It never happens in a 64 bit Linux, but DX10 games won't run under wine. Also my video card is an ATI Radeon 4850 with 512 mb video RAM.

Vista - there's your problem.

Run memtest for a few hours to see if the RAM's faulty. I've my Q6600 overclocked to 3GHz and it runs without problems on Vista, I only had similar problems with constant crashing because my RAM was faulty.

Also, check the speed of the RAM is the same as the FSB (double if DDR2) or not over it's native clockspeed. A CPU at an FSB of 333mhz needs the RAM to be 667mhz or it's native clockspeed, for example. Any higher or lower might cause instabilities.

The chip can see 4 gig, it's the software that's giving you problems.

Yeah, so when 7 comes out get 64 bit?

What happens when you run it at its rated clockspeed? Does it run fine then?

As to the chip being a defective quad core - well, sorta. A problem with one core doesn't necessarily imply any problems with the others, and its been industry standard practice to do this sort of thing for ages. They've even deliberately damaged chips before selling them in some cases (the logic of which is horribly commercial); but anyway, I wouldn't be too suspicious of the processor.

There might be some kind of issue with memory timings and the way the operating system will be addressing only part of the memory (3-and-a-bit, whatever it is.)

If the memory is in 2*2gig, I'd say take one stick out, turn the clock speed down, try a clean install and run it for a while - you could use Prime95 and/or CPU Burn-In or some other stress testers. Then add the other stick, run for a while. Then turn the clock speed up.

Memtest might be best left to run overnight.

Agreed. It's impossible to give meaningful suggestion if you aren't even sure your setup is stable at stock speed. I will personally run Memtest, Prime95, and Furmark each for a day on any new setup.




I dare say Linux IS the problem here because there's no worthy game that can stress both the CPU and the GPU. Not to mention the generally sub-par display card driver that can't deliver every bit the card can offer. Oh wait maybe that's the cure!




A 32-bit OS may not be able to uses all the RAM, but if a rack is unstable, it's unstable no matter what OS it's running on.

I don't remember seeing anything about Linux.

Sorry since the op said

I kinda assume you mean to compare Vista to Linux. My apology.

I don't like the term "stick of RAM" I'll have a stick of chocolate. A stick of bread. Then there's the term Gigs...

Now - you say you ordered 64bit Vista? How much did you pay for it AND what is the price of 32bit Vista compared with 64bit Vista. I would be VERY sure there is a price difference. In which case, I would get onto the suppler of your install disc and either, get a refund to the cost of the 32bit OS OR for them to supply you with a 64bit key. The version of Vista I have lets me install any version of it x86/x64 but I have to enter the right key to match the version I have selected.

Having 4GB RAM and 64bit capable hardware is problematic enough. The software will be sending 32bit instructions and the processor will send 32bit results back - so you have less memory. I would be tempted to remove EVERYTHING that is NOT essential. So, just your standard keyboard, video, RAM (single module if you are running dual channel) CPU @ factory settings. Then run tests on the memory, benchmarks, whatever. In XP, I know there is a way to get it to ignore a set amount of memory so you don't need to remove it physically. At the same time, there is a way to get it to ignore a single core. I don't deal with Vista as much at the time, but I should really. I am sure there is a similar way to get Vista to use two cores, or one core.

The most common problems for crashing are usually restarting which is a basic indicator of the the CPU over heating and standard freezing when using intensive power is usually attributed to the PSU peaking at maximum power at not being able to provide enough power. So, like a diesel (derv) engine, it will run out of fuel and need physical interaction to get going again. Be it pressing the reset button or in my example, priming the fuel.

I really WOULD do something about being sold the WRONG software.... seriously