here comes another bsod thread

[johng]

having had a good old trek around the internet it seems to me you guys are my best bet at working out whats wrong with pc problems, bsod in particular.

now with the flattery out of the way i shall continue

new build, specs as below.
was running fine for the first week then seemingly random bsod's started occuring.

have tried swapping the memory around and found the folowing to be true:
dual channel in either slots 1/2 or 3/4 causes bsod
ram in 2/3 or 2/4 causes pc to freeze
ram in slot 1 = bsod
one stick of ram in slot 2/3 or 4 and things are fine
have ran both mdsched.exe and memtest (10 passes each stick) with no errors, can only do this with single ram though, not with both in place.

have not overclocked anything, wouldnt really know how to!

cant work out for myself if its a problem with the motherboard, the memory, a compatability issue or something else altogether

hope i have included enough information
thanks in advance

 

[ttran]

I can't see any minidump files in the one you uploaded. Please following this instruction instead to post your minidump, and also make sure you have set your system to create minidump:

upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

If you are using any program such as CCleaner, they may clean out your minidump folder, please double check that, if you follow the posting instruction, please run the tool as administrator

 

[johng]

sorry- have added the minidump files now. je suis un n00b!!

 

[ttran]

I suspect your Ralink 802.11 USB Wireless Adapter Driver is causing these BSODs. Please download and install fresh copy of the driver. Make sure to uninstall old driver in device manager before installing new download version.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BUGCHECK SUMMARY:

BugCheck 3B, {c0000005, fffff800033716fd, fffff8800918bee0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpLookupObjectName+21d )

Followup: MachineOwner
---------
BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\netr7364.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr7364.sys
*** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
Probably caused by : netr7364.sys ( netr7364+4f69 )

Followup: MachineOwner
---------

BugCheck 7E, {ffffffffc0000005, fffff88005c50db3, fffff880031a88d8, fffff880031a8140}

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )

Followup: MachineOwner
---------
BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------
BugCheck A, {10000010a, 2, 0, fffff800024a9dc1}

Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+b0f8 )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff88002f88e50, 0, 0}

Probably caused by : tcpip.sys ( tcpip!GetRemoteAddressField+4e )

Followup: MachineOwner
---------

Run system file check please:

Open an elevated command prompt and enter sfc /scannow.

Let us know if you need help

Tuan

 

[johng]

hi. thanks for the reply. i will try what you suggest in the morning. cant do it now, just got back from seeing the pixies in concert and i can just about type let alone do anything complicated!!



edti: uninstalled/reinstalled the driver with no change, ran sfc /scannow and no problems detected.
have memtest running now, currently on 3rd pass with no errors so far. have both sets of ram in slots 1/2.

 

[Dave76]

If you don't see any relief from the system file check, let's get some information on your RAM.

Do you have the part number of your RAM?

Can you D/L CPUZ.
Open CPUZ and take a screen shot of the CPU, Memory and SPD tabs, use the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.

Then post using this method.
How to Post a Screenshot in Seven Forums.

This will give us some information needed to continue.

Did you update your BIOS and any drivers yet?
From the Gigabyte website?

Check the CPUZ Mainboard tab and tell us what BIOS version you have.

 

[johng]

hello again
finished running memtest for 5 passes with no errors, was able to boot from the disc with both sticks of ram as i am able to do when entering the bios. the bsod only happens when windows loads.

have attached cpuz info- can only do one stick of ram but it is a matched pair and the same readings came up for both

is it possiblt to be a compatibility issue with the motherboard and the memory? or something to do with timings (out of my depth with that one!)

have not updated my bios but from the gigabyte website i see there are two available updates but i havent yet jumped in and given this a go! but if its potentially worthwhile then im happy to try

 

[johng]

sorry, forgot to attach the motherboard information

 

[johng]

i took it upon myself to flash the bios from F1 to F2 but this has made no difference either way
i am at a total loss as what to do
should i reinstall windows?
rma the motherboard?
thanks

 

[ickymay]

is your motherboard the rev 2.0 or the rev 2.1 , perhaps take a look inside your box the revision number is in the very corner of your board nearest the Pin1 end of your lowest PCI slot ............

the compatible memory list for the rev 2.0 is View attachment 89365 and for the rev 2.1 is View attachment 89366

your G.SKILL ram is part number F3-10666CL8-2GBRM and I don't see that listed as compatible ?

the voltage or timings may be mismatched to your motherboard and this could be causing your problems ?

the compatible 1066 ram (set) in G.SKILL shows as part number F3-10666CL8D-4GBECO

 

[Dave76]

Good job on the system specs, running memtest86 and the CPUZ snips.

When having problems it's usually a good idea to update your BIOS and drivers.
Just curious, why didn't you update the BIOS to F3A, the latest one?

Did you find any drivers that you could update?
Check the dates and version numbers, be sure to check the chipset driver, if you find a new chipset driver then update it.
Let us know what they are anyway.

With the MOBO and RAM info I'll do some checking and get back to you.

The usual problem is that Intel and AMD boards take different voltages.
RAM that is manufactured to run in an Intel board will cause problems if ran on a AMD board, sometimes you can change the RAM settings and get it to work.

If your MOBO is revision 2.0 then you can D/L your manual here., for reference.

Read through the BIOS section, to get familiar with the BIOS pages and settings.

G.Skill site doesn't list your MOBO for this RAM.
[ Ripjaws ] F3-10666CL8D-4GBRM (2Gx2)

Let's bump the Voltage for integrated memory controller +0.1v,
In your BIOS go to MB Intelligent Tweaker(M.I.T.),
System Voltage Control, set to Manual,
CPU NB VID Control, add +0.1v to the current setting.
Save and Exit.

Let us know if that helps.

 

[johng]

thanks guys.

motherboard is rev 2.0.

i do have the newer bios ready to try, was taking it one step at a time! figured it was safer that way

ive always been happy enough to play about with the bios settings when it comes to boot priority and what not but always been a bit scared of changing anything important! however i shall try what you suggest and get back to you

 

[johng]

tried changing the voltage but still having the same problem, only one stick or ram is tolerated.
what finicky things these computers are!
error this time said the fault was with the cache manager- have put the crash screen up in the hope this helps

 

[johng]

updated bios to latest version, reset the voltage to +0.1 which still hasnt solved the problem but it has changed it!
now the computer boots to desktop, restarts, at post screen emits 3 long beeps, boots to windows starting then freezes.
again, problem only occurs with 2 sticks of ram, all is fine with just the one.

 

[Dave76]

Doing well, so far.

Let's bump the DRAM voltage, it's at 1.5v correct?

If that's correct change it to 1.55v, run the tests.

 

[johng]

well dave76 i think we're headed in the right direction!

bumped the voltage to 1.54 (it was that or 1.56)

both ram in and away we went.......albeit briefly.

no bsod but pc keeps restarting after 30-60 seconds which is definately progress

have to admit to quite im enjoying myself!!

should i boot from the memtest disk and check the memory again with the new settings?

 

[Dave76]

At this point I would try to get it to run stable first.

It's a very good idea to run the memtest86 to see if you have any bad RAM.
RAM can complete several 6 pass tests, then fail on the next. So, it's good to test it several times.

Let's bump the DRAM voltage again, go to 1.6v, let's see if she likes that.

Don't get carried away with the DRAM voltage, you can burn it up, literally.
Most AMD boards run the RAM around 1.6v, but it depends on the RAM also.

Let us know how it responds.

 

[johng]

man you are awesome!

bumped voltage to 1.6, ran memtest86 with 6 passes and no faults, rebooted and so far so good! should i be optimistic and assume its sorted the problem? or cautiously pessimistic and ready for anything?

either way i would have been totally lost without your help, my plan was to send it all back! thanks heaps

 

[Dave76]

That's good news, I would stick with option #2 for now.

If it's still stable, D/L and run Prime95 (64bit) - 25.11, use the torture test.

Be sure to monitor CPU temperatures, D/L Core Temp. Open it and keep it open during any testing.
This test will max out your system and tell you if it's completely stable.
Some people say you should run it for 12 hours, but you will know in a couple of minutes if it's stable.
Several OC sites say an hour or less will tell you if your system is stable and is enough for most people.

Standard disclaimer, run this test at your own risk, it will stress your system and cause high temps on your CPU.

For overclockers, Prime95 has a feature called "Torture Test" that allows maximum stress testing on the CPU and RAM. There are several options allowing the stress test to focus on the memory, processor, or a balance of both.

Usually Prime95 will detect an error within a matter of minutes if an overclock is not stable, however many people like to let the system "burn-in" overnight to ensure long-term stability.

The benefit of this version is that it is multi-threaded and will automatically manage worker threads to fully stress all cores of your CPU.

This is the 64bit version for Windows XP 64bit Edition / Vista 64bit Edition / Windows 7 64bit Edition.

If it's better but not completely stable, then bump the DRAM voltage again, go to 1.65v.

Let us know the results.

 

[johng]

ah well, it was short lived but it gave me hope!

came home from worked and switched on, all ok for a few minutes then i got constant reboots.

upped the voltage to1.65, get a few reboots then 3 long beeps then reboots and keeps on that cycle.

as a thought- could my psu be causing any problems? its not really up to whats required as its only 520w? corsair website suggested 550 or over. mine is also not single rail.