windows 7 more flakey than a cabury's flake!

gadgets · 24 Dec 2009 at 21:18

anyone else have problems with win 7?

i bought the i7 920 D0 Stepping (SLBEJ) 4.00GHz / Gigabyte EX58-UD5 Intel X58 Motherboard / Corsair 6GB DDR3 overclock bundle from OC and put in a new 750Gb drive and installed win 7.

in the couple of days i have had it on i have had numerous BSOD both on start up and while in use and the screen go black and not wake up.

so far i am begining to think i should have stayed with the previous shower of **** Vista!

how hard is it to deliver a working OS?

Dano · 24 Dec 2009 at 21:20

Only seen a couple of BSOD's myself and both were down to driver issues, I'd start looking at updates for your system before blaming W7 myself.

gadgets · 24 Dec 2009 at 21:21

put all the latest drivers on already

asim18 · 24 Dec 2009 at 21:26

Have you actually tried any troubleshooting before concluding that Windows 7 is to blame?

First thing's first; disable the overclock.

RJC · 24 Dec 2009 at 21:29

Have tried running at stock just in case your system is not stable, also run mem-test to check your memory. I had 2 lots of faulty memory on my i7 setup.

theheyes · 24 Dec 2009 at 21:29

If it's a clean install of W7 then I'd be looking at the hardware. I'd run memtest and if you know how, get rid of the overclock - although if you've only just bought it then I'd get in touch with customer support and see what they think.

Is is a legit version of W7? What else is running? Can you get an error code off the blue screen?

The Asgard · 24 Dec 2009 at 21:33

I develop software in Windows 7 64 Bit and I can say it's a solid OS. I would suspect hardware issues.

gadgets · 24 Dec 2009 at 21:44

one would hope that when OC built the bundle and clocked it they did a proper test on it to make sure it could hold the clock

Meatball · 24 Dec 2009 at 22:21

Hardware fault or driver fault, either way not Windows 7's fault imo

.

Meridian · 24 Dec 2009 at 22:44

I found W7 to be less tolerant of high overlocks than XP, so I'd also say turn the o/c down and check again.

M

vanandjuanunited · 24 Dec 2009 at 22:46

no issues here with w7

TbirdX · 24 Dec 2009 at 22:50

Try XP or Vista then but I suspect you'll be wasting your time. As above, it's a hardware/driver problem guaranteed.

Pho · 24 Dec 2009 at 23:22

Look in c:\windows\minidump for files created at the times of your crashes and either post it or email it to me (sig) and I can tell you what caused the crashes.

Most BSODs are from bad drivers, not the OS.

ShakenNstirred · 24 Dec 2009 at 23:54

gadgets said:
one would hope that when OC built the bundle and clocked it they did a proper test on it to make sure it could hold the clock

you would think so, but is it always the case
as said run at stock to see how it runs
win 7 great here, but then so was vista

NachT · 25 Dec 2009 at 01:14

Pho said:
Look in c:\windows\minidump for files created at the times of your crashes and either post it or email it to me (sig) and I can tell you what caused the crashes.

Most BSODs are from bad drivers, not the OS.

Sorry for the hijack,

May I ask if you use a certain program to read said dump files to determine what the cause of BSOD is?

I ask as I've been experiancing BSOD's lately for 'hardware fault' or something similar...

joey1211 · 25 Dec 2009 at 01:20

Could someone briefly explain why drivers make windows crash. Could windows not decide "No, I'm not doing that as it will make me crash".

Pho · 25 Dec 2009 at 01:49

NachT said:
Sorry for the hijack,

May I ask if you use a certain program to read said dump files to determine what the cause of BSOD is?

I ask as I've been experiancing BSOD's lately for 'hardware fault' or something similar...

Yep it's windbg get it from 'Install Debugging Tools for Windows'.

R34pz · 25 Dec 2009 at 01:57

There could be numerous reasons joey, it could be down to the timers in the programming not in sync to the graphics it's trying to render in a graphics card driver (the most common faulty driver). The problem is that most drivers have to cater for many different hardware setups, so they can never be 100% stable on everyone's machine all of the time if you get me. If pc's were all identical like a console then drivers would be much easier to write.
In reply to you gadgets, pc's are incredibly complex things with literally hundreds of millions of circuits nowadays. So a tiny little fault on one component might not show up for months, that's why troubleshooting for bad hardware is such a ballache. The chances are you have something bad in your machine and w7 is accessing that particular thing regularly and crashing. Usually it's either memory, graphics memory or the chipset of the motherboard gone warped due to heat. Sorry I can't help further, you will have to go through your crash logs and try to troubleshoot what's causing the problem. Hopefully it's just a bad driver somewhere, and not something in your machine that's not right. In reality w7 is the most stable OS Microsoft have ever made, it's just unfortunate that you've run into problems, once sorted i'm sure you will really love the OS.

Mattus · 25 Dec 2009 at 03:05

Why are you blaming Win7, which is regarded as a very stable OS, when you have a CPU that's 50% overclocked? Don't you think the cause might lie there, or at least that it'd be worth running the system at stock before you conclude that the OS is at fault?

COYS · 25 Dec 2009 at 11:50

Im afraid its your system thats flaky here