Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bsod - Any Clue?

12 Oct 2010   #11
Southman

Windows 7 Ultimate x64
 
 

Thx for the replies!

Will update this post until I get all the pics & data needed... Will do as much as possible today!


When I increased my Dram volt/QPI volt it was with only a tiny bit. Memory voltage I increased to 1.56v from 1.50v originally. And QPI to 1.2v with 1.1v originally. But yesterday when all the bsods appeared I put them back to auto. (Loaded optimized defaults to see if it would make any difference to the current Bsods.)

(My RAM-memmory is specified at 1.65v @1600Mhz, but in bios they currently are on 1.5v @1333Mhz. I can activate XMP to get them on 1600Mhz, but that also effects my bclk to 160 (133 standard) mhz while the multiplier goes down to 18x which gets my cpu to 2.88ghz. Tested that once but got temperatures like 50C idle on my CPU so i loaded the default settings.)



# Posted the cpu-z pics




# Temps:
Idle: 29-35c.
Load: 42-49.



# Chkdsk:
Have completed chkdsk on both of my harddrives now, none of them had any errors according to chkdsk. Was able to find the logfile for my second hdd, but not the system harddrive. How can that be? But is there any use to paste the logs here if there were no errors?


# Memtest:
Ran memtest for 10 hrs - 15 pass total... No errors!"
Settings: Auto voltage, auto timings (9-9-9-24) & cmd rate 1.

//South


My System SpecsSystem Spec
.
13 Oct 2010   #12
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

You're welcome, good information.

The temps look good, a bit concerning about the temps when you set the RAM at 1600, leave it at 1333 for now.

No need to post the Chkdsk logs as long as there are no errors.

Good job on the DRAM & QPI voltage increase, best to keep them at small increaments, especially the QPI, for future reference max is 1.2V.
You must keep the voltage difference between the DRAM and the QPI no more than 0.5v, this is due to the integrated memory controller.

Manually set the first four RAM timings to the SPD recommended 1333MHz, of 9-9-9-24 and change the 'Command Rate' to 2. Leave the rest on Auto.

Then, run memtest86+ as per the tutorial:

Be sure to run for 7 passes, run overnight if possible. Note any errors and post here.
You can stop the test if you get any errors.

If you get errors, then proceed as per Part 3 of the tutorial.
This is important, you need to be sure you test for bad RAM cards and bad motherboard slots.



If you get errors you can stop the test and let us know the results.

Next step, if required, will be to set the QPI voltage to 1.2v and the DRAM voltage to 1.56v and run memtest86+ again.
My System SpecsSystem Spec
13 Oct 2010   #13
Southman

Windows 7 Ultimate x64
 
 

Okay good to know about the QPI! thx

The standard settings for the RAM was 1333 mhz 9-9-9-24 and cmd rate 2 when i started the computer for the first time, so will keep those settings as you said and put all voltages to auto. Have gotten 8 Bsods today, just in about an hour. Removed one ramstick and now it seems stable. Are going to put it in again when i am going to do the memtest.

I'm getting more and more certain that it's either the bios-settings or a hardware problem. Don't think that it's caused by bad drivers. But who knows, I might just be surprised... We'll find out, i hope!
My System SpecsSystem Spec
.

13 Oct 2010   #14
Southman

Windows 7 Ultimate x64
 
 

Was wrong, the cmd rate was 1 from the start and still is. Why chould i change this?

//South

Have searched the web and many people say that 2t will be more stable and better, som people also got rid of bsods using 2t.. Could this be my issue? :O
My System SpecsSystem Spec
14 Oct 2010   #15
Southman

Windows 7 Ultimate x64
 
 

Finished the memtest! Updated the top-post .

No errors found. I think it is the dram voltage/qpi voltage causing bsods, cause' when i think about it, nearly all bsods have occured on "coold boot". Then one-two hours later it's stable as hell!

What do you think about it?

And is my next step to run prime 95?
My System SpecsSystem Spec
14 Oct 2010   #16
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Did you run Memtest from a cold boot? If not, try that.
My System SpecsSystem Spec
14 Oct 2010   #17
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

You are right about the cmd rate, when set at 2 it will help if you're having stability problems.

Tell us the RAM timing settings and voltages when it passed the memtest86+, just for confirmation.
1333MHz, of 9-9-9-24 and the 'Command Rate' to 2, is this correct?
DRAM 1.5v and QPI 1.1v, correct?
Also confirm if you have set the RAM timings manually, voltages manually.
This issue has been attributed at least partially due to auto settings, set the above manually.

Run memtest86+ at the cold boot scenario, this is important.
This will help to pinpoint the cause, sometimes this can be fixed by adjusting the settings. If that doesn't do it then you need to RMA the RAM.
If you end up returning the RAM, be sure to get RAM from your motherboard compatible list.

Let us know the results from the cold boot memtest86+.
My System SpecsSystem Spec
16 Oct 2010   #18
Southman

Windows 7 Ultimate x64
 
 

Okay, thx for reply!

The ram-timings were on auto, 9-9-9-24 cmd rate 1. Didn't see the point to change the timings manually to 9-9-9-24 when they already were on that settings, and I also kept the cmd rate at 1. I figured that if i would get any errors then I could change the cmd rate to 2 and do memtest again.

Will do the coldboot test soon.

Thx guys!
My System SpecsSystem Spec
27 Oct 2010   #19
Southman

Windows 7 Ultimate x64
 
 

Sorry for this late update, have been away for a little vacation.

Ran the memtest on coldboot also now, no errors.

And also with a lot of testing with different voltages I don't anymore think that they are causing it. Getting bsods with both raised & auto voltages.

I'm also a little concerned cause i'm missing one cable from the front panel, the "sleep led" i dont have, but from what i've rad the front panel shouldn't be likely to cause any bsods.

Started to look inside my computer, and noticed that i had a 8-pin powersupply-connector on my mobo, but with only 4 pins inserted. Googled it and it seems like there should be 8-pins connected instead of my 4. So I decided to connect all 8 of them and do a fresh install, have had the feeling that all the bsods screwed up my hdd a bit.


So a fresh start it is!

What do you think I should do next if the bsods still appears? Any suggestions?

Thanks so far, you guys have been really helpful!!
My System SpecsSystem Spec
27 Oct 2010   #20
CarlTR6

Windows 7 Ultimate 32 bit
 
 

What you are saying is that you think it is possibly a power supply problem - and that could be. Power supply do weird things cause all sorts of varied symptoms.
My System SpecsSystem Spec
Reply

 Bsod - Any Clue?




Thread Tools




Similar help and support threads
Thread Forum
BSOD no clue..
hello Iam new here.I just installed bitdefender 2015 TS 64bit. and run utorretn yesterday night. I also ran SoftEther VPN Client Manager. when I woke up it was already restarted. system log showed error code 6005. can you tell me which was the culprit?:cry:
BSOD Help and Support
BSOD and no clue what happened, please help....
Hey, what's up? I'm really new to these forums, but I have pulled a few useful tips from here in the past. I had a movie playing in VLC media player when I laid down to take a nap. When I woke up, I noticed that my computer had restarted - as it was sitting at the Windows login screen. I tried...
BSOD Help and Support
Random BSOD, No clue and no pattern?
Hey everyone! I used to get BSODs from a poor quality Hitachi Hard drive that HP put in so I swapped it out for a better quality Seagate, but I've gotten 2 or 3 BSODs since I swapped them maybe 2-3 weeks ago. No clue why they happen, last one happened when the computer was just running and I...
BSOD Help and Support
BSOD, no clue why
Hello everyone, The BSOD has struck again (n.b. "again" since I have had it last year october as well, but it got fixed back then thanks to this forum). This time I have no clue what it causes. I thought it was the micro Sd adapter that I had left in the slot. After taking it out, it went fine...
BSOD Help and Support
Clue to my bsod
For the past month i have been sufferinf from BSOD 124 code - Stop 0x124 - what it means and what to try - done this - ive done lots of testing - BUT i have a clue twice i tried to play a Utube video the moment i clicked on play BSOD then later i was watching a video and as the music started to...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:20.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App