windows 7 more flakey than a cabury's flake!

I would have to agree with the others it's more likely your overclocked PC isn't stable, it's not the first time OCUK's overclocked bundles have been problematic.
 
I would have to agree with the others it's more likely your overclocked PC isn't stable, it's not the first time OCUK's overclocked bundles have been problematic.
yea most people who buy the bundles these days dont do it for the overclock because often the settings arent as good as they could be.

its peace of mind knowing the components have atleast been fired up and theres almost zero risk of any of the parts beeing dead on arrival
 
The UD5 is probably going to sleep and not waking up properly, which is a common problem with the motherboard.
 
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.

If you want us to troubleshoot your hardware post the memdump, but it's not the OS.
 
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?

i'm blaming windows 7 because it is a pile of sh$t!

i have put all the latest drivers for everything on, i have removed all overclocking and it is still blue screening!

everytime i use it it blue screens, just ****es me off, next call is to OC as everything bar the hard drive came from them including win 7 so they can sort it out as i have had enough of it!!
 
i'm blaming windows 7 because it is a pile of sh$t!

i have put all the latest drivers for everything on, i have removed all overclocking and it is still blue screening!

everytime i use it it blue screens, just ****es me off, next call is to OC as everything bar the hard drive came from them including win 7 so they can sort it out as i have had enough of it!!

No, your a pile of ****. Just because you have updated everything doesn't mean it has to work. Start from scratch with just Windows 7 and ONLY get the updates Microsoft offer. Don't overclock. Put ALL hardware to stock and then come back and tell OcUK users that Windows 7 is a pile of ****.

If your still getting bluescreens then theres a problem with your hardware somewhere.


Fully star out swearing please
 
Last edited:
No, your a pile of S*!T. Just because you have updated everything doesn't mean it has to work. Start from scratch with just Windows 7 and ONLY get the updates Microsoft offer. Don't overclock. Put ALL hardware to stock and then come back and tell OcUK users that Windows 7 is a pile of S*!T.

If your still getting bluescreens then theres a problem with your hardware somewhere.

shall i suck eggs as well!?!

it was a fresh install onto a new hard drive not an upgrade!

only the updates from MS were put on and only the latest non beta drivers were used, yet it is still blue screening.

so i have tried all your suggestions clever guy!

why the personal attack!?!
 
shall i suck eggs as well!?!

it was a fresh install onto a new hard drive not an upgrade!

only the updates from MS were put on and only the latest non beta drivers were used, yet it is still blue screening.

so i have tried all your suggestions clever guy!

why the personal attack!?!

Why the attack on windows, you obveously ain't a clue. Theres plenty people on the forums who don't get these problems.

Like I said you must have problems with hardware but you can't blame seven.
 
Have you run memtest yet???

People try to help ya know, mibbe your outta your depth on this one

it is a bit hard to run anything as i randomly blue screens and then goes through all the crap about trying to fix it and then tells me it can't.

i looked at memtest and it looked like it had to run through dos, can't remember the last time i had a dos disk probably with win 3.11, is there a way of checking it through the OS?
 
No. If you download the Ultimate Boot CD then it has all the utilities you will need. Get this, run memtest, and come back to us.
AND NO MORE POORLY DISGUISED SWEARING! You will get suspended. Read the FAQ.
 
You can run a memory test from the "F8" menu, this is microsofts built in test

You can boot from the Windows 7 cd and do a system check without a reinstall

You can download an independant memtest tool for free that boots from cd if you have a google

The total collective posts of people trying to help you here pushes 100,000, listen to what we are saying, its your hardware, could be memory, voltage, temps, anything. But its not windows 7
 
Last edited:
No swearing, or half starred out swearing.

Disable the overclock, install W7 again.

Burn a memtest bootable iso (from the zip) from here http://www.memtest.org/#downiso

Burn it using imgburn.



Don't snap at people, you'll find them far less likely to help you if you have a poor attitude
 
Windows 7 is as solid as a rock, not one issue here since install. Unfortunately some companies are still to produce solid drivers for the OS but that's not Microsoft's fault.

You'd be better off trying some of the steps already mentioned here and doing a bit of detective work to narrow down the troublesome driver/hardware/setting. It definitely sounds like a hardware issue.

If you still find yourself getting so worked up that have to post expletive filled posts online then perhaps you should pay a professional to troubleshoot it for you and go back to watching Jeremy Kyle.
 
Last edited:
W7 is the best MS OS since XP without a doubt.

As above, run a memtest, disable overclocks, run hard drive diagnostics.
Also try running without any USB peripherals plugged in, and see if there is a BIOS update available for any of your gear.
 
Download Ultimate Boot CD and burn it to a CD. It has mem test and other tools on it to help find the issue. It will start up if CDROM is set to boot before HD in the BIOS.

http://www.ultimatebootcd.com/

edit: noticed this was suggested already - only read first page :p
 
agree with everyone here, is either an unstable overclock, faulty hardware, or driver issue, definately not an OS problem. Like others have said, remove overclock, test memory first with memtest.
 
Back
Top Bottom