Blue Screen of Death on my Sandy Bridge setup

[BMSilverFish]

I've had my new Sandy Bridge setup for about a week now and to be honest it was an incredibly concerning start.

Here are my specs:

Gigabyte P67A-UD4 Mobo

Zotac GTX 580 GFX

Intel i7 2600k (overclocked @4.1 GHz using Gigabyte Smart6 control)-- I consider this to be quite a mild overclock given its potential

Noctua NH-U12P SE2 Cooler

4GB (2 x 2GB) XMS3 Corsair Ram

850 Watt Corsair PSU

1TB Caviar Black Western Digital Harddrive

Windows 7 Ultimate 64 bit

Right now sometimes even on idle on windows start up the blue screen of death would appear. My temps for my CPU however idle at roughly 39 degrees. Mind you in Sydney Australia, it's insanely hot with my room being 31 degrees as it is. At load running Prime95 running max temp test, it hits roughly 65 to 70.

After I blue screen, my BIOS is apparently corrupted with a Checksum error. Thankfully with the Dual BIOS it saved my ass and was at least able to boot back into windows without any issues.

Anyway, windows gave me the following log as a result:

--------------------------------------

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.256.1

Locale ID: 1033

Additional information about the problem:

BCCode: 101

BCP1: 0000000000000019

BCP2: 0000000000000000

BCP3: FFFFF880009B2180

BCP4: 0000000000000004

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

Files that help describe the problem:

C:\Windows\Minidump\020811-22588-01.dmp

C:\Users\Brian\AppData\Local\Temp\WER-45536-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

--------------------------------------

So yeah, anyone got any ideas what is wrong with my PC?

 

[SieB]

I did a bit of Google fu and after a bit of reading those errors can be caused by a number of things but which one exactly I couldn't find a answer. Some of the thing mentioned were bad hardware Motherboard/Ram/Cpu, driver problems and unstable voltages and CPU overheating.

So you could try making sure all your drivers are up to date, updating to the latest BIOS for your mobo, reseating the CPU and reaplying thermal paste and making sure the heatsink is mounted properly. Also run mem test and check disk, if you find no problems and it keeps happening try a fresh install of Windows 7 and if it still happens it must be a faulty mobo or CPU.

 

[BMSilverFish]

BIOS was updated to latest version i can find.

CPU Cooler was remounted twice, once before and once after the issue.

Strangely, I've stress tested and did performance tests multiple times throughout the week and none crashed during. If it happens again i will have to resort to reinstalling windows all over.

Thanks

 

[bigdog]

did you test your ram as well

 

[happyshoppa2]

BIOS was updated to latest version i can find.

Got the same board and I get a BSOD shortly after updating to the latest bios' (F6 and F7).

Then on reboot it says bios is corrupt and auto restores version F3 with the dual bios thing.

Never get BSOD on F3. Sticking to that from now on.

 

[ciksas]

Newest isn’t always the best

 

[BMSilverFish]

Ok so i did a Memtest for all remaining available ram and it hanged on both 2.4% and 1.8%

Also looking back on my RAM box i just noticed that both the corsair stickers sealing the package has been torn. Knowing I didn't open both ends i'm kinda getting suspicious about the RAM i got.

Think it's conclusive enough for it to be a RAM issue then? cause i did get the BSOD with the line "Physical Memory Dumping"

 

[SieB]

When you get a BSOD it will always do a physical memory dump, that is normal but if memtest does not run properly then i'd say it's safe to assume it's the RAM. Thats my two cents worth anyway.

 

[BMSilverFish]

Well I sent a bit of an angry email

to the support dudes from the store so i'll see if i can get an exchange and run Memtest again.

also....you should be able to at least move your mouse around when running Memtest right??

 

[SieB]

Well I sent a bit of an angry email

to the support dudes from the store so i'll see if i can get an exchange and run Memtest again.

also....you should be able to at least move your mouse around when running Memtest right??

I have never run it myself so I wouldn't know but i'd guess so.

 

[Firat]

No you can't move your mouse, it should look like a old bios setup, controlling the options with just your keyboard

 

[BMSilverFish]

Quick update...

So i ran each RAM individually, one 2 GB module in slot 2 and then the other 2 GB module in slot 2 as well. Both ran fine to 100% in Memtest no problem. I then put both of them in dual channel in slots 1 and 3 and that also ran fine to 100%, then i stopped it.

So now I've got another problem, whenever i start AIDA64 Extreme ie. run the program, my PC hangs and then blue screens.

Am confused now....any words of wisdom?

 

[SieB]

Quick update...

So i ran each RAM individually, one 2 GB module in slot 2 and then the other 2 GB module in slot 2 as well. Both ran fine to 100% in Memtest no problem. I then put both of them in dual channel in slots 1 and 3 and that also ran fine to 100%, then i stopped it.

So now I've got another problem, whenever i start AIDA64 Extreme ie. run the program, my PC hangs and then blue screens.

Am confused now....any words of wisdom?

There is definitely something wrong but I don't know what else it could be, apart form trying a fresh install of Windows on a formated HDD I don't know what else to suggest.

 

[Daza]

Tried reseting your over-clocks to stock on everything.

Bar that the old rule of over clock on a fresh install then reinstall after you've over clocked as windows can get borked from the amount of hard restarts that can occur when your doing it.

 

[BMSilverFish]

Tried reseting your over-clocks to stock on everything.

Bar that the old rule of over clock on a fresh install then reinstall after you've over clocked as windows can get borked from the amount of hard restarts that can occur when your doing it.

I've already reloaded fail safe settings from the BIOS but still BSODing. Fresh install coming up

EDIT:

I've reinstalled a fresh copy of windows 7...still the same issue when running AIDA64 Extreme. Now i'm thoroughly annoyed

 

[bigdog]

try these steps

check your graphics card temp if thay are fine. then uninstall all your drivers. only leave the graphics card driver installed. then try ran AIDA64 Extreme. let me know how it goes

 

[BMSilverFish]

try these steps

check your graphics card temp if thay are fine. then uninstall all your drivers. only leave the graphics card driver installed. then try ran AIDA64 Extreme. let me know how it goes

Well I got a work around solution. Pretty much now I'm using AIDA64 Extreme version 1.5 instead of 1.2 which doesn't support sandy bridge. Whilst 1.2 doesn't support sandy bridge i don't see a reason for it to completely crash my pc when scanning to create a report.

Now it's working perfectly fine with version 1.5 so i suppose everything is fine. Also just if you would like to know, GPU temps on idle are 44 degrees at 40% fan speed. Running Furmark it goes to about 83 degrees at about 60% fan speed. Gaming is much lower, maybe in the 60s or 70s depending on the game.

 

[CRAZYCAP]

my rule of thumb with bios updates is......if it aint broke don't fix it. Too many times I see where people think that the latest is always the best. same with any driver for that matter.