BSoD soon after upgrading to 64bit (win7)

Siar

Active Member
Joined
May 7, 2010
Messages
70
Reaction score
0
So today I get my order of ram. (Corsair Dominator 2gb x 2, 1066mhz) and so upgraded to 64bit win7 to utilize all this ram. Everything worked fine for the first hour or two, then i shut down the pc and went back to uni.

Just got back now and had been running my pc for about 30 minutes when I suddenly get a BSoD. The first one I have EVER had on my machine- 8 years running.

So can anyone help me indentify the problem. List of Major changes in recent days includes:

1) Upgrading to 64bit
2) 1066mhz ram, have to overclock the mobo to be able to use it as 1066mhz else it defaults to 800.
3) New gfx card. MSI R5770 Hawk


At the time of the BSoD I was copying some files from one hard drive onto the other, browsing a forum website that i have regulary frequented over the last 4 years and playing music off iTunes.
 
Does your motherboard support 1066mhz RAM? Sounds like not...
 
What I am about to say will most likley NOT be a solution to a problem you MAY not have, but I am just sharing experience. Also note if you fry your motherboard or RAM, please don't blame me :whistle:

I bought a new PC in May and I had a problem with constant and very random bluescreens in 64 bit Windows 7. 32 bit worked fine.
These BSOD errors persisted until I upped my RAM voltage.

I read somewhere on the net a guy having blue screens in 64bit and then realised his BIOS did not detect the ram voltages properly. Although my Intel DP55WG detected my TeamGroup DDR3 1333 ram properly at 1.5 volts, I overide it to 1.57v (the maximum a DDR3 module should be able to handle without damage to be DDR3 compliant) and my blue screens stopped!!

I then got concearned about over voltage and dropped it to 1.53 and it started again.
Upped it to 1.57 again and stuck on some heatsinks too be safe.

PLEASE, AGAIN, I don't say you should try this as this is only my experience, but maybe as a last resort. I dont know what the maximum voltages are for 1066mhz.
 
The first thing to do is to figure out what's wrong. The next thing is to fix it.

So, firstly check that the ram is properly seated.

Then set BIOS to default setting.

Then check that you have the latest drivers for all devices.

Then see if the BSOD still happens. If it does note the error code, then google for it.

If machine now runs reliably, you can try upping speed.
 
I have (in the past) had hassles with a matched set of Corsair memory modules, so don't rule out that possibility. Unlikely, though possible.

Also make sure that your motherboard BIOS is flashed to the latest release.

Finally, Corsair have an excellent memory module support website, accessible via Corsair's main website. The support website includes timing / voltage / etc recommendations for all of Corsair's products. I would probably start by searching the Corsair website & adjusting according to their recommendations.

Good luck !!
 
Check your logs in the event viewer.

I had a quad core restarting on me and it was caused by having the CSTATE option enabled in the BIOS on 32-bit Windows 7.

Used this site to find my solution : http://www.eventid.net/ .
 
Run memtest86 for 24 hours, once that passes then you can try something else.

The continuous BSOD's will just corrupt Windows 7.

As others have said, it is likely to be a RAM issue.
 
Last edited:
it set bios back to default, and also discovered the my video driver installed the 32 bit drivers by default and i had to go into a seperate folder and run a different setup for the 64bit. No more BSoD. But i think it was most likely my OC of the Mobo to get the 1066mhz out of my ram
 
it set bios back to default, and also discovered the my video driver installed the 32 bit drivers by default and i had to go into a seperate folder and run a different setup for the 64bit. No more BSoD. But i think it was most likely my OC of the Mobo to get the 1066mhz out of my ram

No, it was most likely your video driver.
 
Top
Sign up to the MyBroadband newsletter
X